Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Peakmeter for Columns UI (Read 207209 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Peakmeter for Columns UI

Reply #251
hm, not here. it´s listed in the component-list, but how should i add it?



EDIT: ok, ok. now i got it. my fault. the threat-title says it all. "peakmeter for COLUMNS UI". well, new version of foobar uses new default user interface "UI Elements".

so here´s my question: will there be a version for new default user interface?

Peakmeter for Columns UI

Reply #252
My example is using Dockable panels with the DEFAULT UI.

Peakmeter for Columns UI

Reply #253
My example is using Dockable panels with the DEFAULT UI.


aha, there it is. thx for ur answer.

still @ foo_pm:
peakmeter as an default component in an future up-coming foobar version would be supercool, for sure.

Peakmeter for Columns UI

Reply #254
Same problem as Brainbug : I can see foo_uie_peakmeter in my components list, but I don't know how to add it with the Default UI in foobar 0.9.5b2. What must I do exactly ? (sorry, newbie here)
I have downloaded Columns UI and Dockable Panels, but then...?
Thanks in advance for your help.


Peakmeter for Columns UI

Reply #256
Same problem as Brainbug : I can see foo_uie_peakmeter in my components list, but I don't know how to add it with the Default UI in foobar 0.9.5b2. What must I do exactly ? (sorry, newbie here)
Thanks in advance for your help.


Panels (like peakmeter) written for PUI or CUI do not work with the new default UI.

Peakmeter for Columns UI

Reply #257
YES ! I got it to work with the Default UI, thanks (again  ) nightfishing ! But is there a way to really integrate it within the whole foobar interface, or do we have to see it always as a separate window ?

Peakmeter for Columns UI

Reply #258
Currently, this is the only way to use "panels" with the Default UI.

You can, of course use Columns_UI with the beta and then the "panels" will integrate into the layout as they were intended to.

Peakmeter for Columns UI

Reply #259
Of course, I understand.

Well, I've played a bit with this wonderful plugin, and now I have some suggestions :

1/ I wish there was a way to display the real foobar output level. What I mean is that, if I play with foobar's volume control, I'd like the peakmeter to react accordingly.

2/ I wish there was a way to display the range[dB] in a precise way. Let me explain. My dream is to have the exact equivalent of a real peakmeter I own. The peakmeter has 20 LEDs and it's graduated as follows :
- LEDs 1 to 12 : -43 / -40 / -37 / -34 / -31 / -28 / -25 / -22 / -19 / -16 / -13 / -10 (3dB increments)
- LEDs 13 to 15 : -8 / -6 / -4 (2dB increments)
- LEDs 16 to 19 : -3 / -2 / -1 / 0 (1dB increments)
- LED 20 : >0
This means that the physical spacing of my real peakmeter is the same between all ranges (while in the current version of foobar's peakmeter the spacing seems to be dependant on the range values). I'd love if we could toggle that. Please !

3/ Instead of solid bars with nice color gradients, I'd also love if we could display only rectangular segments (like LEDs turning on and off). In my case, I'd like to be able to display 20 segments, no more, no less. Each segment would have a given height, and we could configure either the height and the spacing between the segments (like we do currently for the spacing between the bargraphs).

4/ It could also be nice if we could select a given framerate (I mean "how many times per second will the bargraphs be updated). The setting could be "automatic" (like it is now), or a given number (e.g. 10 times per second, 5 times per second, 1 time per second, etc.). Of course if we're not in automatic mode, the displayed information would be the peak values for the selected time interval.

I hope I have been clear enough (if not, please ask). What do you think ?

Peakmeter for Columns UI

Reply #260
 Hello ? Anybody here ? 

Peakmeter for Columns UI

Reply #261
another vote for the version that would work in new default GUI.
PANIC: CPU 1: Cache Error (unrecoverable - dcache data) Eframe = 0x90000000208cf3b8
NOTICE - cpu 0 didn't dump TLB, may be hung

Peakmeter for Columns UI

Reply #262
1
If age or weaknes doe prohibyte bloudletting you must use boxing

Peakmeter for Columns UI

Reply #263

My example is using Dockable panels with the DEFAULT UI.

aha, there it is. thx for ur answer.

still @ foo_pm:
peakmeter as an default component in an future up-coming foobar version would be supercool, for sure.

another vote for the version that would work in new default GUI.

+1
Thanx, but i'm sorry cause i can't add "Default UI" support without the new SDK.


First off all thank you for your suggestions Jose Hidalgo.
1/ I wish there was a way to display the real foobar output level. What I mean is that, if I play with foobar's volume control, I'd like the peakmeter to react accordingly.
I think this is problematic because of the different possibilities to change the output volume (foobar, windows play control, sound card driver, amplifier ...). So i believe it's better to show the original song level. But i will remember this for a future option.
2/ I wish there was a way to display the range[dB] in a precise way. Let me explain. My dream is to have the exact equivalent of a real peakmeter I own. The peakmeter has 20 LEDs and it's graduated as follows :
- LEDs 1 to 12 : -43 / -40 / -37 / -34 / -31 / -28 / -25 / -22 / -19 / -16 / -13 / -10 (3dB increments)
- LEDs 13 to 15 : -8 / -6 / -4 (2dB increments)
- LEDs 16 to 19 : -3 / -2 / -1 / 0 (1dB increments)
- LED 20 : >0
This means that the physical spacing of my real peakmeter is the same between all ranges (while in the current version of foobar's peakmeter the spacing seems to be dependant on the range values). I'd love if we could toggle that. Please !
Peakmeter shows a logarithmic scale. The value and the space are linearly dependent, I'm sorry but i don't want to change this.
3/ Instead of solid bars with nice color gradients, I'd also love if we could display only rectangular segments (like LEDs turning on and off). In my case, I'd like to be able to display 20 segments, no more, no less. Each segment would have a given height, and we could configure either the height and the spacing between the segments (like we do currently for the spacing between the bargraphs).
This would be a nice option. The segments could be individually configured by bitmaps. I will remember this too.
4/ It could also be nice if we could select a given framerate (I mean "how many times per second will the bargraphs be updated). The setting could be "automatic" (like it is now), or a given number (e.g. 10 times per second, 5 times per second, 1 time per second, etc.). Of course if we're not in automatic mode, the displayed information would be the peak values for the selected time interval.
Yes, something like this is planned for one of the next releases.

Peakmeter for Columns UI

Reply #264
FYI: i'm now working on a version with a logarithmic spectrum analyzer.

Peakmeter for Columns UI

Reply #265
It looks good!
If age or weaknes doe prohibyte bloudletting you must use boxing

Peakmeter for Columns UI

Reply #266
foo_pm, first of all, thanks for taking my requests into consideration. 


1/ I wish there was a way to display the real foobar output level. What I mean is that, if I play with foobar's volume control, I'd like the peakmeter to react accordingly.
I think this is problematic because of the different possibilities to change the output volume (foobar, windows play control, sound card driver, amplifier ...). So i believe it's better to show the original song level. But i will remember this for a future option.

Yes of course, it's better to show the original song level. I was only seeing that as an option that you could toggle on/off. And to make it simple, it would depend only on foobar's output level.


2/ I wish there was a way to display the range[dB] in a precise way. Let me explain. My dream is to have the exact equivalent of a real peakmeter I own. The peakmeter has 20 LEDs and it's graduated as follows :
- LEDs 1 to 12 : -43 / -40 / -37 / -34 / -31 / -28 / -25 / -22 / -19 / -16 / -13 / -10 (3dB increments)
- LEDs 13 to 15 : -8 / -6 / -4 (2dB increments)
- LEDs 16 to 19 : -3 / -2 / -1 / 0 (1dB increments)
- LED 20 : >0
This means that the physical spacing of my real peakmeter is the same between all ranges (while in the current version of foobar's peakmeter the spacing seems to be dependant on the range values). I'd love if we could toggle that. Please !
Peakmeter shows a logarithmic scale. The value and the space are linearly dependent, I'm sorry but i don't want to change this.

Here also, I didn't mean to change your default logarithmic scale, because it's great the way it is. I see this request only as an option of course. But please allow me to tell you why : this comes from real-life experience.

When you make a professional utilization of a real peakmeter like the ones I own, you can easily understand that it's more important to have a very accurate view of what happens between -10 and 0dB, than to see what happens between -40 and -30dB. And all this must be done with a limited number of LEDs. That's why my peakmeters are built like said above (3dB increments, then 2dB increments, than 1dB increments for the zone where we need accuracy). That makes the measurements much more accurate where they need to, without them being unnecessarily precise where they don't need to. We have 9 LEDs for the -10/limit range, and 11 LEDs for the -43/-13 range. And believe me, that's really useful.

Because we must remember that a peakmeter is not only some fancy pretty colored widget. It is also a professional measurement utility. And I think maybe we should all keep that in mind. A peakmeter is all of this, no more, no less.

So that's the reason why I'd like if we could, OPTIONALLY, toggle this special "measurement mode" on/off (Preferences > Logarithmic mode (default) or Measurement mode (option)). At least to me it would be really helpful. I don't mean to insist anymore, but I hope you'll understand these additional explanations and you'll reconsider your position (hey, it's just an additional option, so why not after all, provided you have a bit of time ? it's not really complicated to implement...).

Of course I'm open to giving you any additional information that you should need in this matter. Thanks again. 

PS : the measurement mode is also logarithmic of course. In fact it's just a series of several consecutive logarithmic ranges.

Peakmeter for Columns UI

Reply #267
I made a nice bitmap for use as a volume bar in peakmeter:



It's made in Paint.Net using this procedure:

1. Make a new bitmap 800x8 pixels
2. Create two extra layers (so you have three total). Name the two "Slashes" and "Colorfade" respectively. make sure the Colorfade layer is the topmost one.
3. Using the paint bucket tool, make the colorfade layer entirely green.
4. Draw two gradients in the colorfade layer. You do that by using the selection tool to confine the gradient. by looking at my finished result you will get the idea.
5. In the Slashes layer you use the text tool to place a string consisting of slashes only in white color.
6. Adjust the layer properties of the colorfade layer and set the blend mode to Multiply.

That's it.

Download the BMP file here (800x8 pixels):
http://saivert.xerc.biz/foobar2000/bar5.bmp


PS hope they get out the new SDK soon. I really want peakmeter as a "UI element".




 

Peakmeter for Columns UI

Reply #271
 

foreground:

background:

images need to be tiled
LAME 3.100.1 -V0

Peakmeter for Columns UI

Reply #272
Thanks (Sly), that's very nice !

What do you mean exactly by "images need to be tiled" ? And how can we implement them within the peakmeter ? (sorry, beginner here  )


Peakmeter for Columns UI

Reply #274
Apparently foo_pm is not very responsive for the time being... (last reply to this topic : november 17th, despite all our posts / questions / comments / etc.)