Subject:Does anybody know the answer?

Posted by: bsilcox

Date:6/27/2002 2:22:30 PM

I want to import some .WMV files that are approx. 300 mg a piece. before I buy Sound forge I was wondering if anyone knows if SF is capable of such large imports. Please respond if you have tried anything of this magnitude and how it worked for you...

Thanks!!!!

britt

Subject:RE: Does anybody know the answer?

Reply by: Chienworks

Date:6/27/2002 2:39:26 PM

I haven't tried anything quite that large, but i can't imagine any reason it would be a problem. You can download SoundForge and use it for free in demo mode if you want to try it before buying it.

Subject:RE: Does anybody know the answer?

Reply by: dcomo

Date:6/27/2002 8:57:52 PM

I have worked with files this size and bigger using a handful of different formats. I have never really had a problem editing them with Sound Forge (any version) or VV3...

Subject:RE: Does anybody know the answer?

Reply by: Mathew Florianz

Date:6/28/2002 7:07:30 AM

Same here, I compose/create all my albums in SoundForge, no problems.

I also do a lot of live/improvised recordings directly into SF. Some sessions easily run over an hour in length. SoundForge will be recordings all that time.

After recording I edit out bad parts or add to this already large file and I never had any problems doing this.

SF 6.0 supports filesizes up to 4 GB. Larger even on an NTSF formated system.

Though keep in mind, if you edit any compressed format, SF will read the file (WMV in your case) and turn it into a standard uncompressed file. You are not editing directly in the WMV format.

When you are finished and save the file, you can choose to compress it again. You will loose something uncompressing and re-compressing, the file will have been compressed twice so to speak. Depending on the source that can sound quite horrible or you won't notice it at all.

Matthew
http://www.liquidmorphine.com

Subject:RE: Does anybody know the answer?

Reply by: rraud

Date:7/2/2002 6:01:44 PM

I frequenty work with 90 minute mono, 44.1 - 16 bit .wav files with no problems. I don't remember the exact size, but they are big.

Subject:RE: Does anybody know the answer?

Reply by: jport

Date:7/2/2002 9:33:21 PM

I don't think SF will have any problems handling files that size.

Your biggest drawback is if your system doesn't have the "muscle" to handle something that big. Meaning if you don't have enough CPU/Ram.

You'll find that if your system is under powered it will be slow when you start cutting/pasting, playing with filters, and processing your audio.

My 2 Cents is once you get it into SF break it down into sections, especially if it's not a continuos audio track. You'll find that playing with it will be more managable.

Subject:RE: Does anybody know the answer?

Reply by: inspector

Date:7/3/2002 7:56:41 AM

I have mastered a cd with cd-architect and written it to a 650mb .wav and then did the same process again with other music, then pasted them together. I have a 1g processor and 512 of ram. As a side note, I them converted the resulting file (~1GB) into an MP3. I don't think that SF software has a problem with file sizes. A friend was able to open a 53GB video file(13 hours of the SiFi channel)in Vegas and was able to edit the file.

Steve

Subject:RE: Does anybody know the answer?

Reply by: rraud

Date:7/3/2002 12:49:08 PM

This is where 6.0 comes in handy, on large files. In the previous versions, even if you deleted just a few miliseconds at the beginning of the file, it would take "ages" to rebuild the entire file..... the closer to the head, the longer it would take. 6.0 works instantly. This is one of the main reasons I upgraded... depite the lack of CD-arch. and DAO burning. And yes, I'm still pissed off about it!

Subject:RE: Does anybody know the answer?

Reply by: dcomo

Date:7/6/2002 11:15:44 AM

That is the beauty of non-destructive editing. Also, I agree... I did upgrade to v6.0 after spending hours thinking about it. It would have been a no-brainer if the DAO recording stuff was added in as well. Even if they charged $50.00 for a plug-in, I would have paid it...