Winamp-VIS-plugs in foobar, foo_vis_bacon doing the impossible Options

[kode54]

Can I please borrow someone else's if it's not too much trouble?

I don't have that file either. How convenient of them to not include it, and assume in the documentation that you already have it. (Documentation says directions for editing it are in comments in the original file. How smart.)

Oh well, I guess you'll have to live without random messages for a while...

Edit:  Also, I noticed that when I have Milkdrop running in a window, if I hover my mouse over the start menu or something similar on the task bar, Milkdrop slows down a lot.  But no big deal.

Can't reproduce. Have you checked the actual frame rate? Also, what are your system specs? (Processor, main board chipset, video card, sound card... Hmm, maybe driver versions while you're at it... Just curiosity, I can't think of any other reason for wanting to know this. :B)

[p0wder]

Can't reproduce. Have you checked the actual frame rate? Also, what are your system specs? (Processor, main board chipset, video card, sound card... Hmm, maybe driver versions while you're at it... Just curiosity, I can't think of any other reason for wanting to know this. :B)

I just tested it again to check framerates, and found the problem kicks in only when the tooltip appears. Any tooltip that appears causes the framerate to slow to ~10 fps. When the tooltip disappears the framerate jumps back up (I capped it at 60 fps).

Here are my specs:

P4C
Abit IC7 875P/ICH5R chipset
Radeon 9800 Pro, Omega Catalyst 4.2
Creative Labs Audigy 2, latest EAX 4.0 drivers

If I am the only one experiencing this I'll try rolling back my video drivers.

[bleh]

This going to be an extremely buggy release, hence "minus 0.5 alpha." I'm sorry. I'm just way too tired to figure out why Milkdrop occasionally barfs up an error message when returning from fullscreen or even something simple like how to get Windows to calculate the amoun of space taken up by the title bar and window borders for you (which is an issue).

Binary
Source

Current issue list:
- AVS windows (or any embeds) are technically too small because of the title bar issues I mentioned earlier.
- AVS version 2.6.0 will not work properly because I just noticed that it doesn't and I'm too tired to figure out how the games it plays differ from those of version 2.81b or whatever it is that came with Winamp 5.
- You cannot configure any plugins while visualization is running. This is technically a feature.
- In addition to the above, if you open the foobar config window while visualization is running, then stop visualization, you need to select a different plugin, then select the original one to configure it.
- The Reset button for the path in the config dialog will not work in the binary. Why? The line that makes that work wouldn't compile for me in Visual Studio .NET 2003 (reset is not a member of cfg_string), so I commented it out :|.

New features:
- AVS version 2.81b works... kind of.
- A one-second timer has been implemented on flush like in foo_vis_simple_spectrum. This means that if you stop playback, the window will hang open for a second, but if you change songs or seek or something and the operation takes less than a second, the visualization won't get shut down and then restarted.
- Visualizations with a header version of 0x030 are now allowed so Startle works.

Yeah I'm gonna go get some sleep now and hopefully have a less crappy release than this out tomorrow >_<.

@p0wder:
I've had tooltip issues with so many different programs that I'm not sure how much can be done with it (nVidia geforce 2 Ultra, Pentium III).
btw http://potatoriffic.f2g.net/milk_img.ini http://potatoriffic.f2g.net/milk_msg.ini

@mig:
That's really up to the Winamp plugins to implement since they create the actual visualization window... I'm not sure if it's even possible or not.

This post has been edited by bleh: Feb 25 2004, 06:11

[Canar]

AVS works! Yay!

Dear me... this is too cool.

It all works pretty well here. Thanks for all the work!

[p0wder]

@p0wder:
I've had tooltip issues with so many different programs that I'm not sure how much can be done with it (nVidia geforce 2 Ultra, Pentium III).

Yea I'm not gonna worry about it too much, I usually have it in full screen anyway. Thanks for the file custom text now working.

AVS a bit buggy but working!

This post has been edited by p0wder: Feb 25 2004, 07:55

[kode54]

Uploaded minus0.4 alpha. w00t. [binary] [source]

I'm just way too tired to figure out why Milkdrop occasionally barfs up an error message when returning from fullscreen or even something simple like how to get Windows to calculate the amoun of space taken up by the title bar and window borders for you (which is an issue).

You probably would have thought of GetClientRect if you got some sleep. :B

- AVS windows (or any embeds) are technically too small because of the title bar issues I mentioned earlier.

Fixed.

- The Reset button for the path in the config dialog will not work in the binary.  Why?  The line that makes that work wouldn't compile for me in Visual Studio .NET 2003 (reset is not a member of cfg_string), so I commented it out :|.

Oops, my SDK is old. 0.8 beta 3... I'll fix it and repost...

Yeah I'm gonna go get some sleep now and hopefully have a less crappy release than this out tomorrow >_<.

Enjoy your much deserved break. You do have a life, after all. :B

I've had tooltip issues with so many different programs that I'm not sure how much can be done with it (nVidia geforce 2 Ultra, Pentium III).

Strangely, I do not have this tool tip problem with my Geforce 2 GTS-V. Maybe it's because I've decided not to use the ForceWare drivers... (That stuff's for FX users anyway.)

Anyway, I also dealt with the warning from Milkdrop and possibly others when they switch to/from fullscreen mode, as well as the embedded plug-in window not getting input focus.

This post has been edited by kode54: Feb 25 2004, 14:26

[p0wder]

Wow development sure is progressing rapidly.

This post has been edited by p0wder: Feb 25 2004, 10:02

[sld]

I have a slight problem with the plugin so far...

I started using one of the earlier versions, which defaulted to <program directory>\Foobar2000\bacon. Then when the option to change the vis directory was added, I used the default <program directory>\Winamp\plugins. However, the vis plugin I currently use, Milkdrop 1.40b, cannot be used anymore, with the error message "Couldn't load DLL". Besides a simple switching of the plugin directory in foo_vis_bacon's config page, what else must I do?

[kode54]

Reselect it from the list. That failing, select another first. Meh.

[Thikasabrik]

I think there are some priority issues. You see, at the moment I'm using a lowly celeron 500 mhz system (I don't really need much more at the moment) and I'm noticing that the spectrum data etc hangs every now and then under conditions of reasonably high cpu usage by a vis plugin. This is especially noticeable in the initial mode of whitecap, where the line that traces the green mesh stays in the same position for periods of up to a second or so. Foobar's built-in vis also freezes at the same time.

I expect this is unavoidable, and I will just have to use the tbird 1000 for vis, but I thought I'd mention it incase it can be fixed, and incase you all have pc's too speedy to notice.

[Smiff]

um something seems broken - milkdrop appears in corner of window, keys don't work, etc.

edit: milkdrop only takes up the top left quarter of its window - isn't anyone else seeing this? it broke between -0.8 and -0.5 i think. i don't have the older versions to check, sorry.

This post has been edited by Smiff: Feb 25 2004, 15:51

[RedSaint]

I guess this is one situation I have never experienced before - Seems funny enough for me, but it kinda sucks for the ones having problems. Ehm, question is, where to turn to get support for the vis plugin since it is ported through a foo plugin. kode54, bleh and hartwork are only developing the foo plugin, but so far the help on the vis plugins have been very good and useful. Uhm, good work, keep it up.

[Thikasabrik]

Regarding my last post, I have now discovered that the cpu usage issues seem to be due to either of foo_looks or foo_tunes. I tried both. The interesting thing is that neither were active when the problems were apparent, and yet deleting them removed the problems. Maybe I'll try and find out which plugin it was later.

[anza]

Yes, using foo_looks (even unactivated) indeed slows the framerate down a bit (makes about 20-40fps difference while it's not installed).

[kode54]

Updated to 0.8 SDK, including the path reset in the source code... Downloading is optional.

[hartwork]

minus0399 - sleep-issue fixed: bacon_0399.zip

i'll try to optimze dataprocessing/interpolation in on_data, okay?

This post has been edited by hartwork: Feb 25 2004, 16:32

[Skates]

Bug in the latest version kode54 has up for download, check it out here...



For some reason some of the vis doesn't show up!

Forgot to say thats running the latest Milkdrop, and only seems to happen with that as GForce works without any problems...

This post has been edited by Skates: Feb 25 2004, 16:51

[ilikedirtthe2nd]

disable "integrate with winamp" in windowed settings.

regards; ilikedirt

[hartwork]

is spectrum_size fixed to [256]?

[bleh]

@hartwork: I've never seen it anything else, but I think it would be a very bad idea to assume that it is. Thanks for working on interpolation, though. It'd be really nice to have.

Version minus0.39 alpha
Binary
Source

- Basically only one change here: a new hack to make Milkdrop 1.04 (the latest version available from the Milkdrop site, not the real latest version, which is 1.04b and may not be available without Winamp 5) and AVS 2.6.0 work properly when they try to embed themselves (should fix issues with Milkdrop only showing up in the corner of the window). Yay deficiencies in the Winamp 2.9 SDK.

[kode54]

OI. I'm having trouble keeping up with you two now. :B

Uploaded minus0.389 alpha. [binary] [source]

I added a DLL manager, so there should no longer be any problems with concurrent loads/unloads.

Configuration no longer keeps the current module resident, and as a result, there should no longer be any problems with using configuration after closing the visualization with the preferences page open. Also, there was a DLL handle leak in both the DLL selector and the WM_DESTROY handler, which were corrected by this change.

Oh yes, and after I merged in hartwork's changes, I crafted my own linear interpolation. Sorry to beat you to job, but maybe you can take a look at my code and improve it. (Or, redo it in a better or more efficient way. :B)

Speaking of hartwork's changes ... What's with that slightly overkill timer code? It seems to increase CPU usage with visualizations such as Startle, which used 0-2% before and now uses 4-6%. Milkdrop has a delayMs value of 0 at startup, but I'm not sure if it changes that dynamically, or just does its own frame regulation.

If we knew that delayMs would be constant, and at least 10ms, it might be better to use a timer event attached to the host window. (Well, 10ms minimum is supposedly only an issue for Windows 2000/XP, but still...)

This post has been edited by kode54: Feb 25 2004, 20:18

[Smiff]

(should fix issues with Milkdrop only showing up in the corner of the window).

it did. well done

[Skates]

(should fix issues with Milkdrop only showing up in the corner of the window).

Definitely fixed thanks...

[kode54]

Yanno... That dll manager is probably totally unnecessary... LoadLibrary of same dll in same location from same module probably always returns the same handle for the duration of the instance, until it is freed. Of course, I don't know this. The manager class is probably tidier, in cases of overlapped load/free when config is fetching info...

Eh, whatever. :B

[PoisonDan]

It's funny: on my system, Milkdrop runs better on foobar2000/foo_vis_bacon than on Winamp.

I have an Audiophile 2496, and the playback always stuttered in Winamp whenever Milkdrop was running fullscreen. I experimented a bit with different ouput plugins (DirectSound, ASIO) and different priority settings, but I never got 100% perfect playback.

Now, thanks to foo_vis_bacon, it runs perfectly "out of the box".

Excellent work, guys. You made my day.