Topic: 3.72 Gig wave file???

[tgakidis]

OK, so I ran my PMD-661 for the first time on Friday.  Love it!  Nice size, easy controls and great meters.  I ran it digi in from my Lunatec V3 at 24/96 with AKG 463's and it sounds excellent!

One major problem though.   For some reason it did not start a new file at 2 gigs.  The first file saved at 3.72 GB (3,999,997,462 bytes).  Now I can't open the damn file up in sound forge because it is bigger then 2 gigs.  I used 16 gig PNY class 4 sdhc that I have use with my r-44.  I can't remember if I formatted the card before using it in the 661.  I assume that is probably the reason but wanted to put it out there to the group.

I would love to get some advice on how to proceed with this 3.72 gig file.  I figure I could do a "live" digital transfer from my r-44 to the the 661, but I am hoping there is a easier way.

[Fatah Ruark (aka MIKE B)]

I seem to recall dropping a 3+ Gig file into CD Wave, and chopping it up in 2 parts, then dropped it in Sound Forge.

Sound Forge 10 seems to open 2+ Gig files for me.

[tgakidis]

I seem to recall dropping a 3+ Gig file into CD Wave, and chopping it up in 2 parts, then dropped it in Sound Forge.

Sound Forge 10 seems to open 2+ Gig files for me.

Duh, I haven't used CD Wave in so long that I didn't even think of it!  Thanks!!

[greenone]

Ted, if that doesn't work, you might want to try using shntool's split feature and see if that works...

[Gordon]

cd wave should work.  wavelab 6.0 has no 2 gig limit and will open it.

[twatts (pants are so over-rated...)]

CDWave should work.  I've never used it for a file that big, but I've run files larger than 2gb into it.

Terry

[mterry]

OK, so I ran my PMD-661 for the first time on Friday.  Love it!  Nice size, easy controls and great meters.  I ran it digi in from my Lunatec V3 at 24/96 with AKG 463's and it sounds excellent!

One major problem though.   For some reason it did not start a new file at 2 gigs.  The first file saved at 3.72 GB (3,999,997,462 bytes).  Now I can't open the damn file up in sound forge because it is bigger then 2 gigs.  I used 16 gig PNY class 4 sdhc that I have use with my r-44.  I can't remember if I formatted the card before using it in the 661.  I assume that is probably the reason but wanted to put it out there to the group.

I would love to get some advice on how to proceed with this 3.72 gig file.  I figure I could do a "live" digital transfer from my r-44 to the the 661, but I am hoping there is a easier way.

Let me know.  I have a file that is +3gb that I tried to split into two files last night using CD Wave. It would not save the file splits, after the program ran I was still left with the same file (not two files)

[OFOTD]

Must be using a really old version of SF.  Versions 9 and 10 open large files without problem and I though 8 did as well.

[kcmule]

wavelab 6.0 has no 2 gig limit and will open it.

[Shadow_7]

Audacity should be able to handle / split < 4GB files.

Sox as well.  sox input output trim 00:00:00 (start) HH:MM:SS (end)

ffmpeg could probably trim it up too. -ss HH:MM:SS (start) -t HH:MM:SS (duration) -acodec copy

If the filesystem handles it, I'm not sure why your application wouldn't?  Unless you're running an old version.  We haven't exactly been running Fat16 (2GB limit) since NT4 and Win98(a decade plus ago).  And in Win98 it was optional?  Depending on the version.  Actually I think that Win95C could do Fat32 / 4GB partitions / files.  () comments not part of the commands.

[scb]

If the filesystem handles it, I'm not sure why your application wouldn't?

not all applications use unsigned ints.  signed, the limit is 2gb

[Massive Dynamic]

Ted's probably moved on, but I think the 661 can split files on its own. This would create two smaller files on the SD card that could be loaded into a wav editor and processed separately, if needed. After making a backup copy on your HDD, try the split feature and see what happens  .

[Shadow_7]

If the filesystem handles it, I'm not sure why your application wouldn't?

not all applications use unsigned ints.  signed, the limit is 2gb

Which is a 32 bit limit.  And even signed, it has a 4GB range (+2GB to -2GB).  Unsigned it's 0 to +4GB.  Plus how long have 64 bit computers been out?  Just saying that applications could handle stuff differently and still function within a 32 bit limit. 

But then again sox has a 4GB limit.  At least on my 32 bit laptop.  As does audacity apparently.  When I work on a file greater than 4GB, it just gives that sliver of a file that is past 4GB.  It's like the 4GB of data before that never existed.  I had to completely rewrite my resampling script to process in segments.  Which works out better anyway as it doesn't take so long to load up the file and start editing.  I tend to get too distracted when recording on location to remember to stop and start a new track once an hour.  Especially when I paid good money for a rig that can record 4+ hours continuously.  Fortunately the field recorder auto breaks every 15 minutes-ish / 1GB at 24/192.  So that's fairly simple to group into useful groups.