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

foo_wave_seekbar

Reply #275 –
Yes. Until a track has been fully scanned and recorded into the database, it is possible to trigger additional scans. In your case, it's from the "scan next track in advance for linear playback orders" logic that enqueues it.
They are harmless and will just burn a bunch of CPU.
Stay sane, exile.

foo_wave_seekbar

Reply #276 –
Can't add this DUI element to foobar v1.0 without having it crash foobar.

Let us know when it's stable and doesn't just invariably shit the bed.

foo_wave_seekbar

Reply #277 –
it works fine in DUI/foobar v1 for me. i think the problem is at your end. 

is your hardware up to it? directx upto date as outlined in the opening post?

foo_wave_seekbar

Reply #278 –
Quote from: kopf on
Can't add this DUI element to foobar v1.0 without having it crash foobar.
Let us know when it's stable and doesn't just invariably shit the bed.

Thank you for the encouraging feedback. Your crashes are Module Not Found while delay-loading d3dx10_42 for some reason. This is very strange, as you've successfully passed the d3dx9_42.dll test. Are you sure that you have installed the DirectX redist for August 2009 or later (February 2010 is available). The only reason I could see for such a crash would be someone grabbing single DirectX components and throwing them into the SysWoW64 folder.
Stay sane, exile.

foo_wave_seekbar

Reply #279 –
Quote from: Zao on
Quote from: kopf on
Can't add this DUI element to foobar v1.0 without having it crash foobar.
Let us know when it's stable and doesn't just invariably shit the bed.

Thank you for the encouraging feedback. Your crashes are Module Not Found while delay-loading d3dx10_42 for some reason. This is very strange, as you've successfully passed the d3dx9_42.dll test. Are you sure that you have installed the DirectX redist for August 2009 or later (February 2010 is available). The only reason I could see for such a crash would be someone grabbing single DirectX components and throwing them into the SysWoW64 folder.


You're very welcome for the crude feedback. I installed the dx redist and all's working now. That hadn't occured to me to be the possible source of the problem, since I'd installed dx with a game or two, and everything else that'd been using it was happy with that setup - i figured it was installed in its entirity.

cheers for the help zao, plugin looks gut

foo_wave_seekbar

Reply #280 –
This plugin is just awesome. I don't now how I could live without it for so long. 

I'm streaming all my music in FLAC from my NAS and at the beginning I was afraid the caching of the waveform data could be very slow, but it works like a charm.

Thank you very much Zao and keep up the good work! 

foo_wave_seekbar

Reply #281 –
Most excellent!

I'm just letting it draw from the layout colours; will play around with that later.

An issue: the highlight doesn't advance smoothly like the vertical bar. I tried to set it up so that the bar would be gone (0px), but highlight would stll be there, and it seems it advances a whole pixel at a time.

foo_wave_seekbar

Reply #282 –
Quote from: dhromed on
An issue: the highlight doesn't advance smoothly like the vertical bar. I tried to set it up so that the bar would be gone (0px), but highlight would stll be there, and it seems it advances a whole pixel at a time.

The highlight indeed does, as it's just a binary test per pixel whether it represents a past or future part.
If you want some light smoothing, consider a same-coloured position bar maybe, or if you're using the D3D frontend, maybe hack around a bit in the highlighting function.
I didn't put much time on smoothness for the played overlay, as the edge is hidden by the cursor.
Stay sane, exile.

foo_wave_seekbar

Reply #283 –
Is it possible to remove dead entries from the .db file?

foo_wave_seekbar

Reply #284 –
Library > Remove Dead Waveforms

Also, any possibility of getting a fix for the freezing when the computer is locked (win+L)?

foo_wave_seekbar

Reply #285 –
Depends. I haven't reproduced it here yet, so it's a bit hard to figure out what's wrong.
I do have some theories, but haven't verified them yet, I probably do not handle lost devices that well.

Does it break on lock even if you have say the GDI or Direct2D frontend, or heck, if you remove all visible bars?
Stay sane, exile.

foo_wave_seekbar

Reply #286 –
When a song ends, the cpu usage goes to 50% (one core), and the next song does not play. Unlocking the computer resumes playback with no errors or anything in the console. This only happens with "Direct 3D 9.0c", removing the UI element also stops the problem from occurring. Possibly related, Process Explorer crashes when viewing foobar's threads, and foo_wave_seekbar.dll seems to be creating and destroying them like crazy even without the UI element visible.

foo_wave_seekbar

Reply #287 –
The Process Explorer bug is a bug with Process Explorer which I have contacted the author about. The seekbar does not create threads like crazy, it's the long symbol names in the DLL that confuses it.
Stay sane, exile.
 

foo_wave_seekbar

Reply #288 –
Suddenly, the seekbar in D2D mode has decided to go to town on one of my cores, occupying between 50% and 100%. It affects the entire computer to the point where I can hardly browse folder in Explorer.

If I remove it from the layout or minimze Foobar or choose GDI, it all returns to normal instantly.

:\

What more details can I provide?

foo_wave_seekbar

Reply #289 –
Quote from: dhromed on
Suddenly, the seekbar in D2D mode has decided to go to town on one of my cores.
What more details can I provide?

I haven't had this happen on any machine I own, but you're not alone.
What OS and GPU are you on? If on Vista or Seven, do you use accelerated Aero or Aero Basic?
Stay sane, exile.

foo_wave_seekbar

Reply #290 –
XP SP3 Classic shell, Ati HD4850, AMD 5050e.
Catalyst 9.3, 2D Driver Version 6.14.10.6925
DX 4.09.000000000000000000(000)00000.0904

foo_wave_seekbar

Reply #291 –
Thank you for this component, it's amazing! Second only to the Channel spectrum panel, I think.

My only problem with it is that it makes resizing foobar incredibly sluggish even after it's hidden with $showpanel in pss, which is something that doesn't seem to happen with other visualizations. Would be nice if it removed itself from memory when it isn't visible (or whatever it is that's happening).

Other then that good job

foo_wave_seekbar

Reply #292 –
Quote from: unclean on
... it makes resizing foobar incredibly sluggish even after it's hidden with $showpanel in pss, ...
Any malfunctions when hosted in CUI are probably due to differences in how CUI handles hidden panels, as I use DUI for development and daily use.
Stay sane, exile.

foo_wave_seekbar

Reply #294 –
Thank you for that! Resizing the width and height to zero does the trick.

foo_wave_seekbar

Reply #295 –
Hi Zao, is the Direct2D display anomaly at high DPI due to driver limitations, and can it be worked around?

foo_wave_seekbar

Reply #296 –
No, it's solely in my code. I've made some misunderstanding of how Direct2D handles and propagates DPI, and it has worked properly in the past.
I'll fix it some day when I get around working on the seekbar again, I've been rather swamped with other work lately.
Stay sane, exile.

foo_wave_seekbar

Reply #297 –
I'm already happy knowing that it's not some fungled-up shoddy coding in Intel's drivers. I'm currently experiencing the same problem in Firefox's DirectWrite alpha. So it can be rectified after all!

Please don't rush a hobby project, whatever brings in the salary is more important. In fact, GDI looks sweeter than Direct2D in the Wave seekbar, just that Direct2D is smoother. Thanks for the good news and a cool component.

foo_wave_seekbar

Reply #298 –
Nice component. I am seeing it in many screenshots.

foo_wave_seekbar

Reply #299 –
I got around rolling up accumulated changes and hacks into a release, this should fix assorted crashes and niggles, including high DPI mode, probably.
Stay sane, exile.