StaxRip x86 (development for x86 has been stopped)

[chagos]

Hi, I have this error using v1.2.2.0:
http://pastebin.com/uV99LXEG

http://thumbnails105.imagebam.com/40306/407b6d403056260.jpg (http://www.imagebam.com/image/407b6d403056260) http://thumbnails107.imagebam.com/40306/ce5c24403056265.jpg (http://www.imagebam.com/image/ce5c24403056265)

[Washka]

Everytime when i open any mkv file in Latest official StaxRip, OpenCL.dll is missing.
I have ATI installed before in my PC now i have Nvidia but i uninstalled drivers with driver cleaner. Maybe because of that or there is some other solution? I didn`t find anything about that in this thread or help.

edit.
When i try to open a VirtualDubMod.exe without StaxRip he pop-up that error also.

Any way to fix that?

[Vulpix]

Hi, I have this error using v1.2.2.0:
http://pastebin.com/uV99LXEG

http://thumbnails105.imagebam.com/40306/407b6d403056260.jpg (http://www.imagebam.com/image/407b6d403056260) http://thumbnails107.imagebam.com/40306/ce5c24403056265.jpg (http://www.imagebam.com/image/ce5c24403056265)

I actually had a similar problem before and found out that my RAM was clocked too high (2400Mhz). It sounds stupid, because I ran various day-long tests (linpack, memtest, prime95). If you overclocked your ram then I suggest you try going down with it one step, or maybe increase voltage a bit.

I know it sounds strange but I had the exact same "weird" problems and once I downclocked, they stopped and never ever happened again.

[chagos]

I actually had a similar problem before and found out that my RAM was clocked too high (2400Mhz). It sounds stupid, because I ran various day-long tests (linpack, memtest, prime95). If you overclocked your ram then I suggest you try going down with it one step, or maybe increase voltage a bit.

I know it sounds strange but I had the exact same "weird" problems and once I downclocked, they stopped and never ever happened again.

Nice find Vulpix.:thanks:
http://thumbnails105.imagebam.com/40341/b9c508403403084.jpg (http://www.imagebam.com/image/b9c508403403084)

I encounter this error multiple times with the last stable version of StaxRip and with previous versions, on this overclocked system. I have G.Skill F3-2400C10D-16GTX clocked to 2400 MHz.
However, I succeeded to encode what I wanted with x264 x64 10 bit, using v1.2.2.0 of StaxRip.

[stax76]

VP9 is amazing, but its encoder is probably the most broken thing I've ever used. The format itself is amazing, but its encoder literally sits around and does nothing all day long.

I can encode a 1 min x265 clip with 16 reference frames, 5 B-frames etc on highest settings in 6 minutes, the same clip running through VP9 encoder set to "Best" and 16 ref frames takes, I kid you not, SEVEN HOURS to process

EDIT: I have to say these random questions whenever I want to make a post is probably the most irritating thing I could possibly think of ever being added to a forum

With help of two members I managed to get vpxenc working, GUI needs so time though.

Everytime when i open any mkv file in Latest official StaxRip, OpenCL.dll is missing.
I have ATI installed before in my PC now i have Nvidia but i uninstalled drivers with driver cleaner. Maybe because of that or there is some other solution? I didn`t find anything about that in this thread or help.

edit.
When i try to open a VirtualDubMod.exe without StaxRip he pop-up that error also.

Any way to fix that?

I don't know much about this DLL, you can try creating a thread with title 'VirtualDubMod reports OpenCL.dll is missing'.

@all

I've uploaded a new beta release, it has a new comparison tool which is useful to find out which codec or codec settings work best.

1.2.2.2 beta


Added support for very long file names by shortening the name of the temp files directory
Added codec comparison tool for codec comparisons (Tools/Advanced/Codec Comparison)
Added the possibility to show the LAV Filters video decoder configuration (Tools/Advanced/LAV Filters...)
Added AVSMeter for benchmarking AviSynth scripts (Tools/Advanced/AVSMeter)
Added SincResize AviSynth filter
Added vpxenc encoding tool for VP9 encoding and added a command line profile, a GUI will follow soon
Improved GUI for QSVEncC (tool for Intel Quick Sync H.264 GPU encoding)
Improved x265 GUI, new options added, improved layout, improved help
Improved thumbnail generator printing more info
Improved MediaInfo Folder View (at Tools/Advanced/MediaInfo Folder View), list of audio codecs, context menu with various options, automatic layout
Fixed crash opening MP4 files with EIA-608 subtitles used by Apple
Fixed help browser not using word wrap
Fixed shutdown not working
Updated x265 to version x265 1.6+174
Updated QSVEncC to 1.33 (Tool for Intel H.264 GPU encoding)
Updated NVEncC to 1.05 (Tool for NVIDIA H.264 and H.265 GPU encoding)
Updated ffmpeg


http://sourceforge.net/projects/staxmedia/files/StaxRip%20beta/StaxRip_1.2.2.2_beta.7z/download

Please note that I take a small PC break, see you guys later!

[Patman]

With help of two members I managed to get vpxenc working, GUI needs so time though.



I don't know much about this DLL, you can try creating a thread with title 'VirtualDubMod reports OpenCL.dll is missing'.

@all

I've uploaded a new beta release, it has a new comparison tool which is useful to find out which codec or codec settings work best.

1.2.2.2 beta


Added support for very long file names by shortening the name of the temp files directory
Added codec comparison tool for codec comparisons (Tools/Advanced/Codec Comparison)
Added the possibility to show the LAV Filters video decoder configuration (Tools/Advanced/LAV Filters...)
Added AVSMeter for benchmarking AviSynth scripts (Tools/Advanced/AVSMeter)
Added SincResize AviSynth filter
Added vpxenc encoding tool for VP9 encoding and added a command line profile, a GUI will follow soon
Improved GUI for QSVEncC (tool for Intel Quick Sync H.264 GPU encoding)
Improved x265 GUI, new options added, improved layout, improved help
Improved thumbnail generator printing more info
Improved MediaInfo Folder View (at Tools/Advanced/MediaInfo Folder View), list of audio codecs, context menu with various options, automatic layout
Fixed crash opening MP4 files with EIA-608 subtitles used by Apple
Fixed help browser not using word wrap
Fixed shutdown not working
Updated x265 to version x265 1.6+174
Updated QSVEncC to 1.33 (Tool for Intel H.264 GPU encoding)
Updated NVEncC to 1.05 (Tool for NVIDIA H.264 and H.265 GPU encoding)
Updated ffmpeg


http://sourceforge.net/projects/staxmedia/files/StaxRip%20beta/StaxRip_1.2.2.2_beta.7z/download

Please note that I take a small PC break, see you guys later!

hi stax,

thanks for the new beta! One question: is sincresize filter in the filter selection? Can't see it...

[stax76]

I've added SincResize and re-added AviSource but didn't want to reset the profiles so users don't loose customizations, if you want you can reset it either in the profiles editor or at Tools/Advanced/Reset Settings > Filter Profiles

If you reset it in the profiles editor you can copy just new filters and then cancel to copy the new filters into the old profiles.

[JohnLai]

stax76, any consideration to include simpleresize filter? This is the most less cpu taxing resizer with some sacrifice on downsizing quality.

[stax76]

I'll look into it but for the rest of the month I'll take a PC break.

[Washka]

@Stax76
New Beta does not report OpenCL.dll is missing...

[alrmothe]

Thank you



Please

add x264 a high 10 profile!!! ( 10 bits depth)

add x265 HEVC a high 10 profile!!! ( 10 bits depth)

[NikosD]

Thank you



Please

add x264 a high 10 profile!!! ( 10 bits depth)

add x265 HEVC a high 10 profile!!! ( 10 bits depth)
There are already 10bit executables for both x264 & x265.

You have to go to Tools -> Settings -> System and select the 10 bit executables for H.264 & H.265 builds

[Vulpix]

I am curious; would it be possible to implement a 2-pass hw encoding mode?

[dvd_maniac]

I just upgraded from 1.1.9.0 to 1.2.2.2 beta and I'm having a problem with the width limiter.
Under Options --> Image I set the "Resize slider width" to 768 but when I load a video it defaults to the width of the video and tries to encode that. Most of my videos are 1080i recordings.
I actually have to move the width slider back and forth after loading the video for it to take the limitation.
This would not be a big deal if I only had to encode a video here or there but I usually use the "File Batch" option to encode 20-30 files at a time. Now I have to open each video, move the slider back and forth and then add it to the queue.

Is there something else I am missing to automatically enforce the width limitation besides the resize slider width setting?

Even if there is not... Staxrip is awesome and I am glad there is still ongoing development :)

[stax76]

I started to work on StaxRip 64-Bit, I don't have a great choice other than dropping 32-Bit altogether, both would simply be too much work to build, too much work to maintain, to many potential problems and too much complexity. I just hope the tools are ready, otherwise I would have too improve my basic C++ skills and work with C++ for a long time.

I am curious; would it be possible to implement a 2-pass hw encoding mode?

Probably yes but only Intel or NVIDIA could do it.

@dvd_maniac

The slider option might generally not be very useful, I think you just miss enabling the resize filter using the checkbox.

[NikosD]

I started to work on StaxRip 64-Bit, I don't have a great choice other than dropping 32-Bit altogether, both would simply be too much work to build, too much work to maintain, to many potential problems and too much complexity. I just hope the tools are ready, otherwise I would have too improve my basic C++ skills and work with C++ for a long time.


Welcome back.

I was ready to make you such a suggestion after fixing the last minor bugs of x86 version [emoji14]

Are you going to release any other x86 version or the last one was 1.2.2.2 ?

[stax76]

1.2.2.2 was the last, I hope everything goes well, there will be a new hardware tool (not free). ;)

[NikosD]

New HW tool ? What do you mean ?

[stax76]

DGDecIM, it's not free but it's stable and in active development.

[NikosD]

Ah..OK

[fantasmanegro]

1.2.2.2 was the last, I hope everything goes well, there will be a new hardware tool (not free). ;)

1.2.2.2 as fas as i know is BETA.... will you release a STABLE version of 1.2.2.2 befere you move to 64bits?

[stax76]

1.2.2.2 as fas as i know is BETA.... will you release a STABLE version of 1.2.2.2 befere you move to 64bits?

Since 1.2.2.2 no significant bugs have been reported, if there is real demand I could make a 32-Bit maintenance release.

[fantasmanegro]

Since 1.2.2.2 no significant bugs have been reported, if there is real demand I could make a 32-Bit maintenance release.

we will be very glad if you do that. :thanks:

[aegisofrime]

DGDecIM, it's not free but it's stable and in active development.

Oh? That's interesting. Last I heard DGDecIM was abandoned due to Donald Graft complaining about the lack of support from Intel. Has he picked it up again?

[stax76]

Oh? That's interesting. Last I heard DGDecIM was abandoned due to Donald Graft complaining about the lack of support from Intel. Has he picked it up again?

I've not followed it in detail, here is the thread:

http://rationalqm.us/board/viewtopic.php?f=5&t=371

[aegisofrime]

I've not followed it in detail, here is the thread:

http://rationalqm.us/board/viewtopic.php?f=5&t=371

Thanks for the link! Will give it a read.

BTW, would you consider adding support for the new Quick Sync encoder Q264?

[stax76]

Thanks for the link! Will give it a read.

BTW, would you consider adding support for the new Quick Sync encoder Q264?

I've not yet looked at Q264, QSVEncC seems to be pretty solid.

Users can integrate any CLI encoder into StaxRip, it's not really difficult, the next alpha will have 4 CLI examples including one that uses piping and one using 2 pass, all necessary macros and other things can be seen in the examples:

The CLI encoder supports multiline for multiple passes.

"%app:x264%" --pass 1 --bitrate %video_bitrate% --stats "%working_dir%%target_name%.stats" --output NUL "%avs_file%"
"%app:x264%" --pass 2 --bitrate %video_bitrate% --stats "%working_dir%%target_name%.stats" --output "%encoder_out_file%" "%avs_file%"

And it support piping and everything else possible in bat files, if there is a line break or piping symbol it's interpreted as bat file.

"%app:ffmpeg%" -i "%avs_file%" -f yuv4mpegpipe -pix_fmt yuv420p - | "%app:NVEncC%" --sar %target_sar% -c h265 --y4m --cqp 36 -i - -o "%encoder_out_file%"

"%app:DivX265%" -i "%avs_file%" -o "%encoder_out_file%" -br %video_bitrate% -10

"%app:xvid_encraw%" -i "%avs_file%" -avi "%encoder_out_file%" -par %target_sar% -single -cq 2 -smoother 0 -max_key_interval 250 -nopacked -vhqmode 4 -qpel -lumimasking -notrellis -max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -threads 1

[Br4twurscht]

Hi,

I really like StaxRip. Great work! :thanks:

But currently I try to remux mkv's to mp4's and it will not work. I used "Just Mux" at Video and Audio and set the container to mp4.

But the there is a hint: "The encoder outputs: 'mkv' but the container 'MP4' supports only avi, ac3, mp4, m4a, 264, h264, avc, 265, h265, hevc, mp2, mpa, mp3." And I can't ignore this hint.
The problem is, that the h264 video stream (encoded with x264) isn't demuxed while adding the mkv. And I can't find an option to force to demux the video stream.

I know that it would be possible to demux the video directly on console with eac3to and mux it with mp4Box or Yamb. But for a batch it would be nice to using StaxRip. And I don't like MkvToMp4 because it reencodes the audio stream.

Best regards
Br4twurscht

[stax76]

Hi, you cannot expect much from mp4box, it has so many shortcomings that it hurts. What you are asking for has however been requested 2-3 times so I've put this on the todo list now.

[lotnybartek]

DGDecIM, it's not free but it's stable and in active development.

Would I be able with this new tool to HW decoding?

So I'd decode using your new tool and encode with QSVenc?

When you're going to release it?

[stax76]

@Br4twurscht

I've added the feature (next x64 release).

Would I be able with this new tool to HW decoding?

So I'd decode using your new tool and encode with QSVenc?

When you're going to release it?

Next x64 release will have DGDecIM as avs decoder and QSVenC will also have a decoder option processing the video from beginning to end bypassing AviSynth entirely.

[Brilliant]

Hi all,

I think something is wrong in 1.3.1.0 beta I just downloaded.

I own a license for DGIndexNV, and I'm using it for all my indexing in all StaxRip versions I've come to use all these years. (BTW, great job Stax76... :) ). So I load a TS, it starts indexing OK. Then, upon completion (the moving pointer at the bottom has already reached the end of the bar) a popup shows:
FAILED TO OPEN SOURCE, TRY ANOTHER METHOD?

Cannot load file 'D:\StaxRip1310\DGDecodeNV\DGIndexNV.exe'
Platform returned code 193:
%1 is not a valid Win32 application.

(D:\Movies\MyMovie temp files\MyMovie_Source.avs, line 1)


DGIndexNV.exe is working OK in StaxRip 1.1.9 and 1.2.2. Actually it ends its job even in 1.3.1.0. I'm rather suspicious about the last line, which points out the first line of MyMovie_Source.avs, being:

LoadPlugin("D:\StaxRip1310\Tools\Plugins\ffms2\ffms2.dll")

I see that DLL is newer than the one in older StaxRip releases, so maybe it's worth investigating. Am I correct?

[StainlessS]

Is it a CPP version ffms2.dll ?,if not try LoadCPlugin.

[Groucho2004]

%1 is not a valid Win32 application
That could indicate that you're trying to load a 64 Bit PE image on 32 Bit Windows.
You are aware that the new staxrip version is 64 Bit only, right?

[stax76]

@Brilliant

You have to re-download DGDecNV as it's only working since yesterday.

@StainlessS

C ffms2 has a memory leak, I don't recommend it.

[Brilliant]

@Stax76

It looks like your advice to re-download (and re-license) DGDecNV (now at release 2049) made it! No more errors, no more calls to ffms2.dll, and much faster too. Thanks, I'm an happy camper again! :)

[someoneXgr]

I moved from 1.1.9.0 today
https://i.imgur.com/rARJq6U.png

and I can't find 2pass x264 in 1.3.1.0
https://i.imgur.com/KCKOnbQ.png

Is there somewhere an option for it?

[Alexander]

I moved from 1.1.9.0 today
https://i.imgur.com/rARJq6U.png

and I can't find 2pass x264 in 1.3.1.0
https://i.imgur.com/KCKOnbQ.png

Is there somewhere an option for it?

I have done so,
Photos are here

http://www5.zippyshare.com/v/Z9MwzI0v/file.html

[someoneXgr]

I have done so,
Photos are here

http://www5.zippyshare.com/v/Z9MwzI0v/file.html
Thank you very much, very detailed.

[jkilez]

@jkilez

I'm sorry, Win XP support is gone too. Working on the application think of it as weight difficult to carry taking away much development time that could otherwise be spent on much more important things.

After this last comment I had resigned myself to using the old 1.1.9.0 StaxRip as I need both Xvid and x264 encoding. Now I see that Xvid support is back in, albeit in a different form. Hurrah! Thanks for including it.

I have jumped right in to the StaxRip x64 1.3.1.0 beta and had some quick feedback.

The good:

Yes! Tooltips can be disabled.
Yes! The "filters" edit window is no longer pops up partly off screen when the main window is at the edge.
Yes! You can choose AQ mode 3 in the x264 options.
x264 encoding appears to be about 10-15% faster than 1.1.9.0.


The bad:

The version of xvid_encraw included does not support the "-metric [integer]" option needed to enable the PSNR-HVS-M VHQ metric. I do not have a build environment to make a 64-bit version of the current 1.3.3 release, but I found an old alpha build (http://freewarepros.com/files/Xvid_14_127_29082012.zip) that had a 64-bit xvid_encraw with that option included. The new version also replaces "-lumimasking" with "-masking [integer]" to allow for Variance masking. It appears to work just fine.
An xvid_encraw encoding process cannot be aborted via the GUI. I imagine this problem exists for any encode using the batch interface. The program needs to be smarter about killing the child processes of the batch process.
While the "filters" edit window now postions itself properly on the screen, it no longer dynamically adjusts its size. I often end up with large filter scripts (often with many "trim()" or "ApplyRange()" chains for different sections) that I now have to view through this little porthole of an edit window. Could that be changed somehow?


The other:

The sample code for xvid_encraw does not include a sample for the compressibility check, which it probably should, since it requires specific file names to work properly. It would also be nice if the code used variables to make for easier editing like:

Instead of:
"%app:xvid_encraw%" -smoother 0 -max_key_interval 250 -nopacked -vhqmode 4 -qpel -lumimasking -notrellis -max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -threads 1 -i "%avs_file%" -pass1 "%temp_file%.stats" -bitrate %video_bitrate% -par %target_sar% -turbo
"%app:xvid_encraw%" -smoother 0 -max_key_interval 250 -nopacked -vhqmode 4 -qpel -lumimasking -notrellis -max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0 -threads 1 -i "%avs_file%" -pass2 "%temp_file%.stats" -bitrate %video_bitrate% -par %target_sar% -avi "%encoder_out_file%"

This:
set b_opts=-max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0
set opts=%b_opts% -max_key_interval 250 -nopacked -vhqmode 4 -qpel -lumimasking -notrellis -threads 1 -bitrate %video_bitrate% -par %target_sar% -i "%avs_file%" -progress
"%app:xvid_encraw%" %opts% -pass1 "%temp_file%.stats" -turbo
"%app:xvid_encraw%" %opts% -pass2 "%temp_file%.stats" -avi "%encoder_out_file%"


The compressibility check code could then look like this:
set b_opts=-max_bframes 1 -bvhq -bquant_ratio 162 -bquant_offset 0
set opts=%b_opts% -max_key_interval 250 -nopacked -vhqmode 4 -qpel -lumimasking -notrellis -threads 1 -par %target_sar% -progress
"%app:xvid_encraw%" %opts% -cq 2 -i "%working_dir%\%target_name%_CompCheck.avs" -avi "%working_dir%\%target_name%_CompCheck.avi"

[dejong12]

I think you should post this in the other topic http://forum.doom9.org/showthread.php?t=172068

I don't think Stax checks this one often.

[jkilez]

for me custom metric works...
It appears that you are referring to the custom matrix option, "-qmatrix [file]". The VHQ metric part of the Motion Precision section, unrelated to the quantization matrix. In newer versions of Xvid, it can be either the default PSNR, or PSNR-HVS-M.

[Patman]

It appears that you are referring to the custom matrix option, "-qmatrix [file]". The VHQ metric part of the Motion Precision section, unrelated to the quantization matrix. In newer versions of Xvid, it can be either the default PSNR, or PSNR-HVS-M.

My mistake, know what you mean. I've found a new version of xvid_encraw x64 and the help option show me

xvid_encraw built at 15:35:18 on Mar 4 2015
Usage : xvid_encraw [OPTIONS]

Input options:
-i string : input filename (stdin)
-type integer : input data type (yuv=0, pgm=1, avi/avs=2) (0)
-w integer : frame width ([1.4096])
-h integer : frame height ([1.4096])
-csp string : colorspace of raw input file i420, yv12 (default)
-frames integer : number of frames to encode (all)

Output options:
-dump : save decoder output
-save : save an Elementary Stream file per frame
-o string : save an Elementary Stream for the complete sequence
-avi string : save an AVI file for the complete sequence

Rate control options:
-framerate float : target framerate (auto)
-bitrate [integer] : target bitrate in kbps (700)
-size integer : target size in kilobytes
-single : single pass mode (default)
-cq float : single pass constant quantizer
-pass1 [filename] : twopass mode (first pass)
-full1pass : perform full quality first pass (disabled)
-pass2 [filename] : twopass mode (2nd pass)
-max_key_interval integer : maximum keyframe interval (300)
-zones [zones] : use `-help zones' for usage guidelines
-zq starting_frame float : bitrate zone; quant
-zw starting_frame float : bitrate zone; weight

Single Pass options:
-reaction integer : reaction delay factor (16)
-averaging integer : averaging period (100)
-smoother integer : smoothing buffer (100)

Second Pass options:
-kboost integer : I frame boost (10)
-kthresh integer : I frame reduction threshold (1)
-kreduction integer : I frame reduction amount (20)
-ostrength integer : overflow control strength (5)
-oimprove integer : max overflow improvement (5)
-odegrade integer : max overflow degradation (5)
-chigh integer : high bitrate scenes degradation (0)
-clow integer : low bitrate scenes improvement (0)
-overhead integer : container frame overhead (0)
-vbvsize integer : use vbv buffer size
-vbvmax integer : vbv max bitrate
-vbvpeak integer : vbv peak bitrate over 1 second

BFrames options:
-max_bframes integer : max bframes (2)
-bquant_ratio integer : bframe quantizer ratio (150)
-bquant_offset integer : bframe quantizer offset (100)

Other options
-noasm : do not use assembly optimized code (use)
-turbo : use turbo presets for higher encoding speed (don't use)
-quality integer : quality ([0..6]) (6)
-vhqmode integer : level of R-D optimizations ([0..4]) (1)
-bvhq : use R-D optimizations for B-frames (don't use)
-metric integer : distortion metric for R-D opt (PSNR:0, PSNRHVSM:1) (0)
-qpel : use quarter pixel ME (don't use)
-gmc : use global motion compensation (don't use)
-qtype integer : quantization type (H263:0, MPEG4:1) (0)
-qmatrix filename : use custom MPEG4 quantization matrix
-interlaced [integer] : interlaced encoding (BFF:1, TFF:2) (1)
-nopacked : disable packed B-frames mode (enabled)
-noclosed_gop : disable closed GOP mode (enabled)
-masking [integer] : HVS masking mode (None:0, Lumi:1, Variance:2) (0)
-stats : print stats about encoded frames (don't print)
-ssim [integer] : print ssim for every frame (accurate: 0 fast: 4) (2)
-ssim_file filename : output the ssim stats into a file
-psnrhvsm : print PSNRHVSM metric for every frame (don't print)
-debug integer : activate xvidcore internal debugging output (don't activate)
-vop_debug : print some info directly into encoded frames (don't print)
-nochromame : disable chroma motion estimation (enabled)
-notrellis : disable trellis quantization (enabled)
-imin integer : minimum I Quantizer (1..31) (2)
-imax integer : maximum I quantizer (1..31) (31)
-bmin integer : minimum B Quantizer (1..31) (2)
-bmax integer : maximum B quantizer (1..31) (31)
-pmin integer : minimum P Quantizer (1..31) (2)
-pmax integer : maximum P quantizer (1..31) (31)
-drop integer : frame Drop Ratio (0..100) (0)
-start integer : starting frame number (0)
-threads integer : number of threads (auto)
-slices integer : number of slices (1)
-progress [integer] : show progress updates every n frames (10)
-par integer[:integer] : set Pixel Aspect Ratio (1)
1 = 1:1
2 = 12:11 (4:3 PAL)
3 = 10:11 (4:3 NTSC)
4 = 16:11 (16:9 PAL)
5 = 40:33 (16:9 NTSC)
other = custom (width:height)
-help : print this help message

NB: You can define up to 64 zones via both the -zones and the -z[qw] options as needed.


I Will tell it Stax.

[stax76]

My replies here:

http://forum.doom9.org/showthread.php?p=1723169#post1723169

[L4a-Thompson]

hi all together,
@Stax - So many thanks for this great tool.

i have a wish for the next release.
Can you an a textfile with the description of your integrated Avisynth Plugins?

an example for Undot() i have these. is this posible to add this descriptions?




//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

Also, this program is "Philanthropy-Ware". That is, if you like it and feel
the need to reward or inspire the author then please feel free (but not obligated)
to consider joining or donating to the Electronic Frontier Foundation. This will
help keep cyber space free of barbed wire and bullsh*t.

See their web page at www.eff.org

***************

Okay, on to business.

WARNING - This version only runs on the Avisynth 2.5 alpha release.

UnDot is a simple median filter for removing dots, that is stray orphan pixels and
mosquito noise. It basicly just clips each pixel value to stay within min and max
of its eight surrounding neigbors.


USAGE - To use it just:

1) Place the UnDot.dll in a directory somewhere. You can get it from
www.trbarry.com/UnDot.zip

2) In your Avisynth file use commands similar to

LoadPlugin("F:\UnDot\UnDot.dll")
Avisource("D:\wherever\myfile.avi")
UnDot()

Of course replace the file and directory names with your own. There are no parameters.


KNOWN ISSUES AND LIMITATIONS

1) Requires either YUY2 or YV12 input.

2) Sorry, currently requires a P-III, Athlon, or higher. Needs SSEMMX support.

3) So far it has only been tested on SSEMMX (P3 & P4) machines.

4) In YV12 format it will filter both luma and chroma. In YUY2 format it will
only filter luma.

FILE LOCATIONS

For now, both source, this readme, and DLL should be at:

www.trbarry.com/UnDot.zip

A copy of this Readme_UnDot.txt file should be at:

www.trbarry.com/Readme_UnDot.txt

***************

Change Log:


2003/01/18 V 0.0.1.1 Use AvisynthPluginInit2

2002/11/03 V 0.0.1.0 Initial test release for Avisynth 2.5 alpha only


thanks for all your work
best reguards
L4a-Thompson

[L4a-Thompson]

for deen a short description:

deen is a set of assembly-optimised denoisers.
http://avisynth.nl/index.php/Deen

how to use:
Deen()
DeenMoreDetails = Deen("a2d",2,3,2)


and my question is why you remove FluxSmoth from the plugins?
undot is not realy an alternative although i like undot

[stax76]

@L4a-Thompson

I'm not sure Deen is available for x64, x86 development is currently stopped, it might continue but probably not, the thread for x64 is here:

http://forum.doom9.org/showthread.php?t=172068

[LoRd_MuldeR]

~closed~

x86 version has been discontinued, please use the x64 thread now:
http://forum.doom9.org/showthread.php?t=172068