VideoHelp Forum




+ Reply to Thread
Page 10 of 13
FirstFirst ... 8 9 10 11 12 ... LastLast
Results 271 to 300 of 390
  1. mkv isn't a format, it's a container. Merging mkv files should work with mmg.
    Quote Quote  
  2. if the encoding setting produce compatible streams merging mkv files with mmg should work
    Quote Quote  
  3. Thanks it worked.
    Quote Quote  
  4. How many reference frames and bframes do you guys use for 720p encodes?
    Quote Quote  
  5. depending on the content and possible hardware restrictions, I normally use:
    reference Frames <= 6
    b-frames <= 6
    Quote Quote  
  6. Going beyond ~4 ref and b frames usually gets you only small improvements in compression (crf encoding) or quality (bitrate encoding). I don't consider it worth the extra encoding time and risk of hardware incompatibility.

    For example, a random 10000 frame 720p sequence encoded at the --slow preset and:

    --ref=4 --bframes=4: 26 fps, 1940 kbps
    --ref=6 --bframes=6: 21 fps, 1908 kbps
    --ref=16 --bframes=16: 9 fps, 1882 kbps

    So going from 4 to 6 ref/b frames got less than 2 percent better compression but took ~24% longer to encode. Going from 4 to 16 ref/b frames got about 3 percent better compression but took almost three times longer to encode.
    Last edited by jagabo; 6th Jun 2013 at 09:08.
    Quote Quote  
  7. Which of the x264 settings are the most important ones?
    Quote Quote  
  8. Read in example http://mewiki.project357.com/wiki/X264_Settings to understand what each feature does, since you wrote before you understood all the basics this should clear all questions.
    From my point of view, wach option has it's own effect and there is no general 'this is the most important setting', if I had to choose I would go for the combination of level, profile and vbv settings, but that's just me.
    Quote Quote  
  9. Have you tried encoding with aq mode 2?
    Quote Quote  
  10. yes, when I use aq, I normally use aq mode 2
    Quote Quote  
  11. could you post some screenshot links for compression artifacts?
    Quote Quote  
  12. no. Don't see a reason to do some googling you could do yourself. At least for me the google image search shows tons of compression artefacts if you google for it.
    Quote Quote  
  13. kernel

    Kernel used by the resizer. Possible values are:

    "point" Nearest neighbour interpolation. Same as PointResize().
    "rect" or "box" Box filter.
    "linear" or
    "bilinear" Bilinear interpolation. Same as BilinearResize().
    "cubic" or
    "bicubic" Bicubic interpolation. Same as BicubicResize(). The b and c variables are mapped on a1 and a2 and are both set to 1/3 by default.
    "lanczos" Sinc function windowed by the central lobe of a sinc. Use taps to specify its impulse length. Same as LanczosResize().
    "blackman" Blackman-Harris windowed sinc. Use taps to control its length. Same as BlackmanResize().
    "blackmanminlobe" Another kind of Blackman windowed sinc, with a bit less ringing. Use taps for you know what.
    "spline16" Cubic spline based kernel, 4 sample points. Same as Spline16Resize().
    "spline36" Spline, 6 sample points. Same as Spline36Resize().
    "spline64" Spline, 8 sample points. Same as Spline64Resize().
    "spline" Generic splines, number of sample points is twice the taps parameter, so you can use taps = 6 to get a Spline144Resize() equivalent.
    "gauss" or
    "gaussian" Gaussian kernel. The p parameter is mapped on a1 and controls the curve width. The higher p, the sharper. It is set to 30 by default. This resizer is the same as GaussResize(), but taps offers a control on the filter impulse length. For low p values (soft and blurry), it’s better to increase the number of taps to avoid truncating the gaussian curve too early and creating artifacts.
    "sinc" Truncated sinc function. Use taps to control its length. Same as SincResize().
    "impulse" Offers the possibility to create your own kernel (useful for convolutions). Add your coefficents in the string after “impulse”, separated with spaces (ex: "impulse 1 2 1"). The number of coefficients must be odd. The curve is linearly interpolated between the
    I'm using dithertools to resize from 1080p to 720p, which of this is the best kernel?
    Quote Quote  
  14. Come on, have at least the decency to search for an answer to your question before simply posting it and if I ever again ask about if something is the best or what is the best at least I will put you on my ignore list.

    It always depends on your taste, there is no absolute and objective measurement for quality so there can be no best.

    Each resizer has it's pro and cons. Read http://svn.int64.org/viewvc/int64/resamplehq/doc/kernels.html go understand the basics and if that is not enough google for some additional resizer comparisons and my be even try some yourself.
    Quote Quote  
  15. Where can i find the 64bit avisynth 2.6 exe file?
    Quote Quote  
  16. There is no such thing and I would strongly recommend not to use the 2.58 64bit version either, since the number of filters that have 64bit versions, which run stable is rather small. If you want to use Avisynth 2.6 use a 32bit version.
    Quote Quote  
  17. How do i fix this error?

    Quote Quote  
  18. easy fix: don't use dither.avsi
    more complicated: look into line 887 of the avsi script you are using and figure out what it going wrong
    you probably either use some incompatible filter versions together, messed around with Avisynth MTs SetMTMode, your source is broken in some way, your system ram might have problems or you are simply doing something that is known to be instable (like doing high bitdepth denoising, which in example isn't supported by SMDegrain anymore since it turned out to be instabel)
    Quote Quote  
  19. You need and explicit SetMtMode() to use some filters.
    Quote Quote  
  20. Avs:

    dgsource("c:\users\abhijith nair\desktop\no_country.dgi")
    crop(0, 132, -0, -132)
    dither_convert_8_to_16()
    dither_resize16nr(1130, 480, kernel="spline36")
    dither_quantize(bitdepth=10, reducerange=true, mode=0)
    dither_out()
    Quote Quote  
  21. Originally Posted by jagabo View Post
    You need and explicit SetMtMode() to use some filters.
    Thanks, the script worked after i did this.
    Quote Quote  
  22. Confused, his script didn't use MT at all, why would using setMTMode(..) fix anything then?
    Quote Quote  
  23. I made some changes in the script.
    Quote Quote  
  24. A few frames of this film looks like this. How do i fix this?
    Source : Italian BD



    Quote Quote  
  25. are these the images from before or after avisynth?
    Quote Quote  
  26. Use the chroma from a nearby frame?
    Quote Quote  
  27. Originally Posted by jagabo View Post
    Use the chroma from a nearby frame?
    Could you tell me how to do this?
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!