NokNod Posted June 2, 2022 Share Posted June 2, 2022 thanks for updating the Mackie Control interface...? Link to comment Share on other sites More sharing options...
Keni Posted June 3, 2022 Share Posted June 3, 2022 I just updated to build 13 Melodyne clips are still becoming invisible in lanes (no talking parent) when muted. As I commented earlier, I reported this back in 2022.02 and was told it was fixed for next release. There is no mention of it in the list of fixes and it is not fixed. If I mute a melodyned clip in it's lane, it disappears! Link to comment Share on other sites More sharing options...
Jonathan Sasor Posted June 3, 2022 Share Posted June 3, 2022 1 hour ago, Keni said: I just updated to build 13 Melodyne clips are still becoming invisible in lanes (no talking parent) when muted. As I commented earlier, I reported this back in 2022.02 and was told it was fixed for next release. There is no mention of it in the list of fixes and it is not fixed. If I mute a melodyned clip in it's lane, it disappears! It's in the queue but we haven't had a chance to get to it yet. Link to comment Share on other sites More sharing options...
Keni Posted June 3, 2022 Share Posted June 3, 2022 41 minutes ago, Jonathan Sasor said: It's in the queue but we haven't had a chance to get to it yet. Thanks Jonathan. I appreciate your time to update my info. I hope you guys can get to it soon. It's quite disconcerting. Unless I’m mistaken, the clips are actually there tho unseen. If I click there (seeing no response) in the empty space and toggle mute, the clip re-appears. Link to comment Share on other sites More sharing options...
Under A Mile Posted June 3, 2022 Share Posted June 3, 2022 8 hours ago, Under A Mile said: hi, I posted on 2022.02 about slowness loading up VST plugins. I downloaded 2022.06 early access and the issue is still there. I have reinstalled new versions where possible of all my plugins. It is taking several minutes to load each plugin, so for the number of plugins I own it is taking almost a couple of hours. This wasn't an issue before 2022.02. I will leave it running overnight to see if it does actually finish the scan, and I will get another log if I can Attaching log file. You can see that I have updated the plugins. There is also more info in this log "VSTSCAN: > dispatcher" lines - I hope this helps. The scan took nearly 3hrs. thanks, Paul VstScan-202206EA.log Link to comment Share on other sites More sharing options...
murat k. Posted June 3, 2022 Share Posted June 3, 2022 I think adding an icon to the Punch Module and a keyboard shortcut to toggle "Extend Takes to Punch Out Time" will be great in the Final Release. Also "Mute Previous Takes" can be added to both in the module and keyboard shortcuts. By this way toggling will be much easier even while in the record. Link to comment Share on other sites More sharing options...
abacab Posted June 3, 2022 Share Posted June 3, 2022 I had the opportunity to briefly test the new control surface settings with my Arturia KeyLab 61 Mk II today. It was mostly a success using the Cubase mode in the keyboard with the Mackie MCU Cubase mode in Cakewalk Mackie Control. These features were all plug and play, using the Mackie Control "Bus" option on the Master Fader, and "Select highlights track" option: jog wheel transport controls, including the loop button track and master faders track pan knobs track select buttons the solo, mute, & record buttons under track controls Read automation button (but write does nothing) Not sure what's going on with the global controls... the metronome button doesn't do anything, the undo button opens the event list. and the save button opens and closes the browser panel. Link to comment Share on other sites More sharing options...
Bill Phillips Posted June 3, 2022 Share Posted June 3, 2022 On 5/28/2022 at 6:29 AM, msmcleod said: The issue is down to a missing string definition in the English resource file. The feature was working at the time it was implemented and tested, but it looks like a subsequent code merge went wrong at some point (merging resource files can be occasionally problematic). This has now been fixed, and will be available in the main public release. In the meantime, the entry is available in all other languages, so as a workaround you can switch to another language and make your binding there, e.g. for French: I'm unable to create a Melodyne Region FX using the Clip Menu drop down. See GIF. I've verified no region FX clip created. I rolled back to 2022.02 and restarted my PC and the problem persisted. So apparently my problem is not related to the update (and likely pilot error), but I also know that Melodyne Region FX were working on Wednesday PM. Link to comment Share on other sites More sharing options...
Kevin Walsh Posted June 3, 2022 Share Posted June 3, 2022 On 5/28/2022 at 8:44 AM, msmcleod said: While Cakewalk isn't running, rename ctrlsurface.dat within %APPDATA%\Cakewalk\Cakewalk Core to ctrlsurface.dat.bak Then start Cakewalk. Cakewalk will now have no control surfaces defined, so you can add the Mackie Control one for your Pro 61. Once you've switched it over to Cubase mode within the Mackie Control surface dialog, remember to save it as a preset. To switch back, quit cakewalk, delete ctrlsurface.dat and rename ctrlsurface.dat.bak back to ctrlsurface.dat - when you restart Cakewalk, it will be using AZ Controller again with your original settings. Sounds like a candidate for a command to switch control surface bindings. Link to comment Share on other sites More sharing options...
abacab Posted June 3, 2022 Share Posted June 3, 2022 2 minutes ago, Kevin Walsh said: Sounds like a candidate for a command to switch control surface bindings. Renaming "ctrlsurface.dat" saved my bacon today! After an initial attempt at adding a new Mackie control surface definition, I was unable to restart Cakewalk until I reset the control surfaces with this method. Cakewalk crashed every time I started it after making the change. It apparently had some conflicts with some earlier settings or something. All good now! 1 Link to comment Share on other sites More sharing options...
Starship Krupa Posted June 3, 2022 Share Posted June 3, 2022 Just wanted to comment that the local help works great. There is so much to love in this version. Xmas in June. 2 Link to comment Share on other sites More sharing options...
Keni Posted June 4, 2022 Share Posted June 4, 2022 Two separate occurrences first with the first build and now again with 13. I have a project I use for mastering. Setup with all the mastering tools I might want, but all are disabled except 2. Twice during this EA, after opening this "empty" project, I import the file to be mastered only to be rewarded with Cake disappearing from screen. No warnings, no dump created. Link to comment Share on other sites More sharing options...
marcL Posted June 4, 2022 Share Posted June 4, 2022 On 5/26/2022 at 6:50 PM, Morten Saether said: Unable to enter "+" character for markers when using non-US keyboard This reminds me of a similar bug in the Event Inspector Module! It does not work there either (and it is essential to be able to change values of multiple clips). But for me it is not that much a big deal, because meanwhile I've got used to press the U.S. key combination for CbB on my Swedish keyboards (does not match the lettering though). ? 1 Link to comment Share on other sites More sharing options...
Skyline_UK Posted June 4, 2022 Share Posted June 4, 2022 2 hours ago, marled said: This reminds me of a similar bug in the Event Inspector Module! It does not work there either (and it is essential to be able to change values of multiple clips). But for me it is not that much a big deal, because meanwhile I've got used to press the U.S. key combination for CbB on my Swedish keyboards (does not match the lettering though). ? Agreed. I'm in the UK and whenever I want to add, say ten, to the velocity of a number of MIDI events in the Event Inspector I have to remember not to use the number pad. It's been an irritation for years! 1 Link to comment Share on other sites More sharing options...
mgustavo Posted June 4, 2022 Share Posted June 4, 2022 (edited) Hi, that's nice to have an Early Access for CbB! Thanks to the bakers! Also I'd like to ask how to CTRL + drag copy nodes on Tempo Track, because I saw there is a fix for an issue on Tempo Map but I couldn't reproduce it (actually CTRL + drag copy doesn't seem to work on Tempo Track, or maybe I'm missing something?). EDIT: Ops, my bad! Maybe it's referring to Arranger Section? Thanks! Edited June 4, 2022 by mgustavo Link to comment Share on other sites More sharing options...
Panu Pentikäinen Posted June 4, 2022 Share Posted June 4, 2022 8 hours ago, marled said: This reminds me of a similar bug in the Event Inspector Module! It does not work there either (and it is essential to be able to change values of multiple clips). But for me it is not that much a big deal, because meanwhile I've got used to press the U.S. key combination for CbB on my Swedish keyboards (does not match the lettering though). ? This is fixed as well. Now + works in in the Event Inspector, at least on my Finnish keyboard. 2 Link to comment Share on other sites More sharing options...
msmcleod Posted June 5, 2022 Share Posted June 5, 2022 On 6/3/2022 at 6:51 PM, abacab said: I had the opportunity to briefly test the new control surface settings with my Arturia KeyLab 61 Mk II today. It was mostly a success using the Cubase mode in the keyboard with the Mackie MCU Cubase mode in Cakewalk Mackie Control. These features were all plug and play, using the Mackie Control "Bus" option on the Master Fader, and "Select highlights track" option: jog wheel transport controls, including the loop button track and master faders track pan knobs track select buttons the solo, mute, & record buttons under track controls Read automation button (but write does nothing) Not sure what's going on with the global controls... the metronome button doesn't do anything, the undo button opens the event list. and the save button opens and closes the browser panel. I'm not sure which button the Keylab is sending for the metronome - there's certainly no button labelled metronome on the Cubase MCU overlay. As far as the other functions, it sounds like these may be firing off the function keys. These were purposely left unmapped as they are user definable in the Mackie Control dialog. You should be able to remap them yourself by selecting the equivalent command or key press. Link to comment Share on other sites More sharing options...
norfolkmastering Posted June 5, 2022 Share Posted June 5, 2022 I have tested the cached Routing and track/bus ordering with AZ Controller and a large compliment of physical I/O Ports. It seems to be working correctly as per the interim release which you provide to me in March for testing. Thanks for taking care of this. 1 Link to comment Share on other sites More sharing options...
abacab Posted June 5, 2022 Share Posted June 5, 2022 (edited) 6 hours ago, msmcleod said: I'm not sure which button the Keylab is sending for the metronome - there's certainly no button labelled metronome on the Cubase MCU overlay. As far as the other functions, it sounds like these may be firing off the function keys. These were purposely left unmapped as they are user definable in the Mackie Control dialog. You should be able to remap them yourself by selecting the equivalent command or key press. Thanks for the tip! This was just a simple "out-of-the box" user report. I was using KeyLab's built-in Cubase DAW mode preset, which cannot be edited. I also tried the KeyLab's built-in "Standard MCU" DAW mode preset, but that didn't seem to work quite as well as the Cubase DAW mode with the Cubase overlay in Mackie Control. Custom mapping might be possible from the KeyLab using with the "User" memory mode. But since things are mostly usable without any customization, I consider this a big "win"! Note: I used MIDI-OX to capture the KeyLab's MIDI messages sent using the buttons, faders, and knobs. All control surface related messages are sent via the device MIDIIN2 (KeyLab Mk II). The primary MIDI in port is reserved for the keyboard keys. Buttons send a MIDI note on, followed by a note off message. Faders send a MIDI note on, followed by pitch bend, followed by a note off. Knobs send a MIDI CC#. The metronome button sends this message (multiple presses shown): Edited June 5, 2022 by abacab Link to comment Share on other sites More sharing options...
dahjah Posted June 5, 2022 Share Posted June 5, 2022 is there a way to get volume level to show on the controller (mackie mode)? info shows up on panning (lcd screen of controller) but not the volume. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now