Subject:SF10 Media Cache & Multichannel wav files
Posted by: kgould
Date:11/12/2009 10:23:54 AM
I was looking for some documentation on using and setting up the "Global media Cache". I am particularly interested in how it would help improve recording multichannel recordings (~8 channels) for long periods of time (1-2 hours) for live concert recording applications. Second question I have is there a procedure for taking a multichannel wav or W64 file and converting it into separate 2 channel stereo wav files? Thanks |
Subject:RE: SF10 Media Cache & Multichannel wav files
Reply by: rraud
Date:11/12/2009 1:48:36 PM
If I understand your needs correctly, you would want 'multi-track' software like Vegas, Acid, PTs, Sonar, ect., ect., ect. SF is an editing/mastering app. which supports multiple channels and "poly' files. It was not designed for multi-track type work. |
Subject:RE: SF10 Media Cache & Multichannel wav files
Reply by: ForumAdmin
Date:11/13/2009 9:07:55 AM
The Global Media Cache feature is intended to speed up processing of existing files by alleviating some of the disk access required. It will have little to no impact on current recording behavior. You can select contiguous channels via normal drag selection behavior. You can also select channels via the left ruler area of the data window, which supports standard click, shift+click, and ctrl+click behavior. Example: 1) Double-click inside or to the left of channel 1 2) Ctrl+click inside or to the left of channel 2 3) drag to a blank area in the workspace or Ctrl+C, Ctrl+E to copy and paste to a new window In event editing mode, you can drag the top and/or bottom of the event to change the number of channels visible. Process->Channel Converter provides another more destructive method. J. Message last edited on11/13/2009 9:08:34 AM byForumAdmin. |
Subject:RE: SF10 Media Cache & Multichannel wav files
Reply by: MPM
Date:11/14/2009 1:15:20 PM
>"...improve recording multichannel recordings (~8 channels) for long periods >of time (1-2 hours) for live concert recording applications. >Second question I have is there a procedure for taking a multichannel wav or >W64 file and converting it into separate 2 channel stereo wav files?" You probably want to stay away from multi-channel wav -- you're approaching the max file size with 2 hr in stereo, & 8 channels would be roughly 4 times bigger. FWIW if you're after downmixing for an additional track on a DVD or something, Vegas will take 5.1 wav & spit our stereo pretty well, but you still have the size of a multi-channel wav to deal with. |
Subject:RE: SF10 Media Cache & Multichannel wav files
Reply by: musicvid10
Date:11/14/2009 4:59:44 PM
Multichannel WAV64 works just fine for me, 5-6 channels, 2-3 hours, no problems. |
Subject:RE: SF10 Media Cache & Multichannel wav files
Reply by: MPM
Date:11/17/2009 1:05:35 PM
>"Multichannel WAV64 works just fine for me, 5-6 channels, 2-3 hours, no >problems." FWIW, I've had good luck with it too, though it's not as portable as wav. Why MS never updated the file type like they did with avi is beyond me... they even came up with tools to use avi &/or wmv as audio-only containers to get around the prob. :-( |
Subject:RE: SF10 Media Cache & Multichannel wav files
Reply by: pwppch
Date:11/17/2009 7:11:58 PM
though it's not as portable as wav. What problems in portability have you experianced? We have been contacted and provided documentation to many third party vendors that are now supporting Wave64. Peter |
Subject:RE: SF10 Media Cache & Multichannel wav files
Reply by: MPM
Date:11/18/2009 7:54:56 AM
>"What problems in portability have you experianced?" No prob. really -- I work mostly with video using a lot of apps (including a few oddballs that aren't/haven't been maintained for ages) so I just stick with mono files when/if multi-channel, & stereo placeholders as necessary. You are right, Peter, that I should probably work (at least much more often) in Wave64 & stop being lazy. ;-) Things would've been so much simpler IMHO if as mentioned MS just updated their complete wav spec so you folks didn't have to. :-) |