Noel Borthwick

If you check the release notes in the latest release its no longer necessary to activate using Assistant. Cakewalk will self activate as long as it has an internet connection and you log in to your bandlab account from within Cakewalk.

As long as you have an internet connection *somewhere* at an internet cafe or something you can activate cakewalk. All you need is to install BandLab assistant there and download the activation request as explained in the documentation. Its dead simple to do and is similar to what we had earlier with SONAR.

No thats the old SONAR help. I had posted a bad link originally, I updated it to the correct link.

It's not a ”flaw” in the system, it's by design. You can authorize an offline machine by following the offline activation workflow. Cakewalk won't get randomly unauthorized beyond the normal 6 month period unless the system has been updated in some way to break the authorization. In the activation message there is an error code that should indicate what the source of the problem is.

Just saw this. There original diagnosis of the problem was by me. This issue had nothing to do with your network interface but it's a faulty asio driver that crashes when loaded. As long as you uninstall it remove the dll it should work fine. Looks like you figured out how to do that.

One exception. There are some drivers with onboard mixing or dsp that expose inputs that are floating point. It makes sense for such drivers to offer 32 or 64 bit inputs because the signal chain is floating point.

@Winstonhulley88 that's great news. In most cases problems with compatibility can be rapidly resolved if you contact the right right party with a solid recipe. Thanks for following through and reporting back.

@Morten Saether can fix that That's sounds right.

It uses the latest LAME encoder internally.

In CbB you can use clean audio disk which works very fast and flags unused audio files within the project folder (unlike SONAR).

The default PicCache size is 500 MB not 20. Are you sure that a 3 hour project took 115MB for one wave file of that duration? My estimate was a too optimistic but a stereo 3 hour wave file at 24 bit 48Khz is about 3.1GB A pic cache file is approx 1.57% of the file size so that would make it about 51MB in size. So a 10 day recording of one file would yield a wave file of size 248GB and a pic cache size of under 4GB. PS I think the overview file can grow greater than 4Gb (it will turn into a Wave64 file under the hood) but we should verify that. As per new CbB versions we allow the pic cache to grow for that session beyond the max size but on next launch it will try deleting files to free space.

Are you using the latest build of CbB? I can't speak for Platinum

You should be able to generate a picture for a 15 day file Picture cache files are very small.

A two hour project should be fine. There will be a small wait while all the waveform pictures are computed. It has to read every weave files on entirety to do this. Once it completes save the project and it will never need to compute the pictures again. Scroll through the full project to make sure it's finished generating the waveforms before saving. And yes this is greatly improved in CbB compared to Platinum.

Havent tried this but it may be worth checking out. https://www.microsoft.com/en-us/p/realtek-audio-control/9p2b8mcsvpln?activetab=pivot:overviewtab# https://www.tenforums.com/sound-audio/135259-latest-realtek-hd-audio-driver-version-2-a.html

Hi @Nick Maltzoff, I tested with the iRig pro I/O. It's working for me and @Kai Olav Fredriksen with no problems so it should work for you. Esp is it's working with amplitude. Please try the release candidate build 84 which has some more related fixes that we posted yesterday. In this build you should only see a single mono input. Let me know if you can't hear the output with this build and we can troubleshoot further. You can also play with the asio driver settings. Also make sure that your master bus is routed to the iiRig output.

If you are not recording and just playing back you should NOT need to use ASIO4All. All onboard audio devices should work with Cakewalk in WASAPI mode. Use WASAPI shared mode by default. There are many advantages to using WASAPI shared. For one it wont block audio if another application like Youtube is using it.

High def audio device is the Microsoft supplied driver that wraps several chipsets including realtek. You can find out what onboard chipset you have via the MSINFO system info utility. My info looks like this. If this is a custom built PC I think by default Windows 10 will use HDAUDIO.SYS. This should be ok generally since it supports the Win10 low latency audios stuff but you may be able to get a manufacturer driver that has better support.

Download the latest installer from this link. We'll be officially releasing it soon.

I've specifically tweaked wasapi to work well with realtek. the main advantage of onboard audio codecs in wasapi is that unlike usb they support the windows 10 low latency wasapi support via IAudioClient3. This means that they will support latencies in shared mode that go down to less than 10 msec. I've had acceptable performance at 3msec buffers. Many consumer grade usb devices won't even go that's low. Of course if you already own a pro audio interface and it's convenient to use you wouldn't choose onboard audio. If you want to use a guitar or mic input portably guitar rig is a nice inexpensive solution and it does work even in wasapi shared mode, allowing you to record guitar while outputting from your onboard audio device in a laptop scenario. It's all about having choices.

Yes the issue has been fixed in the latest release candidate

Many thanks everyone for the stellar feedback to this EA release and helping us make it as stable as possible. We have fixed all the reported issues related to the new features. We also included a couple of small additions. Special callout to @Promidi @Maestro @Steve Harder for all the great feedback on articulation maps. Also @Toy who spent many hours helping us troubleshoot a complex intermittent problem with the arranger and articulation UI. Barring any further issues we should release the final version very soon.

@Frank De Baere and @Toy please check your PM's

Yes I already fixed that last night (after the build you got). In the next release you will not be able to choose a stereo or right channel - that was the problem.

@Frank De BaereWe have a potential fix for the menus not closing themselves. Ive never seen the menus stay after the app has closed. Are you sure that the application actually shut down? Check in task manager. Is this something you can reproduce reliably? If so we'd like you to test a build with the fix if possible.