Noel Borthwick

OK so if I'm summarizing correctly: You import an MPEG4 video file into cakewalk and choose to import its audio. The audio has padding applied at the beginning to line up with the video. Within Cakewalk when you play the imported audio along with the video it plays perfectly in sync. Now if you export just the audio from cakewalk it is out of sync with another app that plays the same video because of the padding. If the above is correct this is related to the video engine that we're using for playback and transcoding. All the video support in Cakewalk is based on Microsoft's built in video support. We don't really have control over how it internally handles video playback and transcoding. In fact if the offset to the audio didn't get applied, then it would be out of sync with the video in Cakewalk itself. I think that would be a far worse problem. I can pass on this information to Microsoft since its not something we can solve internally. If you are taking audio out of Cakewalk that originated from an MP4 your only solution right now is to manually trim the silence from the audio before exporting.

As a shortcut your can also shift click on (ghosted} envelopes on the track to select them and edit

But is the audio synced to the video file it came from within Cakewalk itself? i.e. is the delay problem was introduced at import time, the export step is irrelevant.

Elastique preserves phase coherence so you should have no problems stretching multiple clips. You dont even need to do it destructively via process Length. You can select all the clips and slip stretch them all by the same amount. The shortcut key to do is hold down CTRL-Shift and then Drag the right edge of the clips to slip stretch them to the amount you need. Make sure the stretch method in the clip inspector is elastique pro. This will dynamically and non destructively stretch the audio to the new length.

@Alcar28 I can't read your screenshot but what is the module listed in the crash dialog? Can you also zip up the dump file listed there and send me a link to download it? It looks like some plugin in your project is crashing.

Problems can only get fixed if they are reported accurately and are reproducible. Waiting for a fix for a problem that isn't known could take awhile ESP is not part of our skillset unfortunately.

I'm not sure I understand your workflow here. How are you exporting the audio from Cakewalk? You mention "Audio Exported from MP4 within Sound Forge". What does this mean - are you exporting an MP4 from Soundforge or a wav file which is synced to an MP4 video file. Are you recording new audio synced to a video file and then exporting just the audio? Can you describe the exact steps you are doing in Cakewalk and how it intersects with the MP4 video - I'm not sure at what stage the delay is introduced here.

Hi @John Nelson Thanks for sending the dump file, it was useful. It's a bizarre crash. The problem is actually triggered by the plugin BFD. When shutting down it apparently ends up dispatching windows messages and as a result inadvertently launches the start screen! This crashes the Windows shell. I suspect this is something that may have been fixed by BFD since you have a very old version dated 2012. You can verify that this is the issue by changing CbB to not show the start screen. (Preferences | Display settings | Show start screen). Do you see BFD pop a dialog box or something when you close a project? I've also defensively addressed this in CbB by ensuring that start screen only opens when all projects have finished closing. PS: In the future when using file sharing services please send links that don't require the recipient to create an account. Dropbox has become obnoxious now about forcing recipients to create accounts. Its much better to use something like google drive and send a private link.

@klbailey3 did you try turning off ALL notifications in preferences yet (the main checkbox)?

Who did you send it to @John Nelson? I didn't receive anything.

Who is "they"? This is a universal problem and MP4's from different sources may have different padding so there isnt a simple universal solution I'm aware of.

Disk I/O is on a single thread so even if you have many cores we won't saturate the disk. But there are other factors as well. Many plugins are known to gate the speed by which they can process. To verify if that is the case try globally bypassing all effects in the project from the toolbar before doing the bounce. Using a large buffer size will yield some benefits however. You can set the BounceBufSize variable to a high value to force it to use a large buffer size. There is probably room for optimization but its unlikely to ever achieve full CPU bandwidth.

It wont consume 100% CPU because the hard disk is the gating factor. It can only run as fast as your disk can read and write the project.

Can you try this: In Preferences | Display try turning off "Show Project Load Notifications" and see if it changes anything.

Hi @jono grant we're aware of this issue. The issue is has to do with how MPEG4 audio files or MP3 files are encoded. It is very common for "padding silence" to be added at the beginning of the audio with compressed formats for encoding delay. This padding can vary depending on what encoder is used to compress the file. Encoders are supposed to write a special tag in the file to notate what this delay is in samples. However there are many encoders that do not write this information to the file and there is no standard tag for this. For example ITunes does it one way and other encoders write different tags or may or may not write this data at all. Additionally the Microsoft's SDK we use to decode the audio from these files provides no way to deterministically know what this padding delay is. Since the padding can vary for different sources, even if we guessed a compensation value it wouldn't work for different formats. In summary, it's not an easy problem. For now I'm afraid that the best solution is to manually trim silence from encoded audio files.

At some point we're considering adding resampling on the fly to allow for running projects at different sample rates. We already do this for plugin upsampling so its technically feasible.

@Jim RoseberryCan the processor threads be clock speed locked with earlier intel processors than the I9?

Plug-In load balancing results are very dependent on the actual load of plugins. Load balancing itself can be expensive since its doing some magic subdividing buffers so if you don't have really expensive plugins in the bin it could impact performance adversely. I plan on making this option per bin in the future so you have more fine grained control over it. Note that by default load balancing is ineffective at buffer sizes < 128 samples. This value can be changed in the ini file. More info here. Producer/Consumer mode basically allocates an extra thread and separates out the scheduling of mix engine tasks from actual mixing. On a system with lots of cores this can give you a slight improvement in balancing the workloads. How do you set CPU speed to fixed?

Just uploaded a whole bunch of music from the show recorded on Day 4 of the NAMM show to the Bakers Channel here! All of this was recorded live at the show to 8 tracks in CbB. @Jon Sasor mixed all of this. Some interesting post production using drum replacer for some tracks where the kick drum recordings were weak.

Mix scenes are referenced from the same project file so adding a new mix scene will dirty the project. The actual mix scenes are stored externally but the project file references them. You should always save your project after adding new mix scenes.

The track control manager still exists. It can be access from the track view preset picker as shown in the pic. All settings from the track control manager are also saved with lenses so you can completely customize the track view controls and save a lens preset for it as well.

@Gswitz Can you PM me a full description and recipe to reproduce this. Well look into it. Thanks!

Hi @Terry Williams With regard to the blank window could you please try this and see if it helps. First make sure you shut down BandLab assistant. Either restart your PC or kill any running BandLab assistant tasks. Next in File Explorer go to this folder by pasting this in the address box %appdata%\bandlab-assistant\Cache In the cache folder select and delete all the files. Now restart BandLab assistant. it should prompt you to log in again. Hopefully this may get you past this issue.

Plugin load balancing only applies if you have 2 or more plugins in a bin. And yes as the name implies it distributes the CPU load in parallel across multiple cores. Each effects bin that has 2 or more plugins will be balanced this way and this includes all effects bins across tracks buses, prochannel as well as clip effects. Some caveats: Plug-in load balancing makes the most difference when you have many ( more than 4-5) plugins in a bin and they are expensive to process. These are the cases where normally the load would bottleneck other serial processing of the track or bus. This can be the case when you have a complex mastering chain with many plugins on a single bus. If the plugins require low CPU then load balancing won't help much and may actually consume more CPU since multiprocessing has overhead as well and the task switching cost may not be beneficial in this case. Plug-in load balancing only kicks in when the buffer size is > 64 samples. Otherwise there would be no benefits.

There are no practical limits since it uses wave64 when the chunk size goes larger than 2gb. You should be able to create bundles that are many gigabytes in size. See this link for the details about max length.