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 806866 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_wave_seekbar

Reply #475
0.2.8 released, updating is strongly recommended as this fixes a rare crash bug when drawing detects a lost device.
Stay sane, exile.

foo_wave_seekbar

Reply #476
The 0.2.9 release is dedicated to all the idiots that consider themselves more competent at installing the DirectX runtime than the redist installer.
If you've been manually copying in d3dxN_NN.dll files, don't do that. That's bloody retarded and will lead to glorious explosions. Use the redist like everyone else, gaaaah.

*breathes*
0.2.9 also has a placeholder waveform with all possible channels present, and falls back to GDI more properly on frontend failure.
Stay sane, exile.


foo_wave_seekbar

Reply #478
0.2.10 has an advanced preference to scan tracks not in the media library. It defaults to the current behaviour, which to analyse everything.
Stay sane, exile.

foo_wave_seekbar

Reply #479
All right, thanks
Long waited, very quickly implemented

foo_wave_seekbar

Reply #480
Mmh,

why not "Don't store analysed tracks not in the media library" to still get waveform display but without storing them to the database?

foo_wave_seekbar

Reply #481
Because that's a completely different feature, which would require multiple backends to support the temporary in-memory one then.
That is something that is not trivially implementable, unlike the analysis filter here, which was just a dozen lines or so in one function.
Literally, if (skip_tracks_outside) if (not library->is_track_in_library(make_handle(location))) skip();
Stay sane, exile.

foo_wave_seekbar

Reply #482
Ok, didn't know that. Just sounded more useful to me ;)

Don't actually need these options for me.

foo_wave_seekbar

Reply #483
It would be nice for the display to scale or have ability to scale per volume. Example all my files are mp3gain scanned so they all "look" narrow ranged or quiet, some of the lower volume tracks or portions of tracks appear as just a line. Scale based on db's would be great then one could set max at 89 db's and that should be close on the range. It would give some control over the look of the wave also. Not really a dynamic per track scale as a constant scale, does that make sense?

foo_wave_seekbar

Reply #484
@Zao :

bug (according to me)

on playback STOP, the wave seekbar is still displayed, it shouldn't (no sense)

what about it ? could you fix it please ?

Thanx for feedback.

EDIT: i use latest version v0.2.10

foo_wave_seekbar

Reply #485
I consider it to be a feature that the previous waveform persists, as otherwise you'd get annoying flicker on track changes.
Stay sane, exile.


foo_wave_seekbar

Reply #487
I consider it to be a feature that the previous waveform persists, as otherwise you'd get annoying flicker on track changes.


I'm cool with that! I hate flickering.

foo_wave_seekbar

Reply #488
I don't see what's wrong with that, either.

I'd rather see the waveform of the last track that was played instead of seeing nothing at all.

foo_wave_seekbar

Reply #489
I think Falstaff's suggestion is backwards, personally. I like it the way it is.



foo_wave_seekbar

Reply #492
0.2.11 now has a shiny tooltip when seeking that indicates the target time.
Stay sane, exile.

 

foo_wave_seekbar

Reply #493
0.2.11 now has a shiny tooltip when seeking that indicates the target time.


Very nice. But it should get improved a bit.


I have foobar at upper right screen corner. Dragging (seeking) mouse cursor out of screen (say above foobar in this case) causes tooltip going out of screen too. Tooltip should switch position to stay in foobar window. Same when dragging to the rightmost screen edge -> tooltip should switch position to the left of the mouse cursor to stay in screen. Also when dragging mouse cursor very far away from the foobar window (so that even the seek cursor gets hidden) doen't hide the tooltip. So you can move the tooltip around the whole screen via mouse drag. Should be avoided.

foo_wave_seekbar

Reply #494
Very nice. But it should get improved a bit.


I have foobar at upper right screen corner. Dragging (seeking) mouse cursor out of screen (say above foobar in this case) causes tooltip going out of screen too. Tooltip should switch position to stay in foobar window. Same when dragging to the rightmost screen edge -> tooltip should switch position to the left of the mouse cursor to stay in screen. Also when dragging mouse cursor very far away from the foobar window (so that even the seek cursor gets hidden) doen't hide the tooltip. So you can move the tooltip around the whole screen via mouse drag. Should be avoided.

Already reported and fixed internally.

foo_wave_seekbar

Reply #495
Cool, thanks!

foo_wave_seekbar

Reply #496
Sorry, I somehow didn't underline the part I was talking about.

foo_wave_seekbar

Reply #497
Just wondering... Is Direct2D incapable of the same effects as Direct3D in this case? What are the advantages/disadvantages?

foo_wave_seekbar

Reply #498
I could make the Direct2D mode push the exact same pixels as the GDI mode, but then there would be no need for it.
The Direct2D look is the way it is because it's different and does something (smooth splines) that would be hard to do in the other two frontends.
This is why I do not bundle the Direct3D10 frontend anymore, it doesn't add any value over the Direct3D9 one.
Stay sane, exile.

foo_wave_seekbar

Reply #499
Hello and thank you for the great work.
I have an idea: could you add normalizing of waveforms? It can be very useful for signals with very low peaks
🇺🇦 Glory to Ukraine!