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 797186 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

foo_wave_seekbar

Reply #75
It says it's DX 9.0.
Quote
The Intel® 82830M and Intel® 82852/82855 GM/GME graphics controllers are compatible with versions of Microsoft* DirectX* up to 9.0.


Compatible != compliant.

ok, I missed your reply. I think I have DirectX 9, it must be pixel shader support that I need. That was a problem for me with Shpeck+Milkdrop, I could only run a handful of presets.  (I didn't realise what PS meant in the OP )

Yes, it has no pixel shaders which it needs to be fully directx9 compliant.

foo_wave_seekbar

Reply #76
I have an Intel 82852/82855 GM/GME Graphics Controller: http://www.intel.com/support/graphics/intel852gm/index.htm

The Direct3D9 mode will not work on your hardware, as it's much like the Matrox Parhelia, having drivers built against the DX9 SDK but no real DX9 capabilities. For instance, querying the caps database shows a lack of both the A2R10G10B10 texture format and a supported pixel shader level of 0.0.

Also, would it be possible to scale the waveform according to replaygain values for each track/album?

In the Direct3D version, the effect has a variable that exposes the album gain/peak and track gain/peak. Some trivial math in the shader will do what you want, I haven't been bothered to look into what's in the ReplayGain values myself.
As for Direct2D, it requires explicit support from my side, as it doesn't have programmable shaders.

CUI probably does horrible things to my window when mangling layouts.

So this should be reported in the foo_ui_columns thread, right?

No. They're not Columns UI bugs, they are me not knowing about intended Columns UI behaviour and not testing much in it. musicmusic is not at fault here.

Everything loads fine, but the Waveform Seekbar shows nothing than white space? Seeking works though. (Win XP SP3, Radeon 9550)

Anything interesting in your console?

Can u fix high CPU usage? On Win7 and Pentium 4 i have ~20%, without plugin 0%

The component has a fixed update rate of 60Hz or so, which produces neglible CPU usage on my machine and GPU. I suppose it should probably be tunable.
Stay sane, exile.

foo_wave_seekbar

Reply #77
OK, here's a weird bug - I've installed the DX redistributable and followed all the instructions on this forum, but the component crashes every time I try and make it visible.  I'm using CUI on Windows 7 32-bit with a quadcore processor.  I've got the component installed and *sort of* displaying in my Layout BUT I can't make it visible.  At the moment it's obscured by the caption - if I untick "Show caption"OR if I try to stretch my foobar vertically so as to be able to see this component then my foobar instantly crashes.  This has now happened about 20 times in a row... :-(

foo_wave_seekbar

Reply #78
Quote
Everything loads fine, but the Waveform Seekbar shows nothing than white space? Seeking works though. (Win XP SP3, Radeon 9550)

Anything interesting in your console?

Not at all, thats why I noted 'everything loads fine'.
Console: Seekbar: taking Direct3D9 path. / Seekbar: Frontend initialized. / Wave cache: finished analysis of...

foo_wave_seekbar

Reply #79
It's great to have an "oohh shiny!" component that actual adds to my ability to browse and listen to my music (rather than distract from it, like most shiny components) because it actually lets me look inside my individual tracks.

Great work Zao.
This is a shining example of what third-party components should be about, IMO.
elevatorladylevitateme

foo_wave_seekbar

Reply #80
Thank you for this great plugin.

I have 2 questions/requests :
- Is it possible to choose where is located wavecache.db, i'd prefer to have it at the root of my media library folder instead of within the foobar2000 folder.

- That would be nice it could display the according image of a track (for tracks already scanned) even if playback is stopped. A kind of follow cursor if playback is stopped. And then if this is possible that would be great if double-clicking the wave could start the playback at the desired position.

foo_wave_seekbar

Reply #81
0.1.4 should hopefully give better diagnostic output and crash less for people who haven't got the relevant runtimes installed or dependencies unmet.

I have 2 questions/requests :
- Is it possible to choose where is located wavecache.db, i'd prefer to have it at the root of my media library folder instead of within the foobar2000 folder.

- That would be nice it could display the according image of a track (for tracks already scanned) even if playback is stopped. A kind of follow cursor if playback is stopped. And then if this is possible that would be great if double-clicking the wave could start the playback at the desired position.

Global database location could be configurable, I guess.

Displaying the selected track when not playing has been suggested. I'm just a bit split on whether it should scan selected tracks automatically or only on playback.
As for searching by doubleclicking, that'd probably be possible.
Stay sane, exile.

foo_wave_seekbar

Reply #82
Displaying every selected track would probably put alot of stress on the HDD, if you implement this please make it optional.
Thanks for this nice plugin.

foo_wave_seekbar

Reply #83
FB1.0b6 and WaveSeekBar 0.1.4 produce an error like "Seekbar: taking Direct3D9 path. / Seekbar: frontend creation failed: / Direct3D9: could not create effects." :-/

O$: XPproSp3

DirectX Version: DirectX 9.0c (4.09.0000.0904)
Card name: ATI Radeon 9600 / X1050 Series

Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Not Available
DDraw Test Result: All tests were successful.
D3D7 Test Result: All tests were successful.
D3D8 Test Result: All tests were successful.
D3D9 Test Result: All tests were successful.

How can we better report the errors or ia a debug/log switch possible?

foo_wave_seekbar

Reply #84
If the effect failed to compile, you should have gotten errors in your console, so it's probably a missing file.
Did you extract the effects directory into your foobar2000 or profile directory?
The structure should be:
Code: [Select]
foobar2000/
` components/
  ` foo_wave_seekbar.dll
  effects/
  ` seekbar.fx
Stay sane, exile.

foo_wave_seekbar

Reply #85
Cheers!
Works great! 

Does it consider replaygain tags when drawing?

foo_wave_seekbar

Reply #86
1.0.3 was crashing, but 1.0.4 runs! There's a slight problem on my setup, though: the peaks extend beyond the vertical space set for the seekbar, and the entire diagram seems to be offset downwards by quite a few pixels' worth. In other words, the 0 dB line isn't dead centre. Toggling the border setting provides no benefit.

I'm running Windows 7 build 7100, Foobar2000 1.0 beta 6, GMA945 Intel "Extreme" Graphics, using Direct2D 1.0 mode.

foo_wave_seekbar

Reply #87
Quote
Everything loads fine, but the Waveform Seekbar shows nothing than white space? Seeking works though. (Win XP SP3, Radeon 9550)
Console: Seekbar: taking Direct3D9 path. / Seekbar: Frontend initialized. / Wave cache: finished analysis of...
Unfortunately no changes with version 0.1.4.

foo_wave_seekbar

Reply #88
If the effect failed to compile, you should have gotten errors in your console, so it's probably a missing file.
Did you extract the effects directory into your foobar2000 or profile directory?
The structure should be:
Code: [Select]
foobar2000/
` components/
  ` foo_wave_seekbar.dll
  effects/
  ` seekbar.fx


Uuhm, mea culpa!
It works (now).

THX, rupert

 

foo_wave_seekbar

Reply #89
I have created an effect that also renders the RMS part. Since I didn't like the shading, I changed that to perform a grayscale conversion on the already played part. If you poke around in the script (see below) you can also enable a sepia-like effect.

seekbar.fx: Put this in your profile or installation directory in the effects subdirectory.

foo_wave_seekbar

Reply #90
1.0.3 was crashing, but 1.0.4 runs! There's a slight problem on my setup, though: the peaks extend beyond the vertical space set for the seekbar, and the entire diagram seems to be offset downwards by quite a few pixels' worth. In other words, the 0 dB line isn't dead centre. Toggling the border setting provides no benefit.

I'm running Windows 7 build 7100, Foobar2000 1.0 beta 6, GMA945 Intel "Extreme" Graphics, using Direct2D 1.0 mode.

The Direct2D frontend may very well be misbehaving after making it behave in high DPI scenarios (in which it's broken again).

Quote
Everything loads fine, but the Waveform Seekbar shows nothing than white space? Seeking works though. (Win XP SP3, Radeon 9550)
Console: Seekbar: taking Direct3D9 path. / Seekbar: Frontend initialized. / Wave cache: finished analysis of...
Unfortunately no changes with version 0.1.4.

Somewhat odd. Currently I'm battling some elusive crashes so I haven't looked into this much yet.
A bunch of error checks for next version ought to give some more insight. Otherwise I guess you've got to use some other frontend like the primitive GDI+ one coming up.

I have created an effect that also renders the RMS part. Since I didn't like the shading, I changed that to perform a grayscale conversion on the already played part. If you poke around in the script (see below) you can also enable a sepia-like effect.

Isn't it nice when things are customizable using proper programming languages.
Stay sane, exile.

foo_wave_seekbar

Reply #91
Could the calculation of the wave form (theoretically) be accelerated with GPU support?

foo_wave_seekbar

Reply #92
Could the calculation of the wave form (theoretically) be accelerated with GPU support?

Unlikely. Most of the cost tends to be in decoding the input.
Stay sane, exile.

foo_wave_seekbar

Reply #93
Hello,

actually a nice plugin,couldn't wait to try it.

I think wave seekbar should be perfect for music of the classical genre, e.g. long symphonic movements or the like. RMD level could be a kind of orientation when seeking particular parts like Development, Reprise, a certain loud passage.

But now, having tried, I'm a bit confused. I'm not really sure that the curve calculated by the plugin matches my perception of loudness. Sometimes it seems to me unreliable. Thus I compared the displayed graphics with that of Audacity, using Bruckner, Symphony No.9. There are spots where music is really soft while the plugin's curve makes a large amplitude - and vice versa. The Audacity curve looks quite different and seems to be more suitable regarding orientation matters.

foo_wave_seekbar

Reply #94
Thanks for this component, it looks amazing. And it works in DUI. Dunno if it was mentioned, but traktor has similiar feature and it's great to see that in foobar! Except in traktor the slider was "fixed" and wave was scrolling, and you could move entire wave left and right, causing cool vinyl sliding sound effect  But I realize it would take a lot more work to do.

Back to reality:
I got this
(on this picture we can see that wave is one-coloured)

But I saw screens with two-colored wave, plus dicrect2D mode is also two-colored. Is something wrong? My card supports ps2.0 and I'm running vista.

foo_wave_seekbar

Reply #95
But now, having tried, I'm a bit confused. I'm not really sure that the curve calculated by the plugin matches my perception of loudness. Sometimes it seems to me unreliable. Thus I compared the displayed graphics with that of Audacity, using Bruckner, Symphony No.9. There are spots where music is really soft while the plugin's curve makes a large amplitude - and vice versa. The Audacity curve looks quite different and seems to be more suitable regarding orientation matters.

The scanner divides the track into 2048 sections, and for each section it records the minimum and maximum values (and calculates RMS power). As such, the wave might seem a bit bloated compared to other visualisations.

But I saw screens with two-colored wave, plus dicrect2D mode is also two-colored. Is something wrong? My card supports ps2.0 and I'm running vista.

In the default effect, the colors are interpolated from background colour onto the border of the wave, where it uses the foreground colour. Inside of that, it shoots "past" the foreground colour towards white or black.
Try playing with the color settings in the Configure context menu item.
Stay sane, exile.

foo_wave_seekbar

Reply #96
Ugh, obviously... Thanks

foo_wave_seekbar

Reply #97
Here's a  quick mod of foosion's effect for those who would like to have the RMS rendered, but also keep the shading effect. As usual, place 'seekbar.fx' in the 'effects' folder of your foobar dir. 



Also, I'll see if I can get it to use the replaygain variable present; however, I'm not very familiar with programming, so I'm not sure if I'll have any luck.

Edit: added screenshot.
"Lifting Shadows Off a Dream"

foo_wave_seekbar

Reply #98
Fun fact of the day - this is the same shader language used to create the shaders for real games.
Stay sane, exile.

foo_wave_seekbar

Reply #99
And here's a new modification of 'seekbar.fx' that scales the waveform according to Replay Gain data. By default, it will use the track gain; however, a quick edit of the file will enable the use of the album gain mode instead.
"Lifting Shadows Off a Dream"