View Full Version : StaxRip
Magik Mark
25th February 2021, 04:34
Guys,
Is there a formula or best practice when upscaling 2k bluray to 4k?
I usually use 2pass VBR. I'm not sure how much bitrate to use. I don't want it to bloat or lose too much details.
There must be an ideal solution.
I also upscale the colorspace from 420 to 44416bit using z convert with dithering. Then downscale it to 4448bit when encoding
thanks
DavidRyan
25th February 2021, 08:27
I guess it's more desirable to leave contrasharp as an option so that users can make a choice themselves.
It doesn't matter whether it's false or true as long as MedianBlur2 is loaded.
Let's think of it as a reminder or a placeholder. :)
Ok so as soon as I see the Medianblur2 update commit, I'll add it to the profiles!
Thanks for looking into it :)
44vince44
25th February 2021, 10:54
You're welcome. Thanks to you and to JJKyle !
@Stax76 has updated Mediablur2, and I've updated the filter profiles. You'll see it in next beta hopefully!
tormento
25th February 2021, 11:57
2. Converted an 8-bit source to 10 bits
There is almost no gain in speed to have SMDegrain working in 10 bits instead of 16. I suggest you to use
SMDegrain (whatever, n16_out=true)
and then dither down in x265 (or whatever you use).
44vince44
25th February 2021, 17:32
This is strange. Beta 2.1.8.4 is out with updated medianblur2 to latest version that @Jkyle has tested, yet the error is still there when using contrasharp=True
@JKyle: updating Medianblur2 does not FIX the contrasharp issue in SMDegrain :=(
I tried to reproduce it in 2.1.8.3, and it didn't work.
You must have done something else that you forget to mention maybe... In the mean time, I'm still insvestigating.
Please do not update to 2.1.8.4 yet...
JKyle
25th February 2021, 18:17
@tormento,
Thanks for the info, but I was just testing if `contrasharp=true` option was working in a high bit depth situation.
@44vince44,
The answer is in the GitHub issue tracker. :)
44vince44
25th February 2021, 18:29
yes Thanks @Jkyle, I've read it. And I've provide proof to @Stax76 that the requirement is OFFICIAL. Because the docs do not mention it, but it is mentionned in the header of the SMDegrain avsi file. (see the issue tracker :-))
EDIT: this is being currently fixed by Stax76 :-)
EDIT2: @Stax76 has commited the mods and released a hotfix. I've tested it, and it works, the SMDegrain issue has been finally addressed. Thanks @Stax76 and again @Jkyle and @DavidRyan.
So please feel free to download beta 2.1.8.4 then to overwrite StaxRip.exe with the hotfix, from the same beta repository.
JKyle
26th February 2021, 08:16
If you updated to 2.1.8.4 Beta and overwrote StaxRip.exe with the hotfix exe file in @stax76's beta archive, you need to check if --selective-sao 4 has sneaked into all your x265 profiles. It's what I'm experiencing now.
https://i.imgur.com/IqxV7dK.jpg
This is because the default value for --selective-sao has been corrected to 0 per @tkozybski's issue report (https://github.com/staxrip/staxrip/issues/546), and it seems that somehow the wrong old default parameter setting has popped out and sneaked into the profile. But I don't know exactly why this kind of phenomenon happens.
Some of you may remember the --rskip 0 happening a while ago (v2.1.3.8 Beta and above). Because of this unexpected parameter setting, many users experienced a significant performance loss and reported this as an issue. I guess the same mechanism worked at that time: the default value of --rskip was adjusted and the old value popped out and sneaked in.
Maybe we need to study why this phenomenon happens. But in the meantime, remember that your parameter settings should always be checked out after an update without a reset.
stax76
26th February 2021, 11:37
I currently try to fix it.
JKyle
26th February 2021, 21:51
While trying to see if issue #548 (https://github.com/staxrip/staxrip/issues/548) is fixed, I've found that all my custom video encoder profiles are lost and reset to the factory settings with the hotfix StaxRip.exe. This is also true of the video encoder settings in my custom templates.
I believe this happens because of the fix of issue #546 (https://github.com/staxrip/staxrip/issues/546).
I can reconstruct my custom video encoder profiles and templates, but I guess most users will be embarrassed if they encounter this situation without prior info.
So I strongly believe that the next version, 2.1.8.5 Beta, should come with this warning:
"All custom video encoder profiles and video encoder parameter settings in custom templates are reset in the version.
Please back up your custom settings before update."
And in the meantime, if you are one of those who want to use the hotfix StaxRip.exe in @stax76's beta archive (as of now), don't forget to back up your custom settings before overwriting the StaxRip.exe file. :o
---
[UPDATE]
I see that custom video encoder profiles are saved as the submenus in Backup category.
https://i.imgur.com/XvCsCfg.jpg
So you just need to restore your custom templates. :)
lordalibaski
26th February 2021, 22:25
What's happened here then? think I have had this happen before but forgot what it was!! Just tried converting this recording with a runtime of 2 h 16 min, but only got 21mins of it!!
added the log file as attachment.
Thanks for any help.
JKyle
27th February 2021, 01:12
@lordalibaski,
Seems like you forgot file attachment does not work in this forum.
BTW, try another source filter and see if it works.
JKyle
27th February 2021, 02:00
MKVToolNix is updated to 54.0.0 today, and it resolves this issue (https://github.com/staxrip/staxrip/issues/489) related to 7.1 channel AAC extraction.
See my test (https://github.com/staxrip/staxrip/issues/489#issuecomment-786969509).
lordalibaski
27th February 2021, 16:25
@lordalibaski,
Seems like you forgot file attachment does not work in this forum.
BTW, try another source filter and see if it works.
Didn't know it wasn't working mate, here is the log file anyway
https://www.sendspace.com/file/937x93
Will try another source filter later just doing some other projects at the moment.
Atlantis
27th February 2021, 20:11
Suggestion. It would be great on the encoding line if you could see the hour job finishes. Not talking about the remaining time but the actual hour.
Yups
27th February 2021, 20:49
1. "Fixed-function" CQP encode using HEVC 10-bit is superb. The quality I get with this method is very close to the original. There may be the odd frame here and there where there may be very slight differences in the really fine facial details, but these are few and far between and to my eyes, the differences are difficult to spot and are completely unnoticeable during normal viewing.
It is really good on Tigerlake as well: https://forum.doom9.org/showthread.php?p=1936870#post1936870
4. I use the following settings (using QSV hardware as decoder gives a big speed boost and also keeps CPU usage low):-
--avhw --codec hevc --quality best --profile main10 --open-gop --async-depth 4 --fixed-func --cqp 36:36:36 --qp-offset 2:6:8 --output-res 1920x1080
Good settings. I would also add --bframes 16
lordalibaski
27th February 2021, 22:48
Tried using VapourSynth and it threw up this error straight away
Error Video encoding (2.1.8.4)
Video encoding returned error exit code: -1073741795 (0xC000001D)
--------------------------- Video encoding ---------------------------
x264 0.161.3048+17 gcc10.2.0 Patman Mod
C:\Users\jimmy\Desktop\Stax\Apps\Encoders\x264\x264.exe --crf 14 --sar 16:15 --synth-lib C:\Users\jimmy\Desktop\Stax\Apps\FrameServer\VapourSynth\VSScript.dll --output "C:\Users\jimmy\Desktop\To Convert\2000 ITF World DJ Championship_temp\2000 ITF World DJ Championship_out.h264" "C:\Users\jimmy\Desktop\To Convert\2000 ITF World DJ Championship_temp\2000 ITF World DJ Championship.vpy"
StaxRip.ErrorAbortException: Video encoding returned error exit code: -1073741795 (0xC000001D)
--------------------------- Video encoding ---------------------------
x264 0.161.3048+17 gcc10.2.0 Patman Mod
C:\Users\jimmy\Desktop\Stax\Apps\Encoders\x264\x264.exe --crf 14 --sar 16:15 --synth-lib C:\Users\jimmy\Desktop\Stax\Apps\FrameServer\VapourSynth\VSScript.dll --output "C:\Users\jimmy\Desktop\To Convert\2000 ITF World DJ Championship_temp\2000 ITF World DJ Championship_out.h264" "C:\Users\jimmy\Desktop\To Convert\2000 ITF World DJ Championship_temp\2000 ITF World DJ Championship.vpy"
at StaxRip.Proc.Start() in D:\Projekte\VB\staxrip\General\Proc.vb:line 374
at StaxRip.x264Enc.Encode(String passName, String commandLine, ProcessPriorityClass priority) in D:\Projekte\VB\staxrip\Encoding\x264Enc.vb:line 84
at StaxRip.x264Enc.Encode() in D:\Projekte\VB\staxrip\Encoding\x264Enc.vb:line 55
at System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at StaxRip.GlobalClass.ProcessJob(String jobPath) in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 339
ukmark
27th February 2021, 23:08
It is really good on Tigerlake as well: https://forum.doom9.org/showthread.php?p=1936870#post1936870
Good settings. I would also add --bframes 16
Unfortunately, can't use b-frames and b-pyramid with fixed-function on Ice Lake. I can use them when disabling fixed-function and have used 16 b-frames, but the encode is then about 6x slower. In a few years, I'll probably get the latest CPU when fixed-function AV1 encode is available - until then I'm quite happy with Ice Lake.:)
lordalibaski
27th February 2021, 23:48
Just tried indexing the files with ffmsindex and it looks like it's working, but last time I used ffmsindex it knocked my files out of sync this is why I preferred using DGIndex it worked like a charm but since I did a fresh install of staxrip from 64-2.1.8.1-Beta to 64-2.1.8.4-Beta the old problem has come back.
satstarter
28th February 2021, 02:15
Hi, i am new here and new with staxrip just a simple question is there a bug in staxrip ?
the color transfer in VUI in staxrip for hlg is arib-srd-b67 and it should be arib-std-b67 this is only in nvenc h.265
thats why i get an error while encoding
thanx in advance
JKyle
28th February 2021, 08:11
the color transfer in VUI in staxrip for hlg is arib-srd-b67 and it should be arib-std-b67 this is only in nvenc h.265
thats why i get an error while encoding.
thanx in advance
Thanks for the info. Your report is confirmed. There were typos in NVEnc, QSVEnc, and VCEEnc. I corrected them and submitted a PR.
In the meantime, use the Custom: field instead to avoid an error.
https://i.imgur.com/FCYrFBD.jpg
---
[Update]
Since the fix is merged, the next version will be OK.
JKyle
28th February 2021, 08:26
@lordalibaski,
Try the most recent DGMPGDec package (http://rationalqm.us/dgmpgdec/dgmpgdec2004.zip) for DGIndex and DGDecode.dll(MPEG2Source).
If the problem persists, maybe your source is peculiar. Report to the DGMPGDec forum (http://rationalqm.us/board/viewforum.php?f=7&sid=156cf1910e91561ba540b0808516e902) along with your video sample in that case.
You may be able to see why the problem occurs.
And about the VapourSynth-x264 encode error, report an issue on the GitHub issue tracker (https://github.com/staxrip/staxrip/issues) along with your log.
There's no figuring out why the problem occurs without detailed info.
satstarter
28th February 2021, 08:57
Thanks for the info. Your report is confirmed. There were typos in NVEnc, QSVEnc, and VCEEnc. I corrected them and submitted a PR.
In the meantime, use the Custom: field instead to avoid an error.
https://i.imgur.com/FCYrFBD.jpg
---
[Update]
Since the fix is merged, the next version will be OK.
:thanks:
lordalibaski
28th February 2021, 15:57
@lordalibaski,
Try the most recent DGMPGDec package (http://rationalqm.us/dgmpgdec/dgmpgdec2004.zip) for DGIndex and DGDecode.dll(MPEG2Source).
If the problem persists, maybe your source is peculiar. Report to the DGMPGDec forum (http://rationalqm.us/board/viewforum.php?f=7&sid=156cf1910e91561ba540b0808516e902) along with your video sample in that case.
You may be able to see why the problem occurs.
And about the VapourSynth-x264 encode error, report an issue on the GitHub issue tracker (https://github.com/staxrip/staxrip/issues) along with your log.
There's no figuring out why the problem occurs without detailed info.
Wierd one this, thought I would try it a different way, even though it worked before. Instead of joining the files with vobmerge I added the separate files into Staxrip using the merge file option used DGIndex as normal, it joined the files and actually converted the full 2hr 16mins tried it with the files joined and it failed again now I know there is nothing up with the file I have converted this before several times with Staxrip. I did try adding the latest package but no change.
When I get time I will register on that forum and ask them.
richardpl
1st March 2021, 19:13
Please do not use videoh software, its full of bugs and design flaws.
jlw_4049
2nd March 2021, 02:06
[emoji102]
Sent from my SM-G986U1 using Tapatalk
videoh
2nd March 2021, 03:07
Wierd one this, thought I would try it a different way, even though it worked before. Instead of joining the files with vobmerge I added the separate files into Staxrip using the merge file option used DGIndex as normal, it joined the files and actually converted the full 2hr 16mins tried it with the files joined and it failed again now I know there is nothing up with the file I have converted this before several times with Staxrip. I did try adding the latest package but no change. Cool, then vobmerge is the culprit. You just need DOS /B file+file+file etc., binary concatenation. That's what DGIndex(NV) does. It has nothing to do with Staxrip versions. Staxrip works just fine and as expected.
Wonder Woman
Atlantis
2nd March 2021, 09:13
When having external subtitles, if we add the language at the end like *.English.srt staxrip recognizes the language when loading. Is there a way to also indicate to staxrip that it is a forced track? Something like *.English.Forced.srt?
lordalibaski
2nd March 2021, 13:47
;) ;)
Cool, then vobmerge is the culprit. You just need DOS /B file+file+file etc., binary concatenation. That's what DGIndex(NV) does. It has nothing to do with Staxrip versions. Staxrip works just fine and as expected.
Wonder Woman
Thank you for your input.
Though my question towards vobmerge being the issue, why is it only doing it on Staxrip versions above x64-2.1.8.1-Beta, every other version of Staxrip it converts the file perfectly fine!!
I could share the files but they are 9.4GB in total and it's recorded in NTSC format, hence me having to crop the file and convert it so I can upload it.
videoh
2nd March 2021, 14:42
I could share the files... For any hope for a solution you'll have to find a way to make available the unprocessed source files.
lordalibaski
2nd March 2021, 14:57
For any hope for a solution you'll have to find a way to make available the unprocessed source files.
Yeah I will do, I will leave them separate and upload them to my 1fichier account.
I don't actually mind just using Staxrip to merge and convert them, I think what put me off doing it this way was it failing to merge the files quite a few times, but this was several years ago hence me using vobmerge to join them.
videoh
2nd March 2021, 16:05
There is really no reason for you to have to join the files manually. If you run into issues letting Staxrip or DGIndex(NV) process the non-joined source files, then make a report about that.
Another option if for some reason you must have a single VOB is to rip the DVD with DVDDecrypter with option File Splitting NONE in IFO Mode.
lordalibaski
2nd March 2021, 16:31
I use DVDDecrypter but never used that option, would it actualy read the files when they are on my hard drive? Can't test it my self at the moment just doing some work.
Only asking this because these files are from actual VHS recordings to a Lite-on 760GX HDD/DVD device. I remove the hard drive from the device and transfer the recorded files over to my PC. I do it this way because I record in the highest settings if I burn the files to DVD with the device it loses quality. There is also the problem of burn failures with these old machines this is why I transfer the files to PC.
videoh
2nd March 2021, 16:48
Alright, DVDDecrypter is out for your use case. Just transfer the VOBs to your PC and then let Staxrip process them. As I said there is really no reason to want to merge them manually. But if you must then COPY /B is quite adequate.
lordalibaski
2nd March 2021, 16:57
The main reason why I do merge them is for when I do multiple conversions over night it's just been so much simpler to add single files than having to add multiple files for multiple conversions.
Maybe I need to do a template for when I am doing PAL conversions and one separate one for NTSC conversions. PAL is fine I can just add them and let it do it's job but with NTSC recordings I have to crop them manually and it can be time consuming, I could and should make this much easier for myself.
I have uploaded the files if you want to test them videoh but is it ok to message you the links I don't want to be leaving the links for everyone to grab because of bandwidth on my account.
If anyone else wants to have a look why this issue is happening with these files please say so and I will pm you the links to download.
videoh
2nd March 2021, 17:13
I have uploaded the files if you want to test them videoh but is it ok to message you the links I don't want to be leaving the links for everyone to grab because of bandwidth on my account. Sure, no problem. But I will also need a full description of how to produce your issue, together with version numbers of all tools you used. I won't download anything until I have that.
lordalibaski
2nd March 2021, 17:41
Sent I hope that's enough information you needed.
videoh
2nd March 2021, 18:23
So far so good, thank you.
They are definitely .MPEG files and not VOBs. Investigating...
lordalibaski
2nd March 2021, 18:37
Yeah I know that mate explained it in pm.
I think they are mpeg.ps files, they come off the lite-on as content01,02 etc, then I rename the file extension to mpeg or vob so Staxrip recognises them, that's never been an issue.
If I name them mpeg ffmsindex will index the file before converting but when it does it knocks audio out of sync, when naming to .vob DGIndex will index the file and audio is perfect.
videoh
2nd March 2021, 19:00
Problem duplicated. Hot on the trail...
videoh
2nd March 2021, 20:21
DGIndex was reading the filesize wrong for large files [regression when converting to use GetFileSize()]. This is fixed in DGMPGDec 2.0.0.5. Put 2.0.0.5 in your staxrip apps/support/dgmpgdec directory and update in the Apps dialog (you'll be prompted to do that by staxrip). Your problem should be history. Things only appeared related to the staxrip version because they include different versions of DGMPGDec.
Thank you, lordalibaski, for bringing this to light.
@staxrip guys
Please update to DGMPGDec 2.0.0.5. You have 2.0.0.2 in staxrip 2.1.8.4 beta. Thank you.
http://rationalqm.us/dgmpgdec/dgmpgdec2005.zip
Rocky
lordalibaski
2nd March 2021, 21:23
Hmm...JKyle told me to do this the other day which I did I must have downloaded the same version.
Right mate without me sounding to daft I have just downloaded the latest version copied the files to \Stax\Apps\Support\DgMpgDec tested it and got this
Script Error
Cannot load a 32 bit DLL in 64 bit Avisynth: 'C:/Users/jimmy/Desktop/Stax/Apps/Support/DgMpgDec/DGDecode.dll'.
(C:\Users\jimmy\Desktop\To Convert\2000 ITF_temp\2000 ITF_source.avs, line 2)
Tried it on a fresh install and it's still same error am I copying the wrong files over here?
JKyle
2nd March 2021, 21:34
Script Error
Cannot load a 32 bit DLL in 64 bit Avisynth: 'C:/Users/jimmy/Desktop/Stax/Apps/Support/DgMpgDec/DGDecode.dll'.
(C:\Users\jimmy\Desktop\To Convert\2000 ITF_temp\2000 ITF_source.avs, line 2)
Tried it on a fresh install and it's still same error am I copying the wrong files over here?
Replace DGDecode.dll with the one in the x64 subfolder.
lordalibaski
2nd March 2021, 21:55
Sorted had to copy 2 files over for it to work
The DGDecode.dll from the x64 subfolder.
and DGIndex.exe from the main folder.
Many thanks videoh for all your help looking into this it's been much appreciated knew you would come good in the end.
@ JKyle thanks for pointing me in the right direction in the 1st place.
videoh
3rd March 2021, 00:19
You are most welcome, lordalibaski. Please let me know of any future anomalies if you run into any.
tormento
4th March 2021, 17:13
Is there a way to suspend a x265 encoding and resume after a machine reboot?
jlw_4049
4th March 2021, 19:44
Is there a way to suspend a x265 encoding and resume after a machine reboot?I dont believe this is possible
Sent from my SM-G986U1 using Tapatalk
lordalibaski
4th March 2021, 21:34
You are most welcome, lordalibaski. Please let me know of any future anomalies if you run into any.
This is always the 1st place I come for help so I am sure I will be back again sometime asking for more advice and help.
Here is the end result of the file converted
https://www.youtube.com/watch?v=BDJBk1ZjQZU
Not much I can do with the sound on this video, I was told the cameraman was moving causing sound issues, sound being dropped from the left channel bit annoying but at least I did a decent recording and conversion of the event.
I have a question regarding this conversion as well at a later date just need to get all my information ready for when I ask the question.
craigpro
6th March 2021, 05:49
Hi all, I know it's very much a subject of personal opinion and source quality / content - but can anyone please recommend a good x265 / NVenc settings guide to keep as much quality as possible but reduce file sizes when resizing 1080p down to 720p? Google has plenty of 2015 etc. guides but not much recent info. Thank you.
tormento
7th March 2021, 11:17
There is something I need your help with x264 encoding.
Perhaps I am now a bit spoiled with x265 HBD support and I tried to have the same thing in x264.
I tried to use the x264 (8 bit) --input-depth 16 parameter (unfortunately no --dither found) but what I got is
avs [info]: AviSynth+ 3.7.0 (r3382, 3.7, x86_64)
avs [info]: avisynth 16bit hack enabled
avs [info]: 960x800 0:0 @ 24/1 fps (cfr)
instead of dealing with the original 1080p source.
Is there a way to let x264 properly manage a HDB source?
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.