Noel Borthwick

@Herve Maratrey it seems like you are running a really old laptop with a very old BIOS from 2011. It is very underpowered by todays standards and only has 4GB of RAM. At least for the graphics and memory - the CPU is a quad core which should be fine. What is the PC model? BIOS: BIOS Date: 08/10/11 12:28:49 Ver: 04.06.03 (type: BIOS) Processor: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz (8 CPUs), ~2.2GHz Memory: 4096MB RAM Available OS Memory: 4002MB RAM Page File: 4818MB used, 3534MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 There are no obvious errors in the log but my guess is our code is incompatible with this version in some way. User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) Can you temporarily change your DPI scaling in windows back to 100% and retry to rule out a scaling problem?

No it doesn't. Once imported the data is lost since the file is transcoded. You will need to redo the data if you reexport.

The symptoms sounds exactly like the bug I fixed that's why I wanted you too retest with the new build.

Thanks we'll investigate it.

The simple answer is that you have it because you paid for it. There was never a plan to give away all the Cakewalk plugins free. Only the DAW is free.

Why am I sure that if we disable that behavior some will yell that they relied on it BTW its not double clicking that does that. Double click inserts the audio into the current track. What you are seeing is clicking twice on the same file after a short delay. That triggers the rename behavior like it does in Windows explorer itself. Its totally normal Windows behavior in a file browser that we are inheriting because that is a browser control.

Its definitely possible to start auditioning from anywhere within a section. Two ways: 1. First set the now time on the transport where you want to start from. Then CTRL click the play button on the arrangement section (lower pane in arranger) that you want to start from. Playback will start from the set time within section that you clicked on. 2. First set the now time on the transport where you want to start from. Then press SHIFT-ALT-SPACEBAR. Playback will start from the section that intersects with the set time but from that time rather than the section start.

@Graeme S Brown Can you please try the latest 2020.11 update 1 preview release that we posted today and report back if it addresses this issue? If it still hangs on the splash screen even after this change, capture a minidump for the hang using these instructions and send me a link to a zip file for the same. (it will be big)

This was a limitation for the bypass automation in the Prochannel. It would only work with realtime bounce. I've redesigned it to be independent of playback speed for a subsequent update.

Hi folks, We posted a preview build for update 1 that fixes several user reported issues with the 2020.11 release. We plan to release this very soon but if you were affected by any of the listed issues please download it and report back if it solves your issues here.

This issue is also caused by a bug in the latest VST3 SDK that we updated to recently. Its the same issue that was affecting strings in some plugins like Console One, Waves and Izotope Neutron. I've fixed the issue and notified Steinberg since the bug will affect any host using the latest VST3 SDK. We'll include the fix in the next maintenance release which should be fairly soon.

Hi Folks, It turns out that this problem is caused by a bug in the latest VST3 SDK that we updated to recently. I've fixed the issue and notified Steinberg since the bug will affect any host using the latest VST3 SDK. We'll include the fix in the next maintenance release which should be fairly soon.

I think this thread is confusing bounce with freeze. The main purpose of freeze is to render instrument tracks to audio in-place AND completely release the resources for the instrument. It does exactly that today. If I understand correctly some users want a shortcut to bouncing a instrument track MIDI to an audio track. This cannot be done in place to the same instrument track because it would double the audio. You can already bounce an instrument track to a different audio track from the bounce dialog. I guess I'm not understanding how this process could be sped up.

Rather than looking at the kitchen sink of chord track like features or what other DAW's do, I'm actually more interested in how you use a feature like this or if you haven't tried it what it would do to improve your workflow with music production.

What plugins are used in this project?

@Matthew Simon Fletcher please PM me the link as well as the case number you have.

He was suggesting that you switch from ASIO to WASAPI and open the same project and check if the pictures are recomputed. PS: please check your PM messages.

I'm curious what aspects of a chord track are attractive to you in your workflow. i.e how do you use it. Feel free to make a thread in the feature requests forum.

We'll investigate and fix it. Don't worry about the message there is nothing catastrophic. Its just an overly paranoid translation of a standard Microsoft error code that just means an operation failed

That's not our message. Check if one of your plugins is displaying that message.

I dont think you are describing the same issue in this thread. Please post in the main 2020.11 feedback thread with a description of the problem and if you are getting dropouts list the dropout code. Exporting cannot create dropouts.

@Mark Morgon-Shawcan you try rolling back to the last release just to verify for sure whether this is really a new symptom?

Which version of CbB are you running. Have you updated to the latest 2020.11 build that was released?

@Mark Morgon-Shaw are you sure that its new to this update - did you try a rollback? If its a new issue can you share the project file that has the issue?

No the driver isn't filling with zeros. If its got DSP then its passing on the floating point sample data through the ASIO input. Here is an example of a device that supports floating point ASIO. We added support for this several years back. If cakewalks record bit depth is set to 24 when the driver exposed 32 then we would be discarding the extra 8 bits permanently. Similar to if you set the record bit depth to 16 when the driver supports 24.