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: Waveform Minibar (mod) (Read 110775 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Waveform Minibar (mod)

Reply #351 –
I was under the impression foobar2000 v2.0 beta would be live very soon. I uploaded the new version targetting it in part to test auto update feature and in part to have 64-bit and dark mode supporting version ready in time.

Off topic, but once 2.0 is live you can find the other components I have prepared for it here.

Re: Waveform Minibar (mod)

Reply #352 –
Quote from: marc2k3 on
Eh? You got a direct response from Case here...

https://hydrogenaud.io/index.php/topic,116045.msg1013945.html#msg1013945
Oh.  Sorry.  I don't recall seeing that.  Or perhaps I did, and dismissed it from my mind... I've slept since then.  MY BAD.

Update: I've worked it out.  The big reason for my original feature request was that Waveform Minibar (mod)'s normalise option was making my silence tracks look like noise, but since then I've found the stop-after-track options so I no longer need silence tracks (mostly), so I ignored the update and forgot why I had ignored the update (or that there had been an update).  Yes, I am long in the tooth and the brain isn't very retentive...

Quote from: Case on
I was under the impression foobar2000 v2.0 beta would be live very soon. I uploaded the new version targetting it in part to test auto update feature and in part to have 64-bit and dark mode supporting version ready in time.

Off topic, but once 2.0 is live you can find the other components I have prepared for it here.
I'll be sticking with 1.6.11 (or maybe 1.6.12) for the foreseeable future, so it's pre-2.0 components only for me!
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: Waveform Minibar (mod)

Reply #353 –
Question: I have scanned all my tracks into WBM(mod), but still some seem to be analysing the waveform on select instead of just fetching from the cache.  And then, playback is delayed a few seconds until the waveform has populated.  Yes, I do have the option set to prioritise play over waveform display, so what could be causing both or either of these issues?
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: Waveform Minibar (mod)

Reply #354 –
Is the component configured to store those results? Remember that by default only results for tracks in media library get cached.

Re: Waveform Minibar (mod)

Reply #355 –
Quote from: Case on
Is the component configured to store those results? Remember that by default only results for tracks in media library get cached.
Yes indeed, and most tracks come up instantly.  I've just done a limited spot check using a random library search and importing the result into a playlist, and the odd thing is that this seems to only affect the bottom 15 or so of the 65 entries.  I will investigate further, but I'm now thinking that the items in the search result might be listed in the order they are stored on disk, and for some reason only the "top half" of the library has been cached.  Is there a limit on the number of entries in the cache?

As to the playback being delayed, I'm not seeing this now.  Maybe I was wrong, that's how it seemed at the time, but I have since updated to 1.0.50.

Regarding the replay gain setting: great, except the waveform now only fills about a third of the bar height.  I acknowledge there will be some variation according to the dynamics of the content, but I think it could do with a bit more "boost", maybe double.
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: Waveform Minibar (mod)

Reply #356 –
Quote from: Case on
I was under the impression foobar2000 v2.0 beta would be live very soon. I uploaded the new version targetting it in part to test auto update feature and in part to have 64-bit and dark mode supporting version ready in time.

Off topic, but once 2.0 is live you can find the other components I have prepared for it here.
Hi :) @Case
Case's Conponents for foobar2000 v2.0
https://foobar.hyv.fi/2.0/

> support both 32-bit and 64-bit  / require foobar2000 v2.0 (64bit)

Does it make sense?
Thanks.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)

Re: Waveform Minibar (mod)

Reply #357 –
No text anywhere says anything about requiring 64 bit. So no, it does not "make sense".

If anyone is confused by the single component download, it's because both DLLs are packaged inside following this advice...

https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Development:Overview#Different_CPU_architectures

Re: Waveform Minibar (mod)

Reply #358 –
Quote from: fooball on
Quote from: Case on
Is the component configured to store those results? Remember that by default only results for tracks in media library get cached.
Yes indeed, and most tracks come up instantly.  I've just done a limited spot check using a random library search and importing the result into a playlist, and the odd thing is that this seems to only affect the bottom 15 or so of the 65 entries.  I will investigate further, but I'm now thinking that the items in the search result might be listed in the order they are stored on disk, and for some reason only the "top half" of the library has been cached.  Is there a limit on the number of entries in the cache?
Having investigated the minibar.db file, I find it has stored only the first roughly 2000 results of what should have been a scan containing almost 4000 tracks.  I'll have another go...
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: Waveform Minibar (mod)

Reply #359 –
Quote from: marc2k3 on
No text anywhere says anything about requiring 64 bit. So no, it does not "make sense".

If anyone is confused by the single component download, it's because both DLLs are packaged inside following this advice...

https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Development:Overview#Different_CPU_architectures

> require foobar2000 v2.0 (64bit)
Why not "Works with foobar2000 v1.6 and newer"?
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)

Re: Waveform Minibar (mod)

Reply #361 –
Quote from: Air KEN on
> require foobar2000 v2.0 (64bit)
Why not "Works with foobar2000 v1.6 and newer"?
I have usually made components that work on ancient foobar2000 version and all but WASAPI (for obvious reasons) even still supported Windows XP. But with foobar2000 v2.0 I decided to finally utilize newer compiler and enjoy the benefits of the latest SDK features. This is much simpler and I like making small components as I don't need to bundle so much support code, I can for example rely on SQLite coming with the player. I went with new versioning with 2.0 compatible Minibar so I can still easily backport fixes and possibly features to old version.

Quote from: darkflame23 on
@Case any chance we can get your Meier Crossfeed component in 64 bit too? No hurry, but it's a real fave of mine!
foobar2000 v2.0 actually has Meier Crossfeed built-in.

Re: Waveform Minibar (mod)

Reply #362 –
Quote from: fooball on
Having investigated the minibar.db file, I find it has stored only the first roughly 2000 results of what should have been a scan containing almost 4000 tracks.  I'll have another go...
Having deleted the .db and run sync again, I confirm there is as many entries in the new .db as there are tracks in the library.  Phew!

I guess the previous run must have terminated early for some reason.
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: Waveform Minibar (mod)

Reply #364 –
Quote from: fooball on
Regarding the replay gain setting: great, except the waveform now only fills about a third of the bar height.  I acknowledge there will be some variation according to the dynamics of the content, but I think it could do with a bit more "boost", maybe double.
Can I appeal to the author to release a 1.0.51 with a user setting for scale/magnification, pretty please? (No, I don't mean 2.whatever)
It's your privilege to disagree, but that doesn't make you right and me wrong.
 

Re: Waveform Minibar (mod)

Reply #365 –
foobar2000 v2.0 beta 1 is out: https://www.foobar2000.org/download

Quote from: fooball on
Quote from: fooball on
Regarding the replay gain setting: great, except the waveform now only fills about a third of the bar height.  I acknowledge there will be some variation according to the dynamics of the content, but I think it could do with a bit more "boost", maybe double.
Can I appeal to the author to release a 1.0.51 with a user setting for scale/magnification, pretty please? (No, I don't mean 2.whatever)
I kind of knew adding the option to scale by ReplayGain was a bad idea. Dynamic music can clip and highly compressed music appears quiet. I don't think adding more scaling options will make anyone happy. But if you can convince me that some new option can save the day, I can consider it. What kind of setting you do have in mind?
Personally I use the "Original" option. Showing the actual scale of the source makes the most sense.

Re: Waveform Minibar (mod)

Reply #366 –
> foobar2000 v2.0 beta 1 : 32-bit | 64-bit
> Supported processor architectures: x86 32-bit, x86 64-bit.

I understand.
Thanks.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)

Re: Waveform Minibar (mod)

Reply #367 –
Quote from: Case on
I kind of knew adding the option to scale by ReplayGain was a bad idea.
Don't say that, I think it's a useful option.  It's just that using it, the waveform display shows my tracks as occupying only a fraction of the available space.

Quote from: Case on
Dynamic music can clip and highly compressed music appears quiet.
So the usefulness of ReplayGain depends on the nature of the content, in which case those for whom it is not useful won't be using it and won't use that option in WMB(mod).

Quote from: Case on
I don't think adding more scaling options will make anyone happy. But if you can convince me that some new option can save the day, I can consider it.
Well, it will make me happy, if that's good enough...

Quote from: Case on
What kind of setting you do have in mind?
Just a scaling option to set the level which corresponds to the full height of the waveform display, defaulting to "1.0" but user configurable between 0.1 and 9.9 (say), independent of the Original, ReplayGain (etc) options.

Maybe it doesn't need a user setting for scale – maybe you miscalculated what the correct scale should be once the ReplayGain has been taken into account?  From my observations, the waveform amplitude (when using ReplayGain) needs increasing by a factor of somewhere between 2 and 3.

Quote from: Case on
Personally I use the "Original" option. Showing the actual scale of the source makes the most sense.
Suppose the whole track is quiet.  What is the point of seeing (essentially) a flat line in the minibar?  Use a VU meter to see the source level.  But each to his own.

I would be perfectly happy with Normalise if it had a gain limit or squelch so it didn't expand low level noise to fill the screen (my silence tracks again - I still have some use for them).  I guess you're taking the maximum amplitude in the whole track and then dividing all the amplitudes by that value, so the maximum amplitude is always "1".  When the maximum amplitude is 0, dividing by 0 leads to a problem.  You could just tweak the Normalise function so it ignores amplitudes less than (eg) +/-128.

I am using the minibar to see the overall dynamics of a track, because (for my use-case, ballroom dancing music) that often means I can see where an intro ends, outro starts, and the phrasing in between.  I can do that best with Normalise, but with the irritation of silence tracks.  The music is "normalised" using ReplayGainTrack (which saves me having to adjust the volume for every track), so ReplayGain is an effective alternative to Normalise and overcomes the silence track irritation were it not for the irritation of WMB now displaying an attenuated waveform.

BUT: this is a First World problem.  I'm grateful for what I've got.  "Improvements" are just icing on the cake.
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: Waveform Minibar (mod)

Reply #368 –
There is a minor glitch:
Color change isn't displayed immediately, in the screenshot, all are set to red but remain the same.
Clicking again sets the correct color tho.
| QAAC ~ 192 kbps |

Re: Waveform Minibar (mod)

Reply #369 –
Quote from: fooball on
Quote from: Case on
What kind of setting you do have in mind?
Just a scaling option to set the level which corresponds to the full height of the waveform display, defaulting to "1.0" but user configurable between 0.1 and 9.9 (say), independent of the Original, ReplayGain (etc) options.

Maybe it doesn't need a user setting for scale – maybe you miscalculated what the correct scale should be once the ReplayGain has been taken into account?  From my observations, the waveform amplitude (when using ReplayGain) needs increasing by a factor of somewhere between 2 and 3.
Scale isn't miscalculated unfortunately. It's just that modern music is so loud. You may not know it, but original ReplayGain target playback level was even 6 dB quieter.
If you have any classical music you can see the ReplayGain scale option filling the area more evenly. And some posts back you have an example where the ReplayGain scale even clips heavily: https://hydrogenaud.io/index.php/topic,116045.msg1013946.html#msg1013946.
Also you can easily verify that the shown waveform matches ReplayGained output. Just use Converter to write a track with applied ReplayGain and compare the waveform.

But that said I can consider allowing additional scale here. The scale selection dropdown list has allowed entering manual scale factor in floating point number since the early days. I could just move that option to a multiplier edit box and make the dropdown into regular static dropdown selection list. Then you could use custom multiplier combined with the initial scale.

Quote from: fooball on
Quote from: Case on
Personally I use the "Original" option. Showing the actual scale of the source makes the most sense.
Suppose the whole track is quiet.  What is the point of seeing (essentially) a flat line in the minibar?
That is exactly the point. I want to see what is in the file. When the waveform displays a near flat line I know immediately that the source file is quiet.

Quote from: fooball on
I would be perfectly happy with Normalise if it had a gain limit or squelch so it didn't expand low level noise to fill the screen (my silence tracks again - I still have some use for them).  I guess you're taking the maximum amplitude in the whole track and then dividing all the amplitudes by that value, so the maximum amplitude is always "1".  When the maximum amplitude is 0, dividing by 0 leads to a problem.  You could just tweak the Normalise function so it ignores amplitudes less than (eg) +/-128.
Your silence tracks aren't silent. If they were the normalize wouldn't touch them - digital silence shows up as a flat line with the option. Your tracks have analog noise in them. If you used Audacity to create them, it by default applies dither. You can disable the setting in Audacity or use for example foobar2000 to create actual silence.

Quote from: Shinsekai on
There is a minor glitch:
Color change isn't displayed immediately, in the screenshot, all are set to red but remain the same.
Thanks, fixed versions uploaded.

Re: Waveform Minibar (mod)

Reply #370 –
Quote from: Case on
Your silence tracks aren't silent. If they were the normalize wouldn't touch them - digital silence shows up as a flat line with the option. Your tracks have analog noise in them. If you used Audacity to create them, it by default applies dither. You can disable the setting in Audacity or use for example foobar2000 to create actual silence.
That's interesting, thanks.  I'll look into it.
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: Waveform Minibar (mod)

Reply #371 –
Quote from: Case on
If you used Audacity to create them, it by default applies dither. You can disable the setting in Audacity
Progress: I can't find a setting for dither, but if I normalise in Audacity it reveals the low level noise that WMB picks up.  I originally created the tracks in Audacity 1.2.6... but now with 3.1.3 the generate silence operation seems to produce a proper flat line.

I've recreated my silence tracks and copied them into my library (replacing the originals), but I can't figure out how to make WMB re-scan them - sync doesn't know anything's changed.  Do I have to delete the .db and re-scan the whole library, or is there an easier way?
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: Waveform Minibar (mod)

Reply #372 –
Glad you got the silence issue sorted.
You don't need to wipe the database. There is a rescan command, but it is hidden by default to keep the context menu cleaner. If you hold shift-key while right clicking, you will see all the hidden commands.

The command is 'Utilities' -> 'Regenerate minibar waveform'.

Re: Waveform Minibar (mod)

Reply #373 –
Perfect, thanks.
It's your privilege to disagree, but that doesn't make you right and me wrong.

Re: Waveform Minibar (mod)

Reply #374 –
I've been using Waveform Seekbar for a long time. Since everything moves to 64 bit I've tried this mod.

The only thing I do really need is viewing all channels waveform: if it's stereo I prefer to see two channels, if 5.1 there should be 6. It shows a lot of useful information. I guess it won't be implemented? So I'd stay with 32 bit foobar and older plugin.