Vegas pro 17 wont render using magix AVC above 100mbps , it simply shows unspecified error. Using HEVC works up to 240mbps but crashes half way. Is there any way i can render AVC with around 200mbps without problems ?
Why do you feel the need for 200 Mbps from a delivery render template?
im not sure which template im supposed to be using but i need my footage to be compressed from 700mbps to around 200mbps , 100mbps doesn't satisfy my needs. I need to use vegas as i have added alot of effects to the video.
i need my footage to be compressed from 700mbps to around 200mbps ,
Now that we know your goal is not playback, what do you plan on doing with your video?
i want the high bitrate video for archive purpose, to be able to view my footage with minimal compression. And then i wanna be able to re-encode and compress the video for YouTube later down the line to something like 80mbps
But AVC and HEVC lossy delivery codecs, not archival codecs. Study.
Which codec should I use ? I want my video at 200mbps, for personal use as I AM able to playback the video . It's just that when I render at 80mbps the video looks too compressed as there is sooo much data on the screen due to scene being so complex .
HEVC is visually lossless for my needs , I'm just trying retain as much detail as possible from my near lossless video. I'm trying to add effects to it and render it out so I can preview it at high rate . Forget about the archive bit . It's just for playback .
Post the Mediainfo report for your source video.Tell us which camera or external recorder you use and we'll make a recommendation.
At least B1 and C1 from here:
https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/
Nothing about HEVC is visually lossless. Bitrate is a function of compression, not quality. So different codecs can give the same quality at different bitrates.Here are some software intermediates for you to play with. This is one example where jumping into the middle of a learning curve doesn't work.
But I digress. Let's look at those source properties @john_dennis asked for first. Also, a short rendered sample might help us understand why you need hyperoptimal bitrates in the first place.
vegas 17 (build 284)
Complete name : C:\Users\Oskar\Videos\EVE-20200507154438.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 1.86 GiB
Duration : 20 s 0 ms
Overall bit rate mode : Variable
Overall bit rate : 800 Mb/s
Writing application : Lavf57.62.100
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.2
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 20 s 0 ms
Bit rate : 799 Mb/s
Width : 3 834 pixels
Height : 2 114 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 60.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 1.644
Stream size : 1.86 GiB (100%)
Writing library : x264 core 148 r2744 b97ae06
Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=24 / lookahead_threads=4 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=2 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=2.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Codec configuration box : avcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 19 s 990 ms
Bit rate mode : Variable
Bit rate : 265 kb/s
Maximum bit rate : 384 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 639 KiB (0%)
Default : Yes
Alternate group : 1
Im using a third party in game modification to capture the footage.
at the early 7 second mark i see some heavy compression that is very noticeable to me even with 135mbps, it was only completely fixed with 240mbps. and in the youtube video its even more apparent (1440p).
I know the original source isn't lossless but rendering it lossless creates a filesize thats too big for me and rendering anything lower than 135mbps creates serious compression.
A side note: several updates with fixes since build 284. Download the latest build (currently 421) from MAGIX Download Center using your serial number you got from MAGIX.
On page 2 of the thread below I posted 3 render quality tables of different codecs, including intermediates, GJeffrey did a comprehensive table on page 3 of the same thread. Theres a mixture of FHD and UHD.
@oskaras-u I've mentioned this issue previously, i.e. the hardware encoder nvenc can only encode up to an unspecified output size. If you attempt to render at higher data rates it may or may not do the job.
Sometimes you get a zero byte file, other times the file has audio, no video. The Magix intermediate Nvenc encoder is DOA, as it has all of the above mentioned issues. It would have suited your needs as I'm guessing you would like to get the benefit of HW encoding and good quality.
Some combinations of Nvenc HW encoding simply don't work at all. This small table displays a selection, not all, of possible combinations.
Note that the screenshot to the right highlights the data rate render limitations that I encountered on my laptop testing, only for … Preset = Default and RC mode = VBR. These limitations go away if you use Default & VBR HQ instead, or HQ & VBR HQ. I always use Preset = HQ and RC mode = VBR HQ.
Although I've highlighted number 11 as giving the best quality, using ffmpeg's SSIM and PSNR, it's probably best to avoid. I rendered out a 2 hour project with it and the seek time was unusable. I'm sure is ok for much shorter file durations.
From your Mediainfo report:
Writing application : Lavf57.62.100
It appears your capture application uses FFMPEG under the covers.
Encoding settings : crf=2.0
A CRF number between 2.0 and 18.0 might give you a source video that you could use to edit and archive.
you will gain access to third party encoders that will give you more flexibility than Vegas built-in render templates which are designed for humans who do video.
Warranty
All of my assistance on this forum comes with a lifetime double-your-money back warranty.
@JN- @john_dennis those pieces of information were very useful , thank you!
Oh, I see. You are using high bitrates as a hedge against crappy hardware encoding.
Capture with UT codec (100Mbps) instead. Then you will have no problems in a lightweight lossless format.