Jump to content

dantarbill

Members
  • Content Count

    37
  • Joined

  • Last visited

Community Reputation

1 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. With the drag import it still creates a copy (<filename> (n).wav). Moreover...even if I unselect "Copy audio..." on import...it still copies.
  4. 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?
  5. 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?
  6. 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.
  7. 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?
  8. 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.
  9. Thanks for the quick response though. I appreciate it.
  10. 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>
  11. 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?
  12. 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.
  13. 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?
  14. 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?
  15. 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?
×
×
  • Create New...