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

foo_wave_seekbar

Reply #325
My ulterior motive with this component is to educate the unwashed masses in the finer points of programmable shader pipelines.

Hahaha, I knew there was more to your plan.

Anyway, I'll put it on the todo, if it's not already there somewhere.

Cool, if you get to it, great. Even if you don't, I'm still using and loving this plugin so thanks!

foo_wave_seekbar

Reply #326
Could you add a "force rescan waveform" option? I recently had a few tracks i'd mis-tagged (wrong order), and after I fixed the tags and renamed them again, the old waveforms still applied to the new tracks, with no way to fix them.

That feature accidentally disappeared when reworking the queue system a few versions ago. It should be fixed for the next version, which also will have a rewritten analysis core, which will cure most phase issues.
Stay sane, exile.

foo_wave_seekbar

Reply #327
I've made some work towards supporting multiple channels.
If I decide to do that, there will be slightly more work when loading the waveform as well as an increase in database disk usage (probably) linear to the number of channels.
Is this something that's acceptable? I've added transparent compression so the hit should probably be around 1-1.5x for stereo files, tops.
Stay sane, exile.

foo_wave_seekbar

Reply #328
How and why would it affect stereo file behavior?

foo_wave_seekbar

Reply #329
Because currently I only persist a single channel of mixed down information.
The proposal is to persist each channel individually and display either a mixed down display or separate channel displays.
Stay sane, exile.

foo_wave_seekbar

Reply #330
OK, waiting for your implementation 
It's not very clear to me what you mean with 1-1.5x: is it additional CPU work or you talk about disk space increase compared to current for stereo files
I take your talk for CPU when scanning stereo files

foo_wave_seekbar

Reply #331
I've made some work towards supporting multiple channels.
If I decide to do that, there will be slightly more work when loading the waveform as well as an increase in database disk usage (probably) linear to the number of channels.
Is this something that's acceptable? I've added transparent compression so the hit should probably be around 1-1.5x for stereo files, tops.


I think any increase in CPU usage for extracting the waveform is acceptable because of the extract seekbar option that lets me do all that work up front anyway. 50% increase filesize for double the channels seems reasonable to me as well, I say go for it.

foo_wave_seekbar

Reply #332
The analysis will take twice as long for stereo, six times as long for 5.1, etc. That's already implemented, and won't change.
The disk storage will double for stereo files, etc. Although, with compression, I expect it to rise with 50% or so, at most.
There will be a slight increase in CPU usage for loading a waveform, but it's neglible as the amounts of data is so small.
Stay sane, exile.

foo_wave_seekbar

Reply #333
What will happen with current data?

foo_wave_seekbar

Reply #334
Currently, old data is untouched. It will probably be interpreted as a mono signal.
Rescanning files will replace them with the new format, with multiple channels and compression.
I could implement some compression functionality of old data, but as the generation method has changed, one probably wants to rescan anyway.
Stay sane, exile.

foo_wave_seekbar

Reply #335
Don't want to sound demoralizing but I would also appreciate option not to use this advanced feature if it's somehow possible without sticky "last working for me version" option

Maybe:
- prolong CPU and storage even further with providing "mixed" mode data in normal state, and
- just work (scan and show) in "mixed" mode for users who want single wave representation

foo_wave_seekbar

Reply #336
rescanning would be odd, but nothing serious
compression is appreciated. the db weights a lot currently, even with just mono signatures

foo_wave_seekbar

Reply #337
For me it does not show up at all. the panel just remains blank and if i click on it it restarts the song. that's it. I installed the DirectX August 2009 Redistributable and the DirectX February 2010 runtime redistributable. I also installed Microsoft Visual C++ 2008 Redistributable Package (x86), but im sure that was useless because im running windows 7 ultimate x64. any ideas about how to fix this?

foo_wave_seekbar

Reply #338
For me it does not show up at all. the panel just remains blank and if i click on it it restarts the song. that's it. I installed the DirectX August 2009 Redistributable and the DirectX February 2010 runtime redistributable. I also installed Microsoft Visual C++ 2008 Redistributable Package (x86), but im sure that was useless because im running windows 7 ultimate x64. any ideas about how to fix this?

Try right clicking, configure, and replacing DirectX with GDI. That worked for me.

Great component by the way, the only thing that lacks for now is a tooltip to indicate the track time.

foo_wave_seekbar

Reply #339
Don't want to sound demoralizing but I would also appreciate option not to use this advanced feature if it's somehow possible without sticky "last working for me version" option

Maybe:
- prolong CPU and storage even further with providing "mixed" mode data in normal state, and
- just work (scan and show) in "mixed" mode for users who want single wave representation

I want this too. My computer is slow and old. And I am happy with just showing the mixed way. But sometimes I want to see how the stereo is, or how the multiple channels looks. If there is some difference between channels.

foo_wave_seekbar

Reply #340
There will likely be no significant speed difference between the "old", mono scanning method and the new multi-channel one. There will be a bit more storage, that's about it. Those of you with slow computers do not fear! Zao still loves you.

foo_wave_seekbar

Reply #341
For me it does not show up at all. the panel just remains blank and if i click on it it restarts the song. that's it. I installed the DirectX August 2009 Redistributable and the DirectX February 2010 runtime redistributable. I also installed Microsoft Visual C++ 2008 Redistributable Package (x86), but im sure that was useless because im running windows 7 ultimate x64. any ideas about how to fix this?

Try right clicking, configure, and replacing DirectX with GDI. That worked for me.

Great component by the way, the only thing that lacks for now is a tooltip to indicate the track time.


I can't even do that. When I put it in a panel and right click the option that says waveform seekerbar is faded out

foo_wave_seekbar

Reply #342
For me it does not show up at all. the panel just remains blank and if i click on it it restarts the song. that's it. I installed the DirectX August 2009 Redistributable and the DirectX February 2010 runtime redistributable. I also installed Microsoft Visual C++ 2008 Redistributable Package (x86), but im sure that was useless because im running windows 7 ultimate x64. any ideas about how to fix this?

Try right clicking, configure, and replacing DirectX with GDI. That worked for me.

Great component by the way, the only thing that lacks for now is a tooltip to indicate the track time.


I can't even do that. When I put it in a panel and right click the option that says waveform seekerbar is faded out

Maybe you have to wait a little, like me, it will not show up immediately. It is not play a song and see the waveform. It have to seek in a song for peaks and then display. Happen this to me. I have an AMD XP 2400+ processor and no video card, 512MB RAM. I use GDI.

foo_wave_seekbar

Reply #343
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.


That modification would be oh-so-very useful for me, but for whatever reason it is not working... same waveform regardless if replaygain-values are present or not. Same waveform regardless of album- or track mode. Any idea? Thx.
Back off haters - strictly love we deal with.

foo_wave_seekbar

Reply #344
That modification would be oh-so-very useful for me, but for whatever reason it is not working... same waveform regardless if replaygain-values are present or not. Same waveform regardless of album- or track mode. Any idea? Thx.


It works fine here.. Now waveforms seem to be RG-independent. But non replaygained files return an empty waveform. Guess it's normal.

 

foo_wave_seekbar

Reply #345
When querying for non-existant replaygain, the track and album gain is -1000, and the peaks are -1. Adjusting the effect to test for negative values will likely do the trick.
Stay sane, exile.

foo_wave_seekbar

Reply #346
Just an idea where such seekbar will be also useful - a graphic scale in am/fm radio receiver. One will see the points where signal is clear.

foo_wave_seekbar

Reply #347
That would be quite out of scope of the component though, and more suitable for a domain-specific component, most probably integrated with whatever AM/FM tuner component you're using.
Stay sane, exile.

foo_wave_seekbar

Reply #348
A teaser of things to come:


Is this configuration UI something that looks friendly and usable with regard to reordering the display of channels and toggling their visibility?

In my development version, it's fully functional and the Direct3D9 mode can display channels as can be seen in the above images. It also has other nice features like storage compression, optional multi-channel scanning and storage, an rescan command that actually works, and more. The next release will require some slight modifications to effect files to handle the additional texcoord parameter fed to it, but it should be a three line change in most cases.

And oh, before I forget it, a new Process Explorer version has been released, which fixes the Process Explorer crash bug that my component caused due to being too awesome (and having too long symbols, but I blame it on being awesome).
Stay sane, exile.

foo_wave_seekbar

Reply #349
Awesome. This is the feature I dreamed of.

It would be nice if it would be a part of the toolbar. So it could replace the seekbar completely.