Sam Lee
1
COW Coin
Forum Replies Created
-
It depends on what your content is about. If it is non-dramatic and unscripted (docs, events, sports) are perfect examples), I always use 29.97P or 60P. 23.976 or 24P are more for scripted or planned shoot where you can control your camera movement and reduce the jitter. It is not a good thing to shoot in 29.97 and down convert it to 23.976 in editing. I had to learn the hard way when my content was submitted to Netflix for qc approval and it was rejected. Keep everything in the same frame rate (don’t mix and match 24, 25, 29.97, 60p) with the exception of 120-240fps+ where you can slow down to your timeline’s.
-
h.264/AVC .mp4
-
My angle editor has 3 angles: A cam, B cam, and sound recorder. In the angle editor, I only chose the sound recorder as the active audio angle. If I do this, then only the sound recorder angle gets carried over to the final project right?
If I have clicked on A angle and sound recorder angles (via the purple speaker icons), will both of these angles get carried over to the final project too?
-
Ah. Looking into Teranix. Somehow these hardware devices are undetectable by qc tools such as Orion and Baton. They use propriety algorithm to do their frame rate and up scaling process.
-
The time it takes you to do this will exceed the storage space cost. 12-14 Gb capacity hdd will be out in a few months. 8 Tb are now within $180 range. I got mine about $150 on last month’s Black Friday for a 8 Tb hdd from Seagate. Unless you’re shooting all in cinema raw with very large file size or high 240 fps, I don’t see any real measurable benefits.
-
Burned in subtitles are primarily for costs reason. Audio dubbing is much more costly to produce than subtitles when it’s done in high quantity.
Come to the subject of subtitles, I don’t see Netflix, Amazon have burned in subtitles. They’re all separate on/off options and provided with a separate subtitles file. By using this, there should not be added encoder noise to the video and will pass qc.
I also tried Sugar FX subtitles for Pr CC 2015. The transcoding took about 5-8x longer than in FCPX. The color banding still exists, but dramatically much smaller. I suspect something is not done right with the SugarFX subtitles plugin in handling this.
-
OK. Thanks. Will check these out soon.
-
I have very high quantity of content and want full flexbility in changes and revisions. Massive amount of hours. If it was only a few, no problem. The costs will get out of control when a small change is needed as well. Prefer to keep in house for full control.
The only other way is a separate subtitles file. That seems to be the preferred method for Netflix, Amazon and many others. This way the video will not be subjected to more unwanted noise.
-
Splendid news! A right step on Pr CC to be able to do this on the Windows platform. I’ll revert back to my AVC-I rewrap workflow. Huge time saver and disk space as well.
-
Here’s the WeTransfer link of the AVC-I 100 rewrapped .mov directly fr FCP 7:
Media Info report, but better to actually test it with the file:
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Commercial name : AVC-Intra 100
Format profile : High 4:2:2 Intra@L4.2
Format settings, CABAC : No
Format settings, GOP : N=1
Codec ID : ai13
Codec ID/Info : Advanced Video Coding
Duration : 24s 391ms
Bit rate mode : Constant
Bit rate : 114 Mbps
Width : 1 920 pixels
Clean aperture width : 1 888 pixels
Height : 1 080 pixels
Clean aperture height : 1 062 pixels
Display aspect ratio : 16:9
Clean aperture display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (29970/1000) fps
Original frame rate : 59.940 (60000/1001) fps
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 10 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 1.829
Stream size : 329 MiB (95%)
Language : English
Encoded date : UTC 2016-03-07 22:59:03
Tagged date : UTC 2016-03-07 22:59:03
Color range : Full
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709