722 - corrupt file

[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