Reply to thread

Message

<blockquote data-quote="hoxi" data-source="post: 291966" data-attributes="member: 54318">Milkdrop configuration problems in RC2Used the package from the first post and got Milkdrop up and running without any problem on a RC2 installation. I however had problems getting any of the modifications made in Milkdrop configuration page (within Mediaportal config) to work. It seemed like it always used the &quot;default&quot; settings.Using the wininternals processexplorer I could se that mediaportal was looking for a &quot;milk2.ini&quot; file under:C:\Program Files\Team MediaPortal\MediaPortal\plugins\pluginswhile the configuration page always saved the &quot;milk2.ini&quot; file under:C:\Program Files\Team MediaPortal\MediaPortal\MusicPlayer\plugins\visualizations\winampSo by copying the &quot;milk2.ini&quot; file to the correct path, my new settings made in milkdrop was correctly read. Maybe it would work by just doing a shortcut to the correct file, haven't tried that.Don't know if this is common knowledge, something special with my installation or just a bug. Just wanted to let people know if somebodyelse had this problem <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="hoxi, post: 291966, member: 54318"] [b]Milkdrop configuration problems in RC2[/b] Used the package from the first post and got Milkdrop up and running without any problem on a RC2 installation. I however had problems getting any of the modifications made in Milkdrop configuration page (within Mediaportal config) to work. It seemed like it always used the "default" settings. Using the wininternals processexplorer I could se that mediaportal was looking for a "milk2.ini" file under: C:\Program Files\Team MediaPortal\MediaPortal\plugins\plugins while the configuration page always saved the "milk2.ini" file under: C:\Program Files\Team MediaPortal\MediaPortal\MusicPlayer\plugins\visualizations\winamp So by copying the "milk2.ini" file to the correct path, my new settings made in milkdrop was correctly read. Maybe it would work by just doing a shortcut to the correct file, haven't tried that. Don't know if this is common knowledge, something special with my installation or just a bug. Just wanted to let people know if somebodyelse had this problem :) [/QUOTE]

Verification