Noel Borthwick

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

Im quite impressed I can put the latency down to 16 samples and it works fine here.

@Kai Olav FredriksenThanks for reporting this. I've fixed the issue for the upcoming release. Let me know if you would like to test a build with the fix.

I just tested the rocksmith cable in WASAPI shared and Wasapi exclusive mode and it works fine here. I output through a different headset device. In fact in WASAPI exclusive I could go down to about 5 msec buffer sizes and it worked ok. It also works with my focusrite as an output but the focusrite has poor WASAPI latency. What problem are you running into - do you get any error messages?

This is a bug in the plugin and has been already reported to Akai by us.

I don't see any reason to be snobby about Realtek. Its quite amazing what they do at the cost and its a viable solution for playback when all you have is a laptop. For input you will need a line level signal. Here is an example of their specs: https://www.realtek.com/en/products/computer-peripheral-ics/item/alc898 For recording the bigger problem is that the converters are housed in a PC which typically isn't the best location to avoid interference which is where most of the issues arise from with hum and noise. The OP was not looking for high quality so if the user can get it working without spending a hundred or more its a good thing.

Glad that the dropout diagnostics were of use. Once you followed the instructions ? Based on your project description you have close to 173 tracks. Assuming that they are all audio tracks that is a fair amount of load on the disk. If you have a slow disk a buffer size of 256 may be too slow to keep up esp if its fragmented. Is it an SSD? PS: A dropout is not quite a crash <g>

Glad that the dropout diagnostics were of use. Once you followed the instructions ?

Please try the 2020.10 EA release since there are some optimizations that improve performance when there are many take lanes with muted clips. Also list the dropout code.

Realtek works fine with both Wasapi Shared and exclusive. In fact on Win10 you can get very decent latency with it - it goes down to about 4-5 msec with no issues. You shouldnt have issues overdubbing from the line in as long as you are running at low latency. Audio quality should be acceptable as long as you don't have any electrical noise coming in from the MOBO when recording. If you have a line level signal coming in from a mic into the line-in input you may be surprised. Obviously don't use the onboard mic lol.

@Cédric Lawde this behavior has been improved for the 2020.10 release. Simply adding a synth or loading a project shouldn't be triggering the creation of those files since they are only used during recording so that issue has been addressed. Some notes for others reading this topic later. With regard to the Allow Arm Changes topic please read the help for the Recording Options. In most cases you should always leave the two sub options "Only for Inputs in Project" and "Exclude Synth Inputs" checked because otherwise you can get a very large number of files created if you have many audio inputs available. This will make starting the transport sluggish. 3 files are created preemptively for every input on the system without those options checked. So if you have 16 hardware inputs and 10 synths in the project each with 8 recordable outputs, you will get a massive number of files created each time. 96*3 = 288 files! While these files are very small, file creation takes time and it will unnecessarily overload the system. By leaving "Only for Inputs in Project" checked this will greatly reduce the number of anticipated inputs and be much more efficient while still allowing you to arm on the fly. Another general performance tweak is to only select audio device inputs in preferences that you actually use and leave others unselected. This will also help reduce unnecessary inputs.

Its not Cakewalk crashing its the UAD driver crashing. Bluescreens can never be caused by user mode programs, only kernel mode drivers can bluescreen. This is not a question we can answer, only UA can debug and solve this issue so I suggest contacting their technical support with the recipe.

Hide related VST2 plugins has absolutely nothing to do with VST scanning. It just affects what is shown in Cakewalk's menus and plugin layouts. Its completely coincidental that your change appeared to affect your problem.

Thanks for the great reviews and for spreading the word.

Are you running the latest version of CbB? Please post a video or screenshot of the problem. Also check what your picture cache folder is set to and find and delete all files in that folder. If something is blocking generation of the pictures or you have HD problems it could cause this problem.

We tested the VSL maps and the Vienna folks have had early access to this build of CbB for some time as well.

Cakewalk by default auto scans only newly added plugins and is typically very fast. Of course for shells like Waves it has to load the shell to check that. As scook mentioned you can disable the auto scan if you prefer to manage it manually.

Glad you like it. A lot of effort went into this feature and we wanted to get it right from the get go. @msmcleod did most of the articulation maps implementation so he can comment further. We plan on making a subforum for users to share articulation maps if there is interest but you are welcome to start a thread. Any Cubase compatible map should import into CbB. We already tested the Vienna Ensemble maps and they work fine.