Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Please ignore my last post. While I really could not reproduce the crash on Linux, my main platform, ...

Edit: Scratch that, I can reproduce it on Linux too. Just open filter preview --> boom.

... I can reliably reproduce it on Windows 7. The sample doesn't matter, but any filter which needs to access the previous frame like FluxSmooth or MPlayer Denoise 3D HQ, placed after ResampleFps, will trigger this crash.

I'm looking into it.
22
And my error is not 100% reproduced. Such a feeling that this is a "floating" error for the manifestation of which the coincidence of a set of conditions is necessary. And in the debugger at the time of the fall, you can not send the task - while it starts, a fall record is created and the process ends. In the debugger, the return code is 0 and there is nothing to watch. So I think that it might be worthwhile to deploy the debug build in order to try to catch in it where exactly the failure occurs?
23
Windows / audio drops from 384bps to 64bps when edited
« Last post by reddwarf4ever on October 17, 2017, 11:13:58 AM »
audio drops from 384bps to 64bps when edited

captured some video with replay video capture with 384bps audio the edited MKV video is now only 64 bps

Is there anything i can do settings etc ?

Thanks
24
Main version 2.6 / Re: Denoise Filter settings and a few minor bugs?
« Last post by xtro on October 17, 2017, 10:02:22 AM »
My pleasure. After many years of using avisynth and failing miserably at first, but later after having some limited success, it makes sense to help others as using these scripts and plugin filters are not an easy task to get used to for the beginner.

 My preferred script(other useful software I'd used!) for a very light denoise with light sharpening is:

FFT3DFilter(sigma=0.5, bt=5, bw=32, bh=32, ow=16, oh=16, sharpen=0.4)


For those tricky vhs like sources/recordings you have, increase the sigma to 2.5 or 3.0 with sharpening set at 0.5, or use Fluxsmooth filter alone set at 15 spatial, temporal 15.  Fluxsmooth is good enough to be just used alone and will work well in most situations. However all of this depends on whether the source is progressive or telecined and you might have to decomb telecide first then decomb decimate the source in your filter plugin order for the denoise plugins of avidemux to work as intended as they are deemed to work on progressive only.

http://www.avidemux.org/admWiki/doku.php?id=tutorial:deinterlacing_video
25
Main version 2.6 / Re: Denoise Filter settings and a few minor bugs?
« Last post by Nemesis on October 16, 2017, 06:24:29 PM »
Dear xtro, you are a treasure!
Most tutorials seem too vague about actual parameter values.
I like that you make different suggestions depending on the situation.
Your post is very informative and to the point.
Thank you very much!
26
Main version 2.6 / Re: Denoise Filter settings and a few minor bugs?
« Last post by xtro on October 16, 2017, 05:18:50 PM »
Hello Nemesis thankyou for your interest regarding denoise.  The first two are spatial and the last two temporal with the filter you refer to. With the other version mplayer denoise 3D(much better denoiser!) there are 3 settings only for some strange reason, again set too high and at these settings will destroy fine detail of any source. Set these to: 1:2:3 for a very light denoise or for your slightly noisy DVD 2:1:3 to clean it up. I personally prefer vague denoiser based on wavelet action to clean up things or remove grain(mode 2) for black specks on film sources like you can use in Staxrip or AutoGK.

Now regarding M player denoise 3D HQ follow suit 0:0:3:3 for any clean dvd action based source or any video input which might have slight motion artifacting or 1:1:2:2 for a super light allround denoise on a very clean source. H264 acts as a denoiser itself with its action and tends to smooth these potential problems out, so I would never use this denoiser on any already clean source. I might use it on a slightly grainy source 2:1:3:3 upping the spatial as I go, if the effect is not enough, so 2:1 will become 2:2:3:3 or 3:2:3:3 etc.

For floating specks you can increase the temporal- the last 2 numbers to say 5:5, but this denoiser I find has very little effect on that kind of noise and you might introduce color banding or blacks dots cropping up elsewhere or ghosting. On a video input say where you want to further compress(resize) and avoid mosquito noise just use 0:0:2:2. It will ever so slightly soften the picture, but you won't notice it. Fluxsmooth set at 2:2 or 3:3, is good for this clearing up of artifacts too. You'd be better off with FluxSmooth which is set at its default 7/7, increasing to 10/10 for heavier grained sources. If you can help it avoid using a denoiser full stop.

 All you need to learn about this denoiser HQDN.. and its settings are in the link below. Hope it helps!

https://mattgadient.com/2013/06/29/in-depth-look-at-de-noising-in-handbrake-with-imagevideo-examples/
27
use resize filter and re-encode accordingly
28
 "width and height are different between first and this video stream"

How do I change the first to match the second (which is 1280 x 720)?
29
Thank you, I can't reproduce the crash with your sample and exactly the same collection of video filters.
30
Windows / Re: First post and just a quick question about VBR or Video Quality
« Last post by Jan Gruuthuse on October 16, 2017, 06:42:42 AM »
Use a one minute test video of material you're to use most. Check on the device(s) you want to play for yourself. (Mediaplayer, flatscreen tv's, ....). It is all in the eye of the beholder.

1. Mpeg4 (AVC)
-However I have an nvidia card, should I ever select (Nvidia H264?)
If your card does support hw acceleration? There would be speed gain, possible a (noticeable) quality loss.

Quote
2. AAC (LAV) or MP3 at 192 bitrate..
Check if the combination you want to use, does work on the intended devices, not all do support mp3, mp3 is most of the time stereo only. Unless your device has MP3 surround.
Pages: 1 2 [3] 4 5 ... 10