Winamp Visualisations. Finally :-) (1 Viewer)

[hwahrmann]

Yes, everything seems to run smoothly.
Doing some final testing today. Will then be available via SVN and in the next alpha version

 

[hwahrmann]

First post updated with instructions on how to make Winamp Vis work.
Hope everything is clear now.

 

[mironicus]

AW: Winamp Visualisations. Finally

Tried svn 24891 (with updated bass-files). Milkdrop 2.21 still does not work (Mediaportal freezes on startup), Milkdrop 2.2 does work.

Still all changes to the config-file are not recognized. If I uncheck "Show 'Press F1' for help on startup" it is still shown. The Config-option should be disabled if you really can't change anything.

 

[hwahrmann]

So what's the problem?
Simply use Milkdrop 2.2


Ok, so i found the problem with those ini files.
When you press Config, it write the Ini file into the same folder, where vis_milk2.dll resides.
But as we all know, it isn't taken from there.

When executing the vis, it looks into a folder named Plugins, which is located as a subfolder to the exectuable, Mediaportal.exe in our case.
We have a Plugins subfolder directly under the MP root and this is the folder where all MP Plugins reside.

If you look into this folder when Milkdrop has run once, you will find a mini milk2.ini in there.
Simply move/copy the one which you find in the Vis folder over there and you have what you need to achieve.

I'll search a bit, if i can change that.
If not, i will simply copy the milk2.ini file over, when the config has done.

 

[BassFan]

AW: Re: Winamp Visualisations. Finally

Only for HWahrman

So what's the problem?
Simply use Milkdrop 2.2


Ok, so i found the problem with those ini files.
When you press Config, it write the Ini file into the same folder, where vis_milk2.dll resides.
But as we all know, it isn't taken from there.

When executing the vis, it looks into a folder named Plugins, which is located as a subfolder to the exectuable, Mediaportal.exe in our case.
We have a Plugins subfolder directly under the MP root and this is the folder where all MP Plugins reside.

If you look into this folder when Milkdrop has run once, you will find a mini milk2.ini in there.
Simply move/copy the one which you find in the Vis folder over there and you have what you need to achieve.

I'll search a bit, if i can change that.
If not, i will simply copy the milk2.ini file over, when the config has done.

Ich sagte dir ja schon es ist abhängig von der Plugins_API (Winamp).
Die Plugins legen ihre Daten im Rootpfad der Anwendung innerhalb des Plugins Ordners ab.
Wenn du dich daran nicht hälst wirst du immer diese Probleme haben.

Und!
Du brauchst BassVis_INIT nicht aufrufen wenn du "NUR" die Plugins addierst ohne diese zu starten.
Siehe Configuration.exe.
Die meisten Konfigurationen arbeiten auch ohne das du BassVis initialisieren mußt.
Einige Plugins jedoch, müssen vorher gestartet sein damit du diese Konfigurieren kannst. Siehe "vis_AVS, vis_BassVis" und einige mehr.
Wenn du ein Plugin startest ist es unbedingt erforderlich das du BassVis_INIT mit dem richtigen Kind aufrufst.
BASSVISKIND_NONE gibt dir bei INIT immer false zurück da der Index des jeweiligen Plugins 0 also nichts ist.

Das ist was ich dir in der Mail vermitteln wollte.
Auch wenn du meinst du hast es immer so gemacht. Dann war es immer falsch. Sorry

gruss Emil

EDIT:
Habe mir das letzte SVN geladen und werde jetzt mal in den Quelltext schauen
Wenn ich probleme finde werde ich es ändern und dir mitteilen was.

 

[hwahrmann]

Ok, Emil.
Thanks for the info. Awaiting your suggestions

 

[Blackmave]

Hallo,

Sorry ich schreibe lieber in deutsch... sonst versteht man sicher nicht was ich sagen möchte.

wenn ich milkdrop in root/plugins kopiere findet mediaportconfig das plugin nicht.
also habe ich es wieder in mediaportal/musiplayer/plugins/visualisierung kopiert
läuft auch wunderbar, bis man das erste mal das plugin per mediaportconfig konfiguriert.
denn dann startet er das plugin direkt beim mediaportal start und alles friert ein.
wenn ich die milk2.ini edditiere und die zeile "skin=0" oder "skin=1" lösche
läuft es wieder wunderbar.
bis zur nächsten konfiguration. hier wieder die zeile skin=0 von hand löschen.
dann läuft es wieder.
kann man das nicht doch etwas eleganter lösen ?

I use winamp vers. 5581
and streamedmp skin

ger -> eng. by google

if I copy Milkdrop in root / plugins mediaportconfig not find the plugin.
so I changed it back to MediaPortal / musiplayer / plugins / visualization copies
runs fine until it the first time the plugin configured by mediaportconfig.
because then he starts the plugin directly from the start MediaPortal and everything freezes.
if I edditiere milk2.ini the line and the "skin = 0" or "skin = 1 delete
It is wonderful again.
until the next configuration.must del. the line skine=0 again. and it´s work fine.
can not resolve more elegant?

mfg
bernd

 

[hwahrmann]

Ok, everything i wrote in the first thread about the Pklugin folder applies to the coming 1.2.0 Alpha and svn.
In the current version it needs to stay in the \musicplayer\plugins\visualisation

in my opinion there shouldn't be too much to configure. Once set, there shouldn't be too much need for config anymore.

Anyhow, once the new version is released it should behave exactly like it does within winamp.

 

[hirscho]

Hi hwahrmann

I tested MilkDrop 2.2 with MP 1.2 Alpha according to your configuration description and basically it works. There are two issues for me so far.

1) When starting MP config or MP a MilkDrop pop comes up before for a second.
2) Even if the visualization is not shown in full screen the processor consumption of one core goes up to 100% when playing music. Milkdrop itself tends to stutter. With MP 1.1.x it ran smoothly and the processor consumption was moderate.

Oliver

 

[SiLenTYL]

yo

im wanting to try this out but i dont have a Milkdrop v2.2 ...its just 2.21 in the list..and it seems...nowhere to get it!

plz help


...nevermind..i found the Winamp v 5.572 which contains Milkdrop 2.2

looking great!