Topic: 24-bit workstation questions.......

[F.O.Bean]

so, you guys that use wavelab 5.01b or any wavelab other than wavelab 6 that has the 4GB limit, how do you process the files if it cant write over 2GB do you dither/resample the 2GB chunks and THEN rejoin in wavelab or am i missing something here? I thought samples would be dropped and things wouldnt match up properly if you resampled/dithered AND THEN re-joined maybe im wrong on that end i hope so

oh and i dont care to use any other programs, i have wl 5.0/samplitude 6.0/soundforge 7.0 and i prefer wl 5.01b and i also wanna use the UV22HR dither scheme in it so....

do you just name moe2006-06-09_2496_1a and then moe2006-06-09_2496_1b for the 2 files that consist of the first set same goes for second?

just curious

Thanks,
Bean

[china_rider]

Yea... just split them somewhere logically (track break, etc) with cdwav and then process.  Sometimes when at a show and I know the file size is getting close to the 2gig limit and there is a good break point i'll have the recorder start a new file to save me from splitting when I get home.  I typically track first in cdwav, save the cue file, process everything in 24bit, split the 24bit, dither, than use the cue to resplit the 16bit.

Also... you may want to look at the Ozone MBIT+ dither plugin for wavlab.  To my ears it sounds better than UV22HR.  Then UV22HR comes in second over the others I have tried.

[F.O.Bean]

Yea... just split them somewhere logically (track break, etc) with cdwav and then process.  Sometimes when at a show and I know the file size is getting close to the 2gig limit and there is a good break point i'll have the recorder start a new file to save me from splitting when I get home.  I typically track first in cdwav, save the cue file, process everything in 24bit, split the 24bit, dither, than use the cue to resplit the 16bit.

Also... you may want to look at the Ozone MBIT+ dither plugin for wavlab.  To my ears it sounds better than UV22HR.  Then UV22HR comes in second over the others I have tried.

do you track first so that when you go to join back together, if there are any missing samples you cant tell

the 722 automatically splices them in 2GB files, so i think for now im gonna do the moe2006-06-09_2496_1a and
moe2006-06-09_2496_1b and so on, burn as data WAVS, flac them and burn as data FLACS, then dither/resemple those files and cut into chunks in cdwave last

is there anything wrong w/ that way?

[Crumbo]

edit:  the 722 does seamless splits at 2gb  (I've got mine set at 2gb and it actually splits at 1.85gb :dunno)


this is how I do it

open the first file (2gb) in Wavelab 5.01 and normalize if needed....save that file 2006-06-10xxx.akg483-1n.....do the same for the next set of files....-2n....-3n

open the -1n file in cdwav, track, save cue file, save files as alternate 24 bit format.....repeat for the other files

open first and last track of the whole show and add fades and save

open split tracks (tracks that are split due to 2gb split) and go to edit>insert audio file at end and then save those joined tracks

then I use the batch process to resample and dither all the tracks at once

[china_rider]

The R-4 autosplits too.... Sometimes it's just easier at a show to press a button at a break in the set to start a new file then do it in software at post.  So I never go and join files back together unless I slip up and let the recorder autosplit at a bad point.

I copy the 24bit source to my PC and then make a copy of the files for editing.  Then I split the 24bit into logical portions.  If there was a autosplit in a part that needs joining then I join here.  Then I process the parts (other than dither.)  Once I am happy with them I split with cdwav and save the cue file... So my 24bit master backup will be something like...

bandYYYY-MM-DD-S1T1
bandYYYY-MM-DD-S1T2 ..
bandYYYY-MM-DD-S2T1
bandYYYY-MM-DD-S2T2 ..
bandYYYY-MM-DD-E1T1
bandYYYY-MM-DD-E1T2 ..

(Note: when I archive I don't usually backup the files directly from the recorder, once I am happy with my post work I save the master like mentioned above.  I rarely do any post other than normalize/dither/resample.)

Then I dither the files (the big parts, not the tracks) and then split again with the saved cue to get the 16 bit version.  Here I just name to etree standards.

That may not be the best way but after doing it a few times it works for me and has become second nature.

[Brian Skalinder]

open the first file (2gb) in Wavelab 5.01 and normalize if needed....save that file 2006-06-10xxx.akg483-1n.....do the same for the next set of files....-2n....-3n

One word of caution regarding this method:  if normalizing, make sure to normalize based on the highest peak of all the files in the set, and not based on the peak within each individual file.  If the latter, one may have different gain changes from file to file.

[THE NIZ BIAAAAACH!]

Here is how you do it open the 1st file in wav lab
go to edit pull down
 insert audio file
insert at end of file
pick the 2nd file

You can do this with all of the files from the first set up to and over the 2gig limit
you can not process this file as is on the desk top
you must break it into smaller pieces at a song break or two, make sure to leave some extra room (do not break right at 2gig because you will still run into processing problems)
After you break it into smaller pieces save these as your new files and work on them as a whole file.
Do not split into individual tracks and then process as this will cause droped samples
This method may lose a sample or two but it will be during a song break and I don't know any one who loves to listen to 24bit crowd noise.

[RebelRebel]

use the 2g split on the 722, bean....Actually, Samplitude WILL dither/resample/effects etc over 2g because it uses a different mixing engine than WL. The POW-R 3 dither is fantastic too, I like it much better than Apogee. Triangular Spread dither is slick too..

so, you guys that use wavelab 5.01b or any wavelab other than wavelab 6 that has the 4GB limit, how do you process the files if it cant write over 2GB do you dither/resample the 2GB chunks and THEN rejoin in wavelab or am i missing something here? I thought samples would be dropped and things wouldnt match up properly if you resampled/dithered AND THEN re-joined maybe im wrong on that end i hope so

oh and i dont care to use any other programs, i have wl 5.0/samplitude 6.0/soundforge 7.0 and i prefer wl 5.01b and i also wanna use the UV22HR dither scheme in it so....

do you just name moe2006-06-09_2496_1a and then moe2006-06-09_2496_1b for the 2 files that consist of the first set same goes for second?

just curious

Thanks,
Bean

[Crumbo]

open the first file (2gb) in Wavelab 5.01 and normalize if needed....save that file 2006-06-10xxx.akg483-1n.....do the same for the next set of files....-2n....-3n

One word of caution regarding this method:  if normalizing, make sure to normalize based on the highest peak of all the files in the set, and not based on the peak within each individual file.  If the latter, one may have different gain changes from file to file.

true, I forgot to write a step I do and that's check all 3 files and then normalize all the same

thanks 

[F.O.Bean]

quick wavelab question, after i track my 24-bit sets in wavelab, and go to resample/dither at the same time in the master sectiona nd render, it doesnt change the bit/sample rates in the first track in the output of btach processing, i have the end bit-depth to 16 and sample rate to 44.1k im lost it didnt change the first track of the show on my first attempt, so i changed the header info and it worked, now the second show i went to process, none of the tracks changed at all

[F.O.Bean]

my stepo by step is

1. track in cdwave
2. open first track in wavelab
3. once first track is open, go to master plugin and fix the sample/bit rates and hit render
4. batch process the files in place
5.

[F.O.Bean]

do i have to create new track names how do i batch process and change track names at the same time

[F.O.Bean]

hmmm, it would help if i saved in the right folder, nevermind

[THE NIZ BIAAAAACH!]

Do not resample  one track at a time this will f up everthing, you will have tones of sector boundry errors, and droped samples. Also you must out put to a separate file, IE. create new file, don't select dither in place.

[dmonterisi]

my stepo by step is

1. track in cdwave
2. open first track in wavelab
3. once first track is open, go to master plugin and fix the sample/bit rates and hit render
4. batch process the files in place
5.

bean, be careful in batch processing individual 24/96 tracks down to 16/44, you're gonna get errors at the track breaks (and not just SBE's)...see this thread for the tests i did:

http://taperssection.com/index.php?topic=49027.0