6 replies
Sign in or join Beachball Help to reply.
- 0
soundhacker ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Very bizzare one.
Did you checked the environment; maybe you accidently create an object to do so (however incredible that sounds). - 0
sevensleeper ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
hello, in logic pro : go to "preferences", then select "control surfaces", select "setup" (bottom right of pop-up window). in the setup page (pop-up window), "delete" the "device" from the list which is causing your problem. the c-2 note off triggers should immediately stop.
- 0
BlueRaincoat ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
That did it! I had a Yamaha DM2000 listed as a control surface from a previous project. It was sending the C-2 note off trigger.
Thank you!!
- 0
Charles Houghton-Webb ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi there… I had discovered this quirk also, but I've not been able to explain why it's happening 😟
It doesn't seem "Logical" at all - for instance, if I set control surfaces for a Mackie HUI, 32 channels, I need 4/8 channel banks. Creation of the first three - all calm on the MIDI front. As soon as I create the 4th one, C -2 OFF starts in the transport. If I delete any of the four, it doesn't matter which, it stops immediately.
When I set up my 01V96 as remote, I need two banks for complete control. I set up the first, no MIDI out. As soon as the second is set up, off it goes again C -2 OFF !!
Perhaps it's just that as soon as a "complete" set-up is recognised, it starts automatically, but I can't see it can be of any use for anything. Is this just a bug or what ? - 0
ephemirage ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm seeing the same thing. Just installed a PreSonus FaderPort tonight, and it requires the Mackie HUI module. As soon as it's set up with that module, the trouble starts. Of course, it won't use any other module, but selecting other ones that appear to still talk to the FaderPort a little (keep its lights on) don't cause this issue. Seems like a pretty isolatable problem.
And: Argh! Can we get this ironed out please?
- 0
ephemirage ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Update -- Had some old instructions for the Faderport (and a broken CD when it arrived that had drivers on it). I found the FaderPort native drivers on the PreSonus site and installed them and deleted the HUI setup for this device and the problem went away.