Martin Vigesaa

I see. I was approaching it backwards, and switching windows settings to use my audio device.

When I have cakewalk open, it often, but not always prevents playing audio files outside of Cakewalk, e.g. Windows Media Player, or YouTube... I have tried checking "Suspend Audio Engine When Cakewalk is Not in Focus" but this perhaps is not what i'm looking for? I basically what the audio engine to allow multiple apps to use my audio device. This always worked with my old Windows 7 machine, but with my new Windows 10 setup it seems intermittent and possibly varies with the order I open apps.. Often I have to resort to rebooting the PC just to play an audio file on another app.. I have looked into multiple windows and Cakewalk settings but can't seem to find the correct combination. My PC Info: Processor Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz 2.90 GHz Installed RAM 16.0 GB System type 64-bit operating system, x64-based processor Windows: Edition Windows 10 Home Version 20H2 Installed on ‎4/‎17/‎2021 OS build 19042.1165 Experience Windows Feature Experience Pack 120.2212.3530.0

Correct. I have tried that but found issues implementing that option when recording drums for example. The drummer is in the drum room, ~8 microphones and multiple tracks playing back. If I route a direct, no latency signal to the drummers headphones during recording, when I go to play back the tracks just recorded I have to unmute the just recorded tracks on the headphone monitor bus/mix. Then we go back to punch in I can't find a way to play the previous recording, automatically mute those channels and divert back to the no latency mix... I do full band recordings and a lot of punch ins, switching tracks and repeating.. so I would like a solution where the no latency audio can be somehow directed through the Cakewalk mixer and not have to use the monitoring interface software. Is something like this possible?

Solution: I found a "Hidden" effect on 1 small audio clip buried in the song. It seemed to work well to Archive every track, then 1 by 1 de-Archive testing the latency each time. Finally found it was related to 1 track, the found the "FX" indicator on 1 clip. The effect was the "Acon digital de-clip" Is there a search function to speed the process of finding which clips has FX applied?

I have a project that is getting fairly large with many channels of audio (no virtual instruments). Before I click play or record I can play bass for example and there very little latency (delay). As soon as playback or record is in progress the latency appears and it is too much delay to even play along with (Around 100ms). After stopping record or playback, the latency remains until I click the "FX" (Bypass all effects) button off then back on. Since the issue is only triggered by playback or record, could this mean it is related to the number of audio files, number of sends, channels. Even if I disable all plug-ins (aside from the default pro-channel Eq, compressor, etc) The latency still appears. If I enable a powerful plugin, then it will add latency even before playback or record. I expect this. I could do some clean up and delete some unused Sends, etc, but I would like to get an idea of the cause first. I just switched from a ~ 10 year old Windows pc to a new PC (Intel i7-10700F, 2.9GHz, 16GB RAM, NVIDIE GTX 1660 Ti. The "Performance" monitor appears much lower, I can set the buffer size to 256 samples (5.8ms) and even a step or 2 less, however it sounds like more that 5.8 mS. Disk Load = ~6%, Memory = 39%,. Basically it appears there should be no problem, but there is. I'm Hoping there is some clean up work I can do, maybe use the "Flatten Comp" feature... other, but not sure where to start.

Darcy, Are you setting up a new PC (as I did) and are trying to play projects from the previous machine? Did you delete the effects from the channels FX bins in the tracks and busses? It seems possible or probable there could be other plug-ins besides Scheps that have the issue and it could be it's not the plug-ins fault, but some issue of transferring the plug in to the new machine from an old project file..

Solution found: The issues was narrowed down to the waves plug-in "Scheps Omni Channel". This was the fix Uninstall the plugin Open the project that had the issue. (Likely will have to do this to all projects that contained the plug-in from the previous computer) Delete all instances of the plug in from all tracks and busses in the project. Save project. Re-install the plug in ("Scheps Omni Channel" ) Open Project. Insert the plug in as needed. (unfortunately I lost all settings for each instance of the plug in. I likely could have opened the project on the old PC, then saved the settings for each channel/bus, then transferred the file that contains those saved settings and transferred to the new PC...)

UPDATE: I uninstalled all my waves plugins using their "Waves Central" tool and the project at least opens with no "fatal error". Next step maybe install 1 at a time to determine which one(s) cause the error.

Thanks for the reply. I didn't realize I could still download Platinum. I did that and got all the missing plug-ins. The fatal error still occurs howeve_12112020_004404.dmpr. The dump file is attached. I may try re-installing the Waves plug-ins and I will contact Waves.

I get the fatal error message (image below) when trying to open a project on my new PC. This appears to be related to 1 or more plug-ins as simpler projects with fewer plug-ins open ok. The odd thing is the project does open and works, it just crashes if I click "Yes" or "No" on the error message window. I can Shift-Open the project, but that removes ALL effects and it would be difficult to re-construct the project from that point. Any advise on how to fix the issue so the project will open? Finishing the project on the old PC may not be an option as it has some other issues.

Rather than go through the extra work of setting up my interface software mixer to allow a direct 'no latency' signal. I have always recorded with my Mixing Latency buffer set low in Cakewalk, turned off plugins that cause excessive latency, then do the reverse when mixing. E.g. turn the latency buffer size up, turn plugins back on... As I acquire more plugins recently I am finding I this method may be more time consuming than setting up a "no latency" path for recording. Is the following a normal practice: (Recording a singer example): Use a channel send e.g "Monitor Mix 1" to setup a mix for the singer. This mix is routed from Cakewalk to an audio interface output e.g Output 3. This allows the singer to hear the mix however they want as each channel has a send. Due to latency, the vocal mic channel is not sent to Monitor Mix 1, but instead the Audio interface software mixer is setup to route the vocal mic channel to Output 3. I'm thinking with this setup I may be able to leave most plug-ins ON allowing me to start building a final mix as the project proceeds as long as the latency compensation works, and my PC can keep up. A down side is: Having to bounce back and forth between cakewalk and the audio interface mixer. Probably not a big deal once it becomes habit. Reverb for the vocal will have a pre-delay equal to the latency. In general is it more common to record and live with the slight delay in your monitored signal or is setting up a no latency path more common? Any advice?

I would like the option to place the metronome as a track instead of a bus. The purpose being the ability to Export a mix that includes the click audio without having to record the click. I often need to make mixes that include a click and would like the ability to do this as simply as possible. That said, having the option to record the click as described in this tutorial is far better than no option.

You are correct. It used to work using the manufacturer's panel, but now I will switch to only using the Preferences menu in BandLab. It is actually easier to do it that way anyway. Thanks for all the help.

It is the on board 1394 (I think it's the bold item below and looks like it would be VIA chipset?): And as someone, Noel? suggested, changing the Buffer Size using BandLab instead of the "Mix Control" software interface prevents the issue. The only loss I have is a few in-between Buffer size options so this issue is very minor for me now.

I would suggest possibly rewording the following: I can interpret the wording "prior early access HFEA1 build 59" 2 different ways: 1. Install this if your version is prior to build 59. OR: 2. Install this if you currently have build 59. I have 2019.11.0.54. This is not build 59, but is prior to 59? See the confusion?