-
Compressor 3.5 Problems with m2t
Okay, here’s the deal….
I’m really hoping I don’t have to do reinstalls, but it looks like that is the direction I am headed.I have 4 edit stations, all clean installs of Snow Leopard and FCP Studio Pro 3.
2 stations are 2×2.6 GHz Quad Core Intel Xeon Nahalem
2 are 2.66 Ghz Dual Core Intel Xeon
We also are working off of an EditShare SAN.So the problem is, on all 4 machines, every time I try to make an m2t from a fat movie (usually Apple Pro Res), Compressor locks up and says it will take 500+ hours on it’s second pass. It doesn’t crash, just gets stuck. I have left compressions going on Friday, and they are still going on Monday morning! Also, not been able to cancel or stop these. Basically I have to use Digital Rebellion compressor fix and restart computer.
The same files will compress fine into other formats, and I can make m2ts from them on a different computer with Leopard and old version of Compressor.
I have tried with and without using Q master clusters, but I’ll admit I don’t know all the in and outs of it, so maybe I’m doing that part wrong.
Any ideas????
-
3 Replies
-
what preset or settings are you using to get an m2t?
are these for Blu-Ray or HD broadcast?
There is nothing wrong with Single pass VBR encoding
unless your trying to cram a load of content onto a certain size of media. -
I am making my own setting, but it is the same setting I always use (old system/new system)
setting is based off of Transport Stream preset, but is set to always be between 12-15 Mbps.
HD (either 1080 or 720 depending on source material). frame rate same as source material. 2 pass VBRI have been doing this exact compression spec for 2 years, never had this problem before system upgrade.
-
The 2-pass VBR could be an issue.
try a single pass and see if that works.
Reply to this Discussion! Login or Sign Up