jazzisfaction Posted May 19, 2014 Share Posted May 19, 2014 Hey, yesterday I made midi assignments with my ES2 without any problems. Then I chose a preset of the ES2 - no assignments possible and now even with the standard preset no assignments are possible anymore. Did anybody had problems like that? With ALL other plugIns the assignments are still as easy as before...Just with the ES2 no assignments are possible anymore ! Please help Thanx P Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted May 19, 2014 Share Posted May 19, 2014 How are you making your assignments? Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 19, 2014 Author Share Posted May 19, 2014 Hey David, i'm doing it via Max/MSP...i swear that 2 days ago there was no problem with the ES2 - now nothing works anymore. But the funny thing: really only the ES2 doesn't work anymore. Like I said: I tried a bypass assignment and some other assignments and I tested some other ES2 presets and all of a sudden: no assignments are possible anymore. I'm kind of desperate over here. Cheers P Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 20, 2014 Author Share Posted May 20, 2014 Hey David, once again me. whenever i turn a knob in the ES2 nothing happens in my midi assignment-learn-window...see attachment....I reinstalled the preferences and all from a backup-version...nothing...i run out of ideas here... Quote Link to comment Share on other sites More sharing options...
Eriksimon Posted May 20, 2014 Share Posted May 20, 2014 Don't know much, but I do know this: your Lernen knopf is not eingeschaltet on your picture. But then again I don't know if that's just in the picture. Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 20, 2014 Author Share Posted May 20, 2014 Hey...that's not the problem (it's of course on when i try it)...thanx anyway Quote Link to comment Share on other sites More sharing options...
Eriksimon Posted May 20, 2014 Share Posted May 20, 2014 Then what's the point of the screenshot? Anyway, have you tried the very first thing to try, and the second? Those are: restarting Logic, and restarting the Mac, respectively. If that doesn't help, have you tried it from a new project started from the empty template? If that doesn't help, try it from a newly created user account (with Admin privileges). Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted May 20, 2014 Share Posted May 20, 2014 In addition to what Erik said, I would also quit Logic and trash the control surfaces preference file. J. Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 20, 2014 Author Share Posted May 20, 2014 Hey guys, please believe me...I tried all that ! nothing helps...aaahhhhhh Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 20, 2014 Author Share Posted May 20, 2014 The strange thing is that this only occurs with the ES2 - all other plug-ins work perfectly...maybe because I tried some assignment for the bypass of the ES2 plug-in? maybe I destroyed sty because of that? Is there a way to COMPLETELY de-install and re-install Logic? Don;t know what to do else? I'd really like to use the ES2 for a big project with sensor-remote-control....puhhh Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted May 20, 2014 Share Posted May 20, 2014 Hey guys,please believe me...I tried all that ! nothing helps...aaahhhhhh Can you tell us which preference file you trashed (while Logic was not running)? J. Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 20, 2014 Author Share Posted May 20, 2014 Hey Jordi, this one: com.apple.logic10.plist I even took a whole 'Preference' Folder from an older backup and replaced my whole current 'Preference'-Folder...no success..... Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted May 20, 2014 Share Posted May 20, 2014 com.apple.logic10.plist That's not the one to delete. The one that deals with assignments is the control surfaces preference file: com.apple.logic.pro.cs I even took a whole 'Preference' Folder from an older backup and replaced my whole current 'Preference'-Folder...no success..... Quit Logic, delete the file. Launch Logic again. You'll have a fresh cs preferences file. J. Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 20, 2014 Author Share Posted May 20, 2014 if this works out I'll kiss your feet...wait a second... Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 20, 2014 Author Share Posted May 20, 2014 nope....no success...the problem seems that the communication between the ES2 and the Midi-Learn interface seems to be interrupted...but only for the ES2....whenever I use other controllers, the Midi-Learn interface reacts but with the ES2 it doesn't react at all... Quote Link to comment Share on other sites More sharing options...
hypnotik Posted May 20, 2014 Share Posted May 20, 2014 same problem here, midi learn doesnt work anymore with 10.0.7 and ES2 sounds like a bug Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted May 20, 2014 Share Posted May 20, 2014 same problem here, midi learn doesnt work anymore with 10.0.7 and ES2 sounds like a bug OK, this is getting interesting. I'll have to check it out. J. Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted May 20, 2014 Share Posted May 20, 2014 Yep, it's broken here too. Normally, just clicking on a parameter, this menu gets populated with the name of the clicked parameter. When clicking an ES2 parameter, it remains as "no destination parameter" (as if nothing had been clicked). J. Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted May 20, 2014 Share Posted May 20, 2014 The controller assignments area in the ES2 interface works properly though. J. Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 21, 2014 Author Share Posted May 21, 2014 Puh...I'm glad that you have the same problem. I thought I'm going crazy here. Is there anything I can do against is? Any solution how I can assign ES2 controllers to external sources like Max/MSP? Do I contact Logic to report the bug? Hope u still want to help me Jordi. Thanx so much for your patience. P. Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted May 21, 2014 Share Posted May 21, 2014 Do I contact Logic to report the bug? Definitely: http://www.apple.com/feedback/logic-pro.html Is there anything I can do against is? Any solution how I can assign ES2 controllers to external sources like Max/MSP? The controller assignments area in the ES2 interface works properly though. J. Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 21, 2014 Author Share Posted May 21, 2014 I tell u something: the whole assignment section in Logic Pro X socks like hell. U do the assignments, u close the session, you re-open it and some still work, some not. This is crap. Millions of bugs. I'll built the synths I need by myself...on a stable platform. I'm quite angry here. Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 21, 2014 Author Share Posted May 21, 2014 I went back to Logic 9.1.8 and everything works perfectly.... Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 21, 2014 Author Share Posted May 21, 2014 same problems in Logic 9.1.8. i start to believe that this is a Mavericks / Logic problem Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted May 21, 2014 Share Posted May 21, 2014 I went back to Logic 9.1.8 and everything works perfectly.... same problems in Logic 9.1.8. It works OK in 9.1.8 and 10.0.6 here. Didn't you try my suggestion? It could help you workaround this issue: J. Quote Link to comment Share on other sites More sharing options...
jazzisfaction Posted May 22, 2014 Author Share Posted May 22, 2014 Ah, I didn't know exactly what u meant....I'll try....thanx. BUT: even though I tried the ES1 in Logic 9.1.8. and for example the cutoff assignment works fine, then I close Logic, open it again and it's still assigned but it's not tracking anymore. I have to do the assignment again and then it starts working again. Could u check this also please? So assigning ex the CutOff of the ES1, closing Logic, re-open and see what happens? The same thing with the volume assignment of a track. It works, i close, it doesn't work, i re-assign, it works again.... Quote Link to comment Share on other sites More sharing options...
Jordi Torres Posted May 22, 2014 Share Posted May 22, 2014 Hi, for example the cutoff assignment works fine, then I close Logic, open it again and it's still assigned but it's not tracking anymore That sounds like you quit both Logic and Max. Max uses virtual MIDI ports. Every time you quit Max and then open your patch again, these virtual ports will get a entirely new CoreMIDI ID, even if their name never changes ("from Max 1", etc). This won't happen if Max is left open and you just quit Logic. Here's what the port assignment looks like here after quitting Max and the reopening the patch: It should look like this to work: I have to do the assignment again and then it starts working again. You don't need to redo the assignments, you simply choose the correct port from the drop-down menu. That's done in Expert View in the Controller Assignments window. I should also mention I'm not having this problem with Logic Pro X. I can quit any of them and the assignment doesn't break. Anyway, to work around this issue, use OSX's IAC driver instead of Max's virtual ports. The IAC driver's ports always have the same ID so the assignment won't break if you use that. J. Quote Link to comment Share on other sites More sharing options...
nogginj Posted July 17, 2014 Share Posted July 17, 2014 Wanting to add in here...it seems like this bug exists for midi learn / midi assignment for effect bypass too? I cannot assign an effect bypass to a midi control, and it behaves very similarly to the ES2 bug. Can anyone else confirm on Logic 10.0.7? Thanks. Quote Link to comment Share on other sites More sharing options...
Eriksimon Posted August 13, 2014 Share Posted August 13, 2014 Addition: Touch and Latch modes also do not work on the ES2. All ES2 parameters do still respond to automation though, but the only way to enter it is to draw it in - or abandon it alltogether and use the MIDI assignments at the bottom in conjunction with the modulation matrix, and record the MIDI CC. The advantage is that you can still (musically) perform the automation that way. Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted October 3, 2014 Share Posted October 3, 2014 Awesome workaround found by ValliSoftware: At the bottom of the ES2, click on the right arrow to display MIDI Mono Mode.Set to On (with common base channel 1), but then... ...set it back to Off. Then try to automate with a control on ES2. Works fine for automation but not for controller assignments. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.