Norman Black
Forum Replies Created
-
[Neil Randall] “all my FX render fine, apart from any variation of grain from Film Effects, Add Noise, or Film Grain. “
Maybe you can show us a screen shot of your noise/grain. This is the most difficult thing to encode and requires the most bitrate. I notice your encode settings are extremely tight, almost constant bitrate. You might try raising the max bitate to 40.
The reason I asked about seeing a screen shot is that I once added noise as an effect. Heavy noise that then faded out in a few seconds. I rendered that uncompressed and then used Handbrake to encode at constant quality (crf 22). My media PC could not play that bit smoothly and I looked at the bitrate in BitrateViewer and saw the bitrate of that section rocket up to 110Mbps from an average of about 20Mbps. Of course when I render for internet it does not look even remotely like the editor, but such is life at lower bitrates.
Your bitrate seems good for high quality encodes, but the level of noise may be too much to properly encode. If your noise/grain section is short like I had, then you can raise your max bitrate to help that noise section. If the noise is over long sections then you will have to raise the bitrate or abandon the visual effect. AVC might do better than mpeg-2.
-
With Quicktime installed they can read most any Quicktime MOV file.
Vegas special cases DSLR MOV files and decodes directly via internal decoders. I cannot say about Movie Studio 11. 12 is the version I started with. Anyway with QT installed you should be okay.
If you are going to buy an expensive DSLR then why not purchase Movie Studio 13. The current version. $40US at Amazon. $109US for the suite.
-
Done
EDIT: …but I doubt this will ever happen.
SCS does not write the decoders in Vegas. They come from Mainconcept. HDCAM SR excluded. RED RAW comes from RED. MC does not support Cinema DNG.Supporting RAW, even a portable format like DNG, one needs to develop a sophisticated demosaic code.
Editing RAW directly is always going to be problematic with performance. Of course Vegas can always smart proxy.
-
Vegas special cases Quicktime files which have AVC video and PCM audio. AKA stuff from DSLRs and digicams.
It uses its own internal decoders. You can verify this by right clicking a file in the project media pane and look at the general tab. If the qt7plug plug-in is used the Quicktime is decoding. If compoundplug is used the Vegas is handling directly.
Renaming a file from MOV to MP4 does not do anything. Vegas really identifies the file type from its internal file header. Even though MP4 and MOV are nearly identical file containers, their signature does uniquely identify them.
-
You need to be a lot more specific in your description.
Vegas has its own GPU preference under the preferences menu, video tab. Here you select the video device you want the Vegas video engine to use. The Video engine is what assembles/composites your video from your various sources, and effects into a single video stream. This of course is always used. Playback and file encoding.
Mainconcept AVC file encoder has its own options separate from the Vegas video engine. OpenCL and CUDA. CUDA would be applicable to your Nvidia card.
Sony AVC file encoder has it own options separate from the Vegas video engine. Use GPU when available (CUDA or OpenCL) and it also supports Intel Quicksync. That is the QSV available message you saw. Quicksync is a completely different encoder than the “normal” Sony AVC encoder. Sony just chose to expose this function under Sony AVC.
You can have multiple video devices active. It sounds like you might have drivers installed for both the Intel integrated and Nvidia graphics. The Intel graphics make Quicksync available. The Vegas video preferences will list both cards in this situation. In that case select the one that gives the best performance.
Quicksync should be a very fast encoder.
-
A lot of material works at low(er) bitrates. TV/movies where people are standing around, moving slowly, and talking. Cable TV pushes bitrates down to cram as many channels as they can into their limited bandwidth. TV and movies are typically not as sharp as they can be at HD since most do not want that kind of detail in faces.
To me 4K is about hugh screens at relatively close distance, and/or pixel level detail. Not much material wants pixel level detail.
I watch a 55″ TV from 10 feet. When I watch something like Planet Earth on Blu-ray I don’t know if I would want anything more. I have even sat at half that distance. That is only an average Blu-ray. Put in something reference quality like Avatar or Pirates of the caribbean trilogy and holy c**p.
I compare everything to Blu-ray (unfair I know) and I always want more “D” to go with the “H” in TV and Internet. So when it comes to “UH”, I am not interested unless there is a hell of a lot of “D”.
-
Youtube, Vimeo and others re-encode your video to their standard which is a fairly low bitrate. High frequency detail and/or fast motion will never encode well at low bitrates.
-
The whole 4K thing and internet delivery seems hype to me. I download some 4K samples showcased by Youtube and they do not even, or barely deliver Blu-ray HD bitrates and they have four times the pixels.
Of course the same can be said for Internet 1080 delivery. Poor bitrate.
-
[Selma Citroen] “I made a musicvideo for my friend, in 24fps because I wanted a cinematic effect. Yesterday when I finished the video, I found out that Youtube converts everything to 30fps. :/”
Youtube will keep your video at 24fps. What Youtube does is convert anything above 30fps down to 30fps. Below 30fps they keep the original rate.
They have preserved 24fps with my test.
-
[manuel pimentel] “I’m not sure what he used to compress it, so I do not want to mislead anyone. “
From MediaInfo, it look like he used Quicktime, but some program using Quicktime might still list Quicktime as the writing library. Googling “abm0” does not show any good results.
Format : QuickTime
Format/Info : Original Apple specifications
File size : 47.8 MiB
Duration : 13s 722ms
Overall bit rate mode : Variable
Overall bit rate : 29.2 Mbps
Encoded date : UTC 2014-07-01 00:18:56
Tagged date : UTC 2014-07-01 00:19:00
Writing library : Apple QuickTimeVideo
ID : 1
Format : ProRes
Format version : Version 0
Format profile : Proxy
Codec ID : apco
Duration : 13s 722ms
Bit rate mode : Variable
Bit rate : 27.7 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:2
Scan type : Progressive
Bits/(Pixel*Frame) : 0.557
Stream size : 45.3 MiB (95%)
Writing library : abm0
Language : English
Encoded date : UTC 2014-07-01 00:18:56
Tagged date : UTC 2014-07-01 00:19:00
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
matrix_coefficients_Original : BT.709