Skip to main content
Topic: foo_wave_seekbar (Read 556558 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_wave_seekbar

Reply #50
Thank you very much for this very promising component!

Bugs:
  • The panel is not correctly redrawn when switching (CUI) layouts: the waveform disappears and the whole panel is filled with the highlight colour. Correct appearance is restored when starting playback on a new song. Addition: The behaviour is equivalent to the second bug. The panel only visualises the song's first second.
  • When adding a second panel instance to the same or another layout, both panels stop working properly. No waveform is visible and the panel seems only to visualise the first second of the song, so the selection bar quickly "runs" through the panel and vanishes.

Feature request:
  • Allow mouse wheel to seek (just like the default seekbar does).

foo_wave_seekbar

Reply #51
storing the data in the file tags would be awesome, besides it would take advantage of the compression of the fb2k database

foo_wave_seekbar

Reply #52
thanks for this great component. and well, since everybody's asking questions, i'll ask this - where are the settings saved? i don't see a separate config file in config dir. also checked registry - nothing's there. the settings are kept after deleting wavecache.db, so it's not there. also removing the component and then restoring it ( removing foo_wave_seekbar.dll ) doesn't remove the settings. where are they?

foo_wave_seekbar

Reply #53
In the directory where foobar2000.exe is in file "wavecache.db"

There is no config file because it does need to save any configuration right now.
LAME 3.99.5 -V0

foo_wave_seekbar

Reply #54
Looks like a nice component, but it doesn't work for me. I guess it's my 5 year old laptop not having good enough hardware. I get this in the console:

Seekbar: taking Direct3D9 path.
Seekbar: frontend creation failed: Direct3D9: could not create texture.

The panel draws whatever was on the screen previously, but it still acts as a seekbar. It seems to process the songs properly as well (i.e. create the waveforms). Is there anything I can do?

foo_wave_seekbar

Reply #55
I just want to ask for a tooltip that shows the bars' time when I drag it, like the standard seekbar

Planned eventually.

Bugs:
  • The panel is not correctly redrawn when switching (CUI) layouts: the waveform disappears and the whole panel is filled with the highlight colour. Correct appearance is restored when starting playback on a new song. Addition: The behaviour is equivalent to the second bug. The panel only visualises the song's first second.
  • When adding a second panel instance to the same or another layout, both panels stop working properly. No waveform is visible and the panel seems only to visualise the first second of the song, so the selection bar quickly "runs" through the panel and vanishes.

Feature request:
  • Allow mouse wheel to seek (just like the default seekbar does).

Those aren't bugs, those are features:
  • CUI probably does horrible things to my window when mangling layouts.
  • This and the first is likely due to failing to re-acquire the proper track length, defaulting to 0, showing an infinitesimal slice of the track.

Things I didn't know existed:
  • Heh, didn't know that you could use the wheel for that. Will probably implement some day.


storing the data in the file tags would be awesome, besides it would take advantage of the compression of the fb2k database

The foobar2000 database has compression? I do not believe so. I do need to look into whether it's feasible to compress this data.

thanks for this great component. and well, since everybody's asking questions, i'll ask this - where are the settings saved? i don't see a separate config file in config dir. also checked registry - nothing's there. the settings are kept after deleting wavecache.db, so it's not there. also removing the component and then restoring it ( removing foo_wave_seekbar.dll ) doesn't remove the settings. where are they?

The only settings it has currently is per instance of the UI panel/element, which are stored using the DUI/CUI configuration framework.

Looks like a nice component, but it doesn't work for me. I guess it's my 5 year old laptop not having good enough hardware. I get this in the console:

Seekbar: taking Direct3D9 path.
Seekbar: frontend creation failed: Direct3D9: could not create texture.

The panel draws whatever was on the screen previously, but it still acts as a seekbar. It seems to process the songs properly as well (i.e. create the waveforms). Is there anything I can do?

Ooh, fun.

I have a fallback path that is good enough for the horrible Intel cards, but apparently not horrible enough.
What kind of graphics hardware do you have?
The fallback path uses an A2R10G10B10 (2 bits alpha, 10 bits for each of red, green, blue) for the waveform data, but I suppose one might try A8R8G8B8 if that fails.
Zao shang yong zao nong zao rang zao ren zao.
To, early in the morning, use a chisel to build a bathtub makes impatient people hot-tempered.

foo_wave_seekbar

Reply #56
crashes my foobar when i try to place the component.

win7 x64, foobar 1.0 beta6



will directx 9.0c co-exist peacefully with directx 11?

i ended up having other windows problems to deal with last night. the seekbar works fine and looks cool.

foo_wave_seekbar

Reply #57
I guess zooming (middle scroll) is out of question? (in case some time grid is added as requested)

foo_wave_seekbar

Reply #58
The data set used is rather sparse, just 2048 data points. You'd just be looking at interpolation when zooming or with a large enough window.
Zao shang yong zao nong zao rang zao ren zao.
To, early in the morning, use a chisel to build a bathtub makes impatient people hot-tempered.

foo_wave_seekbar

Reply #59
I wouldn't mind seeing large blocks if it is feasible 
It's CEP/AU behavior I'm used to, scroll to zoom or middle click then slide to go right/left

foo_wave_seekbar

Reply #60
I'll put that under the category »maybe if I'm horribly bored some day«.
Zao shang yong zao nong zao rang zao ren zao.
To, early in the morning, use a chisel to build a bathtub makes impatient people hot-tempered.

foo_wave_seekbar

Reply #61
deal

foo_wave_seekbar

Reply #62
Well just to say thankyou for this component - it's really great .

Also, would it be possible to scale the waveform according to replaygain values for each track/album?
"Lifting Shadows Off a Dream"


foo_wave_seekbar

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

foo_wave_seekbar

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


foo_wave_seekbar

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

I'll update my driver and see if that makes a difference.

I'm afraid you're out of luck.

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

Are you using D2D?

foo_wave_seekbar

Reply #68
DX 9.0c


foo_wave_seekbar

Reply #70
storing the data in the file tags would be awesome, besides it would take advantage of the compression of the fb2k database

The foobar2000 database has compression? I do not believe so. I do need to look into whether it's feasible to compress this data.

right, some compression would be appreciated. The .db file weights 730MB, and the compression ratio is like 75% (using rar). not that it matters, because the indexing of the data and the requirement of secuential reading to decompress the whole db would make it not feasible.

although these sqlite extensions might point you to a better approach, compressing each row with zlib:
http://www.mail-archive.com/sqlite-users@s...g/msg17018.html
(which is wrapped in a better way here)
http://geomapx.blogspot.com/2009/11/fts3-compression.html
or an alternative,
http://lserinol.googlepages.com/sqlitecompress



foo_wave_seekbar

Reply #73
I'll update my driver and see if that makes a difference.

I've updated my driver, problem still exists

A driver update won't resolve the non-existent DirectX 9 support of your GPU.

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.
Windows 10 Pro x64 // foobar2000 1.3.10

foo_wave_seekbar

Reply #74
A driver update won't resolve the non-existent DirectX 9 support of your GPU.

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 )

 
SimplePortal 1.0.0 RC1 © 2008-2018