When I bounce a mix to disk, there is embedded data that goes with it,(proprietary PT data) that keeps it from being able to be written or read as a .wav file in some other applications. For instance, I can't open the wav in media player. I can't burn an audio CD either. I can open the file in Soundforge and resave it without this data, and that has been my workaround thus far, however inelegant. Can this data be excluded from the mixdown? How would I do this?
I can deal with going through another editor (to a point) I just hate and I mean HATE real time bouncing. It is a waste of time. There should be a quicker process like other apps have. citi
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:<HR>Originally posted by Shannon Dunn: Yes they do mistake us. In fact I've even gotten emails intended for her. I'm a guy though. And I can't snowboard for **** .<HR></BLOCKQUOTE>
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:<HR>Originally posted by Shannon Dunn: When I bounce a mix to disk, there is embedded data that goes with it,(proprietary PT data) that keeps it from being able to be written or read as a .wav file in some other applications. For instance, I can't open the wav in media player.<HR></BLOCKQUOTE> You will find this is ONLY with 24-bit .WAV files. I don't get what everyone is going on about proprietary data. Any decent audio application will disregard any unknown data in the wave header. Media player simply doesn't support 24-bit files. I have never had a problem opening 16-bit waves from PT in any application. Cheers, Marcus