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.

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?

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

Planned eventually.

QUOTE (ojdo @ Jan 4 2010, 11:01)

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.

QUOTE (NullString @ Jan 4 2010, 11:26)

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.

QUOTE (fuflo @ Jan 4 2010, 12:08)

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.

QUOTE (TomBarlow @ Jan 4 2010, 13:00)

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:

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.

This post has been edited by Zao: Jan 4 2010, 13:47

--------------------

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.

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.

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 )