StaxRip

[stax76]

Originally Posted by detmek

For some reason encoder show error if I use QSV decoding and cropping. If I turn of QSV decoding it works but trimming can not be used.
Here is a log file:
MARINA VISKOVIC - GDE SAM GRESILA_StaxRip.log

I couldn't manage to download from 4shared, for log files there is nothing better then pastebin with auto expire.

Unfortunately I already found the first problem, crop and trim should only be applied when hardware decoding is used, I upload a new build tomorrow.

edit:

fixed build using crop and trim only when hardware decoding is used:

http://www.mediafire.com/download/g8...QSVEncC_fix.7z

[detmek]

Still error:

https://www.dropbox.com/s/pzdnzatsaz...axRip.log?dl=0

Does Dropbox works?

[stax76]

DropBox is great (with large traffic they lock files quickly though). The command line looks good except -sar is used even when resizing is enabled, this should be a bug. I had the same error and don't really know what's wrong but we'll find out.

[dejong12]

With 1.3.1.0 and 1.3.1.1 the encoding speed with NVEnc drops to ~30fps with TDeint enabled. Version 1.2.2.2 with Yadif keeps the speed at around ~105fps while both versions have ~135fps without a deinterlace filter. All other settings are the same on both versions. Any reason why the x64 versions have such low encoding speeds? Indexing also takes three times longer on the x64 than on the x32 version too. The video is a 1080i AVC TV recording in MKV format.

[detmek]

It seams that it won't work only when crop is used. Maybe my CPU does not support crop?

P.S. I switched OS to Windows 7 SP1 due to a problems with WiFi adapter. Crop won't work even under Win 7.

[stax76]

With 1.3.1.0 and 1.3.1.1 the encoding speed with NVEnc drops to ~30fps with TDeint enabled.

Did you try to investigate it with AVSMeter? You can find AVSMeter at Tools/Advanced/AVSMeter. You could also try DSS2 using LAV Filters which you can configure at Tools/Advanced/LAV Filters config, Nikos reported that deinterlacing works with it. Overall I think there are quite a few options for deinterlacing.

Indexing also takes three times longer on the x64 than on the x32 version too. The video is a 1080i AVC TV recording in MKV format.

you mean ffms2? You can compare the ffms2 indexing speed against l-smash-works, it depends also on the source, there are differences. Can you record directly as MKV? I never knew a software that can do it.

It seams that it won't work only when crop is used. Maybe my CPU does not support crop?

P.S. I switched OS to Windows 7 SP1 due to a problems with WiFi adapter. Crop won't work even under Win 7.

What CPU do you use? I'll try it with my Ivy Bridge CPU.

[detmek]

Intel Pentium G3220 Haswell.

[dejong12]

Originally Posted by stax76

Did you try to investigate it with AVSMeter? You can find AVSMeter at Tools/Advanced/AVSMeter. You could also try DSS2 using LAV Filters which you can configure at Tools/Advanced/LAV Filters config, Nikos reported that deinterlacing works with it. Overall I think there are quite a few options for deinterlacing.

This is being outputted with TDeint enabled in 1.3.1.1.

D:\StaxRip 1.3.1.1>"D:\StaxRip 1.3.1.1\Tools\AVSMeter\AVSMeter64.exe" "D:\Record
ed TV\Korra S4 FHD\De Legende van Korra - S04E01 temp files\De Legende van Korra
 - S04E01_new.avs"

AVSMeter 2.0.2 (x64)
AviSynth+ 0.1 (r1825, MT, x86_64) (0.1.0.0)

Number of frames:                33247
Length (hh:mm:ss.ms):     00:22:09.880
Frame width:                      1280
Frame height:                      720
Framerate:                      25.000 (25/1)
Colorspace:                       YV12

Frame (current | last):         7137 | 33246
FPS (cur | min | max | avg):    26.78 | 13.70 | 41.64 | 32.40
Memory usage (phys | virt):     114 | 117 MB
Thread count:                   9
CPU usage (current | average):  35% | 35%

Time (elapsed | estimated):     00:03:40.312 | 00:17:06.157

Press 'Esc' to cancel the process...

And this is being outputted with Yadif enabled in 1.2.2.2.

D:\StaxRip 1.2.2.2 beta>"D:\StaxRip 1.2.2.2 beta\Tools\AVSMeter\AVSMeter64.exe" "D:\Record
ed TV\Korra S4 FHD\De Legende van Korra - S04E01 temp files\De Legende van Korra
 - S04E01_new.avs"

AVSMeter 1.9.8.0 (x86)
AviSynth+ 0.1 (r1825, MT, i386) (0.1.0.0)

Number of frames:                33247
Length (hh:mm:ss.ms):     00:22:09.880
Frame width:                      1280
Frame height:                      720
Framerate:                      25.000 (25/1)
Colorspace:                       YV12

Frame (current | last):         15099 | 33246
FPS (cur | min | max | avg):    112.0 | 65.88 | 118.1 | 101.4
Memory usage (phys | virt):     91 | 89 MB
Thread count:                   9
CPU usage (current | average):  58% | 56%

Time (elapsed | estimated):     00:02:28.858 | 00:05:27.753

Press 'Esc' to cancel the process...

Originally Posted by stax76

you mean ffms2? You can compare the ffms2 indexing speed against l-smash-works, it depends also on the source, there are differences. Can you record directly as MKV? I never knew a software that can do it.

Yeah with ffms2, but it's faster than I initially said, but a second slower than 1.2.2.2.

I can only record in .wtv because I use Windows Media Center and I haven't found a suitable successor yet. I use VideoRedo to cut out the commercials and save the resulting video in .mkv without recoding.

[stax76]

@detmek

Rigaya replied that it’s a bug of QSVEncC

@dejong12

It seems TDeint is rather slow, you could try Yadif with DSS2.

[detmek]

Thanks. So, we are waiting for a new version.

[NikosD]

A lot of fixes in latest β3 QSVEncC update, among them the crop issue:
http://rigaya34589.blog135.fc2.com/blog-entry-623.html

[Washka]

Originally Posted by NikosD

A lot of fixes in latest β3 QSVEncC update, among them the crop issue:
http://rigaya34589.blog135.fc2.com/blog-entry-623.html

Testing

[luigizaninoni]

Made some more tests on Staxrip 64 bit. In my opinion there are a few important issues:

For the following tests the configuration is: StaxRip x64 pre-release or Staxrip x32 1.2.2.0 - i7-4770S – x265 slow preset – Encode clip 1h 41m (same clip used throughout the tests)

Script:
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\ffms2\ffms2.dll")
Import("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\QTGMC\QTGMC.avsi")
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\masktools2\masktools2.dll")
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\mvtools2\mvtools2.dll")
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\nnedi3\nnedi3.dll")
LoadPlugin("C:\Users\luigi.TZMS\Desktop\Video\Staxrip64\Tools\Plugins\RgTools\RgTools.dll")
FFVideoSource("C:\Users\luigi.TZMS\Desktop\sherlock temp files\sherlock.m2v", cachefile = "C:\Users\luigi.TZMS\Desktop\sherlock temp files\sherlock.ffindex")
QTGMC(Preset="Slow") (InputType=1 for progressive)
SelectEven() (only for interlaced)
RemoveGrain()


ISSUE N.1: AVISYNTH+ GRADUALLY SLOWS DOWN


To show the progressive slowdown of Avisynth+ I made two checkpoints: one at 5.000 frames and one at 150.000 frames (near the end of the encode)

Single-threaded Avisynth+:
Progressive: Encode starts at full steam: CPU at average 75%, fps 19,20 at 5.000-frame checkpoint. CPU is split into about 60% x265, and 15% avs4x26x

However encode gradually gets slower: fps and cpu keep going down. At 150.000-frame checkpoint we have CPU 50% (x265:35% and avs4x26x:15%) and fps 14,50. Fps have gone down 25%

Interlaced: At 5.000 frame checkpoint CPU at average 48% (32% x265 and 16% avs), fps 10,46. Obviously processing interlaced requires more work, so avs produces less frames for x265 to work on. The slowdown of the encoding becomes quite serious on interlaced: at 150.000-frame checkpoint fps are 2,65. Fps have gone down 75% !!

It seems that Avisynth+ is producing less frames over time, so x265 becomes less busy. The more complex the avs script, the more Avisynth+ slows down over time.

I repeated the same test with traditional Avisynth (not plus), and the problem does not exist:
Progressive: 17,75 fps at first checkpoint, 17,89 at second checkpoint. CPU steady around 70%
Interlaced: 11,44 fps and 11,51 respectively; cpu around 51-54%

ISSUE N.2: MULTITHREADED AVISYNTH+ CRASHES TOO OFTEN

For multithreaded scripts add:
SetFilterMTMode("DEFAULT_MT_MODE", 2)
SetFilterMTMode("FFVideoSource", 3) (at start of script)
Prefetch(6) (at end of script)

This issue has already been discussed in this thread, but the problem has not been solved yet. Encoding starts very fast, nearly 22 fps. However at a certain unpredictable point it crashes: it may be at the very beginning, it may be after a couple of hours, it seems totally random. If you are doing a very short encode, you might even manage to complete it without errors. Anyway MT Avisynth+ can’t be trusted at the moment.

ISSUE N.3: SOME 64-BIT PLUGINS ARE NOT AVAILABLE

For my workflow, I sometimes use MCTemporalDenoise for some noisy clips. I managed to find most 64-bit plugins required. However, I haven’t been able to find DCTFilter-64bit, so MCTD can’t be used. Is there any workaround, by the way ?

Although 64bit versions exist for most plugins, there is a still a fair number of 32bit-only dlls. So for more complex workflows you need to stick to avisynth-32bit.

CONCLUSIONS
Although very promising, Staxrip 64bit is not ready for prime time. The problems, it seems to me, lie not in Staxrip itself, but rather in Avisynth+ and/or its plugins (I don’t know exactly where the problem/s lie)

So in my opinion Staxrip 32bit should be kept alive at least for the time being, until problems are solved; not necessarily with the introduction of new features, but at least issuing maintenance releases.

Thanks Stax76 for your great work. Staxrip32 is an excellent program, and I am sure that, eventually, Staxrip64 will become very good,too

[stax76]

@luigizaninoni

Thanks for all the testing and feedback. I really hope these problem can be fixed within a few months, otherwise I will consider making StaxRip builds for both 64x and x86 or start with C++ programming.

StaxRip x64 1.3.1.2 pre-release (2015-05-19)

• Added x265 switch --output-depth to choose between 8bit and 10bit output
• Improved 'Demux Configuration' dialog
• Fixed and changed cropping and resizing with QSVEncC, there is now for both crop and resize a special AviSynth filter profile 'Hardware Encoder' but if AviSynth is bypassed by enabling hardware decoding in QSVEncC then it's not necessary to use this special profiles, any crop or resize profile will do in this case.
• Fixed bug audio streams not being detected for M2TS files
• Updated x265 to x265_1.7+2
• Updated QSVEncC to 2.0 beta 3

http://code.fosshub.com/StaxRip/downloads

https://github.com/stax76/staxrip/releases

[burfadel]

@Stax

QAAC 2.49 was just released yesterday.

[stax76]

Thanks, how did you find out? I've enabled a 'Watch' feature now on the qaac github page, I'm not sure what is does exactly though.

[burfadel]

I saw a new version of Staxrip, and just thought I'd check out the pages for QAAC etc, since I know it's in active development . In other words, I wasn't expecting it, but since I use Firefox all I had to do was type in qa in the address bar and it was the first thing to show .

I notice there still isn't an inverse telecine and decimate filter in the latest build. This is vital if encoding telecined (29.97 fps) material. The filter you had in the 32-bit Staxrip, Decomb, was fine . There is a 64 bit version of it:
http://avisynth.nl/index.php/AviSynt...2B_x64_plugins

I also notice you changed the 'tools' folder to 'apps'. If people just extract over what they already have, they may have a superfluous 'tools' folder... easy fixed I know, but may be worth mentioning .

[Alexander]

@ Frank

[StaxRip x64 1.3.1.2 pre-release (2015-05-19)

with me DGDecodeNV does not work
error message

[Window Title]
StaxRip

[Main Instruction]
Failed to open source, try another method?

[Content]
DGSource: Invalid index file!
(Source.avs, line 2)

[stax76]

@Alexander

There is a issue you can fix yourself:

Tools > Settings > Demuxing > select DGIndexNV > Edit > Input Formats and Input File Types must be comma separated.

I'm still getting errors however, I try to find what's wrong.

@burfadel

I'm not sure Decomb works on Win10, I only include things that work on Win10, I'll try it. I didn't think renaming Tools to Apps could break something. Microsoft uses the name 'App' for both mobile and desktop applications, they will also allow to add desktop applications to the app store. When Win10 arrives I will try to add StaxRip to the app store, I don't know if it will work.

[videoh]

Originally Posted by stax76

I'm not sure Decomb works on Win10, I only include things that work on Win10, I'll try it.

It seems to work just fine on Win8.1 64-bit, so there's no reason it shouldn't work on Win10.