dantarbill

Unfortunately, that's not the problem. The import bit depth is "Original". If not, it would, as you say, convert everything on import. Instead, it's only converting WaveLab created stereo 24/44.1 (or 24/48) files that are longer than some value that's more than somewhere over like an hour and a half, but I don't know what that critical point is yet. Thus the question. That critical length is likely to be file size based rather than time/length based since .w64 was partly an effort to sidestep a 32 bit file length (or data length?) descriptor in the original wav file header chunk spec. Hmm...the max unsigned 32 bit integer is 4,294,967,295. What if WaveLab is representing that as a signed integer? Then that would be more like 2,147,483,647. Maybe that's it...because...in the case above...it's less than the resulting file size. Cake dev's? Comments?

A 24bit 44.1 kHz stereo wav file that’s 2 hours 16 minutes and 42 seconds long (2,170,460,864 bytes) from a QSC TouchMix-30 will drop into a 24/44.1 Sonar session without incident. A stereo file built from QSC mono tracks of the same length and saved as 24/44.1 stereo in WaveLab, ends up with a slightly smaller file size (2,170,460,228 bytes)…but it will get converted on import to Sonar as to a .w64 format (2,893,950,960 bytes). I’ve figured out that trimming the end of such files or cutting them into two chunks sidesteps the issue. However, I like to know what Sonar is looking for in order to make its decision to convert to w64? What exact file length or audio length triggers this?

...anyone else care to weigh in on this?

I totally get that video is not Cake's forte...however. Since it has video support (to a point) what would be the process to get a video that starts here, ends there and has rendered audio? I'm not looking for fades or dissolves or anything even slightly involved. The "real video editor" thing comes later.

CakeSonarLab user since DOS 2.whatever. Complete video noob. I've imported an MP4 video into Cake 2022.11, along with stereo audio from a Tascam DR-40. The audio from the MP4 gets dumped to it's own stereo audio track, which is muted in favor of the DR-40 capture, which has been jam sync'd to the MP4 video/audio. I've marked where I want the video to start and end. Everything's happy so far. In my typical export/render, I'll select all tracks and select the section between my start and end markers. File/Export/Audio etc. My thought would be that export to video would be the same process right? Apparently not, since File/Export/Video just gives you the entire video you started with (not just from Start to End) without any audio. What is the actual process here?

I've found the "secret sauce". The problem was importing 32 bit files into a 24 bit project. However, QSC has a TouchMix Utility to help with track import. One of the options I hadn't noticed before was the option to quantize the tracks down from 32 bits to 24 bits while it's doing the transfer. With 24 bit tracks in had, Cakewalk is happy enough to accept the files without another copy.

Hmm...I tried that, with the same results I was getting before. The difference might be that I'm importing into a project with the audio driver recording at 24 bits, but I'm pulling in 32 bit files (with matching sample rates of 44.1 kHz). The sizes of the original and copied files are slightly different (3,380 bytes). That could be because Cakewalk isn't just doing a OS level file copy. It likely that it's also rewriting the .wav file header with some data that wasn't there before.

With the drag import it still creates a copy (<filename> (n).wav). Moreover...even if I unselect "Copy audio..." on import...it still copies.

Perhaps I wasn't entirely clear... The idea is to copy the files to <projectName>/Audio first. Next import each of the files into Cakewalk tracks, but without selecting "Copy audio to project folder" on the import (and the 4 minute penalty). So now, wav files are assigned to (and referenced by) Cakewalk tracks. My fear is that Cakewalk will then refer to those tracks with an absolute rather than a relative path and get confused when the project is moved. Follow?

I'm dealing with weekly live multi-track recordings captured direct to an external drive from a QSC TouchMix board. When you import a .wav file into a track in Cakewalk, you have the option "Copy audio to project folder" marked by default. When you do that, the file is copied to <projectName>/Audio and is then referred to internally by a relative path...so...when you move the project "projectName" somewhere else, it still knows where that file is. (At least, I think that's how it works.) Let's say then, that I want to avoid costly file copies. I'm dealing with 2 hour, 44.1 kHz, 32 bit tracks that take about 4 1/2 minutes per track to copy on import...one at a time...with about 20 tracks. This is time and labor intensive. What happens if I bulk copy those files directly to the <projectName>/Audio folder and don't select "Copy audio..." on import? In the short term, I imagine that should work, but internally, are those files now referred to by a fully specified path that will lose track of the track files if the project is moved?

Ok...that "kinda" makes sense...ish. The option is disabled, but the clips are getting physically copied to the common "Audio Data" folder rather than a per project audio folder.

Ok...now I'm thinkin'... If it copies audio with the template if there is audio in the source project, then what the <expletive> is the good of having a "Copy all audio with project" option if it appears it will be ignored anyway?

Ah...there you go thinkin' again. I forgot that deleting the tracks doesn't really delete the files. It's the same idea the scook subsequently suggested. Thanks to all.

Thanks for the quick response though. I appreciate it.

That kinda bites. I'm dealing with 2 hour sets of 32 bit wav files with more than 20 tracks. With each weekly iteration, I'm improving the mix and wanting to save the results back and improve the template. You're saying I need to trash the current week's mix project in order to avoid the subsequent pointless copy. <heavy sigh>

When I do a "Save As..." to save the current project as a Template, it insists on also copying all the audio data, even though I go to great pains to keep in from doing so. "Copy all audio with project" is greyed out by default when the Save as type: is Template. But it seems to want to ignore that setting. Am I the only one that's seeing this?

I've seen this before...not like a lot...but I've seen it. Typically, it happens when opening legacy projects. It's been occurring occasionally for years with multiple versions of SONAR/Cakewalk.

BounceBufSizeMsec is already maxed at 250. I don't know that there's a particular "bad actor" in the plugin chain. The only thing was a 32 bit version of Voxengo's legacy Marquis compressor through jBridge...which gave me about 30% better speed. Pulling everything gave me a lot better speed, but then...what's the point? What kind of core usage percentage should I accept and be happy with?

I'm sure this question has been answered before...but I'm not asking about just one active core. It seems that ALL the cores are sandbagging. I have a hex core i7-3930K processor clocked at 3.2 GHz rendering a 2 hour live recording with just 2 stereo tracks and just a handful of plugins that wants to take 20 minutes to render. ALL of the cores are below 20% for pretty much the whole operation. I'm running Cakewalk 2020.11 (25.11.0.88). Is there something I'm doing wrong?

Uh...so... My hope was that the 32 bit v4 might continue to work since v5 is 64 bit only. I have a considerable pile of projects that I haven't pulled into 64 bit land (and continue to use older SONAR versions for). So...they shoot the 32 bit version in the head too?

The ancient version I have only gives you a single value, which may or may not be an average. The more recent, paid for version might support tempo changes. I don't know.

MixMeister Bpm Analyzer can do that. I have an ancient freebie version from 2004 that has a pretty simple user interface. You open the app, drag an audio file onto it and it tells you what the BPM is. They now seem to have a much more feature rich version for a whopping $3.99... http://www.mixmeister.com/bpm.php Note that my 16 year old version still does what it was supposed to do...so I haven't upgraded.

Would that have been... https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.28.html ?

I've been on SONAR for a very long time...and only recently switched over to Cakewalk (by Bandlab). I'm seeing something new (to me) on the timeline that I don't yet understand. It looks like the (yellow) Loop section markers, but it's green and goes across the top of the timeline. When you hover over the green bar, the cursor changes to something like <-S->, suggesting that you can drag the "S" section to do something useful. What is it and what does it do? What keyword do I look for in the documentation? (Ah! "Selection markers in time ruler") Thanks!

I would strongly consider talking yourself into investing in iZotope RX. I've tried notch filter solutions, which only manage to make the hum a little less annoying while doing major damage to the signal you want to keep. When used properly, RX can make the noise just go away. Once I had it in my toolbox, I found that I was using it ALL THE TIME, just as an audio editor since the frequency spectrum display makes it so easy to see and identify events in your audio. The Elements version might work for you, since it has a De-hum feature, but I've found that the Spectral Repair in the Standard version does a much better job (since De-hum is just another notch filter).