StaxRip is good for beginners, certainly, but you don't have to use it to encode anything. A relatively easy alternative might be VirtualDub2 through which you can make your test encodes or your full encodes. Open the AviSynth script, select whatever codec you want from the menu in the Video->Compression area (x264 8-bit?) and Configure it (Default CRF 18, Tuning=Film?), be careful of SAR). Then go File->Save As and choose the container (MP4, MKV, whatever). If you want audio, choose and configure it in the Audio section.
Our website is made possible by displaying online advertisements to our visitors. Consider supporting us by disable your adblocker or try DVDFab and copy, convert or make Blu-rays and DVDs! :)
+ Reply to Thread
Results 61 to 89 of 89
AviSynth at all... but that ship has sailed.
I only recently became aware that x264 has tunes. I've never used one, but if you recommend to use film, I'll give it a try. Would that be your go-to tune except for specific cases (animation, any other case covered by the other tunes) or is there any case where you'd advice against it?
Last edited by MGRV; 19th Dec 2018 at 15:23.
DelayCut to get rid of it.
I've never used one, but if you recommend to use film, I'll give it a try.
PS: I realized I did something pretty stupid: I used VirtualDub2 per manono's suggestion, but used it to encode a script that pointed to my already cut "sample D2V" as a source instead of the (trimmed) original D2V. Now I correctly referenced the original D2V, but using the demuxed audio won't work either, as the audio runs from the start while my video is trimmed. Maybe the AudioDub function helps here, but I don't really need to complicate things too much, I can do away with audio for these short clips.
Last edited by MGRV; 20th Dec 2018 at 02:40.
- My sister Ann's brother
With a minor difference: instead of interleaving, add them:
v1 = WhateverSource("file1.ext") v2 = WhateverSource("file2.ext") v1 + v2
MediaInfo. So you could encode a short clip with different tunings and compare the settings.
preset=slow, tune=none, crf=18: cabac=1 / ref=5 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=8 / psy=1 / fade_compensate=0.00 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / 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=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=crf / mbtree=1 / crf=18.0000 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00 preset=slow, tune=film, crf=18: cabac=1 / ref=5 / deblock=1:-1:-1 / analyse=0x3:0x113 / me=hex / subme=8 / psy=1 / fade_compensate=0.00 / psy_rd=1.00:0.15 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-3 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=crf / mbtree=1 / crf=18.0000 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Just for kicks, I tried a combination of trimming and appending which works as expected, although the audio gets out of sync.
clip1 = AviSource("better_video.avi") clip2 = AviSource("complete_video.avi") clip1a = Trim(clip1, 0, 1000) clip1b = Trim(clip1, 1001, 2000) clip1c = Trim(clip1, 2001, 0) clip2a = Trim(clip2, 1001, 1500) clip2b = Trim(clip2, 2501, 3000) clip1a + clip2a + clip1b + clip2b + clip1c
DelayCut, though I'm a bit confused about this whole deal. I suppose because there are different moments in the process where one can join audio+video, there are also different ways to deal with sync problems.
AviSynth, or should I download one in order to load my AC3 file?
I've been playing around with that and there's already a new question on its way (about making a video out of two different sources ), but I think I'd better hold that off until I'm done with this project.
ReplaceFramesSimple(A,B,Mappings="[1000 2000] [10000 12000] 20000 25555] ")
ReplaceFramesSimple is a part of stickboy's RemapFrames. The frame numbers within the brackets are the start and end frame numbers for the replacement. Movie gets replaced with BetterMovie in those sections.
So I know it can be done, my question was going to be more about whether this can be done without quality loss of at least the better source
Is there any source filter for audio that comes with AviSynth, or should I download one in order to load my AC3 file?
DelayCut to my army of tools, then. I can use the out-of-sync file in PotPlayer to figure how much I need to cut/delay.
Is there a way to do it losslessly (outside AviSynth)? I understood that's what ffmpeg does with concat and using copy, but I'm not sure about anything anymore! I mean, having two videos that share the same specs and joining different segments of them into one single video, without having to decompress them. If that's the case, what I was thinking is I could re-encode only the complete video (worse quality, could use some filtering) and encode it so that it matches the better one before doing the joins.
Last edited by MGRV; 20th Dec 2018 at 13:42. Reason: Found NicAudio.dll !
I checked that NicAudio link and couldn't figure it out either. I'll enclose the DLL and TXT file.
Then you start direct stream copying the the various parts and eventually append all the pieces.
VirtualDub's Direct Stream Copy is designed for use with AVI files. It can Direct Stream Copy AVS scripts but remember that it receives uncompressed video from an AVS script, not the original compressed video. In theory you may be able to remux your MP4 sources (depending on codecs, must be constant frame rate, etc.) into an AVI container and use Virtual Dub to cut/paste in Direct Stream Copy mode.
Keep in mind that key frames may be hundreds of frames apart with long GOP codecs. So the granularity of your cuts won't be great.
There is a class of "smart" editors that can cut frame accurately and only reencode cut GOPs. VideoRedo, for example, can do this with MPEG 2 and h.264 video (in several containers). I believe Vegas can do it with MPEG 2 video.
In theory you may be able to remux your MP4 sources (depending on codecs, must be constant frame rate, etc.)
Keep in mind that key frames may be hundreds of frames apart with long GOP codecs. So the granularity of your cuts won't be great.
Last edited by MGRV; 21st Dec 2018 at 10:57.
VirtualDub calls them K) are encoded as complete pictures, much like a JPEG image. Forward Predicted frames (P frames) reference prior frames (blocks of pixels are copied from prior frames to the P frame). Bidirectional predicted frames (B frames) are similar to P frames but they can copy from both frames before and/or after the B frame.
A Group Of Pictures (GOP) is the I frame and its P and B frames, up to the next I frame. Since the B and P frames reference other frames, and ultimately the I frame, you can't remove the I frame without corrupting the other frames. So simple cut/paste editors that don't reencode the video have to cut-in on I frames (ie, any part you keep must start with an I frame). Some let you cut-out on P frames.
VideoRedo a go sometime in the future. So, what it does is: decompress/reencode only the GOPs affected by my cuts, leave the rest untouched? As long as I provide it with workable sources (i.e. sharing certain specs). I thought it would be as easy as looking at the 'good' file with MediaInfo and trying to replicate the settings when encoding the other one, but I suspect it may be more than I can chew (sorry, I won't get rid of the tooth references until I'm done with these DVDs).
So, back to my original task. I'm considering sticking with QTGMC's fast preset, but I want to make sure it does enough getting rid of interlacing artifacts. What type of segments should I pay close attention to? I imagine: fast motion, camera pans, straight lines... Anything I'm missing?
It's not like I'm noticing a huge loss of detail with slower presets. My eyes aren't trained to know what to look for, so I really don't know. It just so happens that I was expecting to see the infamous flying tooth and could hardly notice it in my first attempts with slower presets (which turn the 'tooth pixels' a bit darker, making them harder to spot against the background at such speed). It became obvious to me because I'm familiar with the footage and knew what to expect at that moment (how could I forget?), otherwise it would have passed me by entirely. But I took it as an indicator (maybe not an accurate one) of how the processing could affect the output elsewhere.
Well, I'm trying to convince you that I'm a sane person not obsessed at all with the tooth, but who am I kidding? It was the first-ever televised bout in which the very first kick caused a tooth to fly. It's a dental piece of history. But if blending it a bit is what it takes to get rid of deinterlacing artifacts for good, there's always the slow-motion replay to fall to.
What type of segments should I pay close attention to?
QTGMC.png = QTGMC slow preset (maybe medium, can't recall)
QTGMC_fast.png = QTGMC( Preset="fast", SourceMatch=3, Lossless=1, Sharpness=0.4, TR2=2)
If you look at the fast QTGMC frame, the guy's shoulder has this serrated look (I'm struggling not to say sawtooth) while the other one looks much smoother.
The settings for the fast one probably make no sense (I was just shooting in the dark), so it probably has to do more with that than with the fast processing. I'm trying just QTGMC(preset="fast") on VirtualDub now and it doesn't look nearly as bad.
Last edited by MGRV; 21st Dec 2018 at 19:38.
Nearly horizontal edges and lines. Closely spaced (nearly) horizontal lines (like horizontal blinds). Examine such details while in motion. Not necessarily a lot of motion but with small motions. Watch for aliasing artifacts, buzzing edges, and moire artifacts.
Also you often find that the two fields that make up a frame don't align perfectly horizontally. After a simple bob they will shake left/right. A smart bob might leave some comb artifacts (serrated vertical edges). The two fields may have slightly different intensities or colors. A simple bob will flicker. Smarter bobs may leave comb like artifacts because alternate scan lines have different intensities/colors. These types of problems can occur on still portions of the image as well as motion portions.
Last edited by jagabo; 21st Dec 2018 at 19:39.
From the QTGMC Doc:
The SourceMatch setting sets the mode: 0=off (standard [Q]TGMC algorithm), 1,2,3 for progressively more accurate but slower processing. Modes 2 & 3 restore almost exact source detail but are sensitive to noise & introduce occasional aliasing (mode 3 is less affected). Mode 1 is a more conservative halfway stage that rarely introduces artefacts.
Thank you both.
Indeed, the aliasing was caused by my own contributions and not by fast processing. I was pretty sure I'd spotted something similar with the fast preset and no extra settings, but I don't see it now. I've done so many tests that it's likely I got them mixed up. So I guess it all boils down to this:
I have a question about SAR (or PAR, according to StaxRip terminology). I've read it can be either set in the video stream or in the mux. I don't know where I'm setting it in my own StaxRip or VirtualDub2 encodes. Is it something I should worry about at all? Is there any way to ensure most players get it right? Maybe set both?
Not much progress done with my filter settings tests. These days have been a bit frantic so I haven't had the chance to do much.
I'm leaning towards doing my encodes with StaxRip, now that I know how to change the QTGMC settings. It's been useful to learn the basics of AviSynth and even get the filter to work there for on-the-fly testing, and I'll probably keep playing around with it to learn more, but I still have a few problems I'd need to sort out if I wanted to encode everything with VirtualDub2. Unless you tell me I will have the same problem with audio sync even if I encode with StaxRip (it just dawned on me). There's also subtitles, chapters, though I haven't even checked how that works yet.
Last edited by MGRV; 28th Dec 2018 at 09:21. Reason: I keep calling VirtualDub2 "VideoDub2"
Happy new year, folks!
As you have helped me so much with this, I figured a little update was due (uninteresting as it may be).
I did a lot of testing lately. I compared slow vs. fast preset frame by frame, but modifying one setting at a time from the slow preset to match the value of the fast one. The logic behind it was to see if any single setting made a noticeable impact on the way the tooth is smoothed out. It's really hard to notice, as the differences are expected to be minimal, but long story short, it's the combination of settings and not just one variable.
So, then I checked for any artifacts during playback that could need a slower preset. I can't say I found any. I tried both in my laptop and on a TV. I do see a better quality in slower presets when I compare frame-by-frame, but I have not been able to spot any major difference during playback.
I also googled to see if there were any other 'practical' comparisons around between QTGMC's different 'speeds', anything that could help me educate myself (or my eyes) further, but couldn't find anything.
So I guess a few more tests are on the way before I make the call. So far, frame-by-frame comparison sways me to slower presets; playback leaves me undecided; the 'tooth factor' (which I took as an indication of possible detail loss elsewhere) makes a cause for the fast preset. I know this is not only subjective but also very much dependent on the source. But would you advice at all against the fast preset, in principle?
I'm pretty happy with the Film tuning, by the way. I had never tried it, but I think I'll be sticking with it.
In case anyone cares to read this far at some point, I should say that further testing proved noticeable differences between slower and faster QTGMC presets. Particularly in one of the DVDs, there is some heavy aliasing that benefits from slower settings. I wasn't able to spot anything like it in the first DVD I tried.