oscwilde Posted April 15 Share Posted April 15 1 minute ago, DamonNnn said: Okay I will do this, before I do however should I be doing this with only the B+ plugged in and turned on? Also should I still be deleting the B+ from the CSS before doing this? By the way, thank you very much for all the help. Im very grateful for all this you have no idea 1. Yep...let's keep it simple. 2. No, leave it as is - for now. 3. Don't thank me yet....and I'm "intrigued" now....so want to find a solution for you/want to sate my curiosity - and hopefully we'll work it out so the next B+ owner will know what to do with it/Logic. 1 Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 15 Author Share Posted April 15 (edited) 55 minutes ago, oscwilde said: 1. Yep...let's keep it simple. 2. No, leave it as is - for now. 3. Don't thank me yet....and I'm "intrigued" now....so want to find a solution for you/want to sate my curiosity - and hopefully we'll work it out so the next B+ owner will know what to do with it/Logic. Okay so it remembers everything I've mapped in Logic Pro When I close IMAP. But whenever you reopen iMap up you have to go back to user define mode and hit send data. So I think it remembers the last thing you send it I think as long as I remember to send the data to the B+ before opening logic it should remember the mapping I did on logic. Now I'm wondering if there's a way to put the stuff I mapped on logic in IMAP as well so this kind of thing can get avoided all together. Edited April 15 by DamonNnn Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 15 Author Share Posted April 15 Well everything was going good and it was all mapped perfectly and then where I mapped my scissors suddenly just became the up cursor button. I was testing the buttons just to see if they'd work. Here's something very horrible. Whenever I pressed where I mapped the audio editor to twice, EQ popped up .. 36 minutes ago, DamonNnn said: Okay so it remembers everything I've mapped in Logic Pro When I close IMAP. But whenever you reopen iMap up you have to go back to user define mode and hit send data. So I think it remembers the last thing you send it I think as long as I remember to send the data to the B+ before opening logic it should remember the mapping I did on logic. Now I'm wondering if there's a way to put the stuff I mapped on logic in IMAP as well so this kind of thing can get avoided all together. I had the iMap window minimized the whole time too just in case 😞 Quote Link to comment Share on other sites More sharing options...
Solution oscwilde Posted April 15 Solution Share Posted April 15 Can you go into the Control Surfaces window and choose the B+ MCU device, and set the MIDI In/Out Ports to No Port (or Logic virtual midi, etc.) This will effectively disable the "control surface", but should still allow the B+ to function as a MIDI input device. Try this with the iMap software open and closed....while assigning key commands in Logic. It seems like it's "close", but we need to hit on the right combination of hardware/software settings. They say patience is a virtue 😉 1 Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 15 Author Share Posted April 15 Okay I just woke up I'll drink some coffee and see what's going on Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted April 15 Share Posted April 15 How about removing the check mark for the B+ auto assignment LUA script (in MIDI Controllers settings)? Quote Link to comment Share on other sites More sharing options...
oscwilde Posted April 15 Share Posted April 15 13 minutes ago, Atlas007 said: How about removing the check mark for the B+ auto assignment LUA script That actually disables the input port....and the device doesn't use a script. Quote Link to comment Share on other sites More sharing options...
JakobP Posted April 17 Share Posted April 17 (edited) I'd also make sure "Automatic Installation" is unchecked under "New" in the CSS window... (Although I guess the B+ shouldn't be recognised as an MCU when in user mode?) Edited April 17 by JakobP 1 Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 17 Author Share Posted April 17 On 4/15/2024 at 2:47 AM, oscwilde said: Can you go into the Control Surfaces window and choose the B+ MCU device, and set the MIDI In/Out Ports to No Port (or Logic virtual midi, etc.) This will effectively disable the "control surface", but should still allow the B+ to function as a MIDI input device. Try this with the iMap software open and closed....while assigning key commands in Logic. It seems like it's "close", but we need to hit on the right combination of hardware/software settings. They say patience is a virtue 😉 I'm very sorry I had to take a couple days off because I was getting really cranky at this thing. I did what you asked right now and the B+ is playing midi notes again and I don't even have the B+ iMap open at all! However when I close Logic and open it back up it wants to add ANOTHER Mackie Controller with inputs and outputs routed to the B+. Now, before I start mapping again using command+L lol Do you think when it's wanting to add the B+ again it'll remap what I put in here? Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 17 Author Share Posted April 17 Also in the assignments window, all the stuff the B+ wants to do is now mapped for "Logic Pro Virtual In" Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 17 Author Share Posted April 17 Good news! I've mapped the top ten buttons (which are F keys) and it asked me "Are you sure you want to reassign the parameters?" ZERO times! Wish me luck 🤘🤘 1 Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 17 Author Share Posted April 17 (edited) On 4/15/2024 at 2:47 AM, oscwilde said: Can you go into the Control Surfaces window and choose the B+ MCU device, and set the MIDI In/Out Ports to No Port (or Logic virtual midi, etc.) This will effectively disable the "control surface", but should still allow the B+ to function as a MIDI input device. Try this with the iMap software open and closed....while assigning key commands in Logic. It seems like it's "close", but we need to hit on the right combination of hardware/software settings. They say patience is a virtue 😉 OKAY! So I just mapped all the buttons, and as long as I keep deleting the B+ on CSS window when it pops up and send "user define" info to it after, it remembers what I mapped with no issue! Also all buttons are mapped on one zone and not scattered all over the place in the assignments window. Is there anything else I should do to make this more efficient? If not I'm very happy with this. It is customized and working with the CS12 and Platform M+ just how I want it! *Edit* I also just noticed... In iMap it says "User Define (MCP)", so it's still Mackie Control Protocol even in User Define... Aaaaah why didn't I notice 😞 Edited April 17 by DamonNnn Quote Link to comment Share on other sites More sharing options...
oscwilde Posted April 17 Share Posted April 17 8 hours ago, DamonNnn said: In iMap it says "User Define (MCP)", so it's still Mackie Control Protocol even in User Define... Aaaaah why didn't I notice Yep noticed this too (and it's odd....but clearly the way the device works). That it wants to create a new MCU device in the Control Surfaces window every time is frustrating/annoying...so not sure how to get around this - but give me/the hive mind here some time to see if there's a way around this. As a test...and this will be a PITA as you need to do it button-by-button....can you go into iMap and change everything to channel 16? Once done - send this to the B+. Note that this "may" break your existing key commands (as the MIDI channel is different)...so you might need to re-assign them (Delete the existing ones). The reasoning behind ^^^^^^^^^ is to see if the "MCP" functionality of the device can be overridden by channelizing. The MCU protocol works on MIDI channel 1....so I'm hoping that Logic won't recognise it as an MCU device if on another channel. This is probably just wishful thinking. 😉 An alternative to channelizing in this way in iMap is to open the MacOS Audio MIDI Setup app.....and in the MIDI Setup window, choosing the "Platform B+" device (double-click it) and seeing what's available. Depending on the driver - you can often specify what MIDI In/Out ports the device can use - so you may be able to "filter" port/channel 1 here. As above...not sure this will make a difference....and it "may" break your existing Logic key assignments (which are possibly using MIDI channel 1). In the meantime - props to you for sticking with it and delighted that it's doing what you want it to do/fitting in with your workflow. 1 Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 17 Author Share Posted April 17 2 minutes ago, oscwilde said: Yep noticed this too (and it's odd....but clearly the way the device works). That it wants to create a new MCU device every time is frustrating/annoying...so not sure how to get around this - but give me/the hive mind here some time to see if there's a way around this. As a test...and this will be a PITA as you need to do it button-by-button....can you go into iMap and change everything to channel 16? Once done - send this to the B+. Note that this "may" break your existing key commands (as the MIDI channel is different)...so you might need to re-assign them (Delete the existing ones). The reasoning behind ^^^^^^^^^ is to see if the "MCP" functionality of the device can be overridden by channelizing. The MCU protocol works on MIDI channel 1....so I'm hoping that Logic won't recognise it as an MCU device if on another channel. This is probably just wishful thinking. 😉 An alternative to channelizing in this way in iMap is to open the MacOS Audio MIDI Setup app.....and in the MIDI Setup window, choosing the "Platform B+" device (double-click it) and seeing what's available. Depending on the driver - you can often specify what MIDI In/Out ports the device can use - so you may be able to "filter" port/channel 1 here. As above...not sure this will make a difference....and it "may" break your existing Logic key assignments (which are using MIDI channel 1). In the meantime - props to you for sticking with it and delighted that it's doing what you want it to do/fitting in with your workflow. you mean this?? Quote Link to comment Share on other sites More sharing options...
oscwilde Posted April 17 Share Posted April 17 9 minutes ago, DamonNnn said: you mean this?? Yep....change it to 16 for both in/out....and open Logic and see if wants to create a new device. Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted April 17 Share Posted April 17 6 minutes ago, oscwilde said: That it wants to create a new MCU device in the Control Surfaces window every time is frustrating/annoying...so not sure how to get around this - but give me/the hive mind here some time to see if there's a way around this. As mentioned by @JakobP, disable "Automatic Installation" by un-markchecking it under "New" in the CSS window... 2 1 Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 17 Author Share Posted April 17 Just now, Atlas007 said: As mentioned by @JakobP, disable "Automatic Installation" by un-markchecking it under "New" in the CSS window... THIS WORKED !! Thank you! 1 Quote Link to comment Share on other sites More sharing options...
oscwilde Posted April 18 Share Posted April 18 So happy days @DamonNnn? At least now we know how the B+ works....so the next user will have an easier time with it. 1 Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 18 Author Share Posted April 18 1 minute ago, oscwilde said: So happy days @DamonNnn? At least now we know how the B+ works....so the next user will have an easier time with it. Yes thank you very much this forum is awesome 🤘🤘 2 Quote Link to comment Share on other sites More sharing options...
JakobP Posted April 18 Share Posted April 18 And now that it's working, make sure to copy the .cs preference file to have a backup in case the controller assignments gets messed up... 3 Quote Link to comment Share on other sites More sharing options...
DamonNnn Posted April 18 Author Share Posted April 18 I was gonna do this with iMap and Snoize, is there a more efficient way to do that?? Quote Link to comment Share on other sites More sharing options...
Atlas007 Posted April 18 Share Posted April 18 9 hours ago, DamonNnn said: I was gonna do this with iMap and Snoize, is there a more efficient way to do that?? The pref file @JakobP is talking about is located in the Preferences folder. To locate it, try this: In the Finder, choose Go > Go to Folder from the menu. Type ~/Library/Preferences in the "Go to the folder" field. Press the Go button. the pref file is named com.apple.logic.pro.cs Note: Type the path exactly as described, including the ~(tilde) -----> ~/Library/Preferences 1 1 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.