AvsPmod (Windows_x86) mod - Page 5

gispos · 28th January 2019, 17:34

Clear all bookmarks is fixed.
Uploaded to GitHub.
At the version number nothing has changed!

All you have to do is replace lib and src directory.

real.finder · 29th January 2019, 07:01

Quote:

Originally Posted by gispos

Clear all bookmarks is fixed.
Uploaded to GitHub.
At the version number nothing has changed!

All you have to do is replace lib and src directory.

it works now, thanks

lansing · 4th February 2019, 18:10

Will there be support for unicode in path finally?

gispos · 4th February 2019, 20:04

Quote:

Originally Posted by lansing

Will there be support for unicode in path finally?

It should be Unicode. Problems? I do not like that.

Groucho2004 · 4th February 2019, 20:41

Quote:

Originally Posted by gispos

It should be Unicode.

It is (screen shot taken on English Windoze):

lansing · 4th February 2019, 22:13

Quote:

Originally Posted by gispos

It should be Unicode. Problems? I do not like that.

The problem is still there. Still got a bunch of question marks when loading files that were not English in the path.

Groucho2004 · 4th February 2019, 22:17

Quote:

Originally Posted by lansing

The problem is still there. Still got a bunch of question marks when loading files that were not English in the path.

Can you upload one of these?

lansing · 4th February 2019, 22:28

Just do something like this

Code:

Directshowsource("e:\アメリカ合衆国に\test.mp4")

Groucho2004 · 4th February 2019, 22:34

Quote:

Originally Posted by lansing

Just do something like this

Code:

Directshowsource("e:\アメリカ合衆国に\test.mp4")

Oh, I see what you mean. As far as I recall, this is an Avisynth issue, you have to use the appropriate system locale (Japanese in the case you posted) to load scripts like this.

However, I'll have to check to be sure.

lansing · 4th February 2019, 23:28

Quote:

Originally Posted by Groucho2004

Oh, I see what you mean. As far as I recall, this is an Avisynth issue, you have to use the appropriate system locale (Japanese in the case you posted) to load scripts like this.

However, I'll have to check to be sure.

That same script can be opened in virtualdub

Groucho2004 · 5th February 2019, 00:22

Quote:

Originally Posted by lansing

That same script can be opened in virtualdub

Please upload the .avs file that causes the problem.

Danette · 6th February 2019, 02:23

Feature request/suggestion:

Some filters accumulate data from each frame. It would be handy to have a command, perhaps from the "Tools" drop-down, that would scan each frame in an entire video so that the right-arrow button wouldn't have to be manually held down to do this.

gispos · 6th February 2019, 20:39

Quote:

Originally Posted by Danette

Feature request/suggestion:

Some filters accumulate data from each frame. It would be handy to have a command, perhaps from the "Tools" drop-down, that would scan each frame in an entire video so that the right-arrow button wouldn't have to be manually held down to do this.

If I did not misunderstand you, then that would be the play button?

Danette · 7th February 2019, 00:11

Quote:

Originally Posted by gispos

If I did not misunderstand you, then that would be the play button?

Both buttons are the same speed. I was looking for a frame-by-frame scan much more rapid than the play function.

quietvoid · 7th February 2019, 01:53

Quote:

Originally Posted by Danette

Feature request/suggestion:

Some filters accumulate data from each frame. It would be handy to have a command, perhaps from the "Tools" drop-down, that would scan each frame in an entire video so that the right-arrow button wouldn't have to be manually held down to do this.

That already exists.
Under Video > Run analysis pass.

Danette · 7th February 2019, 03:37

Quote:

Originally Posted by quietvoid

That already exists.
Under Video > Run analysis pass.

I tried that initially, but I can't see that it does anything useful. The data changes that appear on the screen, when moving through each frame by various filters, do not appear when using this procedure.

StainlessS · 7th February 2019, 04:09

Add
Assumefps(250)
at end of script, & hit play

Danette · 7th February 2019, 15:02

Quote:

Originally Posted by StainlessS

Add
Assumefps(250)
at end of script, & hit play

Perfect (almost), as usual. Thanks.

Interesting use of AssumeFPS. Can I be greedy and ask for more than double the speed? It seems that any value chosen beyond double the source FPS will still yield only about double the playback speed, e.g.; the 250 you suggested is no faster than 70, where fps is 29.97. Is this doubling of the speed the maximum limit possible with AssumeFPS?

ChaosKing · 7th February 2019, 15:23

Maybe 70 is the max render fps. You could try the "Run analysis pass" in virtualdub and compare it.

StainlessS · 7th February 2019, 19:56

Top speed for AssumeFPS, depends upon how fast your machine can display frames [also, I think in VDub, there is some kind of "drop frames when behind" option which would probably have effect, never tried it].
I used to use AssumeFPS(250.0) in VDubMod instead of Run Video Analysis pass, (VDMod did not have that option) and as VD original Run Video Analysis jumped automatically back to frame 0 on completion,
I could not see any metrics on final frame. [Also, AssumeFPS(300.0) or more used to produce some error alert I think, hence 250.0].
I only used to use VD standard Analysis when I did not want to see metrics, and that meant switching from VDMod to VD std., and then back again
(VD Std did not have AVS script editor, VD2 now takes over from both VDMod and VD std functionality [thanks to "Shekh the Magnificent"], and VDub2, now does not jump back to frame 0
[on my request] so not a problem any more).

Run Video Analysis pass in VDub only renders on screen every now and then (maybe every [EDIT: real time] 1.0 second, maybe every 0.5 second, dont know), and so the frames NOT shown on screen are processed but not
rendered/resized for display. So Run Video Analysis is faster at processing only, because of this non display.
[will likely complete earlier than result of AssumeFPS(250)].

EDIT: As well as colorspace conversion, resizing and rendering, there seems to be some kind of beautification done to hide pixel 'squareness', probably some kind of anti-aliasing.
It is sometimes possible to see the un-beautified frames in VDub if you switch to some other window and then back, where pixels do indeed seem a bit coarse and clearly visible.
("beautification", probably part of DirectX stuff, don't know. Maybe Video Renderer ... Overlay Mixer, VRM Windowed etc does it, [no idea really])

28th January 2019, 17:34	#81 \| Link
gispos Registered User Join Date: Oct 2018 Location: Germany Posts: 1,000	Clear all bookmarks is fixed. Uploaded to GitHub. At the version number nothing has changed! All you have to do is replace lib and src directory. __________________ Live and let live Last edited by gispos; 28th January 2019 at 17:36.

4th February 2019, 22:28	#88 \| Link
lansing Registered User Join Date: Sep 2006 Posts: 1,657	Just do something like this Code: Directshowsource("e:\アメリカ合衆国に\test.mp4")

7th February 2019, 04:09	#97 \| Link
StainlessS HeartlessS Usurer Join Date: Dec 2009 Location: Over the rainbow Posts: 10,980	Add Assumefps(250) at end of script, & hit play __________________ I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ???

7th February 2019, 15:23	#99 \| Link
ChaosKing Registered User Join Date: Dec 2005 Location: Germany Posts: 1,795	Maybe 70 is the max render fps. You could try the "Run analysis pass" in virtualdub and compare it. __________________ AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK \|\| VapourSynth Database

7th February 2019, 19:56	#100 \| Link
StainlessS HeartlessS Usurer Join Date: Dec 2009 Location: Over the rainbow Posts: 10,980	Top speed for AssumeFPS, depends upon how fast your machine can display frames [also, I think in VDub, there is some kind of "drop frames when behind" option which would probably have effect, never tried it]. I used to use AssumeFPS(250.0) in VDubMod instead of Run Video Analysis pass, (VDMod did not have that option) and as VD original Run Video Analysis jumped automatically back to frame 0 on completion, I could not see any metrics on final frame. [Also, AssumeFPS(300.0) or more used to produce some error alert I think, hence 250.0]. I only used to use VD standard Analysis when I did not want to see metrics, and that meant switching from VDMod to VD std., and then back again (VD Std did not have AVS script editor, VD2 now takes over from both VDMod and VD std functionality [thanks to "Shekh the Magnificent"], and VDub2, now does not jump back to frame 0 [on my request] so not a problem any more). Run Video Analysis pass in VDub only renders on screen every now and then (maybe every [EDIT: real time] 1.0 second, maybe every 0.5 second, dont know), and so the frames NOT shown on screen are processed but not rendered/resized for display. So Run Video Analysis is faster at processing only, because of this non display. [will likely complete earlier than result of AssumeFPS(250)]. EDIT: As well as colorspace conversion, resizing and rendering, there seems to be some kind of beautification done to hide pixel 'squareness', probably some kind of anti-aliasing. It is sometimes possible to see the un-beautified frames in VDub if you switch to some other window and then back, where pixels do indeed seem a bit coarse and clearly visible. ("beautification", probably part of DirectX stuff, don't know. Maybe Video Renderer ... Overlay Mixer, VRM Windowed etc does it, [no idea really]) __________________ I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? Last edited by StainlessS; 8th February 2019 at 12:16.

4th February 2019, 18:10	#83 \| Link
lansing Registered User Join Date: Sep 2006 Posts: 1,657	Will there be support for unicode in path finally?

6th February 2019, 02:23	#92 \| Link
Danette Registered User Join Date: Apr 2013 Posts: 346	Feature request/suggestion: Some filters accumulate data from each frame. It would be handy to have a command, perhaps from the "Tools" drop-down, that would scan each frame in an entire video so that the right-arrow button wouldn't have to be manually held down to do this.