cwb files > 2GB?

  • Thread starter Thread starter Bulls Hit
  • Start date Start date
B

Bulls Hit

Well-known member
I'm running GT3 and I'm guessing 2GB is the max file size I can save as a cwb?
Anything larger than that and I get the 'audio disk is full' message.

So I have this project where I've recorded 5 tracks of drums, maybe 10 minutes worth at 24/48 and added another 8 or so tracks of guitars etc, anything from about 30 seconds to a couple of minutes each, then bounced a couple of submixes, final mix etc. the usual stuff. Typically this uses somewhere between 500MB & 1GB of space. This time I've split the drums and looped segments of them so each drum track now consists of 30 or 40 bite sized clips. This seems to somehow chew the space like there's no tomorrow as it's now used over 3GB. Which I can't save as a cwb.

So I went back and deleted the original drum & guitar tracks, and just kept the looped clips and final mixes. Guess what, I'm still using 3GB. I did a clean audio folder, and it found no files to delete. If I look in the audio ditrectory, there's dozens of files of the same size in there. I know from past experience if I delete any of them it will say 'missing audio, replaced with silence'.

Seems to me Cakewalk's file management is kinda dumb and not really doing the good thing. Any ideas on how I can reclaim the disk space, make the folder small enough so I can back the dman think up w/o trashing the whole project?
 
This is a complete guess...

Save As... Under a differant file name...

I know Cubase gives you an option to lose the files not used does cakewalk do the same?
 
This time I've split the drums and looped segments of them so each drum track now consists of 30 or 40 bite sized clips.
Click to expand...

Not sure about Guitar Tracks, but in Sonar when you split a clip, all the original data is still retained. You might want to try using the Apply Trimming command on the clips in order to reduce their size.
 
Once I heard 2GB / one file limitation is file system problem... You must format your drive using NTFS to solve this problem... No?
 
James Argo said:
No?
Click to expand...
No. :D






Or at least, that is not the case here. I believe this is a limitation of the wave file format.


http://forum.cakewalk.com/tm.asp?m=558677&mpage=1&key=file,limit&#559551
Wav files contain a header with a field that specifies the length of the file in bytes. The field length is an unsigned 32-bit integer which would define a maximum file size of 4GB. The issue exists because many(most?) OSes and application programs treat(incorrectly) the 32-bit file length field as a signed number, therefore reducing the size limitation of the format to one half what it should be.

In practical terms, yes, you will observe the 2GB issue in Sonar if it "reads" the wav file length field as a signed number.
Click to expand...
 
Yeah, something like that... :o The OS / application won't let you do over 2GB.

[OT MODE = ON]
Maybe it thinks 2GB = verrrry long song = borrrring = bad idea... :p :D
[OT MODE = OFF]


;)
Jaymz
 
Thanks guys.

Yeah that 31-32 bit thing makes sense. The thingis though, none of the individual wav files are greater than 2GB. Presumably the same limitation applies to .cwb files.

As far as retaining the original data goes, I don't think GT3 has an 'Apply Trimming' function. I guess all I can do is to bounce the drums tracks and delete the original clips. By then it will hardly be worth backing up to cwb!
 
You don't have to .bun, just copy the data files and the CWP.
 
Bulls Hit said:
The thingis though, none of the individual wav files are greater than 2GB. Presumably the same limitation applies to .cwb files.
Click to expand...
I forget the specific technical details, but yes, the same limitation applies to bundle files.

Bulls Hit said:
As far as retaining the original data goes, I don't think GT3 has an 'Apply Trimming' function. I guess all I can do is to bounce the drums tracks and delete the original clips. By then it will hardly be worth backing up to cwb!
Click to expand...
If it allows slip editing, I find it hard to believe it wouldn't include the Apply Trimming function.

FWIW, it is located on the Edit menu in Sonar. Or you can also call it up by Right Clicking on the clip.
 
Just out of curiosity, what file system is your hard drive formatted as. The 2GB thing is a FAT32 (the filesystem windows used by default before winXP).. There is no way to have large files on a FAT32 disk. The best bet would be to chang the filesystem of the disk to NTFS (the new one), or use per project folders instead of bundles.
 
MichaelM said:
Just out of curiosity, what file system is your hard drive formatted as. The 2GB thing is a FAT32 (the filesystem windows used by default before winXP).. There is no way to have large files on a FAT32 disk. The best bet would be to chang the filesystem of the disk to NTFS (the new one), or use per project folders instead of bundles.
Click to expand...
This was already brought up in the 4th post in this thread. And, as already noted to that poster, this issue exists with bundle files regardless of the formatting of the hard drive. It is a limitation inherent in the bundle file itself. Reformatting to NTFS will not resolve it.
 
Then use per project folders and winzip/rar to do your backups.
 
Thanks for all the input guys. It's real helpful.

Yeah I have NTFS on all my drives, and I also use per project folders.

I found that Apply Trimming thing dachay, but it seems to only clean up what's been slip edited. What I've done is split a track at 2 places, then copied and pasted the clip a couple dozen times. It seems to create a new file for each clip rather than refering to the clip in the original track.

I think mixsit has the only solution, copy the audio files and cwp across to the other drive
 
On the paste dialog, there's checkbox on down left corner to select Link to original clip(s)... Maybe it helps... :)

;)
Jaymz
 

Attachments

  • linkclips.webp
    linkclips.webp
    17.7 KB · Views: 41
dachay2tnr said:
I forget the specific technical details, but yes, the same limitation applies to bundle files.
Click to expand...
The techinical details: Bundles rearrange the clip to form a very long wave-file. It also contains information on where in this wave-file the individual clips are located.

If I remember correctly... ;)
 
James Argo said:
On the paste dialog, there's checkbox on down left corner to select Link to original clip(s)... Maybe it helps... :)

;)
Jaymz
Click to expand...

I've never used that Link to Original clips Jaymz. If I understand it right, any mods you make to the original clip are mirrored in the 'linked to' clips, which is not usually what I want.

What I don't understand is why are the original tracks/clips kept, even when I explicitly delete them? They're not linked to the copied clips, and when I've pasted those clips, they each have their own individual wav files so there doesn't appear to be any need to refer to the original track
 
Bulls Hit said:
What I don't understand is why are the original tracks/clips kept, even when I explicitly delete them? They're not linked to the copied clips, and when I've pasted those clips, they each have their own individual wav files so there doesn't appear to be any need to refer to the original track
Click to expand...
Have you tried the Clean Audio Folder command? Might be worth a try.

I found that Apply Trimming thing dachay, but it seems to only clean up what's been slip edited.
Click to expand...
Yeah, that's what it does. I didn't fully understand what it was you were doing.
 
MichaelM said:
Just out of curiosity, what file system is your hard drive formatted as. The 2GB thing is a FAT32 (the filesystem windows used by default before winXP).. There is no way to have large files on a FAT32 disk. The best bet would be to chang the filesystem of the disk to NTFS (the new one), or use per project folders instead of bundles.
Click to expand...

I think FAT32 has a 4GB limit.
 
You must log in or register to reply here.
Back
Top