StaxRip 2.0 Support Thread

[Atlantis]

Oh, Avisynth is portable now in staxrip? I remember it installed Avisynth. Mine is still global, pointing to C:. Any advantages, disadvantages?

[Atlantis]

What benefits do you get from extracting DTS to core during the demuxing stage vs extracting DTS to core via the muxing process?

Because as I explained, some people want to encode the 5.1 DTS core. Some people do not want to keep the DTS core. They want to encode it to AAC 5.1 for example.

[jlw_4049]

Because as I explained, some people want to encode the 5.1 DTS core. Some people do not want to keep the DTS core. They want to encode it to AAC 5.1 for example.You can do that without extracting it. You can right click the bottom audio#1 in staxrip and encode aac or ac3 5.1 or what ever you want from the higher quality DTS HD track.

Sent from my SM-G986U1 using Tapatalk

[Atlantis]

I don't understand, doesn't that encode the DTS HD track? I do not want that. DTS HD track can be 6.1 or 7.1. I want to encode the core which is 5.1. I want only 5.1.

UPDATE: If you say to it to convert the DTS HD 7.1 to 5.1. It is not the original mix. It is modifying and mixing the channels. God knows what happens in the final mix. But if you encode the original 5.1 mix, the channels and the mix will be the original untouched.

What happens when it is downmixing 7.1 to 5.1?

[Atlantis]

It's supported in the eac3to demuxer, there is a menu preset for it.
If it's possible what is the step by step to do this inside staxrip GUI?

I want to encode a video in staxrip. I open it in staxrip.

I want to encode the video and only the DTS core. Is there a step by step to do it all in staxrip GUI without leaving?

[jlw_4049]

I don't understand, doesn't that encode the DTS HD track? I do not want that. DTS HD track can be 6.1 or 7.1. I want to encode the core which is 5.1. I want only 5.1.

UPDATE: If you say to it to convert the DTS HD 7.1 to 5.1. It is not the original mix. It is modifying and mixing the channels. God knows what happens in the final mix. But if you encode the original 5.1 mix, the channels and the mix will be the original untouched.

What happens when it is downmixing 7.1 to 5.1?That's something someone with a lot more knowledge on audio would have to explain.

As far as I know StaxRip doesn't support this on demux. Maybe stax76 can add it in.

Im assuming you know that you can extract core with ffmpeg and ea3cto.

EDIT: Upon some testing mkvextract CLI (That I'm 99% sure StaxRip uses to demux) doesn't support extracting DTS to core. It only extracts it to raw data that is the full DTS-HD file. I'll do some more digging and see if it's possible.

[stax76]

The eac3to demuxing dialog is typically used for BD folder demuxing and for M2TS demuxing, it can also be used to demux other things like mkv, probably not a good idea to change the default mkv demuxer from mkvmerge to eac3to. There is however a decoupled demuxing feature under:

Tools > Advanced > Demux.

eac3to does unlike mkvextract support Core only demuxing, maybe somebody should request it for mkvextract which extracts dtshd even when the dts file extension is used, I don't see how that makes sense.

If you open a mkv file with default settings then you have either dtshd in mkv or you have it demuxed, in both cases the audio processing is a two-step process not directly supported by staxrip. You've two options:

1. Instead of using the GUI audio encoder you can use the CLI audio encoder, this is somehow advanced, ideally for people that like working with command line.

2. You can create an GUI audio profile that does nothing but extracting the core. Directly after you opened the source you can choose this audio profile, go into the audio dialog and choose the option Execute Command Line, while this is processing you can do other things like choosing video filters etc., when extracting completes, right-click the audio track in the main dialog and select the extracted DTS Core file as audio source, then choose your aac or opus profile.

[jlw_4049]

@Atlantis

I asked if it was possible in the proper thread for this. https://forum.doom9.org/showthread.php?p=1916504#post1916504

If the author adds the feature to the program then I'm sure Stax76 can easily add it to the Demuxer GUI.

[JKyle]

2. You can create an GUI audio profile that does nothing but extracting the core.

Two methods are possible.

1. Create a new audio profile based on Copy/Mux with Extract DTS Core feature.

Or

2. Create a new command line audio profile that uses ffmpeg.

A screenshot for this:

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

The command line:

"%app:ffmpeg%" -analyzeduration 100M -probesize 50M -i "%input%" -bsf:a dca_core -c:a copy -y -hide_banner "%output%"

You can create either of these audio profiles by launching an empty StaxRip session and clicking Audio > Edit Profiles... > Add > Copy/Mux or Command Line.

(I guess these two are basically the same though.)


And the rest is as @stax76 explained:

After the source file is opened, choose either of these two profiles in the corresponding DTS-HD audio track, right-click the track, and run "Execute".

After the core is successfully extracted, right-click the audio track again and choose the extracted dts audio file for re-encoding.

[44vince44]

JKyle, the following command is enough to extract DTS Core
"%app:ffmpeg%" -i "%input%" -bsf:a dca_core -c:a copy -y -hide_banner "%output%"

Is there a specific reason you would need -analyzeduration and -probesize ?

For the rest I think you gave the best solution possible !

[JKyle]

Is there a specific reason you would need -analyzeduration and -probesize ?

They are for ensuring more accurate stream info detection.

Some containers, esp. MPEG-2 transport streams like ts, m2ts, and mts, have a very tiny packet size, and therefore are more prone to stream probe failure.

In those cases, ffmpeg yields the following error message and comes up with the -analyzeduration and -probesize options.

Could not find codec parameters for stream 0: unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' options

[44vince44]

Thanks JKyle I didnt know that. i'll update my profiles accordingly.

[jlw_4049]

They are for ensuring more accurate stream info detection.

Some containers, esp. MPEG-2 transport streams like ts, m2ts, and mts, have a very tiny packet size, and therefore are more prone to stream probe failure.

In those cases, ffmpeg yields the following error message and comes up with the -analyzeduration and -probesize options.

Could not find codec parameters for stream 0: unknown codec
Consider increasing the value for the 'analyzeduration' and 'probesize' optionsThanks for the information

Sent from my SM-G986U1 using Tapatalk

[hevron]

StaxRip-x64-2.1.3.5-beta, demuxing problem :(

Failed to create soft link.
G:\...\StaxRip-x64-2.1.3.5-beta\Apps\Encoders\ffmpeg\AviSynth.dll

And so every time...
17394

[JKyle]

Failed to create soft link.
G:\...\StaxRip-x64-2.1.3.5-beta\Apps\Encoders\ffmpeg\AviSynth.dll

In order to create a symbolic link on Windows 10, you need to launch a Command Prompt with admin rights.

1) Click Win+r
2) Type cmd
3) Ctrl + Shift + Enter
4) cd to the folder where ffmpeg.exe is located.
5) Create a symbolic link to AviSynth.dll there like this (full path should be specified):

mklink AviSynth.dll G:\...\StaxRip-x64-2.1.3.5-beta\Apps\FrameServer\AviSynth\AviSynth.dll

For further info, refer to this post (https://www.maketecheasier.com/create-symbolic-links-windows10/).

...


But on second thought, do we even need to do this for StaxRip?


I see similar reports of failure to create symlinks for AviSynth.dll here and there, but as for me, I'm not experiencing this problem as of now for both installed and portable AviSynth implementations in fresh start of StaxRip.

Is it something that happens when ffmpeg is employed for preprocessing?


AFAIK, Patman's ffmpeg is built with AviSynth support. Does ffmpeg require AviSynth.dll when it takes an avs input in this case?

But wait. Patman's ffmpeg is static, which means it doesn't depend on external dlls. What am I missing here?


Someone with knowledge please enlighten me. :confused:

[hevron]

mklink AviSynth.dll G:\...\StaxRip-x64-2.1.3.5-beta\Apps\FrameServer\AviSynth\AviSynth.dll

Did not help…
Unable to create file because it already exists

P.S. Why do I need a Command Prompt if I use software???

[stax76]

@JKyle

On my system which is pretty much default Win 10, soft link creation does not require elevated privileges.

If soft link creation of staxrip fails then maybe starting staxrip as admin once for soft link creation might help.

Creating the links manually will not work however, staxrip uses absolute paths for soft link creation, it saves the location in the settings only if the creation succeeds and verifies that the staxrip location hasn't changed, if the creation did not succeed or the location has changed then staxrip will recreate the links.

It's probably not working in Win 7, even with elevated privileges Win 7 might not allow creation without changing permissions.

If avisynth 3.6.1 x64 is installed then users can go into the staxrip settings dialog and disable portable mode, after staxrip is restarted it will use the installed avisynth and don't create any soft links.

[hevron]

It's probably not working in Win 7, even with elevated privileges Win 7 might not allow creation without changing permissions.
If avisynth 3.6.1 x64 is installed then users can go into the staxrip settings dialog and disable portable mode, after staxrip is restarted it will use the installed avisynth and don't create any soft links.

Win 10 x64, avisynth not installed.
Probably now you need to run only with administrator rights.

[JKyle]

Creating the links manually will not work however, staxrip uses absolute paths for soft link creation, it saves the location in the settings only if the creation succeeds and verifies that the staxrip location hasn't changed, if the creation did not succeed or the location has changed then staxrip will recreate the links.

I see.

But as I mentioned in the other thread (https://forum.doom9.org/showthread.php?p=1916701#post1916701), you need Developer Mode enabled to avoid elevation. As a Windows 10 Home user who has updated Windows 10 since before the Creators Update was released, I myself didn't realize this mode was disabled by default. I was able to create symlinks without admin privileges only after I enabled this mode.

I think many users are in the same situation. And that's why they're experiencing soft link creation failure issues when they don't have an installed AviSynth version on their system.

[hevron]

2.1.3.6 Beta
Incorrect command line using VapourSynth

Thank you, works good

[Atlantis]

What site should I use to post a sample video? It's 35MB.

[JKyle]

What site should I use to post a sample video? It's 35MB.

AFAIK, any file share service such as Dropbox, OneDrive, Google Drive, Mega, WeTransfer, Smash(https://fromsmash.com/) etc. will serve the purpose at no charge.

On Google Drive, for example, upload the video file to your Google Drive, create a shareable link to the file (so that anyone with the link can get access to it), and paste the link in your post.

The quota for a free Google Drive account is 15GB, so it's more than enough for your file.
If you have a Gmail account, you're already having a Google Drive account at your Gmail address.

[theincognito]

...
@stax76

StaxRip-x64-2.1.3.7-beta

2 pass x265 encode seems to be broken.

Log:

Error Video encoding (2.1.3.7)

Video encoding returned error exit code: -1073741819 (0xC0000005)


--------------------------- Video encoding ---------------------------

x265 3.4.0.7

avs2pipemod[info]: writing 31025 frames of 24000/1001 fps, 1920x1080,
sar 0:0, YUV-420-planar-8bit progressive video.
avs2pipemod[info]: finished, wrote 5 frames [0%].
avs2pipemod[info]: total elapsed time is 0.251 sec.
avs2pipemod[error]: only wrote 5 of 31025 frames.

StaxRip.ErrorAbortException: Video encoding returned error exit code: -1073741819 (0xC0000005)


--------------------------- Video encoding ---------------------------

x265 3.4.0.7


avs2pipemod[info]: writing 31025 frames of 24000/1001 fps, 1920x1080,
sar 0:0, YUV-420-planar-8bit progressive video.
avs2pipemod[info]: finished, wrote 5 frames [0%].
avs2pipemod[info]: total elapsed time is 0.251 sec.
avs2pipemod[error]: only wrote 5 of 31025 frames.


at StaxRip.Proc.Start() in D:\Projekte\VB\staxrip\General\Proc.vb:line 372
at StaxRip.x265Enc.Encode(String passName, String commandLine, ProcessPriorityClass priority) in D:\Projekte\VB\staxrip\Encoding\x265Enc.vb:line 120
at StaxRip.x265Enc.Encode() in D:\Projekte\VB\staxrip\Encoding\x265Enc.vb:line 43
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 312

[jlw_4049]

@stax76

StaxRip-x64-2.1.3.7-beta

2 pass x265 encode seems to be broken.

Log:

Error Video encoding (2.1.3.7)

Video encoding returned error exit code: -1073741819 (0xC0000005)


--------------------------- Video encoding ---------------------------

x265 3.4.0.7

avs2pipemod[info]: writing 31025 frames of 24000/1001 fps, 1920x1080,
sar 0:0, YUV-420-planar-8bit progressive video.
avs2pipemod[info]: finished, wrote 5 frames [0%].
avs2pipemod[info]: total elapsed time is 0.251 sec.
avs2pipemod[error]: only wrote 5 of 31025 frames.

StaxRip.ErrorAbortException: Video encoding returned error exit code: -1073741819 (0xC0000005)


--------------------------- Video encoding ---------------------------

x265 3.4.0.7


avs2pipemod[info]: writing 31025 frames of 24000/1001 fps, 1920x1080,
sar 0:0, YUV-420-planar-8bit progressive video.
avs2pipemod[info]: finished, wrote 5 frames [0%].
avs2pipemod[info]: total elapsed time is 0.251 sec.
avs2pipemod[error]: only wrote 5 of 31025 frames.


at StaxRip.Proc.Start() in D:\Projekte\VB\staxrip\General\Proc.vb:line 372
at StaxRip.x265Enc.Encode(String passName, String commandLine, ProcessPriorityClass priority) in D:\Projekte\VB\staxrip\Encoding\x265Enc.vb:line 120
at StaxRip.x265Enc.Encode() in D:\Projekte\VB\staxrip\Encoding\x265Enc.vb:line 43
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 312What was your source file?

I had this issue before when I was using the wrong settings for a source file.

Sent from my SM-G986U1 using Tapatalk

[stax76]

I just tried and it's generally working. Your log file says:

avs2pipemod[error]: only wrote 5 of 31025 frames.

So avs2pipemod has problems with your script, if it's reproducible then please post the full log to pastebin, relevant info in there is:

- source file media info
- avisynth script.
- command line

Possible workaround is:

x265 dialog > Input/Output > Pipe > ffmpeg

Or just enter pipe in the search field in the left bottom of the dialog.

[theincognito]

What was your source file?

I had this issue before when I was using the wrong settings for a source file.

Sent from my SM-G986U1 using Tapatalk

No, the setting is the same which worked previously. It wasn't that.

I just tried and it's generally working. Your log file says:

avs2pipemod[error]: only wrote 5 of 31025 frames.

So avs2pipemod has problems with your script, if it's reproducible then please post the full log to pastebin, relevant info in there is:

- source file media info
- avisynth script.
- command line

Possible workaround is:

x265 dialog > Input/Output > Pipe > ffmpeg

Or just enter pipe in the search field in the left bottom of the dialog.


Well, you both pointed me in the right direction. It wasn't the settings. And it didn't need the pipe change. The filename was too long. I renamed it and voila! It works now. :) Thanks a lot :)

[jlw_4049]

No, the setting is the same which worked previously. It wasn't that.









Well, you both pointed me in the right direction. It wasn't the settings. And it didn't need the pipe change. The filename was too long. I renamed it and voila! It works now. :) Thanks a lot :)Leave the program at the default 150 character and you'll avoid this problem.

I believe stax said it was a limitation of .net and windows.

However I could be wrong.

Sent from my SM-G986U1 using Tapatalk

[stax76]

My favorite problem again :), what's planned next for this is shortening temp file paths, there is a tracker issue marked with high priority, it will be addressed after the summer break.

[jlw_4049]

My favorite problem again :), what's planned next for this is shortening temp file paths, there is a tracker issue marked with high priority, it will be addressed after the summer break.I would love if you could increase the limit haha [emoji14]

Sent from my SM-G986U1 using Tapatalk

[Atlantis]

I want to test new avs filters in staxrip [Neo] FFT3D / DFTTest (https://forum.doom9.org/showthread.php?t=181294) which are supposed to be a lot faster.

How am I supposed to do it? I need to write for example
LoadPlugin("neo-fft3d.dll")
neo_fft3d(sigma=2.0, bt=3)

Can I add it in the profiles
neo_fft3d(sigma=2.0, bt=3)

and when selected the
LoadPlugin("neo-fft3d.dll")
be added automatically at the beginning? Is that in the hands of the user?

For the moment I add in the edit code
LoadPlugin("Z:\..........................................\StaxRip\Apps\Plugins\AVS\FFT3DFilter\neo-fft3d.dll")
neo_fft3d(sigma=2.0, bt=3)

interestingly, staxrip also automatically adds
LoadPlugin("Z:\..........................................\StaxRip\Apps\Plugins\AVS\FFT3DFilter\fft3dfilter.dll")
Any idea why? I have copied the neo-fft3d.dll in the same folder as fft3dfilter.dll

[JKyle]

I want to test new avs filters in staxrip [Neo] FFT3D / DFTTest (https://forum.doom9.org/showthread.php?t=181294) which are supposed to be a lot faster.

How am I supposed to do it?

■ If you're using installed versions of AVS and VS,
follow these steps:

Since Neo FFT3D supports both AVS and VS, I think you better put the dll file in the Dual plugins folder.
I assume you put it in %startup_dir%Apps\Plugins\Dual\Neo FFT3D.

[AviSynth+]

Because this new plugin is not registered internally in StaxRip yet, you need to add LoadPlugin(...) line in the Profiles code.
Since FFT3DFilter and FFT3DGPU are registered as sub-items under FFT3DFilter, you better put Neo FFT3D as another sub-item under the same main item FFT3DFilter like this:

FFT3DFilter | FFT3D (Neo) =
LoadPlugin("%startup_dir%Apps\Plugins\Dual\Neo FFT3D\neo-fft3d.dll")
neo_fft3d(sigma=2.0, bt=3, y=3, u=3, v=3)


(Put an empty line before and after.)

[VapourSynth]

Almost the same as with avs except for some adjustments in order to meet the syntax.

Since no FFT3D related filters are registered in the default VS Profiles (weird :confused:), you can add it as a main item in the Profiles like this:


FFT3D (Neo) =
core.std.LoadPlugin(r"%startup_dir%Apps\Plugins\Dual\Neo FFT3D\neo-fft3d.dll")
clip = core.neo_fft3d.FFT3D(clip, sigma=2.0, bt=3, planes=[0,1,2])


Again, you need to put an empty line before and after.

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

As for Neo DFTTest, it's already registered internally, but only for VS although it supports both AVS and VS.
And its code exists in the Profiles but only for VS.
(However, it calls unnecessary DFTTest.dll along with neo-dfttest.dll, which is kind of redundant.)

//
Note for @stax76:
I guess Neo DFTTest folder needs to be relocated to under Dual in order to avoid clutter.
//

Anyway, if you'd like to put it in AVS Profiles as well, insert the following code under DFTTest in Profiles:

DFTTest (Neo) =
LoadPlugin("%startup_dir%Apps\Plugins\VS\DFTTest Neo\neo-dfttest.dll")
neo_dfttest(ftype=0, sigma=2.0, y=3, u=3, v=3)

Again, you need to put an empty line before and after.

(But LoadPlugin("...\dfttest.dll") is inserted unnecessarily in the script code just as in VS, and you have to live with it unless @stax76 fixes this problem or you delete the line manually in the avs file. :()


===============================================

<Note>

Per @stax76's advice (https://forum.doom9.org/showpost.php?p=1917053&postcount=2039), I suggest you better put custom filters somewhere under %settings_dir%Plugins instead of %startup_dir%Apps\Plugins for maintenance of the app itself.

In that case, you need to modify the code a little bit accordingly.

===============================================


■ If you're using portable versions of AVS and VS,
just put the plugins in Tools > Folers > Plugins folder, and they will autoload.
(See this post (https://forum.doom9.org/showpost.php?p=1917028&postcount=2036) by @44vince44.)

In this case, you just need to add the filters in AVS/VS profiles without LoadPlugin lines.

[JKyle]

@stax76:

Currently, calling Neo f3kdb and DFTTest Neo filters invokes unnecessary old dlls. (flash3kyuu_deband.dll in AVS for Neo f3kdb, DFTTest.dll in VS for DFTTest Neo).

I think you need to clean up this mess.

And for future addition of Neo plugins, please keep consistency in naming the plugins (Neo ~ vs ~ Neo).

:thanks: in advance.

# I put these as issues on the official StaxRip GitHub repo.

[44vince44]

Well just be careful, since there are still major issues (multithreading, leaking) being adressed in these plugins. Keep watching the releases. I would't advise to make the switch right now.

[44vince44]

And remember that Staxrip has now a structure for external plugins, if you are using portable AVS and portable VS: open Menu Tools > Folders > Plugins, there you can put the AVS and VS external plugins. They will autoload. This folder is in the settings folder, so the plugins are kept along with your settings.
Plugins in those folders are autoloaded.

[JKyle]

Well just be careful, since there are still major issues (multithreading, leaking) being adressed in these plugins. Keep watching the releases. I would't advise to make the switch right now.

I see. Noted.

And remember that Staxrip has now a structure for external plugins, if you are using portable AVS and portable VS: open Menu Tools > Folders > Plugins, there you can put the AVS and VS external plugins. They will autoload.

I updated my post accordingly. :thanks:

[Atlantis]

Thanks. Yes my staxrip is using the global installed AviSynth. How can I tell it to use the portable version?

Tools > Folders > Plugins goes here for me.
C:\Program Files\AviSynth+\plugins64+

It's a mess. If I uninstall the main AviSynth, it will point to the portable?

Also I have no experience with the portable version, will I be able to use avs scripts on my system out of staxrip?

[stax76]

@JKyle

Wouldn't it be easier putting custom filters in the settings folder? A customized startup folder cannot be replaced with a new staxrip version without loosing customized files.

Currently, calling Neo f3kdb and DFTTest Neo filters invokes unnecessary old dlls. (flash3kyuu_deband.dll in AVS for Neo f3kdb, DFTTest.dll in VS for DFTTest Neo).

The dependencies are loaded automatically, possibly this detection can be improved or replaced with another design. It's probably still more efficient than using the plugin auto load feature because as far as I know it loads all plugins contained in the auto load folder into memory, I don't know much about it but this approach appears inefficient to me compared to a delay load approach where manifest data is loaded first.

Thanks. Yes my staxrip is using the global installed AviSynth. How can I tell it to use the portable version?

I suggest using the last beta because it fixes portable mode issues. Portable mode is enabled by default in the last beta, there is a setting:

Tools > Settings > General > Use included portable AviSynth

Tools > Settings > General > Use included portable VapourSynth

Plugin auto loading is supported in portable mode and in non-portable mode, the folder for each mode are different and can be opened at:

Tools > Folders > Plugins

In non-portable mode the regular auto load folder is used, in portable mode the auto load folder is located in the settings folder and the regular auto load folder is ignored.

[Atlantis]

Suggestions: Add the ability to play a sound when an encode is finished. You can have settings for it to play after each file or at the end of the job list.

[JKyle]

Wouldn't it be easier putting custom filters in the settings folder? A customized startup folder cannot be replaced with a new staxrip version without loosing customized files.

Sounds reasonable.

But there's one thing I propose you need to consider in designing the %settings_dir%Plugins folder structure.
There's no folder under it for filters supporting dual mode.
Neo filters support both AVS and VS. Where am I supposed to put them?

If I put, for example, Neo FFT3D under %settings_dir%Plugins\AviSynth, isn't it NOT possible to use it for VapourSynth if I run VS in the portable mode because StaxRip loads only %settings_dir%Plugins\VapourSynth and its subfolders?

Since I'm running installed AVS and VS only, I'm not sure about this.

Anyway, I decided to make a subfolder named 'Dual' under %settings_dir%Plugins and put all dual mode plugins there, including DGDecNV itself. Although I need to modify AVS/VS Profiles code and DGIndexNV command code, I think it's very worth it.


The dependencies are loaded automatically, possibly this detection can be improved or replaced with another design.

Got it. :thanks:

[JKyle]

Suggestions: Add the ability to play a sound when an encode is finished. You can have settings for it to play after each file or at the end of the job list.

You can use Event Command... in Tools > Advanced menu.
See this (https://forum.doom9.org/showthread.php?p=1914283#post1914283) for an example.

[Atlantis]

Thank you so much. Very useful.

[crystalfunky]

I don't know if this has been posted or asked already:
Can you implement Neo_FFT3D and Neo_DFTest in the next build?

https://forum.doom9.org/showthread.php?t=181294&page=7

[Atlantis]

Yes. Please add this. It's faster and works well. I have already switched to this and encoded with it. It works.

Neo FFT3D (https://github.com/HomeOfAviSynthPlusEvolution/neo_FFT3D)

This seems is already in but needs integrated with avisynth

Neo DFTTest (https://github.com/HomeOfAviSynthPlusEvolution/neo_DFTTest)

[Z'Hadum]

Has anyone else trouble to use the portable version of avisynth with a networkshare?
I mapped the networkshare to an drive letter to use the same settings/job queue on different computers.
but I cant set the symlinks on the networkshare, because as normal user I'M not allowed to set the links,
as Administrator (UAC) I'm in another context and can't see the mapped drive letter from the user....

Has anyone any suggestion how to circumvent this? Many thanks in advance!
At the moment I switched back to the installed version of avisynth.

[Disturbance]

Hello, bit of a strange thing happening, all of a sudden my encodes using the latest 2.1.3.0 Stable build have started having the frame rate messed with.
Instead of the input:
Framerate : 23.976023 (24000/1001) FPS
The output instead now reading as:
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS

I have even removed and then reinstalled the stable build making sure to have removed the settings and it still does it, I have tested also on another machine with a fresh copy of the stable build all on just the default encoder settings and also does it. It is not just this file but any file I try to encode (I have even tried to encode video that I have previously encoded just fine and the output fps was correct). I will even force the --fps 24000/1001 option to no avail. Attached is the log file in case there is anything anyone can spot causing this issue, stripped out everything besides the video on the source to make it easier and only encoded a clip for faster checking. I have also tested the files encoding with HandBreak as a sanity check and they come out at the right "23.976 (24000/1001) FPS"

https://pastebin.com/sBMWenNN - log

[-QfG-]

Hello, bit of a strange thing happening, all of a sudden my encodes using the latest 2.1.3.0 Stable build have started having the frame rate messed with.
Instead of the input:
Framerate : 23.976023 (24000/1001) FPS
The output instead now reading as:
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS

I have even removed and then reinstalled the stable build making sure to have removed the settings and it still does it, I have tested also on another machine with a fresh copy of the stable build all on just the default encoder settings and also does it. It is not just this file but any file I try to encode (I have even tried to encode video that I have previously encoded just fine and the output fps was correct). I will even force the --fps 24000/1001 option to no avail. Attached is the log file in case there is anything anyone can spot causing this issue, stripped out everything besides the video on the source to make it easier and only encoded a clip for faster checking. I have also tested the files encoding with HandBreak as a sanity check and they come out at the right "23.976 (24000/1001) FPS"

Sometimes it is a piping mistake. If u using Avisynth, add this in your Avisynth Script:

AssumeFPS(24000, 1001)

If the target is a x264/AVC Stream, you can change the framerate in the bitstream with mkvtoolnix after the encoding process.

[Disturbance]

Sometimes it is a piping mistake. If u using Avisynth, add this in your Avisynth Script:

AssumeFPS(24000, 1001)

If the target is a x264/AVC Stream, you can change the framerate in the bitstream with mkvtoolnix after the encoding process.

Hello, I have tried adding that to the script as well as post encoding muxing the video and setting it as 24000/1001 and it will still show the same thing. I have done that via Avisynth as well as VS and they both do the same thing, also have tried switching piping method between avspmod and ffmpeg with no change, I have also tried between x264 and x265 and nothing seems to help :/

[JKyle]

Has anyone else trouble to use the portable version of avisynth with a networkshare?
I mapped the networkshare to an drive letter to use the same settings/job queue on different computers.
but I cant set the symlinks on the networkshare, because as normal user I'M not allowed to set the links,
as Administrator (UAC) I'm in another context and can't see the mapped drive letter from the user....

Has anyone any suggestion how to circumvent this? Many thanks in advance!
At the moment I switched back to the installed version of avisynth.

Just a suggestion: have you tried enabling developer mode?

[JKyle]

Instead of the input:
Framerate : 23.976023 (24000/1001) FPS
The output instead now reading as:
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS

Well, my suggestions are

1) Try another source filter.
2) Try the latest beta if 1) doesn't work.

BTW, your attachment cannot be read because it's pending approval. Why don't you post it on https://pastebin.com/ and put the URL here?

[Disturbance]

Well, my suggestions are

1) Try another source filter.
2) Try the latest beta if 1) doesn't work.

BTW, your attachment cannot be read because it's pending approval. Why don't you post it on https://pastebin.com/ and put the URL here?

I have tried all of the source filters as well and they all seem to keep doing it, I have also tried the latest beta and it still occurs >_<

Versions I have tried - 2.0.8.0-stable, 2.1.3.0-stable, 2.1.3.7-Beta

also here is the paste for the log data - https://pastebin.com/sBMWenNN