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

foo_wave_seekbar

Reply #500 –
Hi Zao,

Thank you for this great component!

I use it since a long time but actually i have found a problem when tagging a file, short time after start playing :

Message:
'Could not update tags (Sharing violation) on: "<musicFileName>"'

I have installed a fresh foobar with foo_wave_seekbar only, same problem.
Hope it can help you resolving this. 

foo_wave_seekbar

Reply #501 –
Quote from: Dandruff on
I have foobar at upper right screen corner. Dragging (seeking) mouse cursor out of screen (say above foobar in this case) causes tooltip going out of screen too. Tooltip should switch position to stay in foobar window. Same when dragging to the rightmost screen edge -> tooltip should switch position to the left of the mouse cursor to stay in screen.

This still happens with 0.2.12!


Quote from: Dandruff on
Also when dragging mouse cursor very far away from the foobar window (so that even the seek cursor gets hidden) doen't hide the tooltip. So you can move the tooltip around the whole screen via mouse drag. Should be avoided.

This is fixed in 0.2.12, thanks!

foo_wave_seekbar

Reply #502 –
Hi,

thanks for this component. I would like to come back to 0.2.10 version. Where can I download it please?

foo_wave_seekbar

Reply #503 –
What do you dislike about the new version?
 

foo_wave_seekbar

Reply #504 –
It's just visually. It doesn't render the same thing, I'd rather the 0.2.10 (I didn't test the 0.2.11) for this point.

foo_wave_seekbar

Reply #505 –
Quote from: Steve Forte Rio on
I have an idea: could you add normalizing of waveforms? It can be very useful for signals with very low peaks


It's deep in the todo somewhere, along with ReplayGain adjustment.

Quote from: Kobs on
Message:
'Could not update tags (Sharing violation) on: "<musicFileName>"'


Known, but the fix is tricky and not robust. If I behave properly, any other component that tries to concurrently access the file will break it the same way.

Quote from: Dandruff on
Quote from: Dandruff on
I have foobar at upper right screen corner. Dragging (seeking) mouse cursor out of screen (say above foobar in this case) causes tooltip going out of screen too. Tooltip should switch position to stay in foobar window. Same when dragging to the rightmost screen edge -> tooltip should switch position to the left of the mouse cursor to stay in screen.

This still happens with 0.2.12!

Quote from: Dandruff on
Also when dragging mouse cursor very far away from the foobar window (so that even the seek cursor gets hidden) doen't hide the tooltip. So you can move the tooltip around the whole screen via mouse drag. Should be avoided.

This is fixed in 0.2.12, thanks!


The former needs querying of monitor rectangles and finding out the dimensions of the tooltip window itself. That requires effort, so I've put it on the mythical todo.
Hiding the tooltip on the other hand, is trivial and thus, it's done already.
Normally, the changelog tells the whole truth about what's in a release, unless I forget some minor fix or tweak.

Quote from: Nii2 on
Hi,

thanks for this component. I would like to come back to 0.2.10 version. Where can I download it please?


As far as I know, the components site only keeps the latest version, as it should.

Quote from: Nii2 on
It's just visually. It doesn't render the same thing, I'd rather the 0.2.10 (I didn't test the 0.2.11) for this point.


What frontend do you use, have you've rescanned the files with the later version?
What's different, scale, form, foot-tappityness?
Stay sane, exile.

foo_wave_seekbar

Reply #506 –
Quote from: Zao on
It's deep in the todo somewhere, along with ReplayGain adjustment.

Quote from: Kobs on
Message:
'Could not update tags (Sharing violation) on: "<musicFileName>"'


Known, but the fix is tricky and not robust. If I behave properly, any other component that tries to concurrently access the file will break it the same way.




Ok ! Thanks Zao!

foo_wave_seekbar

Reply #507 –
Ok, I'm gonna try to explain clearly with my poor english :S
I use Direct3D and I didn't rescan the files.
In previous version, I just had only one waveform for both channel display selected (right and left channel). Now, with 0.2.12, I have 2, and with my samll config it's not very nice. So, I would like to return to only one waveform. The other (minor) thing is the foreground color with latest version. It doesn't render the same nice "effect" with the same RGB adjustement than in the version 0.2.10. It's white instead of blue..
Here it is, I hope this is understanding.

Anyway, a suggestion, would it be possible to have tooltip indicating target time when focus with mouse on waveform seekbar?

foo_wave_seekbar

Reply #508 –
There is an option in the configuration for the element to downmix to just one channel. You just have to have the Center (mono) channel enabled and it will be just like before.
Stay sane, exile.

foo_wave_seekbar

Reply #509 –
I'm experiencing 50% CPU Usage (guess this is 100% on one of two cores) while using Direct3D 9.0c on this system:

AMD Athlon II X2 250
2 GB RAM
Windows XP 32bit
ATI Radeon HD 4600 Series (latest drivers)

Using foobar2000 v1.0.3 DUI (didn't try in CUI)
Waveform seekbar 0.2.12

On other system with Win7 64bit this doesn't happen.

Also, when I switch to GDI, cpu falls down to 0%.

foo_wave_seekbar

Reply #510 –
Run Process Explorer, find the thread that is consuming a whole core, copy a few representative stack traces, or create a minidump and upload it somewhere.
Stay sane, exile.

foo_wave_seekbar

Reply #511 –
Zao,

here is the screenshot of both foobar2000 and processexplorer in DUI,



and this is what happens when I use this plugin in CUI (direct3d only, GDI is good): no significant CPU usage, but it displays just this fixed glitched image:


Thank you for your time!

foo_wave_seekbar

Reply #512 –
I would blame ATI drivers. It's convenient, and wouldn't surprise me much.
Is that stack trace always the same, or does it vary a lot?
Stay sane, exile.

foo_wave_seekbar

Reply #513 –
Could be that it's due to the ATI drivers... I've had problems with ATI cards before. I recently bought a GeForce and wouldn't go back to ATI for nothing (and on that PC this doesn't happen).

foo_wave_seekbar

Reply #514 –
Quoting the 1st post:

Quote from: Zao on
Extract the archive into the foobar2000 directory (so that the effects directory is directly in your foobar2000 directory and not inside the components directory

I think you need to update these installation instructions. As of the 0.2.12, the distribution .zip contains only one file: the .dll, which apparently goes in the components directory.

Quote from: Zao on
Effects will only be loaded from profile directory now, if you have the effects directory in the application directory, move it to the profile directory (somewhere in the roaming application data, to get there, use the hidden [hold shift] »Browse configuration folder« command on the file menu).

That hidden command doesn't exist in my version of foobar2000 (1.0.3).
Maybe recommend this instead: Start > Run > %APPDATA%\foobar2000\effects
Also consider adding to this post something about the fact that seekbar.fx exists, and what it is?

Quote from: Zao on
Add UI element to the Default UI or Columns UI as normal

Took me a while to figure out that after doing this (in Columns UI), it was there, just collapsed. I had to drag the edge of the caption a bit to get the actual window to appear. Is this how it was for everyone, or does it depend on the existing layout?

Suggestion: If in the advanced prefs you have unchecked 'Analyse tracks not in the media library', and you attempt to manually extract a seekbar signature, write some kind of message to the console.

Anyway, thanks for the work you put into this component. It's awesome!

foo_wave_seekbar

Reply #515 –
Yay, feedback!
The changes in this version were mostly to conform to component site guidelines, so I changed the code and archive and didn't pay much attention to boring things such as documentation.
I've got a branch where I'm removing the .fx files completely, where the effect instead is stored in per-instance configuration. That would allow you to export your whole configuration cleanly as .fth or .fcl (I guess, don't use Columns).

As for your Columns UI snafu, it's probably due to the layout you're in, or my component not advertising a recommended size or something if there's such a thing in Columns.
In my world Columns is a second-tier platform, as I do not use it and rely on people on IRC who do to report misbehavior.

I've been blessed with a HA Wiki account recently, so I'll probably put some more structured information there eventually.
Stay sane, exile.

foo_wave_seekbar

Reply #516 –
FWIW, here's what I've done with my effect... plot is a 30 dB scale instead of linear; the plot is normalized to the track peak; orange=maxval, blue=minval, dark gray=rms.

foo_wave_seekbar

Reply #517 –
Cute. A bit too jaggy for my taste, but still.
Stay sane, exile.

foo_wave_seekbar

Reply #518 –
I have had this problem ever since using older versions of foo_wave_seekbar.
When using Direct2D mode on Windows 7 (x64, ATI Mobility Radeon HD 3650), the waveform appears outlined, while GDI is filled.

foo_wave_seekbar

Reply #519 –
The Direct2D frontend intentionally looks different. If it looked the same, there would be no need to have it.
Stay sane, exile.

foo_wave_seekbar

Reply #520 –
A taste of future freedom:

It will have a fallback effect if you make errors, it stores per-instance effects, and has live preview and error reporting.
Stay sane, exile.

foo_wave_seekbar

Reply #521 –
Cool!

foo_wave_seekbar

Reply #522 –
I feel pretty stupid but I've looked through a lot of this thread and it seems like I am the only one with this problem.
I can't figure out how to make the bar horizontal. It's stuck in the vertical position for me.

EDIT 1: Woo I figured it out. I think.

foo_wave_seekbar

Reply #523 –
It automagically detects whether it should be vertical or horizontal from the size of the element. It will be orientated such that the bar follows the longest dimension. It used to be a configuration toggle.
Stay sane, exile.

foo_wave_seekbar

Reply #524 –
Quote from: Zao on
It automagically detects whether it should be vertical or horizontal from the size of the element. It will be orientated such that the bar follows the longest dimension. It used to be a configuration toggle.


Ah that explains it. I ended up making a horizontal splitter doodle to rest it on. It made the demons in my head stop.