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

foo_wave_seekbar

Reply #200 –
Change AddressV in the sampler to Clamp instead of Wrap.
The reason is that with Wrap, the texture is tiled and the topmost texel is filtered together with the bottommost and vice versa.
Your texture coordinates may be slightly off, but it should not be noticeable much.
Stay sane, exile.

foo_wave_seekbar

Reply #201 –
Thank you for this nice plug-in
v0.1.10 seems to be a bit faster on analyzing than v0.1.9. With v0.1.10 it takes about 1,5 seconds on average to analyze, v0.1.9. used up to 3 seconds to analyze.

foo_wave_seekbar

Reply #202 –
I'm for looking for some help on editing the seekbar.fx file.  This should be easy, but I can't figure it out.  Basically, I'd like to add a 1px border around the selection rectangle.  I like using the "no border" option and making the background blend into my UI.  Unfortunately, I don't like the transition from the background color to the highlight color. 

So, what I have currently is this (using Hengest's replaygain effect):


What I'd like is this:


Thanks.

foo_wave_seekbar

Reply #203 –
Code: [Select]
float4 played( float pos, float2 tc, float4 fg, float4 bg, float alpha)
{
    float4 c = bg;
    float2 d = 1 / viewportSize;
    if (pos > tc.x)
    {
        if (tc.x < d.x || tc.y >= (1 - d.y) || tc.y <= (2 * d.y - 1))
            c = fg;
        else
            c = lerp(c, fg, saturate(alpha));
    }
    return c;
}
Stay sane, exile.

foo_wave_seekbar

Reply #204 –
Thanks, that worked well.

foo_wave_seekbar

Reply #205 –
2Zao

Everest.exe report about version directx in my Windows 7/32 ultimate  - 11.
I  run dxwebsetup.exe and install all updates of directx 9.0.
Now I try change frontend mode to Directx3d 9.0c and waveseekbar panel is freeze.
Console report:
"Seekbar: taking Direct3D9 path failed."
I use Nvidia 8500 GT graphic card.

foo_wave_seekbar

Reply #206 –
Did you install the specific DirectX August 2009?
Windows 10 Pro x64 // foobar2000 1.3.10

foo_wave_seekbar

Reply #208 –
For future information, the only usage scenarios I've personally verified works are as a DUI element or inside of a regular vertical/horizontal splitter in CUI.
A long time ago I tried it inside that Panel Stack plugin and made so that it at least didn't crash much, but I wouldn't say it "supports" PSS.

Quote from: pIv on
Now I try change frontend mode to Directx3d 9.0c and waveseekbar panel is freeze.
Console report:
"Seekbar: taking Direct3D9 path failed."
I use Nvidia 8500 GT graphic card.


I have searched my codebase and cannot find that message being emitted. Can you copy/paste it as-is?
Stay sane, exile.

foo_wave_seekbar

Reply #209 –
Quote from: Zao on
Quote from: pIv on
Now I try change frontend mode to Directx3d 9.0c and waveseekbar panel is freeze.
Console report:
"Seekbar: taking Direct3D9 path failed."
I use Nvidia 8500 GT graphic card.


I have searched my codebase and cannot find that message being emitted. Can you copy/paste it as-is?


Sorry now I place rigth condole log (copy-paste)
Quote
Seekbar: taking GDI path.
Seekbar: Frontend initialized.
Seekbar: taking Direct2D1 path.
Seekbar: Frontend initialized.
Opening track for playback: "I:\Audio\Jazz\Various Artists\2000 - El.Condor.Pasa\01 Lianto de una paloma.mpc"
Wave cache: finished analysis of "I:\Audio\Jazz\Various Artists\2000 - El.Condor.Pasa\01 Lianto de una paloma.mpc"
Wave cache: finished analysis of "I:\Audio\Jazz\Various Artists\2000 - El.Condor.Pasa\02 Thinku.mpc"
Seekbar: taking Direct3D9 path.
Seekbar: frontend creation failed: Direct3D9: could not create device.
Seekbar: taking Direct2D1 path.
Seekbar: Frontend initialized.
Reopening played file after update: "I:\Audio\Jazz\Various Artists\2000 - El.Condor.Pasa\01 Lianto de una paloma.mpc"
Seekbar: taking GDI path.
Seekbar: Frontend initialized.


I choose GDI, Direct2D1 and Direct3D9 frontend mode, then GDI again.

foo_wave_seekbar

Reply #210 –
That's ... surprising.
I guess I should add more error handling in that area, but it should have no problems whatsoever on that card.
Do you have proper drivers from NVIDIA installed?
Stay sane, exile.

foo_wave_seekbar

Reply #211 –
Quote from: Zao on
That's ... surprising.
I guess I should add more error handling in that area, but it should have no problems whatsoever on that card.
Do you have proper drivers from NVIDIA installed?


I use 195.62_desktop_win7_winvista_32bit_international_whql early and yesterday when I found bug  I install 195.81_desktop_win7_winvista_32bit_international_beta.

Error appears in both versions of this NVIDIA drivers.

Also I use two monitors connected to my graphic card (desktop extended to both monitors).

foo_wave_seekbar

Reply #212 –
can't play/pause when gaming with this/

foo_wave_seekbar

Reply #213 –
Quote from: noisia on
can't play/pause when gaming with this/

What do you do, what happens, what do you expect will happen?
Stay sane, exile.

foo_wave_seekbar

Reply #215 –
I assume from your horribly short description that you're playing a game (windowed?), try to click in the foobar2000 toolbar (DUI/CUI?) to play/pause, and it does what (freeze, crash, nothing at all) while looking normal (not redrawing?)?
Stay sane, exile.

foo_wave_seekbar

Reply #216 –
While trying to customize the effects file, I'm frequently running into this error:

"Compiled shader code uses too many arithmetic instruction slots (66). Max. allowed by the target (ps_2_0) is 64"

Is there anything that can be done about this, or is it just a limitation of the pixel shader that has to be worked around?

foo_wave_seekbar

Reply #217 –
Quote from: Hitchhiker427 on
While trying to customize the effects file, I'm frequently running into this error:

"Compiled shader code uses too many arithmetic instruction slots (66). Max. allowed by the target (ps_2_0) is 64"

Is there anything that can be done about this, or is it just a limitation of the pixel shader that has to be worked around?

Assuming you have the hardware, you can change the version in the technique to one of ps_2_b, ps_2_a or ps_3_0, in rough order of competence, latter is better.

The 2_a and 2_b levels have 512 combined arbitrary instructions and the 3_0 level has a minimum of 512 instructions supported.

I made the base effect use 2_0 as it's supported on the widest base of hardware.

Notable is that my shader isn't remotely efficient. It's written for legibility.
Stay sane, exile.

foo_wave_seekbar

Reply #218 –
Changing it to 3_0 worked.

EDIT: One more thing.  Is it possible to access the "track peak" info, rather than just "track gain"?  Thanks.

foo_wave_seekbar

Reply #219 –
Nevermind, I figured it out.

foo_wave_seekbar

Reply #220 –
ZAO,I also cann't  run it under my FX5200.What should I do ?

foo_wave_seekbar

Reply #221 –
The four available ReplayGain values are available in the same float4, as per the comment.

I have currently lent out my FX card, so I cannot verify why it fails.
There's plans to make device creation more robust and verifying more.
What failure do you get? The device one?
Stay sane, exile.
 

foo_wave_seekbar

Reply #222 –
Hi, this component seems to give me 403 forbidden errors when listening to last.fm radio, would it be accessing the tracks at all? It definitely seems to be caused by this component as I can listen fine when I remove it from my config, otherwise I get a 403 error after about 20 seconds then it skips two tracks forwards.

foo_wave_seekbar

Reply #223 –
Quote from: cc_bbs on
ZAO,I also cann't  run it under my FX5200.What should I do ?

the information is :
"Failed to load DLL: foo_wave_seekbar.dll
Reason: ?????????  "
and i have installed DirectX August 2009.

the same version of foo_wave_seekbar.dll,I used in a Q35 mainbroad,it is run .
So,is the FX5200's reason?
when  you can test it ,please tell me the result .thank you very much!

foo_wave_seekbar

Reply #224 –
Quote from: TomBarlow on
Hi, this component seems to give me 403 forbidden errors when listening to last.fm radio, would it be accessing the tracks at all? It definitely seems to be caused by this component as I can listen fine when I remove it from my config, otherwise I get a 403 error after about 20 seconds then it skips two tracks forwards.


I assume that last.fm tracks are one-time listen only.
This component assumes that playable locations are idempotent. That is, you get the same output on subsequent decodings and you can decode it more than once.
This does not hold for regular streams, random: and some other input components.

Currently there is a blacklist of input paths that it should not attempt to decode. How does such a mysterious last.fm location entry look?
Stay sane, exile.