StaxRip

[JohnAStebbins]

That's why I posted the link above :)
I didn't read to the second page, so I missed the HandBrake quote.

Once again, someone at AMD is operating in a vacuum. No patches for this have been socialized. Current HandBrake svn has none of this.

Not only is this really bad form to announce HandBrake support before discussing it with the HandBrake developers. But it also makes it impossible to independently validate any of their claims.

And if their patch resembles what they have delivered in the past, It *will not* get merged into HandBrake. We already have some really awful code for OpenCL scaling, DXVA decode, and QSV encode that is all substandard that must be fixed before we add more crap on top of crap.

[NikosD]

We already have some really awful code for OpenCL scaling, DXVA decode, and QSV encode that is all substandard that must be fixed before we add more crap on top of crap.

I agree with most you wrote, but one.

QSV encode is substandard and awful code ?

It's the first time I hear this, given that the code produced by a collaboration of Intel and Handbrake devs.

Are you sure about that ?

It's a little off - topic because we are posting at StaxRip's thread, but you really surprised me.

[stax76]

I changed the order for frame rate change and cutting but the audio track is still only half as long it should be.

I attached two images, as you can see the order is identical, 1.1.9.0 produces audio track as expected but 1.3.1.4 beta not.

Please mail me the log file, my email address can be found in the main menu, you can also post it to pastebin with auto expire enabled. For images you can use email, a image hoster or a cloud drive.

[JohnAStebbins]

I agree with most you wrote, but one.

QSV encode is substandard and awful code ?

It's the first time I hear this, given that the code produced by a collaboration of Intel and Handbrake devs.

Are you sure about that ?

It's a little off - topic because we are posting at StaxRip's thread, but you really surprised me.
Right, we should take this elsewhere (like HandBrake forums) if it continues.

There are many things I am not happy about with the QSV code in HandBrake. But it's my own fault for not taking the time to review it properly when it was introduced. At the time, I was busy with other things and just couldn't be bothered.

[stax76]

@Dogspoin

You are the second reporting the exact same problem, I'll think about how it can be improved, unfortunately it's a bit tricky, I believe these two methods will currently work:

1. change frame rate within the source filter section before you cut with the preview.

2. change frame rate after the cutting filter section after you cut with the preview.

[stax76]

@Dogspoin

Next version captures the frame rate and frame count that was used in the preview for cutting and uses this values for the blank script used for mkvmerge cutting. It should not matter where and how the frame rate was changed and StaxRip will detect when it was changed after cutting was performed and will show a assistant message:

The frame rate was changed after cutting was performed, please ensure that this change is happening after the Cutting filter section in the AviSynth script.

I hope it will solve the entire problematic, I'm not sure about crazy NTSC but hope it will be mostly fine.

[Dogspoin]

Great, both methods solved the problem.
Looking forward to next version. :)

@Dogspoin

You are the second reporting the exact same problem, I'll think about how it can be improved, unfortunately it's a bit tricky, I believe these two methods will currently work:

1. change frame rate within the source filter section before you cut with the preview.

2. change frame rate after the cutting filter section after you cut with the preview.

[ShamisOMally]

Having a bunch of problems here with batch encodes

If you set up the profile for encoding before you import, or even after you select the files, whatever you selected for Variable/average bitrate is discarded, and it sets some ungodly high number like 2982929 for it

If you do it one file at a time, it keeps the VBR setting you used, but any more than one file and it goes nuts

Also if you want my suggestion in the GUI with the audio track problem do what mediacoder does, have a drop down option and allow you to pick track 1 or track 2 before you start encodes, and then it will always take track 1 or track 2 etc depending on what you picked.

For some reason thet "Prefer english" option is not working, it just grabs the first audio track every time.

[stax76]

If you set up the profile for encoding before you import, or even after you select the files, whatever you selected for Variable/average bitrate is discarded, and it sets some ungodly high number like 2982929 for it

This looks like the same topic discussed a few days ago here:

http://forum.videohelp.com/threads/369913-StaxRip-x64-based-on-AviSynth-x64?p=2393151&viewfull=1#post2393151

Also if you want my suggestion in the GUI with the audio track problem do what mediacoder does, have a drop down option and allow you to pick track 1 or track 2 before you start encodes, and then it will always take track 1 or track 2 etc depending on what you picked.

This is currently not supported and I'm not gonna think about it unless somebody describes a very detailed scenario why it would be worthwhile. This looks like being incompatible with StaxRip's way of doing things and in any case would be huge amount of work with doubtful benefit.

If you describe your scenario in detail I might be able to help you, picking up tracks by language works. Please tell us the complete story starting what the source media is looking like in detail and how the source media was created.

[Jeroi]

Stax does the ripper be capable to do recursive encoding already? And organise the file structure like the original folder structure?

Edit seams not.

And I report again the batch encoder don't remember bitrate level fro encoder. I try to use --bitrate 900 in 2 pass mode but encoder keeps outputting 12000 bitrates and huge files. Please fix the 2 pass encoding mode.

To the audio encoding I would like check boxes that reads encode or allow or similar to prevent multiple audio track appearing in mp4 encodes. Currently it encodes always 2 tracks weather you want or not.

[stax76]

Stax does the ripper be capable to do recursive encoding already? And organise the file structure like the original folder structure?

There isn't direct support yet but the dialog for adding files for batch encoding supports drag and drop. It's possible to use windows explorer search to find all files including files in all sub-directories, the search result can then easily be added for batch processing via drag and drop.

And organise the file structure like the original folder structure?

I'm not sure what you mean.

[NikosD]

I tried using MP4 container with DTS and DTS-HD audio stream, but StaxRip didn't allow it.

I had to convert it to a different format in order to continue processing.

[stax76]

I can enable it if somebody confirms that MP4Box can mux it.

[jones1913]

In the past DTS audio was not supported by mp4box, I dont know if this has changed meanwhile.

L-Smash (https://github.com/l-smash/l-smash) muxer has support for DTS in mp4.

[stax76]

Here is a small guide on how to use StaxRip's MediaInfo GUI in windows explorer. Customizing the context menu of windows explorer can be done with the registry but there are some disadvantages and limitations. It's also possible with a shell extension and this is what I prefer. There is a generic shell extension called Open++ described here:

http://www.guidingtech.com/1363/add-items-customize-right-click-menu

and there is a Open++ alternative that can be downloaded here:

http://www.mediafire.com/download/9gna9modyj1sbvq/StaxExplorerMenu.7z

I've built it myself but never released it even though it wasn't simple to build, source code is included.

My configuration looks like so:

http://oi60.tinypic.com/2uzcd3p.jpg

The file types use macros which are defined in the options like so:

%video% = mpg avi ts vob mp4 d2v divx mkv avs 264 mov wmv part m2ts flv ifo h264 asf webm dgi m2ts mpeg mpv y4m avc hevc 265 h265 m2v mts
%audio% = mp2 mp3 ac3 wav m4a dts dtsma dtshr dtshd eac3 thd thd+ac3 ogg mka aac opus flac
%subtitle% = sub sup idx ass aas srt

The GUI has menu options to register and unregister the shell extension, it's a normal COM+ component so it simply calls regsvr32 with admin privileges. The shell extension is native/unmanaged and the GUI is a separate process so at no time the .NET CLR is loaded into explorer process space, I choose this design for memory efficiency.

I don't remember having tried Open++ but from the screenshot it don't seem to support top level menu which my extension does, it does however not support icons and dynamic arguments which does not really interest me.

Screenshot how my menu looks like (I struggled too many Win10 bugs so I'm back on Win7...):

http://oi60.tinypic.com/2zr14qp.jpg

I don't know what other MediaInfo GUIs exist, StaxRip offers a tab for every stream and it has a filter function:

http://oi60.tinypic.com/2l9oabl.jpg

Here is another related tool of mine, locally I have a slightly improved version, I use this mainly to easily clean up my menu, I hate it when applications trash it:

http://www.stax76.bplaced.net/index.php?slab=filetyperegistryviewer

http://www.stax76.bplaced.net/files/applications/FileTypeRegistryViewer/FileTypeRegistryViewer.png

Also useful sometimes the MediaInfo folder view found in StaxRip's advanced menu. It features a context menu with various options. I plan to add user defined custom columns and make it optionally recursive to include sub-folders and to add a filter feature to find any property including properties not shown.

http://oi58.tinypic.com/282nci8.jpg

[SeeMoreDigital]

In the past DTS audio was not supported by mp4box, I dont know if this has changed meanwhile.

L-Smash (https://github.com/l-smash/l-smash) muxer has support for DTS in mp4.Word to the wise...

Although it's possible to place DTS audio within the .mp4 container, it can only be done as a 'private stream', as it's not officially supported by the standard ISO/IEC 14496 MPEG-4 standard.

Which means there's no obligation for hardware playback devices to support it!


Cheers

[Kurtnoise]

Hi SMD,

Word to the wise...

Although it's possible to place DTS audio within the .mp4 container, it can only be done as a 'private stream', as it's not officially supported by the standard ISO/IEC 14496 MPEG-4 standard.

Which means there's no obligation for hardware playback devices to support it!

It's time to update your skills...;) This has been officially supported since 2011 according to the specs (http://www.etsi.org/deliver/etsi_TS/102100_102199/102114/01.03.01_60/ts_102114v010301p.pdf). Thats why it's implemented in l-smash tools.


And I confirm, DTS is not supported yet by the GPAC tools...

[SeeMoreDigital]

Hi SMD,


It's time to update your skills...;) This has been officially supported since 2011 according to the specs (http://www.etsi.org/deliver/etsi_TS/102100_102199/102114/01.03.01_60/ts_102114v010301p.pdf). Thats why it's implemented in l-smash tools.Oh wow, my profuse apologies... How did I miss this? What was I doing in August 2011?

Does anyone have any conformant samples I can test with my hardware playback devices. A channel check sample would be nice?

Cheers

[NikosD]

Also useful sometimes the MediaInfo folder view found in StaxRip's advanced menu. It features a context menu with various options. I plan to add user defined custom columns and make it optionally recursive to include sub-folders and to add a filter feature to find any property including properties not shown.



I've been looking for those features of MediaInfo folder view.
The ability to include sub-folders and the addition of interlaced property and scan type.

A user defined column and a filter to find properties are very useful.

[ShamisOMally]

Stax does the ripper be capable to do recursive encoding already? And organise the file structure like the original folder structure?

Edit seams not.

And I report again the batch encoder don't remember bitrate level fro encoder. I try to use --bitrate 900 in 2 pass mode but encoder keeps outputting 12000 bitrates and huge files. Please fix the 2 pass encoding mode.

To the audio encoding I would like check boxes that reads encode or allow or similar to prevent multiple audio track appearing in mp4 encodes. Currently it encodes always 2 tracks weather you want or not.

Ditto, I am getting this as well. Makes doing batch encodes impossible

[stax76]

Stax does the ripper be capable to do recursive encoding already?

Yes, in the next release.

And I report again the batch encoder don't remember bitrate level fro encoder. I try to use --bitrate 900 in 2 pass mode but encoder keeps outputting 12000 bitrates and huge files.

I'll investigate it.

Currently it encodes always 2 tracks weather you want or not.

There is a audio profile called 'No Audio'.

[tamasnemeti]

Hello, I am new to this forum and I am not a power user or an encoding enthusiast. I am trying to save space by converting stuff to HEVC and cutting down audio quality in some cases as well.

So far everything is working perfect, only had one problem yet (still have it).

Basically I have an episode of Archer on my hand, with two audio streams. If I want to reencode the streams to a lower bitrate (did not test higher) then StaxRip uses the raw output (? not sure here) which is around 4500kpbs. I don't see why it would do that, but it definitely does. It also includes a PGS sub which does not seem to be supported (?), but I can do without it and remove it. They might be in connection(?). Just muxing the audio does what it is designed to.
Here is two pictures:
https://p1.picsto.re/4bt5d.png
https://p1.picsto.re/pUgrD.png

On all other movies/series it works just fine...am I missing something?

I have a second question about batch encoding. I understand I can modify the container to include two subs (manually browsing the additional ones) for single encodes, but is it possible to include them automatically when doing a batch? Lets say, from the temp folders?

[stax76]

Hello and welcome,

I guess it's a bug in ffmpeg, please mail me the log file.

It also includes a PGS sub which does not seem to be supported.

You mean not supported by MP4 or your playback device/software?

I have a second question about batch encoding. I understand I can modify the container to include two subs (manually browsing the additional ones) for single encodes, but is it possible to include them automatically when doing a batch? Lets say, from the temp folders?

It's supposed to add subtitles automatically so it could either be a configuration problem or a bug. The routine that adds the subtitles is identical in normal and batch mode. In the options under subtitles the languages to add can be configured, the default is English and your local system language. There is also a convert option which might help with the problem PGS being not supported. It makes a difference if subtitle demuxing is enabled which is the default, next version will have a new GUI for audio and subtitle demuxing.

[tamasnemeti]

Thank you for the prompt reply!

This is what I get when trying to encode while a sub with .sup extension is included during the process.
Checking the "Convert Sup (PGS/Blu-ray) to Sub (IDX/DVD)" box did not make a difference either.
https://p1.picsto.re/g1NKZ.png

About the subtitles: thank you for enlightening me, it works just fine now!

You can find a log attached (includes the .sup error and the high bitrate stream 'bug' as well). Let me know if this isn't the log you are looking for...

Edit.: It seems to note that
Writing the destination file failed.
Aborted at file position ******.

I am running the application as Admin.

[stax76]

It can take a while until attachments get approved so I recommend to use mail or pastebin. Regarding PGS support in mkvmerge, I believe mkvmerge will mux PGS ripped with MakeMKV or eac3to, I don't know what could be the problem, you have to convert the subtitles somehow, I also don't know why StaxRip's sup to sub routine failed here, I can test if the routine works when I see the log file. You absolutely don't need to run StaxRip or any included application as admin.

[NikosD]

StaxRip complains about MKVmerge with this file, but MKVmerge works fine as Mosu said in his thread:

http://forum.doom9.org/showthread.php?p=1726889#post1726889

The file is this:
http://www.filedropper.com/1latraviata

The complain is this:

mkvmerge v7.9.0 ('Birds') 64bit
Error: The file 'D:\Video\Test Audio Video\Video HD test\1080i\H.264\1.La Traviata temp files\1.La Traviata ID3 English.sup' has unknown type. Please have a look at the supported file types ('mkvmerge --list-types') and contact the author Moritz Bunkus <moritz@bunkus.org> if your file type is supported but not recognized properly.

------------------------------------------------------------
Error Muxing using mkvmerge
------------------------------------------------------------

Muxing using mkvmerge failed with exit code 2

mkvmerge v7.9.0 ('Birds') 64bit
Error: The file 'D:\Video\Test Audio Video\Video HD test\1080i\H.264\1.La Traviata temp files\1.La Traviata ID3 English.sup' has unknown type. Please have a look at the supported file types ('mkvmerge --list-types') and contact the author Moritz Bunkus <moritz@bunkus.org> if your file type is supported but not recognized properly.

[sneaker_ger]

No lines = 0 byte extracted file = cannot be detected as sup

[stax76]

Adding messages would be difficult since adding subtitles can happen from different locations and in different modes so I just changed it to silently ignore 0 byte subtitles.

edit:

When there are no normal subtitle files StaxRip checks mkv and mp4 for subtitles and adds mkv and mp4 as subtitle source, this will result in mkvmerge adding the empty subtitle without error code, I can't do much here.

[tamasnemeti]

It can take a while until attachments get approved so I recommend to use mail or pastebin. Regarding PGS support in mkvmerge, I believe mkvmerge will mux PGS ripped with MakeMKV or eac3to, I don't know what could be the problem, you have to convert the subtitles somehow, I also don't know why StaxRip's sup to sub routine failed here, I can test if the routine works when I see the log file. You absolutely don't need to run StaxRip or any included application as admin.

Here it is.
http://pastebin.com/7nzJU7RK

[stax76]

It's unclear why eac3to don't transcode from DTS to AC3, maybe it works with the latest StaxRip version. I'm not sure but the default processing method for this type of operation might have changed using ffmpeg instead of eac3to, you can also force to use ffmpeg, there is a option for this in the audio dialog but you should use the latest StaxRip version.

[Patman]

Here it is.
http://pastebin.com/7nzJU7RK
Hi tamasnemeti,

I saw that you use arcsoft decoder with eac3to. Which version do you use? The newer ones make some problems.

[stax76]

the bulk of the work of VapourSynth integration is done, the biggest problem is distribution of everything needed which is VapourSynth, Python and plugins to run QTGMC. There are few options:


make one big package and integrate everything
make one big installer with install options
provide download links and setup instructions for AviSynth+, VapourSynth, Python, plugin bundles, etc. Some people might have problems to follow download and install instructions and some people might use outdated components which might fail to work, this is more experience rather than being overly pessimistic

[luigizaninoni]

provide download links and setup instructions for AviSynth+, VapourSynth, Python, plugin bundles, etc.
[/LIST]

I must be missing something: why would you want to install both Avisynth+ AND Vapoursynth ?

[stax76]

Some things are currently not working at all with AviSynth+ x64, QTGMC is practically unusable even in single threaded mode, some goes for other complex scripts and plugins. In VapourSynth x64 QTGMC and various other things work just fine. VapourSynth development is very active while there isn't much if any visible AviSynth+ development. Python is more difficult than AviSynth but also more powerful and extremely popular especially for people with Linux background, in StaxRip it's not making a big difference because most things can be done with the GUI, it's possible to switch between scripting engines even if files are already loaded, not even the index must be recreated, profiles and menus are completely separated, so when VapourSynth is used nothing AviSynth related is visible.

[luigizaninoni]

I see, I like the idea of being able to switch between the two engines.

I have no experience with Vapoursynth, and it seems to me that it is still lacking some avs plugins and scripts that I occasionally use (smoothadjust, MCTD et al.).
However, given that, as you say, it is in very active development, I am willing to try, they might fill the gaps in a relatively short time.

From my point of view solution n.1 (or maybe n. 2) would be the easiest. In my opinion it ought to be the best also for the general public: I think that a noob would be more scared by the idea of downloading and installing programs, plugins, bundles etc. rather than by the mere size of a single download. ymmv, of course.

[stax76]

The downside of 1. and 2. is a download size of 100-150 MB and disc space up to 400 MB which is somehow insane. :)

StaxRip itself is very efficient in regard of file size I believe, it should be around 50 000 lines code resulting in 1,3 MB executable, it has a lot more features than many applications at comparable size.

What also could be done is a dynamic dialog that analyses the environment and list everything missing, outdated or damaged, it would have descriptions and instructions and download links.

[tamasnemeti]

Hi tamasnemeti,

I saw that you use arcsoft decoder with eac3to. Which version do you use? The newer ones make some problems.

I am not quite sure how to downgrade it to be honest.
Also, forcing ffmpeg has no effect on it whatsoever.

If I just mux the audio that is working fine, but the DTS audio eats up 220 megs of space, where the video stream is around 180-200 per episode. AC3 448kbps would be around 70 megs, which is a nice improvement and the quality would be good enough for me. You see, the size difference would be around 10-15 gigs for the whole series which is not negligible for me.

Not sure what to do..

[stax76]

Please remux to a 50 MB file using mmg or mkmerge-gui and retry re-encoding with the latest StaxRip release 1.3.1.4, if the problem persists then please upload the 50 MB file to dropbox or somewhere else and send me the link as private message.

[Lupissimo]

As can be seen by the attached logs, the latest version 1.3.1.4 changes the fps from 23.976 to 25fps, whereas the 1.2.2.2 version encodes correctly:

[Patman]

I am not quite sure how to downgrade it to be honest.
Also, forcing ffmpeg has no effect on it whatsoever.

If I just mux the audio that is working fine, but the DTS audio eats up 220 megs of space, where the video stream is around 180-200 per episode. AC3 448kbps would be around 70 megs, which is a nice improvement and the quality would be good enough for me. You see, the size difference would be around 10-15 gigs for the whole series which is not negligible for me.

Not sure what to do..

Hi,

use command eac3to.exe -test and you will see which version is installed. ArcSoft version 1.1.0.0 works fine. If you want you can send me a link as private message and i will test to encode the audio file.


As can be seen by the attached logs, the latest version 1.3.1.4 changes the fps from 23.976 to 25fps, whereas the 1.2.2.2 version encodes correctly:

Hi,

i can't open attached files, please use pastebin.

[stax76]

first alpha/tech preview adding full first class VapourSynth support. I'm not aware of broke or missing things but quite a bit code was changed or added...


New: Added full first class VapourSynth support including plugins and profile for QTGMC
New: Added possibility to switch dynamically between any source filter back and forth including DGSource and DGSourceIM. Indexing is triggered automatically in case no index file is present
New: Added vinverse plugin to remove residual combing from NTSC
New: Added GUI for demuxing MKV and MP4
New: Added feature to easily enable certain parameters for certain filters in the AviSynth editor. Currently supported are FFVideoSource and DGSource, more parameters and filters might be supported on request. Use it by right-clicking on FFVideoSource or DGSource in the AviSynth editor, the menu shows then NTSC options and hardware cropping and resizing options.
New: Added Play option for MPC playback in the AviSynth editor
New: Added two new options in the dialog to define files for batch processing to add a entire folder and a entire folder including sub-folders
New: Added new subtitle UI based on data view
New: Added option to generate subtitle names based on the subtitle language
Fix: Disabled audio demuxing for MKV and MP4 by DGIndexNV and DGIndexIM because it's already demuxed by MP4Box and mkvextract
Fix: Tools/Directories/Plugins wasn't pointing to the AviSynth+ plugin directory
Update: QSVEncC 2.0 beta 7
Update: x265 1.7+207
Tweak: DTS bitrate is now unrestricted
Tweak: Moved field processing filters to dedicated category like before in StaxRip x86
Tweak: Replaced LinkLabels with Buttons in eac3to dialog
Tweak: The help for all included AviSynth plugins can now be accessed per menu in the AviSynth editor
Tweak: ProjectX is enabled by default in case Java exists, otherwise dsmux will handle MPEG-2 TS
Tweak: In the dialog to define files for batch processing the 'Create Jobs' option was renamed to 'Demux and index before adding jobs', regardless of if this option is enabled jobs are always created
Tweak: Removed x86 and VS C++ 2013 from AviSynth+ installer bringing it from 18 MB down to 4 MB. Very often VS C++ 2013 is already installed and in case it ain't already installed StaxRip will show the Apps dialog which has a download button for VS C++ 2013.
Tweak: replaced avs4x26x with ffmpeg


http://thumbnails108.imagebam.com/41765/adee8a417643493.jpg (http://www.imagebam.com/image/adee8a417643493) http://thumbnails105.imagebam.com/41765/f4d9a1417643496.jpg (http://www.imagebam.com/image/f4d9a1417643496) http://thumbnails108.imagebam.com/41765/c7cf22417643498.jpg (http://www.imagebam.com/image/c7cf22417643498) http://thumbnails108.imagebam.com/41765/f5d8ed417643500.jpg (http://www.imagebam.com/image/f5d8ed417643500) http://thumbnails105.imagebam.com/41765/3415cd417643501.jpg (http://www.imagebam.com/image/3415cd417643501) http://thumbnails108.imagebam.com/41765/f9b9bb417643505.jpg (http://www.imagebam.com/image/f9b9bb417643505) http://thumbnails108.imagebam.com/41765/dc720a417643508.jpg (http://www.imagebam.com/image/dc720a417643508) http://thumbnails105.imagebam.com/41765/c5a7b0417643509.jpg (http://www.imagebam.com/image/c5a7b0417643509)

http://www.mediafire.com/download/2fsqchz4juse7m2/StaxRip_x64_tech_preview.7z

[Lupissimo]

@patman: https://www.dropbox.com/s/h2nzff8y1fbdcly/Logs.zip?dl=0

[stax76]

@Lupissimo

What the latest release does is it demuxes VOB with DGIndex to m2v, this is a pretty bad idea, the latest alpha shows a message box every time a user opens VOB stating clearly that it has many disadvantages over ripping with MakeMKV, there are some alternative methods to MakeMKV involving tools like AnyDVD, DVD Shrink, DVDSubEdit, ProjectX, BDSup2Sub++, it can be absolutely done and works even with DVD structures that have problematic timestamps, it's just MakeMKV is much more convenient. What the old StaxRip did different with the fps is using MediaInfo to detect it but this causes issues with other sources so I can't do anything here. Also StaxRip x86 was using DGDecode for DVDs which is not available for x64, ffms2 works just as well and I added a new feature for changing FFVideoSource and DGSource parameters dealing with NTSC conveniently with the context menu in the new scripting editor, it can be seen in one of the screenshots and it can be expanded for other filters on request. It's not clear if DGIndex or ffms2 causes the fps problem, if you really want to process this way you can try another source filter or manually add AssumeFPS to the script. For properly processing VOB automatically I would basically have to write a demuxing tool which currently don't exist in order to successfully handle DVD structures with problematic timestamps. Pretty much all tools don't handle this properly with few exceptions like Handbrake and VidCoder which I believe do also handle other issues properly like erroneous TS files so I think the Handbrake engine is fairly good.

[burfadel]

The new Staxrip doesn't encode to x265 properly.

This is using the default settings for x264 and x265. Also, no filters, resize, cropping etc apart from deinterlacing (did this for the filters and encoder to isolate the issue):
X264: https://www.dropbox.com/s/wf35tsn15286y4b/NewStax-x264.mkv?dl=0
x265: https://www.dropbox.com/s/0id29obdafxyh8p/NewStax-x265.mkv?dl=0

Of course, it makes sense it is related to the piping from ffmpeg to x265, since x264 does not have the piping. It worked fine in the latest non-tech preview Staxrip.

[burfadel]

@Stax
Oh wait! I found the solution :)

You need to add:
--y4m

to the x265 command line in the tech preview. Problem solved!

Also, very importantly, for x265 rev 211 onwards (not 207 as in the tech preview), you need to add:
--output-depth 10
http://x265.readthedocs.org/en/latest/cli.html#cmdoption--output-depth
for 10-bit output, otherwise it will default to 8 bit output. So, an option needs to be added.

Also, there is a recently new option:
--limit-refs
http://x265.readthedocs.org/en/latest/cli.html#cmdoption--limit-refs

[stax76]

@burfadel

I was hoping replacing avs4x26x with ffmpeg would be fine, I've seen this effect before with piping but am rather clueless what it is and how it can be fixed other then reverting to avs4x26x, does anybody know what's happening here?

VapourSynth has a own piping tool, maybe you want to try VapourSynth, it has great potential as far as I can tell, everything I tried just worked wonderfully, I definitively want to add more plugins for both AviSynth+ and VapourSynth, as long as the download is below 100 MB it's no problem I guess, currently it's "only" 60 MB.

[stax76]

@Stax
Oh wait! I found the solution :)

You need to add:
--y4m

to the x265 command line in the tech preview. Problem solved!

Also, very importantly, for x265 rev 211 onwards (not 207 as in the tech preview), you need to add:
--output-depth 10
http://x265.readthedocs.org/en/latest/cli.html#cmdoption--output-depth
for 10-bit output, otherwise it will default to 8 bit output. So, an option needs to be added.

Also, there is a recently new option:
--limit-refs
http://x265.readthedocs.org/en/latest/cli.html#cmdoption--limit-refs

OK, thanks

[burfadel]

I also notice in the default filter list, you have crop listed before 'Field' (deinterlacing). Shouldn't deinterlacing be done before cropping?

[stax76]

I also notice in the default filter list, you have crop listed before 'Field' (deinterlacing). Shouldn't deinterlacing be done before cropping?

I'm not sure, for mod 2 it's probably a problem depending on used filters but for mod 16 it's faster to crop first when you use a slow deinterlacer like QTGMC, I always crop with mod 16 and never resize.

[burfadel]

I'm not sure, for mod 2 it's probably a problem depending on used filters but for mod 16 it's faster to crop first when you use a slow deinterlacer like QTGMC, I always crop with mod 16 and never resize.

Ah ok! Come to think of it, since it's cutting by mod 16 etc it would be better to crop first :).

I notice in the tech preview that abort doesn't work with x265 either. I guess it was pointing to the old pipe method? If you pause and abort ffmpeg, it pauses and aborts x265 cleanly :).