Norman Black
Forum Replies Created
-
I just tried it and got three and four lines to work in Titles and Text.
Sorry, I forgot to mention you might need to put blank spaces in for the lines. If you change the anchor point to top left this can be avoided in many cases.
It is a bit quirky entering the second and subsequent lines. When I selected the blank space and typed the second line the first character went on the second line but the rest wanted to go to the third unless I moved the cursor back to the second line. I did not play with this to figure what is going on.
I tried protype titler and it was pretty easy there using keyframed opacity to control when each line becomes visible.
As always, Go with what is easiest.
-
The .raw file ML creates is something ML just created. It is not an actual agreed upon file format by anything out there. Hence the need for the ML tool to get workable file(s) out.
Certainly Sony and others could support a ML .raw file, in similar way to the way RED camera raw files are supported. Unlikely unless the ML tweak gains major momentum.
I really see someone developing a pre-processor tool that lets you enter your raw conversion settings and outputs some common intermediate video format for NLEs to edit.
-
AFAIK the only “RAW video” out there is from the RED camera and Sony supports this.
The Magic Lantern stuff is a hack which creates a rather unusual workflow. By this I mean you do not get a video file out of ML.
-
I did something like this with two lines and the Titles and Text tool, having the second line pop in to a musical cue.
In entered my first line with a blank second line.
Click the Animate (keyframe) button for the text and enter the text for the second line. Note the first line is in the second line text. Move the keyframe for that second text element to the proper time.The NewBlue titler can do this pretty easy since it has it’s own internal timeline you can use for positioning and overlapping text items.
I have never use the Protype titler but it seems to have an internal timeline as well.
The internal timeline thing just lets you have multiple independent text things going on in a single Vegas video event.
-
Flash cards transfer at mega bytes per second and video is at mega bits per second.
The flash card is an unlikely limitation. Any limitation would be with the TV, and here you just have to try it.
-
The high bitrate compressed H.264 is too much for the CPU. You need a proxy in something like MPEG-2. You have Vegas 11 so you don’t have the VP12 Smart proxy feature so unfortunately you would have to do this manually.
As a point of reference, my core i7 860 2.9Ghz, can edit GoPro 1080p30 20Mbps files okay, but has issue with 1080p60 30Mbps files. The DSLRs put out more like 40Mbps.
-
You should notice that during a file encode render that the preview window is always at best/good full. Best or good based on your preferences. This will be the case if your are editing at preview or draft quality.
-
Yes, Sony added the 720p and 1080p templates to Sony AVC in B563.
MC AVC defaults to CPU only. You can see this in the options at the bottom of the render as dialog.
For MC AVC.
If you have an ATI/AMD video card 57xx or newer you can try “Use OpenCL if available”.
If you have an NVidia card you can try Use CUDA if available.OpenCL/CUDA will be faster but probably lower quality at low bitrates.
You are the judge of quality, regardless of encoder used. Try them and compare.
-
Two different encoders written by different companies. I believe the MC encoder was first in Vegas. Actually more than just two different encoders as for the MC encoder the OpenCL and CUDA encoders are distinct from the CPU encoder.
I have made no analysis as to which encoder is “better” at low bitrates. The MC CPU encoder has historically fared well here, but x264 still kills both MC and Sony AVC in quality at low bitrate.
The Sony AVC encoder is much faster unless you can use the MC OpenCL or CUDA, then those are faster.
Sony put the internet templates back into the Sony AVC encoder list in build 563. For some reason they took them out on Vegas 12.
-
DNxHD codec comes in a few flavors. DNxHD does not use inter frame compression so it needs much higher bitrates for quality than H.264 for example.
36Mbps which is only intended for proxy files.
145Mbps 4:2:2 8-bit
220Mbps 4:2:2 10-bit
440Mbps 4:4:4 10-bitThe proxy format is not a high enough bitrate for storage, IMO, and the others will generate very, very large files due to the high bitrate. Consider that a commercial Blu-ray’s are typically around twenty something Mbps average bitrate.
Your best file size to quality ratio would be with the AVC format.