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: foo_wave_seekbar (Read 814494 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

foo_wave_seekbar

Reply #250 –
Quote from: _oao on
weird, i'm using this component since the official release and my "wavecache.db" file is only 83.8MB...


I couldn't find a red-faced smiley to insert here to indicate my embarrassment.  OK, OK, it's only MB not GB!  Still, the database will just keep growing in size, whereas personally I don't see the need to store the results for future use at all.  A 2 second delay for the results appear really doesn't bother me, and I'd prefer that to thinking of this ever-growing signature database lurking on my system.

Mike

foo_wave_seekbar

Reply #251 –
Canar: You're probably seeking to the first second or so, I'd reckon.
drmrbrewer: I guess you could create a file in its place, setting permissions to VERBOTEN, preventing the component from using it. Theoretically.

I'll probably add a transient mode to preferences the day I get around adding a preferences page. Real life is rather bogged down currently, so this component is on the back burner for now.
Stay sane, exile.

foo_wave_seekbar

Reply #252 –
That's it. Could we change it to do nothing in that case? Just display an empty frame?

foo_wave_seekbar

Reply #253 –
It should be falling back to the fully functional GDI mode. You should see something, even if the view state (track length, etc) fails to propagate.
Stay sane, exile.
 

foo_wave_seekbar

Reply #254 –
Would it be possible to add the option to manually start the plugin via the View -> Visualization -> Wave seekbar (like other visualizations included in foobar2000), so that I don't actually have to have the panel included in my config, but can open it at will?

foo_wave_seekbar

Reply #255 –
Quote from: jeremija on
Would it be possible to add the option to manually start the plugin via the View -> Visualization -> Wave seekbar (like other visualizations included in foobar2000), so that I don't actually have to have the panel included in my config, but can open it at will?

This is not a visualization though...

foo_wave_seekbar

Reply #256 –
Just because it doesn't use FFT analysis and display it with all of the fancy effects or doesn't animate much, it doesn't mean that it couldn't be considered a music visualization. It's like a static oscilloscope, or an oscilloscope which displays once already recorded data. If the author likes that idea and has the will to do it, I really don't see no reason why it could not be implemented from the technical point of view.

foo_wave_seekbar

Reply #257 –
I think he meant that it doesn't use visualization API, while Zao is considering some kind of switch for non media library files AFAIK, which is closest to what you asked, or if I misunderstood you can use it with dockable panels

foo_wave_seekbar

Reply #258 –
So, there is a lot of profound awesomeness in this plugin, and I am using it, but I'm still a little critical.

First, I don't consider my system that sluggish - a P4 2.4 with a 6600GT running XP with two monitors in horizontal span mode - but it seems like running D3D mode in parallel with anything else using D3D (in my case, JEdit, making use of Java2D's D3D acceleration) occasionally sucks CPU like a dog. It goes away when I minimize foobar2000. I'm not really sure this is your problem to begin with, but it sure is aggravating.

Using pixel shaders on a 2D texture to encode a 1D height map has to be akin to drilling holes in wood with a 10-gauge. Wouldn't this have been easier to write in assembly language?  You're basically using several gigaflops of computing power, to.... draw a few lines.

foo_wave_seekbar

Reply #259 –
Your problem probably lies mostly with running XP, I'd reckon.
Multiple concurrent D3D/GL contexts tend to interfere on XP, especially with multiple monitors involved. I may be able to make the component be kinder to such situations, but it's not high on the priority list as I do not have any living non-virtual XP machines. Most have exploded.

As for using pixel shaders, it's a matter of programmability. End users can customize the look greatly in a language suitable for the task. I do agree that it's slightly overkill though, but you should be happy to know that the Direct3D10 frontend isn't up to date.

As for update rate, I intend to make it configurable to lessen the load for the kind of people that do not need super-smooth sub-pixel position indicator movement.
Stay sane, exile.

foo_wave_seekbar

Reply #260 –
Quote from: 2E7AH on
I think he meant that it doesn't use visualization API, while Zao is considering some kind of switch for non media library files AFAIK, which is closest to what you asked, or if I misunderstood you can use it with dockable panels

Yeah, I meant something like that, but AFAIK dockable panels are a bit outdated so I made a suggestion because this component is a really useful tool, but looks better on bigger layouts...

foo_wave_seekbar

Reply #261 –
If there is some standalone UI element host in the API I can use, it wouldn't be horribly hard. If there's not, I'm not going to implement my own.
Stay sane, exile.

foo_wave_seekbar

Reply #262 –
I'm running Win7 with fb2k 1.0 here, and for some reason I don't get the waveform at all.

I right clicked on a track (FLAC), chose Extract Seekbar Signature, and then created a Waveform UI Element in the Scratchbox.
I can seek by clicking on various locations on it, but I do not see a waveform.

foo_wave_seekbar

Reply #263 –
did you try to restart the player after adding the panel to the main layout?

foo_wave_seekbar

Reply #264 –
Quote from: jeremija on
did you try to restart the player after adding the panel to the main layout?


That did the trick, thanks.

Too bad this cannot go on the actual toolbar on top and replace the real seekbar.

Another feature suggestion: hovering the mouse on various positions could show a "ghost" seeker there and show the time of that spot in a hint or whatever.

foo_wave_seekbar

Reply #266 –
first of all, thanks to Zao for this component.

i just have a little query though - i have no idea about audio analysis or how this works but most of my library shows a nice symmetrical result. but listening to one album this morning (Underworld - Second Toughest In The Infants) is showing these odd patterns. i'm just wondering if anybody has any idea why this is?






foo_wave_seekbar

Reply #267 –
yeah, i noticed some anomalies myself. by the idea it would seem that the wave should always be symetrical vertically, but i had a couple of tracks where for several seconds the wave is a little dropped. i'll post screenies when i find the specific tracks (if that's needed) ...

foo_wave_seekbar

Reply #268 –
That's how the track really looks, for certain values of "looks".
A sound wave is a sequence of signed amplitude samples, which are measured against a zero reference. When playing back, zero is no speaker movement while positive/negative amplitudes translate to movement along the speaker element axis.
There's nothing that says that a waveform should be symmetrical, it's just that most of them tend to be. In computer generated music, especially chiptunes and old video game music, it's quite common with lopsided signals.
Also, as previously mentioned, I downmix before analyzing, and a downmix will always be vulernable to phase shifts.
Stay sane, exile.

foo_wave_seekbar

Reply #269 –
oh.. i didn't thought of that. i thought it only measured amplitude.. well that's an oversight by me, thanks for clearing that up

foo_wave_seekbar

Reply #270 –
Bug report :
When the converter is active on a playlist while playing another, the component seems to analyze the tracks of the converting playlist, not the one that is playing, thus the seekbar is displayed empty.

Awesome component by the way.

EDIT : False alert, the waveform is displayed after ~1min, probably because the converter is eating all the CPU time, and the analyzing thread is running at a low priority.
Opus 96 kb/s (Android) / Vorbis -q5 (PC) / WavPack -hhx6m (Archive)

foo_wave_seekbar

Reply #271 –
The worker threads intentionally have idle priority to not impact the system or the rest of foobar.
Stay sane, exile.

foo_wave_seekbar

Reply #272 –
hey Zao, thank you for this great component, i have been enjoying it for a few weeks now.

iv ran into a very strange problem today however that appears to be due to wave seekbar.
when im playing a particular album (Venetian Snares - Printf) it takes over a minute to analyze the next track & in the process freezes foobar making it completely unresponsive.
iv tried other tracks since noticing this issue & they work fine as usual, only appears to be isolated to the tracks on this one album.

i dont know what other information i can provide at the moment as all that shows up in the console is track start then a minute later the wave seekbar finalization text.
however, if i can provide more info please ask.

thanks again

foo_wave_seekbar

Reply #273 –
I have breathed life into my old P2 which contains a Geforce FX 5600 card on XP, and the seekbar runs perfectly fine, so I cannot reproduce the failure you two FX guys cited.
Stay sane, exile.

foo_wave_seekbar

Reply #274 –
is the component analysing the same track twice when there is only 1 item in the playlist? i just noticed this in my console....

Code: [Select]
Wave cache: finished analysis of "F:\downloads\DJ_Retardo_-_What_the_North_Koreans_listen_to-Feb-2010\DJ_Retardo_-_What_the_North_Koreans_listen_to-Feb-2010.mp3"
Wave cache: finished analysis of "F:\downloads\DJ_Retardo_-_What_the_North_Koreans_listen_to-Feb-2010\DJ_Retardo_-_What_the_North_Koreans_listen_to-Feb-2010.mp3"