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

foo_wave_seekbar

Reply #375 –
Quote from: Zao on
I'll add those silly foo_lastfm_radio: and lastfm: protocols to the next version,

Thanks, the latest version works great.

Quote from: Zao on
but your HTTP claim bothers me.
Can you show a complete URL that it tries to scan together with the console output for it? If it contains sensitive fields like user/pass, censor those.
Note that messages like "Wave cache: skipping location ..." are from when the exclusion filter works. Any file that that message appears for will not be scanned.

Oops, never mind.  I misunderstood what was meant by "skipping" a track.  It skips the http:// tracks just fine (doesn't try to calculate the waveform, and the message you mentioned appears in the console), however, the progress bar tries to appear.  The progress bar flashes over the length of the seekbar a few times, and then goes to the end and stays there while the song is playing.  I'm guessing that this is because it can't properly compute the length of a streaming track, right?  Is it possible for the progress bar to completely ignore http:// tracks?

foo_wave_seekbar

Reply #376 –
Quote from: Zao on
You could use the Direct2D mode, as that draws a line at the upper and lower bound of the waveform


This mode isn't avaliable here. I guess because I'm on XP.



Quote from: Zao on
or edit the shader for Direct3D, artificially adding a constant factor to the waveform.


Ok. But shouldn't that be done by default (with the next update) to make it looking better?

foo_wave_seekbar

Reply #377 –
Quote from: Hitchhiker427 on
Is it possible for the progress bar to completely ignore http:// tracks?


Yeah, I wanted to ask the same. Would be nice if the seekbar would only show the background color for http streaming. At the moment it gets filled completely with the highlight color which is looking odd.
 

foo_wave_seekbar

Reply #378 –
I see you're on XP. That's too bad, as the following Direct2D shots will make you want to upgrade.



I played around with the shader and I couldn't hack up a decent look for such thin waveforms. The current architecture is not designed for such a thing.
Stay sane, exile.

foo_wave_seekbar

Reply #379 –
Quote from: Zao on
I see you're on XP. That's too bad, as the following Direct2D shots will make you want to upgrade.



I played around with the shader and I couldn't hack up a decent look for such thin waveforms. The current architecture is not designed for such a thing.


Alright. Thanks for trying! No big problem. But the Direct2D screenshot is looking very good indeed!

foo_wave_seekbar

Reply #380 –
Hello, this is probably going to sound retarded because I don't really know anything about computers, but I'm going to try posting about it.

A week ago, I installed the foo_wave_seekbar (0.1.11) component into foobar2000 (v1.0.1). I was very pleased with it. I promptly generated waveforms for the music I had in my playlists (only about 20 songs or so) so I could take care of the bulk of the CPU usage at once. So everything seemed dandy.

However, over the past week after installing the component, my computer has started acting up. For example, seemingly at random times, my computer would get extremely, extremely sluggish. More specifically, my CPU usage would spike to 100% for a few seconds at a time, which would cause everything on to be sluggish as one would imagine. If foobar2000 was playing music, the music would start stuttering during these slow downs, and my computer basically would be unresponsive/unusable during these periods.

If I merely had foobar2k open without any music playing, and was, for example, playing a video in MPC and my computer started slowing down, the video file's audio stream would be uninterrupted (it would NOT stutter) but new frames of the video stream would not render or whatever (basically my video and audio would desync because of the immense spike in CPU usage, I guess).

At first, I didn't think it would have been caused by foo_wave_seekbar. The first thing I did was scan my computer for spyware and viruses, which turned up nothing. Then I used SeaTools to check my hard drives (just did simple SMART and Short Drive Self Test (Short DST)), and then I verified and rebuilt my RAID unit. Anyway, after that the spike in CPU usage+slow down persisted; I then saw that v0.2.0 of foo_wave_seekbar had been released, so I upgraded to that version. However, my computer still experienced CPU usage spikes at seemingly completely random intervals.

At this point, I said "o ok" and tried removing foo_wave_seekbar from my foobar2000 components directory. Apparently, I haven't had any problems since then. I wasn't smart enough to check ProcExp or Resource Manager to see exactly what process/threads/whatever was behind the CPU usage spiking, but what I can say is that after I removed foo_wave_seekbar, I have not had any slow downs.

I really would like to use the component, so it makes me sad that foo_wave_seekbar was apparently the culprit. What I would like to ask is if anyone can give me any advice as how to truly isolate whether it is the component that caused the slow downs. Like I said, the CPU usage spikes seemed to happen entirely randomly, whether I was putting my system on load or whether I was just sitting in front of the computer chatting with people and doing nothing else---the only condition for the CPU usage spikes seemed to be to have foobar2000 open with foo_wave_seekbar installed.

If it helps, this is how I have things setup:
- Vista x64
- foobar2k outputs to a USB Audio DAC
- DirectX 10 (does it matter?)

And yeah, if I said anything dumb, it's because I don't really know anything about anything. Basically just wanted to report this and hopefully find out whether it is possible for foo_wave_seekbar to be the culprit, and if it is, whether it is possible to fix. If it isn't possible for foo_wave_seekbar to be behind my CPU usage spikes, then it must have been some strange coincidence that the sluggishness started after I installed it, and stopped after I removed it.

Also, I did check my list of components against the foobar2000 troubleshooter thing and it said that there were no problematic components found.

tl;dr version: I'm retarded, but I think that foo_wave_seekbar causes my computron to explode with massive spikes in CPU usage at random intervals. I did various scans/tests to try to figure out what the problem was, but the only thing that seemed to solve the issue was to entirely remove foo_wave_seekbar from my foobar2k directory.

foo_wave_seekbar

Reply #381 –
First you could test whether it occurs on a freshly started foobar2000 without any UI elements from it in your layout. It should do absolutely nothing then.
Then you could test whether the behaviour differs between the three frontends available (Direct3D, Direct2D, GDI), as the Direct3D one has had a bit of trouble with lost devices.
I can't really see it doing much to disturb the system in general, except for maybe excessive timer usage, or a slow disk.

If you manage to catch it in the act, try to get to the threads view of the foobar2000 process and see which thread that's eating all the CPU.
Stay sane, exile.

foo_wave_seekbar

Reply #382 –
Unfortunately, I won't be able to use the computer I've had the problems on for another 4 days or so. However, once I return, I will try the things you have suggested to possibly isolate the problem (if it pops up again).

Anyway, thanks for the reply.

foo_wave_seekbar

Reply #383 –
I think I'm having the same problem. It does not occur with no UI elements present at startup, but as soon as the element is added it eats up the cpu. Music doesn't have to be playing and changing the frontends doesn't help.

Here's the threads:


foo_wave_seekbar

Reply #384 –
What frontend are you using, and is there anything interesting in the console?
Stay sane, exile.

foo_wave_seekbar

Reply #385 –
I guess I should have checked the console first, it's rescanning all the songs again. I have no idea why, since they've all been done already. Is there a shortcut key to rescan them which I might have pressed or something?

foo_wave_seekbar

Reply #386 –
If you've terminated foobar incorrectly, the component will continue with all the scanning jobs that were in queue at last successful shutdown. I can't see how it could be anything else, really.
I've just released 0.2.2 by the way, which fixes a nasty bug at shutdown. Upgrading is strongly recommended.
Stay sane, exile.

foo_wave_seekbar

Reply #387 –
The wave seekbar doesn't work with ogg vorbis.
Could you solve this problem in one of the next updates? 

Or am I not able to install it correctly?

foo_wave_seekbar

Reply #388 –
What happens? Does it crash, does it not show any waveform, does the console say anything, what UI do you use?
Stay sane, exile.

foo_wave_seekbar

Reply #389 –
Working fine here with Ogg Vorbis.

foo_wave_seekbar

Reply #390 –
Quote from: Zao on
Changelog:
0.2.3 (2010/04/06)
Fixed the blocking on track change and 100% CPU when display is locked or some game are running.

Foobar now crashes when changing tracks while the computer is locked, the seekbar was on screen before locking, and the track changes; when foobar is minimised it works. Report submited.

foo_wave_seekbar

Reply #391 –
Curse you users, finding holes in my code!
0.2.4 is up, probably fixes the problem and ensures that all relevant state is updated on device re-acquire.
Stay sane, exile.

foo_wave_seekbar

Reply #392 –
Here two screenshots of 0.2.4:






The first image is looking ok. Taken after foobar2000 starting up in maximized window (1920x1176 pixels). The second image was taken after foobar2000 starting up in small windows size (634x387 pixels) and maximized afterwards. Obviously the waveform isn't recalculated/redrawn properly automatically on window maximize!? Looks quite ugly. Too blurry ...

foo_wave_seekbar

Reply #394 –
A problem with 0.2.4 in GDI mode:


-> maximize foobar2000 (so that we see a large waveform) - in my case the foobar window is 1920x1176 pixels large
-> open waveform seekbar configuration panel

=> Takes several seconds to open!? Makes it look like a hanging application. In "Direct3D 9.0c" mode it opens immediately!

foo_wave_seekbar

Reply #395 –
Okay it works fine with ogg vorbis.
I just rescaned all waveforms and now it works.
Before that it shew nothing, i could skip but there were no graphics.
The console doesn't say anything about the seekbar, no error or anything else.

But now it works after rescan.
I use CUI.

foo_wave_seekbar

Reply #396 –
Dandruff: Both your bugs should be fixed in 0.2.5.
The stretching was due to the device loss fixes accidentally destroyed the reset call needed to resize the backbuffer. It reused the backbuffer from first creation, no matter the window size.
The load time was because the frontend recreated the rendered waveform once per channel in the list, at least. This has been fixed.
Stay sane, exile.

foo_wave_seekbar

Reply #397 –
Quote from: Zao on
Dandruff: Both your bugs should be fixed in 0.2.5.
The stretching was due to the device loss fixes accidentally destroyed the reset call needed to resize the backbuffer. It reused the backbuffer from first creation, no matter the window size.
The load time was because the frontend recreated the rendered waveform once per channel in the list, at least. This has been fixed.


Confirmed. Both fixed! Many thanks!



Any chance to get an option to disable antialiasing completely in the future? For my taste the whole waveform drawing is too blurry ...

foo_wave_seekbar

Reply #398 –
If you're using the Direct3D mode, replace line 128 (the one with lerp from bgColor to textColor) in seekbar.fx with
: textColor;
Stay sane, exile.

foo_wave_seekbar

Reply #399 –
And for GDI mode?