Comments

Chienworks wrote on 12/8/2003, 5:25 AM
If you want to go to other software you should probably save them as standard .wav files instead of .w64 files. Yes, the other SONY media software will read .w64, but software from other companies won't.

Other than that, i'm not sure what you are asking. If you have the song on Vegas' timeline then render it to a .wav file. If you need to have individual sections stored in individual files, highlight each section separately and render toa file selecting "Render loop region only", then select the next section and render ... repeat until all the sections are saved.
drbam wrote on 12/8/2003, 6:28 AM
This is indeed a problem. The audio world (sans Protools) recognizes the wav file as standard. Is there a way to set Vegas to default to wav when rendering and/or trimming? I realize the purpose for wav 64 but its unnecessary for most audio only projects,and IMO, not defaulting to standard wav only serves to further distance Vegas from the mainstream audio software market.

drbam
Former user wrote on 12/8/2003, 6:43 AM
I agree with drbam....This is a very large problem. And the single reason that I had to move from Vegas to Nuendo. After the 4.0 upgrade, I found that all the bits and pieces of all my projects were quietly converted to Wave64. I do not believe I was asked by the software if this was okay and before I knew it...it was too late (or too much hassle) to revert back.

In the end, when sending materials to other studios...I was SOL due to the formatting issues.

Cuzin B
SHTUNOT wrote on 12/8/2003, 10:16 AM
Cuzin B....

Hey dude I hope you put in a suggestion in the "tell us what you need" thread so that this problem of yours can be fixed in version 5. If you haven't done so ofcourse through other channels.

Ed.
Former user wrote on 12/8/2003, 4:52 PM
Shtunot,

This used to work fine as far as I remember in V3. I had a ton of projects with normal .wav files that were not effected.

Since I am long since done with Vegas...no real point in sending something into the developers but I appreciate the suggestion. However - I would have thought something like this would be real obvious to SF to get their apps to fit in workflow circles with other apps/studios.

Cuzin B
Chienworks wrote on 12/8/2003, 5:25 PM
Hmmm. I guess i'm a little lost here. As far as i know, Vegas only forces the use of .w64 when using the "trim and save all media with project" function. I would consider this to be something one does when a project is finished, rather than done when preparing to move files to other software. Other than that, Vegas never converts files; it uses them in whatever format it finds them. If you are rendering out sections of the project to be editing in other software then it's just as easy to choose Microsoft WAV as it is to use SONY .W64.

Or am i just not understanding your workflow? I do agree that standard WAV should be an option with the trim & save feature though.
drbam wrote on 12/8/2003, 5:35 PM
Yes, I'm primarily referring to the "trim and save" function. This is where I assemble projects to be sent to other parties and I've had to re-do this because I forgot about the 64 default. If I'm sending to another Vegas user its no problem, but as we all have agreed in this thread, its a general problem and should be changed or at least allow for users to select a default format of their choosing.

drbam
MJhig wrote on 12/8/2003, 5:42 PM
Ahh, this was one of my requests in the "What does Vegas need" thread but for a different reason. When I archive to CD or DVD I'd like to do so in *.pca format to save space but alas there is no choice.

MJ
Geoff_Wood wrote on 12/8/2003, 8:05 PM
Is there not an option to set wav as default filetype ?

geoff
Chienworks wrote on 12/8/2003, 8:08 PM
Geoff, in the "trim and save media with project" function? No. Any project audio that is avi or wav will be saved as W64. No other options are allowed.
drbam wrote on 12/9/2003, 6:06 AM
>>Any project audio that is avi or wav will be saved as W64. No other options are allowed. <<

Until this thread I actually hadn't realized what a critical problem this could be! This single issue could easily cause/force users to choose another app. Unless I'm missing something crucial, this seems incredibly shortsided on SoFo/Sony's part.

drbam
Former user wrote on 12/9/2003, 11:39 AM
It caused me to reconsider pretty fast. I still remember the day when I tried to send a project that I thought was .wav as .w64. Quite a reaction from the folks on the other end of that CDROM....

Cuzin B
frogman06 wrote on 12/9/2003, 11:53 AM
im screwed !!!!!!!
Chienworks wrote on 12/9/2003, 2:29 PM
Frogman06, how many files do you have? If it's not too many, you can load each one onto the timeline and then Render As to standard Microsoft .wav format. The files will still be identical in every respect (assuming you choose the same sample rate, bit depth, number of channels, etc.) so you won't lose any quality at all. Vegas is capable of outputting standard .wav files that any other application can open and use.
Caruso wrote on 12/10/2003, 1:49 AM
Chienworks:

I"m reading this thread wondering to myself why such doom and gloom over this issue ("I'm screwed) ("I've already moved on") ("Until this thread I actually hadn't realized what a critical problem this could be!") and such.

I'm guessing that most of the files in question are 100% audio, no video involved. That being the case, how much more time would it take to load/re-render as .wav audio files that have been "trimmed and saved"? Not that long.

I agree there should be an option, and it's probably something that could be implemented by Sony without too much fuss - but this shortcoming certainly isn't a fatal flaw - the work around (even with audio/video files) is fairly simple - such is the flexibility of Vegas.

Caruso
drbam wrote on 12/10/2003, 6:40 AM
I agree its not a "fatal flaw" but it does highlight some of the oversight issues that seem to plague Vegas and keep it from competing fully in the market. I have a studio owner friend who is just now getting into a full DAW system. I REALLY encouraged him to go with Vegas, which he tried, along with demos of most of the other available PC apps. I found out last night that he ended up choosing a ProTools system for all the reasons many people do. His comment to me was "Yeah Vegas is great but . . ." (and most of us here can fill in the blank.)

Rendering session tracks twice may not take "that long" but while I'm doing it, I'm feeling annoyed and certainly it wouldn't be ethical to pass along the extra time charges to a client.

drbam
Chienworks wrote on 12/10/2003, 7:28 AM
There is always the situation that if your editing involved large numbers of cuts, then each of these pieces would become a separate .w64 file (1 file per audio event on the timeline). In some editing situations i could see this becoming hundreds or thousands of files. It certainly wouldn't be practical to rerender every one of these to a .wav file. (Maybe Batch Converter would be useful here.)

On the other hand, if this is the scenario you're ending up with, then the person you're sending the files to probably doesn't want to deal with that many little pieces anyway. You would probably be better off rendering whole sections to new files rather than using the "trim & save" function.

For that matter, a CD-R can hold 24 minutes of 96KHz 24bit stereo audio or 79 minutes of 44.1KHz 16bit stereo, and a DVD-R can hold 162 minutes of 96/24/stereo or 530 minutes of 44.1/16/stereo. I would think that in most cases it's probably feasable to send the entire project with original files as is without using the "trim & save" function at all.