Topic: 722 - corrupt file

[halteh]

I taped my first show last night with the 722, just my luck though i seem to be having a problem opening the file in cool edit pro and soundforge. the show is split over 3 files, 2 very small ones (which are fine) and 1 large 4 GB file. I set the 722 to break files in 4 GB chunks (this a bad idea?) and taped at 24/192. Anyone have any idea why i am having this problem? I am sure the problem is not with transfering the file from the firewire, because i tried opening it straight from 722 with it connected to the firewire and i still get the problem. In cool edit pro the file opens as 22 minutes (even though it's 57). When i listen to the file on the SD it plays all the way through (flawlessly) just as long as i don't forward or rewind - in which case the machine sorta just pauses. Same goes with playing the wav in winamp. If i try to forward or rewind i get terrible static noises in winamp. Anyone have any idea what it is i can do? I am guessing an alternate option would be to use the digital out and go straight to my soundcard. Also, more importantly, anyone know why this happened? It's the first time i use the device and i formated right before the show. Also, if it means anything, the battery died on me as i was transfering the show. I just deleted all the currently transfered files, retarted the 722 on AC power and started over again.

Any help is much appreciated.
ps. anyone know the address to the sound devices 722/744 board?

Thanks again

[nickgregory]

we had similar problems, and the reason was the file size...once we set the break to 2 Gb, we have had no problems.  Seems Wavelab choked on anything bigger

[halteh]

we had similar problems, and the reason was the file size...once we set the break to 2 Gb, we have had no problems.  Seems Wavelab choked on anything bigger

Thanks so much for reply were you ever able to recover your files that were corrupted?

--fares

[nickgregory]

we had similar problems, and the reason was the file size...once we set the break to 2 Gb, we have had no problems.  Seems Wavelab choked on anything bigger

Thanks so much for reply were you ever able to recover your files that were corrupted?

--fares

cd wav was able to open them, at which point they were chopped up (becoming much smaller files), then wavelab was able to deal with them...hope that helps.

[Joe w.]

http://www.sounddevicessupport.com/

fwiw, I have it set to split at 1gb. Just makes the files much easier to work with in post.

[tmfraley2]

joe I was unable to get the entire file back at 24/96, was saying parts of the file were 24/48, as nick said once you go at 2 gb or less you are fine

[fsulloway]

We had the same problem Fri night in Chi. The battery also died about 3 min before the set. When i tried to send that file to my laptop it said the file was corrupt. However I can't seem to find that file now on the 722. I tried transferring files from last 24 hrs, 48 hours and finally all files. I couldn't have deleted from the 722 though right?

[mhibbs]

I set the 722 to break files in 4 GB chunks (this a bad idea?) and taped at 24/192.

Yes.  Bad idea.  The .wav standard is defined as 2gb.  As a result, Wavelab (in particular) will not work w/ files bigger than 2gb. 

[Brian]

can you record on the 722 as two mono tracks or is it always an interleaved stereo file?

[trajhip2000]

I run my 744T at 24/96 recording 4 mono channels on a regular basis.

Steve

[Brian]

cool.  i htought i read that 722 did as well on another forum but i just wanted to be sure, hence why i asked some of you guys here.

i don't mind recording two mono files and interleaving them later if it's going to help save me some from some of these issues.  As a matter of fact having two mono files is easier for me to work with in post and create a better product.  that's just me though.

[dmonterisi]

  As a matter of fact having two mono files is easier for me to work with in post and create a better product.  that's just me though.

why is that?

[Brian]

easier to fix level issues, individual EQ'ing and processing.  can import into other programs with ease and compatibility. irealize you can do this all with a stereo inter-leaved file.

it's total personal preferance.  one of my teachers went on a rant some day abuot how it takes up less processing but i can't really recall why or if he is even right.

[dmonterisi]

gotcha...the only thing that i ran into when working with dual mono files is that if the combined dual mono files will be greater than 2 gigs, you have to split the individual files at the exact same spot.  if you know what you're doing (i recognize a big assumption with most of us  ), it's not a problem, but you gotta be careful.

[Brian]

not too mention the whole 2gb limit issue workaround as well.

what programs were you experiencing this with? the greater than 2gb thing?  most of the files i work with are broadcast wave files with the smpte time code burned into the data track.  lining up break points is never an issue.

i'm not quite understanding what you are talking about.

[dmonterisi]

not too mention the whole 2gb limit issue workaround as well.

what programs were you experiencing this with? the greater than 2gb thing?  most of the files i work with are broadcast wave files with the smpte time code burned into the data track.  lining up break points is never an issue.

i'm not quite understanding what you are talking about.

what workaround do you mean?

i'm referring to wavelab.  i had split some 24/96 files into mono tracks.  so when i went to combine them, wavelab wouldn't allow me to do it because each mono file for the second set was (for example) 1.25 gigs.  so i opened the left channel in wavelab.  split it using the auto-split on markers function.  then copied the marker file and renamed it to match the right channel so that when wavelab opened the right channel it imported the marker in the same place and then ran the auto split function.  I then rejoined the dual mono files together so that i had 2 stereo files for the second set.  does that make sense?

i'd be curious if you had another way of doing it.

[Brian]

that's weird, i'd assume wavelab would let you import each 1.25 gb file and be fine.  that's how every other program i know of works.  that's the workaround i was talking about.  a stereo interleaved file will be larger than one of the mono files thus allowing you to work on these files in the mastering/mixing program of your choice.

in your case something might have been screwy because it was originally a stereo interleaved file.  not sure how to troubleshoot that one.  but i've heard of plenty of mastering engineers split up the stereo masters they get to work on them as mono files.  not sure where/how/when your problem arose.

[dmonterisi]

huh...i wish i remembered when i got the error, whether at opening of the dual mono, trying to process or saving or something else.  the way i did it ended up working out fine, but it was a bit more involved that i guess it needed to be.

[nickgregory]

wavelab wont let you save a file that is bigger than 2Gb

[Brian]

wavelab wont let you save a file that is bigger than 2Gb

exactly.....which is why one could work with two mono files and just save each channel individually(which wavelab lets you do).

that's all i was trying to say

[nickgregory]

wavelab wont let you save a file that is bigger than 2Gb

exactly.....which is why one could work with two mono files and just save each channel individually(which wavelab lets you do).

that's all i was trying to say

understand now...

[Brian]

cool.  you actually made me double check to see if I said anything dumb

just out of curiosity, have you tried recording two mono files to the 722 yet?

[nickgregory]

cool.  you actually made me double check to see if I said anything dumb

just out of curiosity, have you tried recording two mono files to the 722 yet?

nope, just run stereo tracks so far....

[Brian]

if you, or any of you 722 guys would be willing to do so next show and report back your experience from recording to mastering,  i would greatly appreciate it!

or if somebody has and I missed that thread, a link to said thread would also be greatly appreciated.

thanks!

[nickgregory]

if you, or any of you 722 guys would be willing to do so next show and report back your experience from recording to mastering,  i would greatly appreciate it!

or if somebody has and I missed that thread, a link to said thread would also be greatly appreciated.

thanks!

I would be happy to...I may try it for one of the crowes opening acts this week...dont want to temp fate by trying it with the black crowes shows...

[Brian]

totally understandable.  Thanks a lot for trying it out!  + in 12

[scb]

you should be able to get the original 4 gig file open in an app that can read unsigned wav files.  most apps treat wav files as signed ints, and have a 2gb limit.  but treating it as unsigned, it's 4gb