John Pale
Forum Replies Created
-
I used to be bothered by this, but I then realized that I rarely ever needed to turn off the whole track.
Just disable the specific clip (select clip, then cmd-B). Then you only need re-render the specific area where the clip was, assuming you couldn’t undo your way out of it. -
You would not call an NTSC to PAL conversion an Uprez simply because the frame size is larger, would you?
-
You still can’t rule out the RAID, as there are other factors besides drive speed. But, assuming it is functioning normally..
What Easy Setup are you using while playing your sequence?
-
Compressor does a nice job with basic cross conversion
-
https://www.newegg.com/Product/Product.aspx?Item=N82E16835186017
Worth spending $20 to see if it solves your problem. The green lines just might mean its overheating. It might not be totally shot.
-
Sorry for your troubles. I have worked with XDCAM a great deal, but on pre-AMA systems….
Hopefully they get this bug fixed before I work on an “upgraded” system!
-
Might be worth an e-mail or phone call to the Mocha tech support people
-
[Mike Procyk] “oes the render not also change the audio rate? Could that be the problem?
“No. It does not, unless you tell it to. FCP will try to handle it in realtime, but not always do a good job.
Also, if the audio is compressed in some way and not PCM, this will cause problems even if you render it.
-
Not sure this will work, but …
In Quicktime Player, open the clip then open the Movie Properties (cmd+J)
Select the name of the movie and then click the Presentation tab. Then set Conform Aperture to “Encoded Pixels”. The image will now squeeze to 960 x 720. Save your movie.
Hopefully Mocha will now read it correctly.
-
Sounds like you are set to Direct Out but your system does not have a mixer configured to work with multi-channel audio.
Go to your Audio Tool and set it for stereo…or set up your external mixer to properly monitor more than 2 channels of audio.