Noel Borthwick

@paulo There are some more WASAPI improvements in 2020.01 (esp for exclusive mode) so please try it there as well. What output device are you when using the mic in Cbb? This is important because both the output and input have to support the same sample rate and bit depth for it to work. The fix I am referring to has to do with how some devices deal with 16 bit audio. We had a case where a device would only work when the bit depth was set to 24 bit manually. This has been fixed in 2020.01 and such devices should now connect properly. Let me know if updating fixes this issue. If you are still having a problem PM me and we can do some more troubleshooting.

@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.

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.

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.

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)

It should be called speed step-down

Wow thats bizarre. The Windows scheduler continues to confound me when it comes to real time performance Could this somehow be related to hyper threading - perhaps threads are being assigned to virtual cores that have lower performance. Just hypothesizing I have no idea if that is true. Just for comparison do you see the same behavior in SONAR (in case you have it)

Static/distortion is a symptom of the DAW not being able to produce audio fast enough for the driver at that buffer size. Try raising your buffer size to something higher like 64 or 128 samples and check again. @Frank DeFede Are you sure that you were previously running with the device set to 32 samples? That is a very low sample size and not many drivers handle those smaller sizes. Also which version of Cakewalk specifically did you have installed previously? Please attach a screenshot of the Device settings page from preferences.

In ASIO mode when Cakewalk starts it enumerates all ASIO drivers installed on the system to check if they are valid. While doing this it goes through each of them and sets the driver to the same sample rate as report back by the driver. i.e. this should have no effect since its setting the sample rate to the same value. Subsequently, if you create a new project it sets the driver to the default sample rate as set in preferences. Alternatively if you open an existing project it sets the driver to the sample rate as used by that project. These are the only 3 ways that the sample rate is set. However if you have multiple ASIO drivers that use the same physical hardware it can cause confusion. For example in step 1 while enumerating drivers if one of the drivers reported 44100 and the other driver reported 96000 the sample rate will flip between the two. (Cakewalk has no idea that two different drivers access the same device) It's not a good idea to have multiple drivers for the same device so if you have that its its best to uninstall any other generic drivers and only keep the native manufacturer's driver installed.

@reza sadeghi It would appear that this is a driver issue. Please notify the vendor that when Windows is set to 96K it is affecting ASIO playback. However as ProMIDI says there is no good reason to have Windows use the driver at 96K. In fact you should preferably not route windows to your main audio interface all the time to avoid unwanted interactions with the driver from Windows while using ProAudio applications.

If you send a dump file I can take a look. We are not supporting windows 7 anymore however.

If so it isn't ours to fix. Plugins expose buses and it's up to the plugin developers to expose them or not. Contact the vendor for an explanation

If you are interested in submitting a project for our NAMM showcase please respond to the linked thread.