AVSMeter 3.0.9.0 - Page 11

wonkey_monkey · 11th September 2019, 00:21

Is there a technical reason why multiple instances of AVSMeter can't run concurrently, or is it only blocked to avoid misleading statistics?

Groucho2004 · 11th September 2019, 01:37

Quote:

Originally Posted by wonkey_monkey

Is there a technical reason why multiple instances of AVSMeter can't run concurrently, or is it only blocked to avoid misleading statistics?

AVSMeter.ini, setting "AllowOnlyOneInstance", set it to 0. It's documented.

Atak_Snajpera · 29th September 2019, 16:23

Technical question: After version 2.5.3 have you changed how you output text to console? Some time ago I wrote a simple GUI for AVSMeter and it worked fine up to version 2.5.3. (the capturing code also works fine with ffmpeg.exe/x264.exe/x265.exe and so on)

Now with 2.5.4 and newer version of avsmeter my code gets those weird looooooong spaces in avs info section.

Correct captured text from v2.5.3 (each line finishes with proper CRLF marker)

...and now weird capture v2.5.4 and newer

Looks like instead of CRLF marker for each line now we have those artificial spaces?

txt files in case if you want to examine them in notepad++ -> https://www.mediafire.com/file/9cs3p...x/logs.7z/file

Groucho2004 · 29th September 2019, 16:51

Quote:

Originally Posted by Atak_Snajpera

Technical question: After version 2.5.3 have you changed how you output text to console?

Yes. In some situations, characters from a previous text output were not erased so I changed the code a bit. I don't know how this change affects screen capture (apart from your observations).
FFMpeg has different text output routines. I use the console API to be able to position the cursor where I need it on the screen which probably explains some oddities when trying to capture the output.

Atak_Snajpera · 30th September 2019, 17:36

Quote:

I use the console API to be able to position the cursor where I need it on the screen which probably explains some oddities when trying to capture the output.

Yeah. That api just inserts artificial spaces in order to position cursor in desired position. It really breaks capturing to GUI.

Groucho2004 · 30th September 2019, 17:46

Quote:

Originally Posted by Atak_Snajpera

That api just inserts artificial spaces in order to position cursor in desired position.

No, it doesn't, I insert those spaces. It's a function that prints a line with padding spaces to the end of the console window making sure that any characters that were on that specific line will be overwritten.

However, that function was already present in 2.5.3 so I'll check again what I changed. There might well be a workaround that won't break the capturing.

Atak_Snajpera · 30th September 2019, 18:02

Quote:

Originally Posted by Groucho2004

No, it doesn't, I insert those spaces. It's a function that prints a line with padding spaces to the end of the console window making sure that any characters that were on that specific line will be overwritten.

However, that function was already present in 2.5.3 so I'll check again what I changed. There might well be a workaround that won't break the capturing.

Ok. Makes sense now.

Groucho2004 · 30th September 2019, 18:10

Are you capturing stderr or stdout? Also, what are your default console dimensions (number of rows/columns)?

Groucho2004 · 30th September 2019, 18:20

Atak,
Here is a slightly modified 2.5.4, let me know if that behaves differently.

Atak_Snajpera · 30th September 2019, 18:39

Quote:

Originally Posted by Groucho2004

Atak,
Here is a slightly modified 2.5.4, let me know if that behaves differently.

Works fine!

videoh · 30th September 2019, 18:53

Is there any plan to implement a decent GUI or are you committed to this obsolete console/CLI interface? Maybe you prefer the retro look? If there is an existing GUI, please advise. Thank you.

ChaosKing · 30th September 2019, 19:21

There is a "gui" for the plugin scan part: Avisynth Info Tool https://forum.doom9.org/showthread.php?p=1864714

videoh · 30th September 2019, 19:22

Quote:

Originally Posted by ChaosKing

There is a "gui" for the plugin scan part: Avisynth Info Tool https://forum.doom9.org/showthread.php?p=1864714

Thank you!

Groucho2004 · 30th September 2019, 19:25

Quote:

Originally Posted by videoh

Is there any plan to implement a decent GUI

No, neither decent nor indecent.

videoh · 30th September 2019, 19:27

Thank you for your witty reply.

leoenc · 22nd October 2019, 12:05

I noticed that sometimes the INI file gets overwritten with a default one. Not sure why this happens.

Is there a way to prevent this?

If not, it would be great if you could add AllowOnlyOneInstance to the CLI options, or better yet, make it default to 1.

Thanks

Groucho2004 · 22nd October 2019, 12:17

Quote:

Originally Posted by leoenc

I noticed that sometimes the INI file gets overwritten with a default one. Not sure why this happens.

That should not happen. Which version of AVSMeter are you using?

Quote:

Originally Posted by leoenc

If not, it would be great if you could add AllowOnlyOneInstance to the CLI options, or better yet, make it default to 1.

'1' is the default.

leoenc · 22nd October 2019, 12:27

Oops, I meant 0.
I'm using 2.9.3.

Groucho2004 · 22nd October 2019, 12:30

Quote:

Originally Posted by leoenc

Oops, I meant 0.
I'm using 2.9.3.

Well, I can't reproduce it. If I change the value to '0' it stays that way after running AVSMeter.

leoenc · 22nd October 2019, 12:40

The problem is it happens randomly. It can be fine for a few days and then suddenly its back to the default.
By reading the docs this should happen if AVSmeter doesn't find the INI file. Maybe some OS issue prevents it occasionally from reading the INI.

Is there a reason why the default value of AllowOnlyOneInstance is 1?

11th September 2019, 00:21	#201 \| Link
wonkey_monkey Formerly davidh***** Join Date: Jan 2004 Posts: 2,496	Is there a technical reason why multiple instances of AVSMeter can't run concurrently, or is it only blocked to avoid misleading statistics? __________________ My AviSynth filters / I'm the Doctor Last edited by wonkey_monkey; 11th September 2019 at 00:25.

29th September 2019, 16:23	#203 \| Link
Atak_Snajpera RipBot264 author Join Date: May 2006 Location: Poland Posts: 7,815	Technical question: After version 2.5.3 have you changed how you output text to console? Some time ago I wrote a simple GUI for AVSMeter and it worked fine up to version 2.5.3. (the capturing code also works fine with ffmpeg.exe/x264.exe/x265.exe and so on) Now with 2.5.4 and newer version of avsmeter my code gets those weird looooooong spaces in avs info section. Correct captured text from v2.5.3 (each line finishes with proper CRLF marker) ...and now weird capture v2.5.4 and newer Looks like instead of CRLF marker for each line now we have those artificial spaces? txt files in case if you want to examine them in notepad++ -> https://www.mediafire.com/file/9cs3p...x/logs.7z/file __________________ Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper Last edited by Atak_Snajpera; 29th September 2019 at 16:27.

30th September 2019, 18:10	#208 \| Link
Groucho2004 Join Date: Mar 2006 Location: Barcelona Posts: 5,034	Are you capturing stderr or stdout? Also, what are your default console dimensions (number of rows/columns)? __________________ Groucho's Avisynth Stuff

30th September 2019, 18:20	#209 \| Link
Groucho2004 Join Date: Mar 2006 Location: Barcelona Posts: 5,034	Atak, Here is a slightly modified 2.5.4, let me know if that behaves differently. __________________ Groucho's Avisynth Stuff

30th September 2019, 19:21	#212 \| Link
ChaosKing Registered User Join Date: Dec 2005 Location: Germany Posts: 1,795	There is a "gui" for the plugin scan part: Avisynth Info Tool https://forum.doom9.org/showthread.php?p=1864714 __________________ AVSRepoGUI // VSRepoGUI - Package Manager for AviSynth // VapourSynth VapourSynth Portable FATPACK \|\| VapourSynth Database

30th September 2019, 18:53	#211 \| Link
videoh Useful n00b Join Date: Jul 2014 Posts: 1,667	Is there any plan to implement a decent GUI or are you committed to this obsolete console/CLI interface? Maybe you prefer the retro look? If there is an existing GUI, please advise. Thank you.

30th September 2019, 19:27	#215 \| Link
videoh Useful n00b Join Date: Jul 2014 Posts: 1,667	Thank you for your witty reply.

22nd October 2019, 12:05	#216 \| Link
leoenc Registered User Join Date: Mar 2007 Posts: 192	I noticed that sometimes the INI file gets overwritten with a default one. Not sure why this happens. Is there a way to prevent this? If not, it would be great if you could add AllowOnlyOneInstance to the CLI options, or better yet, make it default to 1. Thanks

22nd October 2019, 12:27	#218 \| Link
leoenc Registered User Join Date: Mar 2007 Posts: 192	Oops, I meant 0. I'm using 2.9.3.

22nd October 2019, 12:40	#220 \| Link
leoenc Registered User Join Date: Mar 2007 Posts: 192	The problem is it happens randomly. It can be fine for a few days and then suddenly its back to the default. By reading the docs this should happen if AVSmeter doesn't find the INI file. Maybe some OS issue prevents it occasionally from reading the INI. Is there a reason why the default value of AllowOnlyOneInstance is 1?

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode