StaxRip 2.0 Support Thread

[stax76]

I hope it's getting more stable because I really want to get that 2.0.8.0 stable release out, please help to test.


2.0.7.6
-------

- fix: format compatibility was improved with an automated test
- fix: in the preview dialog the start position for mpc
and mpv was incorrect when cut ranges were active
- fix: chapter file not being picked up
- fix: in the filter setup profiles dialog a exception could
happen and loading a filter setup from the menu could fail
- fix: the filter parameter menu in the code editor was adding
parameters even if they were already existing with different casing
- fix: cutting could cause an error where staxrip generates
a chapter file without containing a ChapterAtom

- new: the logic to create and edit cut sections in the preview
dialog is now smarter and more flexible
- new: the assistant tells in case of a script error that the
full error can be shown by clicking the preview button
- new: MiniDeen avs filter added
- new: Advanced Info in the code editor was moved to the top level menu
and AviSynth Info() can be shown directly from the Advanced Info
without adding Info() to the script, staxrip generates the script
with perfect font size and shows it with mpv (paused, no osc, no osd)


https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS

[NikosD]

For your next version ALL rigaya's HW transcoders have new versions:

NVenc v4.68
QSVenc v3.33
VCEenc v5.04

[stax76]

@NikosD

I've updated it locally.

[Spunkmeyer]

I'm not even getting a chance to run a script when choosing VS as filters, it just bombs after demuxing as above.

[JKyle]

And Subtitle Edit was updated to 3.5.14 yesterday:

https://github.com/SubtitleEdit/subtitleedit/releases/tag/3.5.14

BTW, I noticed a sub-folder name change in the StaxRip\Apps\Plugins folder: Both ⇒ Dual

Well, just for you guys who just overwrite the whole folders/files. :)

[Patman]

For your next version ALL rigaya's HW transcoders have new versions:

NVenc v4.68
QSVenc v3.33
VCEenc v5.04

With the update of these three apps, a new option was added for each: --input-option
Another option has been added for QSVEnc: --vpp-colorspace

[stax76]

@Spunkmeyer

Look for a file that ends with _staxrip.log


@JKyle

I've updated it.

[FreaQ]

Hi,

I tried 2.0.7.6 and it's not usable.
I open a new video file with source "automatic". Demuxing is working, but then the program fails and I get the error message, that AviSynth+ was not found even so I installed 3.5 prior.

------------------------- Error opening source -------------------------

AviSynth+ installation cannot be found

LoadPlugin("D:\_Programme\_Portable\StaxRip-x64-2.0.7.6-beta\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("D:\Video\Der Film_temp\Der Film.mkv", colorspace = "YV12", \
cachefile = "D:\Video\Der Film_temp\Kim Possible - Der Film.ffindex")


But what is even more painful is, that my version of 2.0.6.0 is also not working anymore.
I use both versions as portable installations with the settings folder in each portable folder. I reverted AviSynth+ to the previous version but 2.0.6.0 keeps on failing.

------------------------- Error opening source -------------------------

FFVideoSource: The index does not match the source file
(D:\Video\Billy the Kid_temp\Billy the Kid_source.avs, line 3)

LoadPlugin("D:\_Programme\_Portable\StaxRip-x64-2.0.6.0-stable\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("D:\Video\Billy the Kid_temp\Billy the Kid.mkv", colorspace = "YV12", \
cachefile = "D:\Video\Billy the Kid_temp\Billy the Kid.ffindex")


Edit: 1.7.0.6 still works flawlessly.

[stax76]

With the update of these three apps, a new option was added for each: --input-option
Another option has been added for QSVEnc: --vpp-colorspace

I've already added it locally, don't anybody worry that a switch will be missed, it's not gonna happen. :)

https://github.com/staxrip/staxrip/blob/master/General/Test.vb

https://github.com/staxrip/staxrip/blob/master/Encoding/QSVEnc.vb#L116

[stax76]

@FreaQ

Post one screenshot of the AviSynth page in the apps dialog and one screenshot of your Windows Uninstall dialog showing your AviSynth+ 3.5 x64 installation.

[FreaQ]

https://abload.de/img/avisynth1sekuf.jpg

https://abload.de/img/avisynth252jql.jpg

[stax76]

In the apps dialog there is a runtime section where you can find 'Visual C++ 2015-2019', is that installed?

[FreaQ]

Yes. Status is OK.

[Patman]

@FreaQ have you updated the name of your folder that contains the AviSynth and Vapoursynth plug-ins? New name is dual, not both for staxrip 2.0.7.6 beta...

[FreaQ]

Where should I update it?
The path is: D:\_Programme\_Portable\StaxRip-x64-2.0.7.6-beta\Apps\Plugins\Dual
So I think I am fine here.

[stax76]

Is there any other tool that can open an avs script? You could create a version or colorbars script and then try to open with mpv or mpc, everything x64 of course.

[stax76]

It might be a dependency missing, as far as I know avs has only vc 2019 as dependency that is not part of all windows versions. You could try FileMon to find out which lib fails to load.

[FreaQ]

Is there any other tool that can open an avs script? You could create a version or colorbars script and then try to open with mpv or mpc, everything x64 of course.

I tried a version script.
It did not work with AviSynth 3.5.

But when I reverted to back to 0.1 R2772 it played fine in MPC-HC and VirtualDub.

[stax76]

Try reinstalling AviSynth 3.5 x64, for the case that AviSynth isn't working in general you have better chances somebody can help when you create a new thread. I don't see a reason why StaxRip should not work with on older AviSynth version.

https://github.com/pinterf/AviSynthPlus/releases

And you can also try VapourSynth, does almost exactly the same.

[stax76]

Could also help, all in one vc redist package:

https://github.com/abbodi1406/vcredist

[FreaQ]

You were right about dependencies.
Even so VC 2015-2019 was installed, I installed the latest versions (14.24.28127.4) for x86 and x64 which fixed the problem.
Thank you for your support, even the fault way my configuration.

[JKyle]

MKVToolNix 44.0.0 is released today.

https://www.videohelp.com/software/MKVToolNix

:)

[stax76]

MKVToolNix 44.0.0 is released today.

https://www.videohelp.com/software/MKVToolNix

:)

I've updated it.


@FreaQ

I notice now that the error handling needs improvement, it was calling the function LoadLibrary("AviSynth.dll") and it returned null which means error, staxrip reported this but it's not good enough because the OS can also provide a meaningful error message on request (by calling the GetLastError function), I'll fix it.

[fredlkrue]

You were right about dependencies.
Even so VC 2015-2019 was installed, I installed the latest versions (14.24.28127.4) for x86 and x64 which fixed the problem.
Thank you for your support, even the fault way my configuration.

Thank you, that fixes the issue I had with Windows 7.

[stax76]

@FreaQ

I further investigated the issue and the outcome was sadly that Windows only reports that a module failed to load but it's really not telling the name of the module, Windows only reports:


126 / hex 0x7e
ERROR_MOD_NOT_FOUND (winerror.h)
The specified module could not be found.


There are however system tools that can monitor the system and tell the name of the module, people in programming forums are saying that FileMon or Process Explorer can be used to get this information.

edit:

Even so VC 2015-2019 was installed, I installed the latest versions (14.24.28127.4) for x86 and x64 which fixed the problem.

I'll add a check that verifies a recent version is installed.

[Natty]

i would like to request 2 features, only if it's easy to implement.

1) compressibility test in CRF mode. currently it shows that option only in 2pass mode. please give some option to CRF which can estimate final bitrate with a small test.


2) batch only audio encoding. currently we need to drag-drop audio 1 by 1 in audio tab and right click - execute. not very useful for encoding 10-20 audios at once.

:thanks:

[stax76]

I cannot make promises, in particular not for the near future but I can tell you that I often bookmark posts that contain issues or request.

[JKyle]

Just out of curiosity:

Is there any way that I can change the UI font?

The default font is somewhat too wide, so sometimes the status bar message (such as estimated file size, etc.) is cropped.

I'd like to change the font to another fixed width font that's not too wide. :)

(FYI, I know about the UI Scale Factor option in Tools > Settings, but I don't want to re-scale my current UI.)

[TomSmith]

Just want to let you know that bitdefender is showing rav1e.exe being infected with ' Trojan.GenericKD.42833991' (2.0.7.6 beta).

Does anybody know anything about that? Is it serious?

[stax76]

Just out of curiosity:

Is there any way that I can change the UI font?

The default font is somewhat too wide, so sometimes the status bar message (such as estimated file size, etc.) is cropped.

I'd like to change the font to another fixed width font that's not too wide. :)

(FYI, I know about the UI Scale Factor option in Tools > Settings, but I don't want to re-scale my current UI.)

There ain't, next build increases the processing dialog width from 45 to 46, I hope that this fixes it


Just want to let you know that bitdefender is showing rav1e.exe being infected with ' Trojan.GenericKD.42833991' (2.0.7.6 beta).

Does anybody know anything about that? Is it serious?


Please try some online test on this file.


@all

The verification code needed some enhancement in order to enforce an up to date version of VC++ 2019, the code was a bit messy, so I had to rewrite much of it, I've tested it as good as possible so hope it's fine. The apps dialog got some improvements too.

Please everybody help to test so the stable version can be released as soon as possible, so I can take a longer break from staxrip, there has been much progress made since the last stable release.


### 2.0.7.7 Beta

- new: the apps management, verification and diagnostic has been improved

- fix: usage of too old VC++ 2019 runtime is now prevented

- update: qsvenc 3.33
- update: nvenc 4.68
- update: vceenc 5.04
- update: MiniDeen r6


https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS

[JKyle]

There ain't, next build increases the processing dialog width from 45 to 46, I hope that this fixes it.

I see. Thanks for the reply.

BTW, I think you forgot to mention that mkvtoolnix has been updated to 44.0.0 in 2.0.7.7 Beta.

-------------------------

And here's my questions:

1) Can't I change the default player in StaxRip from mpv.net to the Windows default player or something else?

I admit that mpv.net is a very powerful player, but sometimes I miss more convenient functions from other players. :(

2) In Preview, the Tools > External Player menu launches mpv.net (StaxRip default player) but doesn't seem to automatically open the video file in it.

https://i.imgur.com/zJqYpWW.gif

:thanks:

[stax76]

Can't I change the default player in StaxRip from mpv.net to the Windows default player or something else?
I admit that mpv.net is a very powerful player, but sometimes I miss more convenient functions from other players.

Which features do you miss in mpv.net? In the code editor and in the preview there is mpv and mpc support, you have to reset or config the preview menu, you don't see it in the menu because it was added after your settings were created. The old function uses internally the new function, I just tried it and it worked, maybe you use a vapoursynth script, the current libmpv build from shinchiro doesn't have vapoursynth enabled, I will have to create my own libmpv build which I will do when mpv.net development continues, very soon.

[JKyle]

Which features do you miss in mpv.net?

AFAIK, there's no way I can zoom in/out a video to a specific level like 50%, 100%, 150%, etc. or arbitrarily in mpv.net.
I'm not talking about 'fit to screen' or 'pan & scan'. I just want to zoom in/out a video based on its original resolution, not on the screen size.
(Fix me if I'm wrong.)
And mpv.net autofits a video based on its setting, but I'd like to view a video in its original resolution when it starts playing.

Besides, I can't seek a video based on the subtitle lines in mpv.net. By contrast, in PotPlayer (my default player), I can press Home or End button to seek to the previous/next subtitle line. I miss this function a lot.

In the code editor and in the preview there is mpv and mpc support, you have to reset or config the preview menu, you don't see it in the menu because it was added after your settings were created.

Thanks for the advice. (Sorry about my ignorance.)
Per your advice, I reset the Preview menus along with the overall menus (Tools > Edit Menu > Reset Everything).
Now the right click menu in Preview seems up to date:

https://i.imgur.com/J7MD9nG.jpg

However, the problem of not loading the avs script in mpv.net still exists. (I tried both 5.4.3.0 and 5.4.4.0 of mpv.net.)
On the other hand, 'Play with MPC' launches MPC-BE and plays the avs script very well.
But with VS, neither works (as you pointed out, maybe.)

What am I missing? :(

[JKyle]

However, the problem of not loading the avs script in mpv.net still exists. (I tried both 5.4.3.0 and 5.4.4.0 of mpv.net.)
On the other hand, 'Play with MPC' launches MPC-BE and plays the avs script very well.

Well, I finally figured out what was the problem: non-English/European-language filename.

The filename was in Korean, and the temp path automatically includes this Korean letter in it. This seems to prevent mpv.net from opening the avs script in the temp folder.

At this point, I raise this question: why can't mpv.net play an avs script in a non-English/European-language path whereas MPC-BE can?

I guess this is a bug in mpv.net and please fix this in the next version.

:thanks:

[stax76]

@JKyle

I've bookmarked the post on mpv.net.

Unfortunately I cannot reproduce the text encoding bug, generally avisynth does not support Unicode, because of that staxrip will show an error instead of loading the file, ANSII works here. I'm German, and we have three characters called Umlaute (ä ö ü), I've tried a file with the name of my favorite animal Eisbär (Polar bear) and mpv.net loads Eisbär_play.avs fine, please try if mpv opens an avs file with Korean characters:

mpv.exe "좋은 하루.avs"

Please also try to open the original mkv/mp4 file with mpv.net.

I hope it's not my bug because I would have to change my regional setting (risky?) or I would have to set up a VM.

Please show your system settings.


Desktop> Get-Culture

LCID Name DisplayName
---- ---- -----------
1031 de-DE German (Germany)


Desktop> Get-WinSystemLocale

LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)


Desktop> [Text.Encoding]::Default


IsSingleByte : True
BodyName : iso-8859-1
EncodingName : Western European (Windows)
HeaderName : Windows-1252
WebName : Windows-1252
WindowsCodePage : 1252
IsBrowserDisplay : True
IsBrowserSave : True
IsMailNewsDisplay : True
IsMailNewsSave : True
EncoderFallback : System.Text.InternalEncoderBestFitFallback
DecoderFallback : System.Text.InternalDecoderBestFitFallback
IsReadOnly : True
CodePage : 1252

[JKyle]

Please try if mpv opens an avs file with Korean characters.
Please also try to open the original mkv/mp4 file with mpv.net.

The thing is, if an avs file is named in English and placed in a path that doesn't include any Korean letters, mpv.net opens the file very well, which is quite natural.
(And video files, of course.)
Even if some of the letters in the path are in Korean, mpv.net successfully plays a video file in that path regardless of whether the filename is in English or Korean (via right click).
However, as for avs files, if any of the folder names in the path or the filename is in Korean, mpv.net fails to load (via right click) the avs file.

On the other hand, MPC-BE and MPC-HC successfully open the same avs file in the same path (via right click).

Here's the code of the avs file that causes the problem in mpv.net:

LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\Dual\L-SMASH-Works\LSMASHSource.dll")
LSMASHVideoSource("D:\Work\temp\테스트 영상.mp4")
#AssumeFPS(25)
Trim(1847, 6347)

The text in the avs file is encoded in ANSI.
Its name is "테스트 영상_new.avs" (Korean letters in the filename) and it is located in this path (Korean letters in the path):
D:\Work\temp\테스트 영상_temp\

("테스트 영상" means "test video" in Korean.)

Even if I move this avs file to the same folder where the video file("테스트 영상.mp4") is located("D:\Work\temp")(no Korean letters in the path), mpv.net still fails to open it.

But if I change the filename to "Test Video.avs" (no Korean letters in the filename along with no Korean letters in the path), mpv.net now successfully opens the avs file even if there's Korean letters in the avs file itself.

Please show your system settings.

Here it is:

PS D:\Work> Get-Culture

LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)

PS D:\Work> Get-WinSystemLocale

LCID Name DisplayName
---- ---- -----------
1042 ko-KR Korean (Korea)


PS D:\Work> [Text.Encoding]::Default


BodyName : ks_c_5601-1987
EncodingName : Korean
HeaderName : ks_c_5601-1987
WebName : ks_c_5601-1987
WindowsCodePage : 949
IsBrowserDisplay : True
IsBrowserSave : True
IsMailNewsDisplay : True
IsMailNewsSave : True
IsSingleByte : False
EncoderFallback : System.Text.InternalEncoderBestFitFallback
DecoderFallback : System.Text.InternalDecoderBestFitFallback
IsReadOnly : True
CodePage : 949

:thanks:

[stax76]

Please run this:


Desktop> Get-Culture; Get-UICulture; Get-WinSystemLocale; Get-WinDefaultInputMethodOverride; [Text.Encoding]::Default | select EncodingName,CodePage

LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)
1033 en-US English (United States)
1042 ko-KR Korean (Korea)

InputMethodTip : 0407:00000407
Description : German (Germany) - German


EncodingName : Korean
CodePage : 949


I can reproduce that mpv.net can't open the avs file with this culture settings but not any other player can open it either! Not mpv, not mpc-be, not mpc-hc, if mpv cannot open it than I can only file a bug report. Please try mpv, drag the Korean avs file on the mpv UI or use powershell, if you are not familiar with it, you can use absolute paths like so:


& 'absolute path to mpv.exe' 'absolute path to avs file'


Or use the crappy old cmd interpreter like so:


"absolute path to mpv.exe" "absolute path to avs file"


Not sure what the problem could be, we'll see, staxrip and virtualdub2 can open the Korean avs file, for mpc the reason why it works for you and not for me could be usage of different filters, in the mpc-be context menu choose 'Copy filters list to clipboard' while the Korean avs file is successfully loaded, show the list. A screenshot collection would help to replicate your environment exactly, right now it looks like a bug in mpv but it reports ffmpeg/demuxer as error source, I've tried ffmpeg -i and that works.

In mpc-be I get this filters for avs:


MPC-BE 1.5.4.4969
Filters currently loaded:
- Default DirectSound Device
- Enhanced Video Renderer (custom presenter)
- Audio Switcher
- LAV Video Decoder
- MPC Audio Decoder
- LAV Splitter Source
- MPC MP4/MOV Source


This is the error I get from mpv:

https://i.postimg.cc/7ZGmS3Sz/Untitled.png

I open files with mpc-be using Open with++ but I also tried with drag and drop, neither works.

[JKyle]

@Stax

I get the following results. Almost the same as yours except that my MPC-HC and MPC-BE can open a Korean named avs file in a Korean named path.
I'm attaching my test result.

[Environment Variables in PowerShell]
PS D:\Work\tmp> Get-Culture; Get-UICulture; Get-WinSystemLocale; Get-WinDefaultInputMethodOverride; [Text.Encoding]::Default | select EncodingName,CodePage

LCID Name DisplayName
---- ---- -----------
1033 en-US English (United States)
1033 en-US English (United States)
1042 ko-KR Korean (Korea)

InputMethodTip : 0412:{A028AE76-01B1-46C2-99C4-ACD9858AE02F}{B5FE1F02-D5F2-4445-9C03-C568F23C99A1}
Description : Korean (Korea) - Microsoft IME

EncodingName : Korean
CodePage : 949

[AVS file path\name]
D:\Work\tmp\테스트 영상_temp\테스트 영상_new_play.avs

[AVS file content: encoded in ANSI]
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\Dual\L-SMASH-Works\LSMASHSource.dll")
LSMASHVideoSource("D:\Work\tmp\테스트 영상.mp4")
#AssumeFPS(25)

[Run mpv in Powershell: mpv-x86_64-20200308-git-28ea1ed, Portable]
PS D:\Work\tmp> & 'D:\Utilities\mpv\mpv.exe' 'D:\Work\tmp\테스트 영상_temp\테스트 영상_new_play.avs'
PS D:\Work\tmp>

=> returns to prompt without any response

So I registered mpv in the user PATH environment variable and moved the cwd to the Korean named folder.
I ran mpv in Powershell again this time with a different command line.

PS D:\Work\tmp\테스트 영상_temp> mpv '.\테스트 영상_new_play.avs'
[ffmpeg/demuxer] avisynth: Import: couldn't open "D:\Work\tmp\�׽�Ʈ ����_temp\??? ??_new_play"
[lavf] avformat_open_input() failed
[ffmpeg/demuxer] avisynth: Import: couldn't open "D:\Work\tmp\�׽�Ʈ ����_temp\??? ??_new_play"
[lavf] avformat_open_input() failed
Failed to recognize file format.

Same result as yours. I suspect both mpv and avisynth are responsible for failing to parsing the path/name.
Or maybe PowerShell cannot transfer the path\filename in the correct text encoding that ffmpeg can recognize (UTF-8 or whatever).
Just in case, I changed the codepage of PowerShell to 65001(UTF-8) but I get the same error.

I tried mpv.net(5.4.4.0, Portable) instead, but I get the same results. (No wonder... :()

This time I open the same Korean named avs file (in the Korean named path) successfully in both MPC-HC(installed) and MPC-BE(portable).

Here's the filter info:

[MPC-HC (Nightly, 64-bit, 1.9.1.34 (a771140f7)), Installed]
Filters currently loaded:
- madVR
- AVI/WAV File Source

[MPC-BE (64-bit, 1.5.4 (build 4969)), Portable]
MPC-BE 1.5.4.4969
Filters currently loaded:
- MPC Video Renderer (external)
- AVI/WAV File Source

Well, I know AviSynth+ doesn't support UTF-8 encoded avs files, but I didn't know it doesn't support non-English filenames either. :(
Or is it a bug embedded in mpv?

And my impression with PowerShell (or Windows) is that the codepage inconsistency (UTF-8 vs localized ANSI) makes a lot of problems.
With the default localized ANSI, PowerShell can't parse unicode(UTF-8) error messages from FFmpeg correctly.
When I change the codepage to UTF-8(65001), this time PowerShell doesn't allow me to type in Korean letters. :(

Anyway, thanks a lot for your precious time and concern.
I hope we can find a fix for this problem.
:thanks:

[JKyle]

@Stax

For your reference, I screen-recorded my test: right-click to open a Korean named avs file in a Korean named folder.

https://youtu.be/PzMYhZYDBqs

As you can see, all my players except mpv.net/mpv can open this avs file.

(Since madVR cannot be recorded in my screen recording app, I skipped it, but MPC-HC with madVR certainly opens the file.)

[Spunkmeyer]

I have managed to resolve the VS errors I was getting, seems it didn't like the beta versions of VS or Python.

Keep up the good work Stax.

[stax76]

@JKyle

Looks like a bug in mpv, I've just reported it here:

https://github.com/mpv-player/mpv/issues/7522

For mpc we simply have different settings resulting in different source filters used.

Thank you for the tests and detailed info!

[JKyle]

Looks like a bug in mpv, I've just reported it here:

https://github.com/mpv-player/mpv/issues/7522


Thanks a million. But your issue was closed by one of the mpv maintainers, wm4.

Well, it looks obvious that mpv developers are not interested in making mpv play avs/vs files correctly.

So for this reason plus others, I'd like to ask you if you could add an option in StaxRip to change the default player (source or target right-click > play) to some other players or add PotPlayer in the Apps menu.

(The default binary path to PotPlayer 64bit is C:\Program Files\DAUM\PotPlayer\PotPlayerMini64.exe)

Yes, it is my personal desire, and if you think it is too much, you can just ignore it. :)

:thanks:

[stax76]

Thanks a million. But your issue was closed by one of the mpv maintainers, wm4.

Well, it looks obvious that mpv developers are not interested in making mpv play avs/vs files correctly.

I think he is the lead dev and from the same country as me but likely uses Linux as primary OS like most mpv devs so it's understandable that he has little interest in this issue. There are some Windows devs for instance Rossy, maybe I can fix it if nobody else does.

So for this reason plus others, I'd like to ask you if you could add an option in StaxRip to change the default player (source or target right-click > play) to some other players or add PotPlayer in the Apps menu.

I've only limited amount of respect for mpc and hardly any for potplayer as it's not open source but uses open source code and adware. So far I think staxrip passes time position, aspect ratio, subtitles and audio tracks via command line to mpv and next builds will also pass color info, almost nothing of this can be achieved with any other player, they hardly ever helped me with anything, they can't even play my files, only mpv can play my 4K 50 fps HDR files with my low end GT 1030card.

https://mpv.io/manual/master/#video-filters-%3Ccolormatrix%3E

[JKyle]

Maybe I can fix it if nobody else does.

I'd appreciate it if you do so.

I've only limited amount of respect for mpc and hardly any for potplayer as it's not open source but uses open source code and adware. ...only mpv can play my 4K 50 fps HDR files with my low end GT 1030card.

I see. Thanks, and keep it up! :)

[stax76]

@JKyle

It's not solved but there is a very interesting workaround, changing the default code page of the OS to UTF-8, this will enable full Unicode support for AviSynth, it's working and hopefully does not break other things, I've enabled it and hope for the best.

https://forum.doom9.org/showthread.php?p=1903639#post1903639

[JKyle]

It's not solved but there is a very interesting workaround, changing the default code page of the OS to UTF-8, this will enable full Unicode support for AviSynth, it's working and hopefully does not break other things, I've enabled it and hope for the best.

https://forum.doom9.org/showthread.php?p=1903639#post1903639

You mean this, right?

https://i.imgur.com/fa2MpaP.jpg

Yes, you're right. This setting enables non-single-byte language named avs files to be played in mpv/mpv.net. I'm really happy to see that. I appreciate your advice.

However, there's one catch: Korean input via Korean IME does not work well in some 32-bit (maybe?) apps. XYplorer, my favorite file management app, is a typical example. I know this is a bug in those apps, so I'm gonna report to the developers about this.

Meanwhile, I'll be sticking to your solution. Thanks again. :)

[stax76]

A new stable release 2.0.8.0 is now available.

It features fast rendering in the preview and crop dialog and many small detail improvements.

Thanks to Patman and everybody else for helping with updates and builds, testing and reporting issues.

I'll be working a little on mpv.net and some other project next and hope being able to write documentation for staxrip sometime this or next year.


Changelog:

https://github.com/staxrip/staxrip/blob/master/Changelog.md


Download:

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

[craigpro]

Thank you stax76!

[Atlantis]

Thank you for the new version.
I tested and 2.0.8.0 is slightly faster than 2.0.6.0 when encoding using x265.

[DavidRyan]

Thanks for all your work on the new version.