AVSMeter 3.0.9.0

[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?

[Groucho2004]

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. :rolleyes:

[Atak_Snajpera]

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)
https://i.imgsafe.org/0c/0c91fdfe0b.png

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)
https://i.imgsafe.org/0c/0cbb830b40.png

...and now weird capture v2.5.4 and newer
https://i.imgsafe.org/0c/0cbb6bb58d.png
https://i.imgsafe.org/0c/0cbb6aede1.png
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/9cs3pj8d2funidx/logs.7z/file

[Groucho2004]

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]

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]

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]

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]

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

[Groucho2004]

Atak,
Here (https://www.dropbox.com/s/ofbei1r76lq3mzy/AVSMeter64.7z?dl=1) is a slightly modified 2.5.4, let me know if that behaves differently.

[Atak_Snajpera]

Atak,
Here (https://www.dropbox.com/s/ofbei1r76lq3mzy/AVSMeter64.7z?dl=1) is a slightly modified 2.5.4, let me know if that behaves differently.

Works fine!
https://i.imgsafe.org/23/23ddf1f5ad.png

[videoh]

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]

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

[videoh]

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

[Groucho2004]

Is there any plan to implement a decent GUINo, neither decent nor indecent.

[videoh]

Thank you for your witty reply. :sly:

[leoenc]

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]

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?
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]

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

[Groucho2004]

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]

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?

[Groucho2004]

By reading the docs this should happen if AVSmeter doesn't find the INI file.Correct. It will write a new file with default values.

Is there a reason why the default value of AllowOnlyOneInstance is 1?Yes. Most people use only one instance and this setting prevents accidentally running two or more instances without noticing which would produce wrong results.

In which directory is your AVSMeter located?

[leoenc]

Its located in C:\Tools\AVSmeter.

[Groucho2004]

Its located in C:\Tools\AVSmeter.OK. Still don't know what the problem could be...

[leoenc]

In that case, I'd be very grateful if you could add AllowOnlyOneInstance to the CLI options to override the INI file.

[Groucho2004]

v2.9.7
- Timing optimisations
- Minor fixes

[FranceBB]

v2.9.7
- Timing optimisations
- Minor fixes

Thank you! :D

[Groucho2004]

v2.9.8
- Updated libcpuid to support AMD Threadripper (Castle Peak)
- Updated AVS+ headers
- Cosmetics

[JackBrody]

I have troubles downloading the AVSMeter - "The connection has timed out...".

[StainlessS]

Here tis (I had probs too) :- http://www.mediafire.com/file/i0mu7q6nqqpp4mm/AVSMeter298.7z/file

[Groucho2004]

I have troubles downloading the AVSMeter - "The connection has timed out...".I've added a Dropbox mirror (https://www.dropbox.com/sh/leze79pvu5shbqo/AADBkM9XOMiFDzNI01oJlUcQa?dl=0&lst=).

[l00t]

I've added a Dropbox mirror (https://www.dropbox.com/sh/leze79pvu5shbqo/AADBkM9XOMiFDzNI01oJlUcQa?dl=0&lst=).

This leads to a nasty 404 error...

[Groucho2004]

This leads to a nasty 404 error...Changed the mirror to mediafire (http://www.mediafire.com/folder/x6f7yqjufdg7c/Groucho's_Avisynth_Stuff).

[JackBrody]

Thank you, mediafire was fine. :-)

[Sparktank]

Changed the mirror to mediafire (http://www.mediafire.com/folder/x6f7yqjufdg7c/Groucho's_Avisynth_Stuff).

:thanks:

[Music Fan]

Hi,
I installed v2.9.8 and set LogUseFileSaveDialog on 1 but AVSMeter does not prompt with any file save dialog :scared:
And I didn't write anything beside LogDirectory.

[Groucho2004]

Hi,
I installed v2.9.8 and set LogUseFileSaveDialog on 1 but AVSMeter does not prompt with any file save dialog :scared:
And I didn't write anything beside LogDirectory.Works for me. What was your exact command line?

[Music Fan]

No command line, I open the avs file with AVSMeter with a right click, send to.

[Groucho2004]

No command line, I open the avs file with AVSMeter with a right click, send to.Without the "-log" switch, no log file will be created.

[Sparktank]

No command line, I open the avs file with AVSMeter with a right click, send to.

Open the property box on the shortcut and add -l to the end of the executable:
C:\Apps\AVS\AVSmeter\AVSMeter64.exe -l

you can add other switches, too. like range, etc.
Create multiple shortcuts with different switches for different purposes and rename the shortcut to reflect your settings.

[Music Fan]

Without the "-log" switch, no log file will be created.
That's for command line, but I don't use the command line.
It used to work with old versions.:confused:
I mean with the log set on 1 in the ini and send to.

[Music Fan]

Open the property box on the shortcut and add -l to the end of the executable:
C:\Apps\AVS\AVSmeter\AVSMeter64.exe -l

you can add other switches, too. like range, etc.
Create multiple shortcuts with different switches for different purposes and rename the shortcut to reflect your settings.
Thanks, that worked ;)

edit : and this is strange because the ini file works because if I set LogUseFileSaveDialog on 1, the dialog box opens, otherwise the log is created in the avs file directory.
Thus I don't understand why the log was not created before I use your trick.
That's maybe not ini related.

[Groucho2004]

Thus I don't understand why the log was not created before I use your trick.Read my last post (#238) again. It seems rather unambiguous methinks.

[Music Fan]

I saw it, but the switch concerns only command line, isn't it ? As I said, I don't use command line to use AVSMeter.
With old versions, it worked with send to without having to use Sparktank's trick.
But I found in my old notes that the ini was different, there was a CreateLog line, which isn't there anymore.

edit : in other words, if you drag & drop an avs file on AVSMeter.exe v2.9.8, no log is created, whatever the ini settings, because there isn't CreateLog anymore.

[StainlessS]

With old versions, it worked
Use the old version then.

[Music Fan]

Use the old version then.
:rolleyes:
I believe a new version is not supposed to remove some useful functions.

[Groucho2004]

I saw it, but the switch concerns only command line, isn't it ? As I said, I don't use command line to use AVSMeter.What? It doesn't matter if you type the command line in a console window or use a shortcut with that command line to run the program.

As for the missing ini file options - they were removed in order to de-clutter the ini file. Nobody complained except you.

[Music Fan]

What? It doesn't matter if you type the command line in a console window or use a shortcut with that command line to run the program.
Of course, but before Sparktank's message, I didn't realize that a shortcut used with the sendto folder could contain more than just the path to the program. I didn't see it as a command line.

As for the missing ini file options - they were removed in order to de-clutter the ini file.
Ok, but that's just one line, that's not big.

Nobody complained except you.
A lot of changes in softwares are reported by only one person (because it's generally enough), I just told you what I noticed.
I didn't know if it was a bug or not, now I know.

[Groucho2004]

Ok, but that's just one line, that's not big.OK, I'll put the 'CreateLog' option back.

[Music Fan]

Thanks, as you want.;)

[Groucho2004]

v2.9.9
- Added GPU power consumption sensor readout
- Put back 'CreateLog' and 'CreateCSV' ini options