[CLOSED] Cakewalk 2022.06 Early Access [Updated to Build 22]

[John Nelson]

30 minutes ago, dahjah said:

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.

You can select that under the Meters option.

[dahjah]

@John Nelson That's how mine is set and doesn't work on the Qcon Icon G2, I asked them about it and they said it was the software (cakewalk/sonar/cbb)

Edited June 6, 2022 by dahjah

[msmcleod]

10 hours ago, dahjah said:

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.

The display shows the value for what is currently being controlled by the v-pots.  By default, this is pan.

Engaging flip is an easy way to swap pan/volume ( so the v-pots now control volume, and the sliders control pan ).

Alternatively, your controller may offer other ways to change the currently edited parameter.

On a real MCU,  pressing the Edit / Global button will allow the Channel left/right buttons to change the current v-pot parameter.  Pressing left once will go from pan to volume; pressing right once will put it back to pan.  You can press the Name/Value button to get it to flip between the parameter name and value, so you can make sure you're picking the right one.

On my 01X it's even easier - just pressing Display up/down allows me to cycle through the track parameters being controlled by the v-pots.

[Galapas]

I have run into an issue and felt I needed to report it. The issue has only started since I did the EA update and has never happened before (that I remember).

The problem is when I adjust a parameter while playing, (so far, track pan & send) an instrument (or sometimes more) will drop out. It will stay out until I restart the song (song position doesn't seem to matter). I don't have to be adjusting the track that drops out, it can be any track. It's ALWAYS my drums (Superior Drummer 2) that drops out and sometimes other instruments as well. As I said, I've never had this to happen before.

I usually have several audio tracks as well as VSTi tracks, all with various plugins. Basically a backup band with multiple recorded guitars & vocals.

I'm a looong time CW user (since DOS version) and know CW well. Nothing has changed on my system in several months, so it wasn't a Windows update or anything (updates are locked).

I'm running:

MS Windows 10 Pro

ASRock MB w/American Megatrends BIOS

AMD FX-6300 3500 Mhz (3cores, 6 Processes)

8 Gig memory (yeah, I need more)

MOTU 24i Audio interface (latest drivers)

 

[dahjah]

On 6/6/2022 at 5:27 AM, msmcleod said:

The display shows the value for what is currently being controlled by the v-pots.  By default, this is pan.

Engaging flip is an easy way to swap pan/volume ( so the v-pots now control volume, and the sliders control pan ).

Alternatively, your controller may offer other ways to change the currently edited parameter.

On a real MCU,  pressing the Edit / Global button will allow the Channel left/right buttons to change the current v-pot parameter.  Pressing left once will go from pan to volume; pressing right once will put it back to pan.  You can press the Name/Value button to get it to flip between the parameter name and value, so you can make sure you're picking the right one.

On my 01X it's even easier - just pressing Display up/down allows me to cycle through the track parameters being controlled by the v-pots.

At least I now know it's possible. When I press flip the rotary encoder for panning turns into the volume knob while the faders turn into panning, but the numbers do show up on the lcd, just gotta figure out how to flip it the right way now.

Edited June 7, 2022 by dahjah

[petemus]

1 hour ago, Galapas said:

I have run into an issue and felt I needed to report it. The issue has only started since I did the EA update and has never happened before (that I remember).

The problem is when I adjust a parameter while playing, (so far, track pan & send) an instrument (or sometimes more) will drop out. It will stay out until I restart the song (song position doesn't seem to matter). I don't have to be adjusting the track that drops out, it can be any track. It's ALWAYS my drums (Superior Drummer 2) that drops out and sometimes other instruments as well. As I said, I've never had this to happen before.

I usually have several audio tracks as well as VSTi tracks, all with various plugins. Basically a backup band with multiple recorded guitars & vocals.

I'm a looong time CW user (since DOS version) and know CW well. Nothing has changed on my system in several months, so it wasn't a Windows update or anything (updates are locked).

I'm running:

MS Windows 10 Pro

ASRock MB w/American Megatrends BIOS

AMD FX-6300 3500 Mhz (3cores, 6 Processes)

8 Gig memory (yeah, I need more)

MOTU 24i Audio interface (latest drivers)

 

I started getting this, too, but it's only a short crackle when I for example start adjusting panning. This is new to me, never happened before.

My system:

• MS Windows 10 Pro, latest updates
• ASUS TUF Z390M-PRO GAMING
• Intel Core i7-9700K CPU @ 4.40GHz
• 32 Gigs of memory, DDR4 3466 MHz
• 1 TB Samsung SSD 970 EVO Plus 1TB
• RME Fireface UCX, latest drivers

 

[Michael Vogel]

On 6/5/2022 at 1:40 AM, Panu Pentikäinen said:

This is fixed as well.

Now + works in in the Event Inspector, at least on my Finnish keyboard.

Hey Panu, long time no see. How’s things?

[Under A Mile]

On 6/3/2022 at 8:38 AM, Under A Mile said:

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 1.25 MB · 2 downloads

This has kind of gone away (for now) but I will note down what I have found, as I do not know the root cause and I'm not convinced it won't reappear. I will try to be as specific as I can (am an Embedded SW dev myself ) but these are the (perhaps coincidental) findings:-

- when the problem hits, it's really slow to scan VST, impossible to use, then, somehow it gradually gets better, not always for anything I've actively done. This happened on 2022.02. I realise I haven't proven the problem is with Cakewalk itself yet, respect guys for the generally great (and Free to use!) DAW. The multitrack comping works really nicely these days, I use across 5 grouped drum tracks, that's much better than the last version of Sonar Pro I had before BL. Anyway, I digress.

- I'd given both machines thorough checks with Ccleaners and Antiviruses (paid versions) which did not seem to help. 

- since last Thursday, in the last 2 days it seems to be a getting better and I could load projects again in a shorter time, reducing to a few minutes.  Yesterday CPU/memory intensive (mixdown) and other operations -  PS I tried some groove quantize for the 1st time - extracting midi from a clip - are working fine despite the slow scans.

- the VST scan appeared to start quite quickly, and then slow down, but could vary. As the scan seems to be 1 thread(?) I don't think any one plugin was slowing down, all seemed to take the same time (few mins each) when slow.

- Once a project was loaded, adding plugins from different vendors was slow too.

- As a Windows 10 update was available to try, today I installed this:

                        06/06/2022  2022-05 Cumulative Update Preview for Windows 10 Version 21H2 for x64-based Systems (KB5014023)
                            Install this update to resolve issues in Windows. ...

- this seemed to alleviate the problem further. So I tried on my 2nd machine before updating windows, to see if the problem was there, it was not (with 2022.02 I had seen the issue on both machines) The 2nd machine (laptop -both are i7 machines, 2x SSD ,16GB RAM -see attachment) didn't seem to be suffering at all. I updated to 2022.06, still ok, then updated windows, still ok.

- Looking back now, there were windows updates around Feb'22 when this started being a problem, but I'm not drawing conclusions.

- I couldn't do an exact like-for-like since I have some Waves plugins which are licensed only on 1 machine. I know one can move them around, ...but I was having other problems with them (some missing from the install). I bit the bullet and paid to upgrade those as some were a few years old, and with v13 I get a 2nd license on them (although for 1 yr only unfortunately), so I can now replicate the setup.

- Both machines are now working fine, scanning ok, and loading up new plugins is ok.

I attach my machine details from a scanning tool, FYR.
 

 

Documents.zip

[Galapas]

7 hours ago, petemus said:

I started getting this, too, but it's only a short crackle when I for example start adjusting panning. This is new to me, never happened before.

My system:

• MS Windows 10 Pro, latest updates
• ASUS TUF Z390M-PRO GAMING
• Intel Core i7-9700K CPU @ 4.40GHz
• 32 Gigs of memory, DDR4 3466 MHz
• 1 TB Samsung SSD 970 EVO Plus 1TB
• RME Fireface UCX, latest drivers

 

Since I started paying attention to this, I've noticed audio from different instruments fading in and out, but only happens after I touch one of the track or VST controls. It will continue until I stop the playback and start again. As long as I don't touch anything, it plays fine.

[KWILD]

Same issue for me, very weird!

[KWILD]

13 hours ago, Galapas said:

Since I started paying attention to this, I've noticed audio from different instruments fading in and out, but only happens after I touch one of the track or VST controls. It will continue until I stop the playback and start again. As long as I don't touch anything, it plays fine.

Same issue for me, very weird!

Edited June 7, 2022 by KWILD

[Olaf]

14 hours ago, Galapas said:

Since I started paying attention to this, I've noticed audio from different instruments fading in and out, but only happens after I touch one of the track or VST controls. It will continue until I stop the playback and start again. As long as I don't touch anything, it plays fine.

In my experience this has been present from previous releases. Synths either drop out or start playing out of sync until you stop and restart playing. It happens either when you tweak VST controls or when you resize/move audio clips in/across tracks.

[Leonardo Sanchez Gamboa]

Puse fx , y me aparecio al momento.Todo bien ¡

[Beau Sterling]

Using a Behringer X-Touch One (firmware 1.08) set to Cubase mode, with Mackie Control in Cubase emulation mode, the only button that doesn't do what it says is Automation-Write enable. Automation-Read toggles correctly, but not Write. Nothing happens but the mouse pointer activity wheel turns when I push the button on the controller.

Also the Ch. Select button on the X-Touch One seems to have no function. It just stays lit green and will not select/deselect the track in Cakewalk even if the track is displayed as active on the controller, or one of the track M/S/R/etc. buttons is highlighted using the controllers navigation arrows.

Fader had to be adjusted while the track was selected in Cakewalk to get them to pair, but after initial pairing, choosing the track on the controller then moving the fader in either Cakewalk or on the controller will move the other, and the motorized fader will then auto-adjust to the correct position instead of 0 when cycling through tracks.

Everything else works fine so far. Could not test with footswitch because I don't have one. Will keep playing around and update my post if I find anything screwy.

 

Windows 10 Pro (21H1);  Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz;  32GB RAM;  NVIDIA Quadro P2000;  PreSonus Studio1824c; CbB v2022.06 (Build 013, 64 bit)
 

Edited June 8, 2022 by Beau Sterling
added system specs and fw rev

[Timothy Reynolds]

Thank You, Morten Saether! 

Looking forward to this new EA update. 

My fingers are crossed that the updated MCU will work even better with my Komplete Kontrol S-88 mkII.

Installing now...

 

Timothy

[Starship Krupa]

On 5/26/2022 at 9:50 AM, Morten Saether said:

Automatically extend final take when loop recording in Comping mode

My only quibble with how this is implemented is that Cakewalk still truncates the clip and makes the automatic splits if I stop recording in the middle of a take, rewind, and start again.

I'd rather have it extend all incomplete takes out to the end of the loop.

[Olaf]

6 hours ago, Starship Krupa said:

I'd rather have it extend all incomplete takes out to the end of the loop.

Or just let them end where they end, without automatically splitting anything, it would effectively be the same thing. It's hard to understand the reasoning behind that automatic splitting.

[marcL]

On 5/26/2022 at 6:50 PM, Morten Saether said:

Shelf tool does not work with multiple clips in the same lane

This is one of the best bug fixes I have ever seen!!! ?  (I have complained about it more than once) It improves working with Clip Gain a lot!

On 5/26/2022 at 6:50 PM, Morten Saether said:

Unable to enter "+" character for markers when using non-US keyboard

It works now correct also in the Event Inspector (as @Panu Pentikäinen mentioned)! Thanks!

On 5/26/2022 at 6:50 PM, Morten Saether said:

Automatically extend final take when loop recording in Comping mode

Also this change makes life much easier! Great improvement! ?

The only criticism (IMO): The setting "Extend Takes to Punch Out Time" should be default! Though anyway, I don't understand the need of this setting to be off, because if you set a punch region you NEVER expect recording out of its range IMO!

[norfolkmastering]

I just installed the latest Build 13 and on starting Cakewalk I'm getting the old 'Activation required' request.  This takes you to the Bandlab login.  After a couple of attempts I was able to get logged in to my Bandlab account and reactivate Cakewalk.  So far this seems to have stopped the message reappearing but I will keep testing.

[JoseC]

5 hours ago, Olaf said:

Or just let them end where they end, without automatically splitting anything, it would effectively be the same thing. It's hard to understand the reasoning behind that automatic splitting.

It seems clear to me. You set your loop to record a phrase, you record a couple of takes and get the second half of the phrase right, but not the first part.  So, you just record that a couple of times and don´t bother to continue playing  the whole phrase every time. CbB then splits the phrase in two in all the takes so you can comp it whith what you actually played.