11/28/2023 0 Comments Xmedia recode constant quality![]() Please note that if I make an Ultra-fast conversion (this is Slow) the file works perfectly.įormat profile : (It says shouldn't it say That's what I selected in XMedia)Įncoding settings : cabac=0 / ref=4 / deblock=1:0:0 / analyse=0x1:0 / me=umh / subme=8 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=0 / weightp=0 / keyint=239 / keyint_min=23 / scenecut=0 / intra_refresh=0 / rc_lookahead=50 / rc=crf / mbtree=1 / crf=18.0 / qcomp=0.60 / qpmin=10 / qpmax=69 / qpstep=4 / vbv_maxrate=9500 / vbv_bufsize=24000 / crf_max=0.0 / nal_hrd=none / filler=0 / frame-packing=4 / ip_ratio=1.40 / aq=1:0. Here's the offending MediaInfo from a snippet I've made with the same results: Here is the MediaInfo of a VidCoder-encoded perfectly playable file: XMedia gives me the "unsupported video codec" message on TV, as well as the error (little X) thumbnail.ĭoes anyone know which settings should I accomodate in XMedia Recode so I can replicate the functioning VidCoder encoding? ![]() The constant quantizer works fine, but not CRF. it is outputting my file in the same bit rate, around 3000 kbits. ass subtitles (which are necessary for 3D viewing). Have any of you notice that the CRF setting in Recode 3.5.1.3 (using h.264) virtually has no change in the quality of the output file No matter CRF 16, 23, 10, etc. ![]() As title says, I'm having problems encoding files through latest XMedia with the same configuration as VidCoder, which works perfectly for my TV USB native player but doesn't allow me to burn-in.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |