Oki Pienandoro
Forum Replies Created
-
On many cases the mistake from new mocha user is :
1. The Mocha Project and AE Comp is not EXACTLY the same (you need to check everything is the same; comp size, fps, fields/progressive, PAR)
2. You didn’t pasted on the very first frame in AE.
3. The replacement screen should be the exact frame size with AE Comp.Btw, on most cases using Mathias Möhl’s MochaImport script is tremendously help pasted the data correctly.
https://aescripts.com/mochaimport/
——————————————
Sorry for the english, not native speaker. -
——————————————
Sorry for the english, not native speaker.Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Your first mistake is to export the intermediate files from FCP into h.264.
h.264 is a lossy compression.
Instead, you should directly export to MPEG2, this way you can avoid one lossy chain.
I rarely use fcp/compressor, so maybe someone who use compressor daily can chip in.Jagged /pixelated result is called macro blocks.
This is the way MPEG2 to compress, they group the pixel into “blocks”.Most of the times this occur because you use a very low bitrate.
On most cases you can get good result with minimum bitrate at 2 Mbps, Average at 5 Mbps, Max at 9 Mbps. Use 2 pass.
If there’s motion estimate option in compressor, set that relatively high (at the expense of longer encoding time, but the file size is not affected). Motion estimate IS the heart of mpeg encoding.Your total runtime is about 56 min. This is actually very low runtime and can fit DVD perfectly with a very good result.
edit :
If you use Adobe Media Encoder, there’s option “Use Maximum Render Quality“. What this actually do is resize the HD source into SD using higher samples/method, the result is crisper image.Sorry if that doesn’t help you much. I work almost exclusively with Premiere, Encore and Adobe Media Encoder. I very rarely use FCP and compressor unless the client demands it.
——————————————
Sorry for the english, not native speaker. -
Oh, i see.
Hmm the only thing i can think of is using fake menu. yeah it was not a real solution, but if the client insist, this can be a workaround.——————————————
Sorry for the english, not native speaker. -
You mean like director commentary ?
https://help.adobe.com/en_US/encore/cs/using/WSbaf9cd7d26a2eabfe807401038582db29-7eb4a.html#WS9DE8493A-465A-4463-99E6-3769A379A10Aa——————————————
Sorry for the english, not native speaker. -
Just push the bitrate to 9 MB.
All DVD player spec at the very minimum should/can sustained 9,8 Mbps.Excerpt from https://www.mpeg.org/MPEG/DVD/Book_B/Video.html
Contrary to popular belief: all DVD players are required to decode video streams up to 9.8 Mbit/sec for indefinite periods of time. The popular average rate of 3.5 Mbit/sec or 4.7 Mbit/sec are merely canonical figures created by the notion that only single sided, single layer discs will hold feature length films. Should Single Sided, Double Layer discs prevail, the average rate would be almost twice as great. ALL DVD PLAYERS MUST SUSTAIN A 9.8 MBIT/SEC VIDEO DECODE RATE
It’s not worth it to increased the bitrate if the result is good.
My rule of thumb were, if there are no noticeable macro block artifact, then it’s good enough.
There are very-very little improvement if you increase the bitrate.Instead of wasting DVD-DL for the sake of testing, you can directly compare the result with the export files using AE/Premiere.
If you feel fancy enough, you can compare the result automatically using MSU Video Measurement Tools. It will give you nice graph.
(you need to know how to use basic AVISynth)https://www.compression.ru/video/quality_measure/vqmt_download_en.html#free
Oh,.one more thing i forgot to mention earlier. The downside using DVD-DL is when the head is changing the layer during playback, there will be some kind of hiccup. Most of the times the playback will freeze a bit when changing layer.
This can be avoided if the layer break information is really good (DON’T use layer break information generated by Adobe Encore).
Just google how to use PGC Edit.IMO burning to DVD-DL is the last thing i wanna do unless there are no other option left.
On my case, i put some text disclaimer at the start of video for viewers, “This DVD is DVD-DL, there will be pause during playback due changing layer, bla-bla-bla”
——————————————
Sorry for the english, not native speaker. -
Yes that was normal. Also rendering in GPU renderer speed things a bit.
Yes, the ‘average’ means ‘target’ bitrate. Maybe i was wrong about this, but in many other application, the component were ‘min, max, and average’. So i assume Adobe changed the naming scheme from average to target ? Idk. CMIIW.If the whole sequence is mostly flat scene (little camera movement, no noise, etc that affect compression efficiency) then yeah,..you can fit 120 minutes into single layer DVD.
In my case i deal with many camera movements, scene changes, multiple stream subtitles and animated menu, this will produce a bigger file size.
Setting 4 Mbps on target introduce macroblock in my case.
In the end, your result may vary and really depends on your case.
Just put the default target, see if there’s macroblocks especially in camera movement scene. If the result were good and under 4,7 GB, you’re good to go.
If it produce macroblocks, you need to increase the bitrate. But for 120 Min files it may produce file bigger than 4.7 GB if you increased the bitrate, see my above reply.
——————————————
Sorry for the english, not native speaker. -
You can save to previous version of CC. Just go to save as | save a copy as CC(12).
Are you on Mac ? There are some issue with CC 2014 on Mavericks from what i’ve read on forum. But not performance like you mentioned though (i assume the issue you were talking about is rendering times ?)——————————————
Sorry for the english, not native speaker. -
Using this script helps a lot to automatic detecting beat:
https://aescripts.com/beat-assistant/——————————————
Sorry for the english, not native speaker. -
Hope this helps:
https://lifehacker.com/5598716/what-are-the-rules-on-mixing-two-different-types-of-ram——————————————
Sorry for the english, not native speaker.