Noel Borthwick

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.

Hi folks, Like we did last year at NAMM we'd like to showcase a few projects featuring the diverse work that you all do. At the booth, we like to have a playlist of projects that show the breadth of work done by our users with Cakewalk by BandLab. If you would like to have one of your projects considered for our showcase please post a link to the music in this thread with maybe a screenshot of the loaded project if possible. If you have a great sounding project that were produced primarily in CbB and showcases the application please post a link to the music in this thread with a screenshot of the loaded project. An easy way to audition mixes is to publish a mix of your project to BandLab and embed the BandLab link. (click the bandlab icon on the toolbar in the post editor to embed) The ones we picked last year should give you some guidelines on stuff that could work as a demo. NAMM can be noisy! Guidelines: We need a project file for a submission so please don't list songs that you cannot submit as a project file. All projects will be played from a Surface Book 2. We have some pretty heavy projects that play fine on the SB but freezing tracks might be required if the load is too much. Plug-ins. We normally have a suite of all Cakewalk plugins as well as some of the more popular third party plugins installed (Waves, NI, Melodyne, Slate Digital, FabFilter, ..) Please indicate what 3rd party plug-ins are used in every submission. If accepted we'll try and accommodate installing the plugins used if resources are available. We're looking for some diverse material so things like modern electronic music, film scores, jazz, metal, rock, etc are all viable candidates. Project's that showcase heavy use of certain features or production techniques are also viable candidates. e.g vocal comping, multi tracked drums, vocalsync, melodyne, advanced mixing, parallel compression, sidechaining, etc. We can also accommodate video files if the project has a video to accompany it. Video projects are attractive for demos. If you do have a video preferably submit a MPEG file or a format compatible for playback within CbB . The video must be synced to the audio. You must have rights to share the music and may need to sign a release form Accepted projects will need to be uploaded to a shared folder or a download link will need to be provided by you Time is short so we'll need these by end of next week to get prepped. Thanks!

Best to contact celemony to help troubleshoot it

Thanks to David at Lynx for the fast turn around on this!

It's best to post a video of what you are doing since there may be some confusion with how you are describing the issue. Which channels are getting muted? when you record on a track it's normal for previous audio on the same track to get muted. Other tracks should be unaffected by recording.