Noel Borthwick

@Steve Moddelmog I looked at all (well several) of the dump files you sent. These are all 100% plugin crashes - the stacks are not even remotely in Cakewalk code so its not something I can analyze further. The crashes are all in a shared plugin dll that they are loading called Chromaphone 2 Shared.bin. I suggest that you get in touch with AAS and give them the same dump files. They should be able to analyze why the plugins are crashing since its within their shared plugin code. I know the AAS guys well so if they need any assistance from us ask them to contact me. Its likely some incompatibility or a bug in the plugin thats being exposed under some conditions on your system. I've included some relevant snippets from the dumps. One more thing suspicious in your dump files. I see that you are running outdated Microsoft runtimes for the VC redistributables. Here are the time stamps you have: mfc140u.dll *C:\Windows\System32\mfc140u.dll 14.16.27024.1 11/7/2018 1:49 PM VCRUNTIME140.dll *C:\Windows\System32\VCRUNTIME140.dll 14.16.27024.1 11/7/2018 1:35 PM The ones we redistribute are much later so I'm not sure why your system isn't up to date. Maybe you reverted the install somehow or another app put old files there. The versions from the Cakewalk installer are as below: mfc14u.dll 14.20.27508.1 3/8/2019 vcruntime.dll 14.20.27508.1 3/8/2019 Please do an install of the latest VC redists by following this link. After ensuring that you have more current versions of these files please redo the test and see if it crashes. I'm not sure if your crash issues are related but having old redist files can definitely cause crashes and other incompatibilities. 'Untitled_01312020_125802.dmp' (Minidump): Loaded '*\\?\C:\Users\User\AppData\Local\Temp\Chromaphone 2 Shared.bin 64\Chromaphone 2 Shared.bin'. Module was built without symbols. Unhandled exception at 0x0000000054EE4660 (Chromaphone 2 Shared.bin) in Untitled_01312020_125802.dmp: 0xC0000005: Access violation reading location 0x0000000066B15180. 'Untitled_01252020_092413.dmp' (Minidump): Loaded 'C:\Windows\System32\explorerframe.dll'. Unhandled exception at 0x00000000A8FF834C (Chromaphone 2 Shared.bin) in Untitled_01252020_092413.dmp: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF. ntitled_01262020_184418.dmp' (Minidump): Loaded '*c:\program files\common files\VST3\Chromaphone 2.vst3'. Module was built without symbols. 'Untitled_01262020_184418.dmp' (Minidump): Loaded '*\\?\C:\Users\User\AppData\Local\Temp\Chromaphone 2 Shared.bin 64\Chromaphone 2 Shared.bin'. Module was built without symbols. Unhandled exception at 0x00007FFE4A80A839 (KERNELBASE.dll) in Untitled_01262020_184418.dmp: 0x20474343 (parameters: 0x000000007D5DF370). Untitled_01262020_185903.dmp' (Minidump): Loaded '*c:\program files\common files\VST3\Chromaphone 2.vst3'. Module was built without symbols. 'Untitled_01262020_185903.dmp' (Minidump): Loaded '*\\?\C:\Users\User\AppData\Local\Temp\Chromaphone 2 Shared.bin 64\Chromaphone 2 Shared.bin'. Module was built without symbols. Unhandled exception at 0x0000000072754660 (Chromaphone 2 Shared.bin) in Untitled_01262020_185903.dmp: 0xC0000005: Access violation reading location 0x000000000078A180. 'Untitled_01262020_190505.dmp' (Minidump): Loaded '*c:\program files\common files\VST3\Chromaphone 2.vst3'. Module was built without symbols. 'Untitled_01262020_190505.dmp' (Minidump): Loaded '*\\?\C:\Users\User\AppData\Local\Temp\Chromaphone 2 Shared.bin 64\Chromaphone 2 Shared.bin'. Module was built without symbols. Unhandled exception at 0x0000000071784660 (Chromaphone 2 Shared.bin) in Untitled_01262020_190505.dmp: 0xC0000005: Access violation reading location 0x00000000722E8180. 'Untitled_01262020_195535.dmp' (Minidump): Loaded '*c:\program files\common files\VST3\Chromaphone 2.vst3'. Module was built without symbols. 'Untitled_01262020_195535.dmp' (Minidump): Loaded '*\\?\C:\Users\User\AppData\Local\Temp\Chromaphone 2 Shared.bin 64\Chromaphone 2 Shared.bin'. Module was built without symbols. 'Untitled_01262020_195535.dmp' (Minidump): Loaded '*c:\program files\common files\VST3\Ultra Analog VA-3.vst3'. Module was built without symbols. 'Untitled_01262020_195535.dmp' (Minidump): Loaded '*\\?\C:\Users\User\AppData\Local\Temp\Ultra Analog VA-3 Shared.bin 64\Ultra Analog VA-3 Shared.bin'. Module was built without symbols. Unhandled exception at 0x00007FFE7027A839 (KERNELBASE.dll) in Untitled_01262020_195535.dmp: 0x20474343 (parameters: 0x000000008AA21B50).

Another way to do this is to SOLO the MIDI track which will auto solo the synth audio track. Then bounce to track without a selection. The reason why it requires a selection of the MIDI track is the operation doesn't know which MIDI tracks you may want to include in the bounce. I think we can improve this by being smarter and auto selecting all associated MIDI tracks if nothing is selected, to avoid confusion like this.

This looks like a memory leak leading to this. Can you reproduce this by just creating a project and inserting Revo Pro?

Hi @Steve Moddelmog can you please send me a dump file to analyze? Here is info on how to capture a dump file for a hang.

@rv729 can you send me the log file please - which directory name is being skipped specifically? Where are the toontrack plugins installed?

Will send you a PM to try and get to the bottom of why you are getting a Win7 warning. Nobody else has reported this yet so we'll have to do some further troubleshooting. Regarding the crash its unlikely to be related to this release. Can you zip the dump file and upload it to any file share and send me a link please?

the new mode is completely independent of the other modes so should be fine going back. The new mode can use threads differently from prior modes since it supports task stealing. Did you also get the clicks with load balancing turned off? Maybe it exposes threading issues in that Kontakt instrument.

@Terry Kelley You are running win 10 and got this install warning? What flavor and version of Windows 10 are your running?

@Matthew Sorrels I doubt the final release had anything to do with it. There were a few completely unrelated fixes. Loadbalancing could potentially impact certain plugins negatively is one thought.

You can reload the ASIO driver manually in Cakewalk at any time by pressing CTRL and clicking the Reset button. However when I have seen this happen this doesnt solve the problem. Some devices physically need to be power cycled. Its a hardware/driver issue.

@JL Hmm I havent run into that. Does it only happen with the aggressive mode?

@noynekkerLate buffers is just a term I cooked up to indicate buffers that took too long to process. If you aren't seeing any late buffers it means that you aren't hitting any limits and that the CPU is able to process all workloads ahead of time. I will write an article about it later but in a nutshell it works like this. For each audio buffer, the audio engine allocates workloads for processing all tracks, buses etc to cores. It then waits for all the cores to finish processing their workloads. After the cores finish their work the final mixed audio buffers are delivered to the audio driver. Then the process repeats for the next buffer. If for some reason ALL workloads take longer to process than the deadline for the buffer (deadline = audio latency in milliseconds) the driver will get its buffer late. Hence its called a late buffer. Late buffers are shown in the CPU metrics. While a few late buffers will be completely imperceptible and shouldn't be anything to be concerned about, if you are getting hundreds of late buffers you should probably raise your latency. Higher latency means the deadline is longer and it gives the CPU more headroom to finish processing.

Yes we plan to at some point allow editing MIDI automation on simple instrument tracks. It is not available today unless you split the tracks add the automation and then re-combine them again.

That sounds like a local problem then independent of this thread - perhaps your machine identity changed.

Um no you misunderstood my answer. As I said activation is completely independent of the version installed today. IOW it doesn't check the currently installed version. If you are asking if a currently installed version will work forever the answer is no. There is no guarantee that OS changes won't break something and we don't support old versions indefinitely which is why we have periodic updates. As far as Windows 7 goes, at some point we will stop allowing updates because changes will be incompatible with Win7. We can't predict what will happen in the future but as long as BandLab assistant continues to work on Win7 activation should still be possible.

If your send me the dump file I can send it to Steinberg. It appears to be a crash in their plugin

Unfortunately wasapi shared mode doesn't allow us to tweak the buffer size to make it larger than the default from windows.

Activation is independent of installing a new version. You can choose to reactivate at any time from the bandlab assistant menu.

Was it running an old build of Cakewalk? Also what specfic error code did you get? The issue we're discussing here was a case that only affected new installs.

Well, that is also used when adding normal tracks so instances is not appropriate in that context.

The most important thing is to note what the dropout code says. The help link in the dropout toast message lists the meaning for all the codes and possible resolution steps.

In case you missed it, we have a new early access build available. We plan to release sometime next week, so please post in the thread if you notice any issues. There is a brand new "Instrument track per output" feature that is useful for multitimbral synths like Kontakt, and also some audio engine optimizations and better engine load metrics.

@Kevin Perry deleting files shouldn't be necessary. Just choose refresh activation from BandLab assistant and it will automatically reauthorize the application. The original issue was caused by a server outage and would only have affected new installations. Were you installing to a new PC?

Picking a higher sample rate in the export dialog will not help at all if the original project is at a lower sample rate. The project isn't converted to 96k. All the export is doing is upsampling the FINAL output of the render, essentially processing and mixing all tracks at the lower sample rate and then converting the final result. This isn't very useful other than producing a file at 96K. If you want to take advantage of upsampling in plugins you should use the the plug-in upsampling feature which will add a upsample -> process -> downsample stage to all plugins you choose to upsample. Or have all the tracks in the projects at 96k.

not in the main release builds. You can however see which ASIO devices are installed on the system in the registry here: HKEY_LOCAL_MACHINE\SOFTWARE\ASIO If you delete an entry under that key, Cakewalk will stop enumerating the driver. (back up the reg key before you try and delete it so you can restore it later)