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

foo_wave_seekbar

Reply #700 –
The problem is that I've got lots of half-arsed changes in there, due to some version control misuse.
I've got a visual shader editor that kind of works. I've got per-instance effects for the D3D case. I've stopped using a filesystem file for the effects. It has each frontend (almost) in a separate DLL.
It will require you to rescan all your tracks again (due to the malformed data problem).

But sure, if you feel adventurous - 0.2.13 here.
Do let me know how it works, I haven't tried deploying it to anyone outside my circle of insane testers.

Make sure to backup the configuration, as I've never meant it to be downgradable.
Stay sane, exile.

foo_wave_seekbar

Reply #701 –
Quote from: Zao on
The problem is that I've got lots of half-arsed changes in there, due to some version control misuse.
I've got a visual shader editor that kind of works. I've got per-instance effects for the D3D case. I've stopped using a filesystem file for the effects. It has each frontend (almost) in a separate DLL.
It will require you to rescan all your tracks again (due to the malformed data problem).

But sure, if you feel adventurous - 0.2.13 here.
Do let me know how it works, I haven't tried deploying it to anyone outside my circle of insane testers.

So far I had no problems. I can confirm that the memory doesn't increase anymore. As for the new features I wouldn't know how to try them. (Well, I could change stuff per panel and use the new mirror option, and noticed the "frontend settings" which I have no clue what is for)

foo_wave_seekbar

Reply #702 –
0.2.13.1 should be slightly more accepting of old shaders, if someone's affected by that.
Remember, it's still not production quality.
Stay sane, exile.

foo_wave_seekbar

Reply #703 –
Wooo progress 

Some things I've noticed so far:
  • Ctrl+a doesn't work in the frontend settings
  • Clicking load default doesn't update the waveform the way pasting it in does
  • Perhaps Extract/Remove signature in the context menu should be grouped
  • A search for "%waveform_channel_count% MISSING" freezes foobar2000, possibly the same problem as foo_covers freezing with "%albumart_front% MISSING"
  • %waveform_channel_count% does not display correctly when added as a custom column in the playlist view, most tracks show the number 18 and when selected change to nothing
The last two may have been due to the malformed data problem, with a new database "%waveform_channel_count% MISSING" appears to work .

EDIT: first crash after making an autoplaylist of missing waveforms, extracting some, and then watching it flicker in EsPlaylist for a bit.

foo_wave_seekbar

Reply #704 –
When I'm trying to replace old version with it I got startup error:

Failed to load DLL: foo_wave_seekbar.dll
Reason: This component is missing a required dependency, or was made for different version of foobar2000.


foobar 1.1.5

foo_wave_seekbar

Reply #705 –
Anomalous:
The effect editor is miserably inconsistent and pitiful, so don't expect it to be working that well at all.
As for the crashes you have, I've probably botched something with %waveform_channel_count% as it's been a bit spuriously visible here.
I should probably force a database purge next to ensure that any old incompatible data is really gone.

rol:
It is now out of necessity built against the dynamic VC10 runtime, so you need this redistributable installed.
Stay sane, exile.

foo_wave_seekbar

Reply #706 –
Hi Zao,
thanks for this great add-on.

Can I offer a few trivial suggestions, as long-time user of foobar, but one who has never bothered with add-ons in the past.

It would have saved me a bit of time and confusion if there was a bit more detail in the instructions.
Example: for the DX runtime, add the explicit statement that "this is required for all systems, including Window-7."
As was apparent in recurrent posts to the forum, it is not clear to ordinary users that this provides extra features not present in the standard DX-11 installation.
In addition, the linked page is now dated November-2010 for the web installer, although the offline download is labelled as the June 2010 update. Perhaps just calling it the "latest version" would be simpler.
I think part of the confusion, at least for me, lies in Microsoft's obscure naming system.  As far as they are concerned the "Direct-X runtime" is already installed with the OS. This extra installation is the "Direct-X end-user runtime", although I am baffled as  to how I am supposed to tell them apart with names like that.

For the DX2D you could say the Platform Update is "not required for Win-7."

foo_wave_seekbar

Reply #707 –
In a perfect world, users would take the instructions at face value and stop making assumptions.
Stay sane, exile.

foo_wave_seekbar

Reply #708 –
Hi Zao,
Nice to see updates regarding the component again.
Any update about media library notifications integration (automatically re-scan on file change under the same name etc.).
Thanks.

foo_wave_seekbar

Reply #709 –
The only Media Library-related functionality I have currently is a setting to avoid scanning tracks that are not present in the Media Library at all.
It's on the suggestion list, somewhere.
Stay sane, exile.

foo_wave_seekbar

Reply #710 –
Hi Zao! Great plugin, and works perfectly for me!

Feature request, though: normalize the waveform so that it's as tall as the seekbar.

Again, this plugin is kickass!

foo_wave_seekbar

Reply #711 –
Quote from: Zao on
The only Media Library-related functionality I have currently is a setting to avoid scanning tracks that are not present in the Media Library at all.
It's on the suggestion list, somewhere.


Thanks for the quick reply, Zao.
Glad to hear it's still being considered 
Any idea when you might have time to implement new features such as this one?
 

foo_wave_seekbar

Reply #712 –
Somewhere between Duke Nukem Forever and the heat death of the universe. As usual, I'm completely bogged down with work. I'm not really actively developing, I just dedicated some procrastination time to fixing the memory leak above.
Stay sane, exile.

foo_wave_seekbar

Reply #713 –
Quote from: Zao on
Somewhere between Duke Nukem Forever and the heat death of the universe. As usual, I'm completely bogged down with work. I'm not really actively developing, I just dedicated some procrastination time to fixing the memory leak above.


  appreciated.

foo_wave_seekbar

Reply #714 –
Nice plug! Thanks!
Please add a pseudo-transparent background option!

foo_wave_seekbar

Reply #715 –
A good while ago the D3D backend supported loading arbitrary textures you could sample from in the effect file.
That functionality may still be alive, I haven't looked at that part of the code in ages.


It is (essentially) impossible to attain proper transparency (in panel stacker or so) in the D3D case, and nothing I have bothered implementing in GDI or D2D.
Stay sane, exile.

foo_wave_seekbar

Reply #716 –
Hi forum!
I love waveform seekbar. Thanks a lot for that component, Zao!

A while ago, I asked for a seekbar.fx file, that scales with replay-gain information, so that all waveforms have the same size. I have absolutely no idea how he did it, but some nice guy uploaded me this file:
http://dl.dropbox.com/u/7136456/seekbar.fx

It worked perfectly. If a waveform was too flat (because the track volume was too low), I scaned the file and the volume and wavform were raised.
That has changed now. Don't know why, but when I replay gain-scan my files, the waveforms get smaller now. They're all set to 3/4th of the size of my waveform seekbar. I want full 4/4th!

Can anybody help?

foo_wave_seekbar

Reply #717 –
0.2.13.1 turned my foobar really sluggish. After switching 4 or 5 songs foobar would just freeze for a couple of seconds. I had to go back to 0.2.12

foo_wave_seekbar

Reply #718 –
What a nice contribution to my Foobar2k setup!

I use it borderless and in mono mode. Perhaps this seekbar can hint at what songs are subject to overdriven compression in the mixing/mastering.

Question: Does this seekbar have some kind of 3D display function?

The configuration has a 2D and a 3D option for the rendering. I just cannot tell if the difference is that great.

foo_wave_seekbar

Reply #719 –
What actually gets rendered isn't quite the same from mode to mode, but no, nothing is 3D! Windows has different APIs for drawing things on the screen. GDI+, Direct3D, Direct2D ... the component can use whichever of these is available. The difference is mainly how much CPU usage they take... GDI+ requiring the most effort.

foo_wave_seekbar

Reply #720 –
SASN: I had no idea that you had edited your message with a question, as the forum only notifies me on new posts.
As mjb2006 says, there's no "3D" mode as far as drawing some kind of geometry, I only use Direct3D to get cheap rasterisation of the waveform image, as that is a task that programmable shaders excels at.
It _would_ be possible to write something fancy if I had bothered to expose the waveform API to other components, but there's no such thing currently.
Stay sane, exile.

foo_wave_seekbar

Reply #721 –
A little suggestion: Please make it possible to display the channel names in the seekbar. For example common 4 channel audio might yield FL, FR, SL, SR and usual stereo tracks may yield L and R.

foo_wave_seekbar

Reply #722 –
Maybe for the future. I thought that I exposed the channel number for the D3D mode as a semantic, but it seems that it's not present.
As for actually drawing text, that would be a bit painful, and wouldn't be remotely customizable, as that involves way too much UI.
Stay sane, exile.

foo_wave_seekbar

Reply #723 –
Quote from: Zao on
Exit foobar2000.
Download the sqlite3 shell, unpack somewhere.
Then drag the wavecache.db onto the sqlite3.exe to launch it.
Finally type the command DELETE FROM job;

That will purge all pending scan jobs from the seekbar.
Some day in the far future, I might add in that functionality into the GUI, but as it involves creating new UI, it's quite low priority. Something else I've been considering is adding a menu item to remove signatures.


Why is it necessary to download the dll? Just throw the seekbar data file in the trash manually. It would be great if there's were a option to manually enter how the cache behave in seekbar.

foo_wave_seekbar

Reply #724 –
Quote from: djchristian on
Quote from: Zao on
Exit foobar2000.
Download the sqlite3 shell, unpack somewhere.
Then drag the wavecache.db onto the sqlite3.exe to launch it.
Finally type the command DELETE FROM job;

That will purge all pending scan jobs from the seekbar.
Some day in the far future, I might add in that functionality into the GUI, but as it involves creating new UI, it's quite low priority. Something else I've been considering is adding a menu item to remove signatures.


Why is it necessary to download the dll? Just throw the seekbar data file in the trash manually. It would be great if there's were a option to manually enter how the cache behave in seekbar.

I said to download an EXE, and the purpose was not to get rid of all the data, but to selectively remove jobs that for some reason are stuck.

As for an option to control what it stores and where, it's been on the todo for a good while, but it's something that has wide ramifications if it goes wrong, and adds lots of complexity, both configuration-wise and code-wise.

Currently, there's limited support to ignore things not in the media library. It might degrade decently if you scan the music you want and then write-protect the database file as a stopgap measure.
Stay sane, exile.