mediainfo_crap WDX - Help removing some suffixes

[advice2020]

Not sure if you would be interested but I was wondering if you would be willing to help me with removing some suffixes that show up in columns generated by MediaInfo_crap WDX plugin? I do not think these will make it into the actual plugin bundle version (unless you feel they should) but maybe I can edit the cpp files if the updates are easy enough?

---

Audio: Bit rate, aprox

First off, I do not remember the original version having this?
Did you add this to your version? I was looking for something like this that rounds bitrate values up/down removing any decminal places.
Whoever added this thank you very much for doing this, I have tested this out a little and works great so far.

The only thing I was wondering about this was how to remove the KBps suffix that shows up with each files bitrate value
It shows up as
KBps
Example:
128 KBps

I looked in the cpp file and maybe has something to do with one of the following lines?
line 214
line 254

---

Audio: Sampling rate, KHz

Currently the values show up like this
44.1 kHz
I would like to remove the kHz and just show the following if possible
44.1

In the cpp file I tried editing the following line
{"Audio: Sampling rate, KHz", ft_string, "", "Audio;%SamplingRate/String%",
changing
"Audio;%SamplingRate/String%",
to
"Audio;%SamplingRate%",
but this then shows
44100

Again if possible would like the standard samplerate values to show up
44.1
48 (no decimal if possible)
96 (no decimal if possible)

If only feel like helping with one, I would say the 'KBps' is the most desired out of the two.

Thank you for any help provided

[j2969719]

yes, this field was added. the main difference is that in the search window it has a drop-down list and it gives approximate values ​​from the prepared table gBpsUnits. the displayed text is the first column in the table, the second column is the exact value, the third column is the acceptable range of the value at which it is considered acceptable.

taproxbps gBpsUnits[] =
{
	// name,	value	+/-	0 = Bps, 1 = KBps, 2 = MBps, 3 = GBps
	{"16 KBps",	 16,	  2,	1},
	{"32 KBps",	 32,	  2,	1},
	{"96 KBps",	 96,	  2,	1},
	{"128 KBps",	128,	  2,	1},

if the value does not match any option from the table, it will be printed as is.

					if (!is_found)
					{
						if (num >= pow(1000, 3))
							snprintf(bps, sizeof(bps), "%.0f GBps", num / pow(1000, 3));
						else if (num >= pow(1000, 2))
							snprintf(bps, sizeof(bps), "%.0f MBps", num / pow(1000, 2));
						else if (num >= 1000)
							snprintf(bps, sizeof(bps), "%.0f KBps", num / 1000);
						else
							snprintf(bps, sizeof(bps), "%.0f Bps", num);

						gFields[i].value = strdup(bps);
					}

here is a modified version with an additional numeric sample rate field
plugin.cpp.gz

[advice2020]

@j2969719
Thank you for providing this update, I was able to test this and the samplerate suffix kHz is now removed as desired.
Oh, I always overlook that there is a "Plugin" tab in the "Find" tool, I never thought about what plugins would be compatible to use in it. I did not realize that Bit Rate Aprox was for this purpose.
When I did keyword search for "KBps" I saw that table but questioned what it was for, good to know, thank you for explaining. I have not tried it yet but I can already think of some uses I can have for this in the "Find" tool.
When I mentioned in my post I was referring to using this in file pane "Columns" which end up showing
KBps suffixes for each item similar to how the samplerate does kHz.
I was wondering, would there be an easy way to keep the current behavior for Bit Rate Aprox so that it works in the "Find" tool but then if used as a file pane column, then have the KBps suffixes be removed/hidden?

Thank You

[j2969719]

you can edit the text in quotes in the first column (you can write anything there), and if that's not enough, you can also edit the text in quotes in the if statement in the second block of code (it's best not to lose %.0f there). but in the case of floating values, this is a very questionable change because you can't explicitly set units of measurement for such a field, and the video bitrate can exceed 1mbps.

[advice2020]

Ahh okay, thank you.
I figured the text in quotes could be modified, just was not sure if it would have any affect on how the Find tool (Plugin Tab) functioned when using this plugin.
Speaking of the Find tool plugin tab, I was able to also try what you mentioned about the main purpose for this Bit Rate Aprox parameter, works great in the Find tool, could be very useful.
Great idea because not all values are exact, so this prevents having to setup two parameter instances lowest/highest to achieve these results.
Thank you for including this in this plugin, and again for creating this plugin in general.

[advice2020]

I apologize, I have one more question about KBps suffixes, if interested.
This is not that important, I actually kind of like the results produced because it makes odd bit rate values standout but was just curious about something.

I do not think that this can be achieved because the code is designed to round bit rate KBps numbers off, but I noticed that when using the following parameter
Audio: Bit rate, aprox
again the official WDX plugin shows KBps suffix for each value.
I removed this from the taproxbps gBpsChoices[] = table, as you suggested, which generally works.
However (as mentioned above, probably due to rounding off) I noticed that some audio file bit rates/ video file audio bit rates are not standard/common values.
When they are not common values, the KBps suffixes do still occur.
Some examples
48 KBps
64 KBps
112 KBps
126 KBps
Again not that important, but was just wondering if there was a simple way to avoid this, using the current cpp code, if for some reason I wanted to in the future.

Thank You

You mentioned another solution in your reply above, I did not try this because you mentioned might not be desired.
I do not think that second solution would have anything to do with what I just mentioned above?

[j2969719]

yes, for results not from the table you need to additionally edit if statement. in the current version need to delete it here