I've never had that problem with my three FSM's. But I don't use Logic or any other Apple products.
They work fine on Win10 with Studio One with UC v1.7.6..The problem is likely Catalina. The Firestudio Mobile does not have properly compatible drivers for that OS: Universal Control https://www.presonus.com/products/FireStudio-Mobile/downloads I know some users have gotten various models of Firestudios to "work" under Catalina, but that doesn't mean they working 100% correctly. You might want to have a look at these threads: https://forums.presonus.com/viewtopic.php?f=160&t=22154 https://forums.presonus.com/viewtopic.php?f=156&t=39763
https://soundcloud.com/cristofe-chabot/sets/main
PC'S: HP XW6000 Dual 3.2GHz Intel Xeon, 8GB RAM WinXP SP2 HP 6005 Pro AMD Athalon X2 B24 3.0Ghz, 4GB RAM Win8 Pro Dell Latitude E6410 Laptop Intel i5 2.67Ghz 8GB RAM Win7 Pro x64 Audio Interfaces: Terratec EWS88MT PCI (2), Audiobox 1818VSL USB & Firestudio 26x26 Firewire, Line 6 PodXT, Roland GS-10, NI Rig Kontrol 3 Monitors: Yamaha HS50M's DAW: S1 3.2.1 Pro To add your software and hardware specs to your signature to make it easier for us to help you, click HERE. |
cristofe wroteI've never had that problem with my three FSM's. But I don't use Logic or any other Apple products. Thanks for your reply. Yeah, even if the original issue was unrelated to Catalina, I shot myself in the foot when I attempted to uninstall and reinstall Universal Control. Apparently, it's supposed to work fine if you upgrade to Catalina as long as UC was installed on a prior OS. It's frustrating that this is the case and that I had to discover this issue after the fact in a not so easy to find forum thread. So I ordered a Focusrite Scarlett 2i2 and am saying goodbye to PreSonus for now. For Mac users out there, I should also point out that I continued to experience panning issues even after converting to the Scarlett, namely I seemed to be stuck in mono. After much digging, I discovered that it was an accessibility setting in Mac settings. Frustrating that there's no warning in Logic that this was impacting output. I'd think with it being an Apple product, it would be smart enough to know this setting could inadvertently be enabled. I'm not sure how it was enabled in the first place. |
Users browsing this forum: No registered users and 7 guests