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

foo_wave_seekbar

Reply #775 –
Could you (with proper backups of your profile and components) try 0.2.13.6? It's a preview release, not tested enough to be a properly released.
Stay sane, exile.

foo_wave_seekbar

Reply #776 –
Quote from: Zao on
Could you (with proper backups of your profile and components) try 0.2.13.6? It's a preview release, not tested enough to be a properly released.

Any other change than the character fix?

foo_wave_seekbar

Reply #777 –
That depends on which version I last linked in public. Squinting at the commit history since 0.2.13.1:
  • Frontend discovery using the right encoding for paths.
  • Preliminary CUI toolbar element support.
  • Fixed a bug with drag cancellation.
  • Holding the control key while dragging on the seekbar decodes the region to the clipboard for pasting into audio editors.
  • Added LZMA compression for waveforms. Edit: not actually used yet, just has rudimentary benchmarking of waveform sizes.
  • Added Scintilla editor pane for D3D effects.

There's probably more in there that's not covered by commit messages.
Stay sane, exile.

foo_wave_seekbar

Reply #778 –
It works!

foo_wave_seekbar

Reply #779 –
great job of seek bar wave, I use it for a long time foobar, Hair of the scrambled audio as inthe clipboard not work for me ..All DLLs are in the same folder as user foobar components .. or have a different location each? use the 0.2.13.6. danks

foo_wave_seekbar

Reply #780 –
You should not need to extract it manually at all. Just drag the ZIP onto the Components pane in Preferences and it installs for you.
If you really really want to install it manually, everything should be in the user-components\foo_wave_seekbar directory of your foobar2000 profile.

What did you mean by "Hair of the scrambled audio as inthe clipboard not work for me"?
Stay sane, exile.

foo_wave_seekbar

Reply #781 –
Hallo..:-)
wanted to know if you can drag a selection of audio, as I read before, or got it wrong:
"Holding the control key while dragging on the seekbar decodes the region to the clipboard for pasting into audio editors."

That would be great ..jej  since I work with sound effects, and that in foobar, and that would be fine in foobar ..

foo_wave_seekbar

Reply #782 –
Quote from: eddi5 on
Hallo..:-)
wanted to know if you can drag a selection of audio, as I read before, or got it wrong:
"Holding the control key while dragging on the seekbar decodes the region to the clipboard for pasting into audio editors."

That would be great ..jej  since I work with sound effects, and that in foobar, and that would be fine in foobar ..

You can. There is just no feedback visually. You just see the cursor moving

foo_wave_seekbar

Reply #783 –
As mzso said, the copy functionality has no visible UI and is quite unpolished. It will also not copy anything longer than a few minutes as a safeguard against accidentally copying a five hour megamix. I made it by request from some lad on ICQ earlier this summer. (Hi Gleb!)
The set of applications that understand clipboard audio seems to be a bit limited. Adobe Audition understands it, while Audacity doesn't.

Hold Ctrl, press down the mouse cursor where you want to start copying from.
Drag it (without any visual showing) to where you want to stop copying.
Release and the data should be on your clipboard.
Stay sane, exile.

foo_wave_seekbar

Reply #784 –
thanks to everyone, the installation of the componet was not really the problem, after several attempts I managed to have an audio on the clipboard, and I've taken two audio editors. the few seconds to get enough sample, It works! ;-)
Zao, they really appreciated the componet ... thanks

foo_wave_seekbar

Reply #785 –
When I play some tracks for the first time, they get analyzed once. When I play other tracks for the first time, they gets analyzed twice. That is, sometimes the console will say Wave cache: finished analysis of "(whatever)" two times in a row (after the same delay and CPU spike) instead of just once.

I haven't figured out why this happens or how to make it happen consistently, but it happens so often, it's causing me grief when I play very long tracks. During the analysis of a long track (90-minute DJ set or whatever) my laptop's CPU gets pegged, and then to prevent overheating, the CPU is being throttled. The throttling just trades one problem for another; the CPU temp doesn't drop, it just holds steady while the analysis runs that much longer, and the longer it goes, the more likely the temperature is to creep up past whatever the threshold is that makes the OS go to sleep. When it tries to go to sleep as the CPU is throttled and overheating, the computer is useless for 15 minutes.

Even if I set the concurrent threads to 1, that just causes the analyses to be done in series instead of in parallel; it's not really much help.

Is there anything that can be done?

foo_wave_seekbar

Reply #786 –
Have you've considered fixing the underlying cause - the computer that can't handle some load? 
On a more serious note though, I could probably add an advanced preference that inhibits pre-emptive scanning of the next track and implicit scanning of tracks you're just starting to play.

As for dual scanning, I can't quite pinpoint what would cause it, but it might be a benign race in queuing the track and attempting to retrieve the waveform, or it might be related to the next-track functionality.
Stay sane, exile.

foo_wave_seekbar

Reply #787 –
I've definitely been looking into ditching this laptop (HP Pavilion dv4-1125nr), but it's my only option at the moment.

The dual scanning doesn't seem to be related to the scanning of the next track. I mean, it happens even if there's no next track.

foo_wave_seekbar

Reply #788 –
Quote from: mjb2006 on
I've definitely been looking into ditching this laptop (HP Pavilion dv4-1125nr), but it's my only option at the moment.

The dual scanning doesn't seem to be related to the scanning of the next track. I mean, it happens even if there's no next track.



Older reply from Zao: http://www.hydrogenaudio.org/forums/index....st&p=719090

foo_wave_seekbar

Reply #789 –
Seems like the internet has a better memory than I do 
Stay sane, exile.

foo_wave_seekbar

Reply #790 –
Quote from: Zao on
Could you (with proper backups of your profile and components) try 0.2.13.6? It's a preview release, not tested enough to be a properly released.

Trying it at the moment.

By the way, do you remember my problems with tracks skipping at the beginning until the waveform was scanned. Well, I think I narrowed it to this component as I am not using that buggy lyrics component any more. Let's see if this new version has fixed the problem.

foo_wave_seekbar

Reply #791 –
Hi!

Just noticed (with ati tray tools osd) that the waveform seekbar runs at ~11 fps. Why is that? I wouldn't think that moving a line on a static background would use considerable processing power. And its rather stuttery when shorter songs play.

foo_wave_seekbar

Reply #792 –
The update rate is tuned as to not consume excessive resources for no discernible gain for typical songs.
If you wish to adjust the update rate, there's an advanced preferences setting where you can bump it up to 200%.
Stay sane, exile.

foo_wave_seekbar

Reply #793 –
Quote from: Zao on
The update rate is tuned as to not consume excessive resources for no discernible gain for typical songs.
If you wish to adjust the update rate, there's an advanced preferences setting where you can bump it up to 200%.

Where? How?

foo_wave_seekbar

Reply #794 –
Preferences > Advanced > Tools > Waveform Seekbar.
Windows 10 Pro x64 // foobar2000 1.3.10
 

foo_wave_seekbar

Reply #796 –
Using 0.2.13.7, just wondering if it's normal to see "Memory - Commit Size" go from 90MB to 480MB when you play one track, then to 860MB when you play a second track. Great components, cheers.

foo_wave_seekbar

Reply #797 –
Quote from: bwsilverbolt on
Using 0.2.13.7, just wondering if it's normal to see "Memory - Commit Size" go from 90MB to 480MB when you play one track, then to 860MB when you play a second track. Great components, cheers.

Yeah, but it tops off at that value.  Anyway, I can confirm that it leaks pretty badly. Rather unfortunate, that it was introduced with the released stable version. of which I didn't know because it wasn't announced in this forum.

foo_wave_seekbar

Reply #798 –
I cache away one LZMA encoder for each analysis thread to avoid recreating them constantly. Apparently they keep a whole lot of state.
Stay sane, exile.

foo_wave_seekbar

Reply #799 –
Latest version is a leaker. This is how ram consumption evolved in my case (MEMORY - COMMIT SIZE, both in MB)
Foobar startup: 114 - 160
Track 1: 196 - 555
Track 2: 200 - 560
Track 3*: 331 - 1.315
and it seems to stick there

* this track was scanned for the first time ever.