Milkdrop 2 MediaMonkey Port

Post a reply

Visual Confirmation

To prevent automated access and spam, you are required to confirm that you are human. Please place a check mark next to all images of monkeys or apes. If you cannot see any images, please contact the Board Administrator.

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Milkdrop 2 MediaMonkey Port

Re: Milkdrop 2 MediaMonkey Port

Post by GMGJ » Wed Apr 26, 2017 4:57 pm

Install Milkdrop 2 like this

Winamp plugins needs to be installed as Administrator not as User.

start mmw as administrator
Go to Tools -> Extensions -> ADD
Locate Milkdrop2 plugin installation download
Disable Per User Plugin installation
restart MMW

I got some very strange and misleading error messages. After a few tries, I got a link to download prior versions of Directx.
https://www.microsoft.com/en-us/downloa ... px?id=8109
this works as well
https://www.microsoft.com/en-us/downloa ... aspx?id=35

Example error message - Error Compiling ps_2_0 warp shader[/quote]
Compos

Re: Milkdrop 2 MediaMonkey Port

Post by Peke » Wed Oct 12, 2016 6:07 pm

Hi,
Please let us know the results. Try also to search web for errors in nvd3dum.dll, as from what I see it is not lone problem.

Re: Milkdrop 2 MediaMonkey Port

Post by tarasis » Wed Oct 12, 2016 4:25 pm

Peke wrote:Hi,
Error in nvd3dum.dll indicate issue with buffer release/allocation within driver itself. I teste dand do not have such issue with resolution 3840x1200 on ATI R9 280x card.


Cheers Peke. I guess I should try the 368.xx series of drivers and see if they work properly.

Re: Milkdrop 2 MediaMonkey Port

Post by tarasis » Wed Oct 12, 2016 4:22 pm

mstrange wrote:
Peke wrote:Hi,
Error in nvd3dum.dll indicate issue with buffer release/allocation within driver itself. I teste dand do not have such issue with resolution 3840x1200 on ATI R9 280x card.


Hi Peke, is it a constant issue? Do you know which NVIDIA card specifically you're seeing this on? I have an NVIDIA card myself and haven't had any issues so my first thought is hitting a hardware resource limitation of some kind.

You can see if going to Configuration | MORE SETTINGS and setting

Pixel Shaders to "Shader Model 2"

Makes a difference.


Hi mstrange, it was me that was having the issue not Peke :)

The NVidia card is a GTX 970 (Gigabyte Gaming G1), connected with display port to an LG 21:9 monitor (2560x1080).

Test At Native Resolution

If I run with native resolution then the Desktop mode only fills a portion of the screen and the icons flicker through.

Image

Link to image as its only showing half the image here

Using Fullscreen it starts with the screen black and then goes back to the desktop with no visualization running and no errors that I can find anywhere. Setting the Fullscreen resolution to 1920x1080 in the MD2 settings makes no difference.

Test at fixed 1920x1080 resolution

If I set the video card desktop resolution to 1920x1080 (and configure Md2 to use 1920x1080), then desktop mode works properly and fills the whole desktop.

If I try Fullscreen using either Pixel Shader 2 & 3 (in MD2 options), it runs fine but upon exiting (pressing ESC) I get a black screen except for a mouse pointer which reacts to windows that aren't visible and then after a few minutes I get the whirly busy icon on the mouse pointer and the desktop appears properly and the following is in the Windows Error logs:

Faulting application name: VisHelper.exe, version: 0.0.0.0, time stamp: 0x57ea5656
Faulting module name: nvd3dum.dll, version: 21.21.13.7306, time stamp: 0x57f0081d
Exception code: 0xc0000005
Fault offset: 0x00690ea5
Faulting process ID: 0x3698
Faulting application start time: 0x01d224cd2fb55738
Faulting application path: C:\Program Files (x86)\MediaMonkey\VisHelper.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3baaab0007230109\nvd3dum.dll
Report ID: 98ade2ad-6206-42b2-9e5a-5426dd6dfa08
Faulting package full name:
Faulting package-relative application ID:

Re: Milkdrop 2 MediaMonkey Port

Post by mstrange » Tue Oct 11, 2016 6:38 pm

Peke wrote:Hi,
Error in nvd3dum.dll indicate issue with buffer release/allocation within driver itself. I teste dand do not have such issue with resolution 3840x1200 on ATI R9 280x card.


Hi Peke, is it a constant issue? Do you know which NVIDIA card specifically you're seeing this on? I have an NVIDIA card myself and haven't had any issues so my first thought is hitting a hardware resource limitation of some kind.

You can see if going to Configuration | MORE SETTINGS and setting

Pixel Shaders to "Shader Model 2"

Makes a difference.

Re: Milkdrop 2 MediaMonkey Port

Post by Peke » Tue Oct 11, 2016 5:59 pm

Hi,
Error in nvd3dum.dll indicate issue with buffer release/allocation within driver itself. I teste dand do not have such issue with resolution 3840x1200 on ATI R9 280x card.

Re: Milkdrop 2 MediaMonkey Port

Post by tarasis » Tue Oct 11, 2016 5:23 pm

I'm having an issue with Fullscreen and Desktop Modes on Windows 10.

When I run my desktop at 2560x1080, and neither mode works properly for me. Fullscreen turns the screen black for a short time and then returns to the desktop & MediaMonkey. In Desktop mode is only fills about a 1/3 of the desktop on the right hand side.

If I force the GFX card to use 1920x1080 for the desktop, then the Desktop mode runs properly. Switching the res for Fullscreen mode in options to 1920x1080 works, except that when quitting (pressing Esc) it causes the screen to go black except the mouse pointer is visible and changes as appropriate for going over windows. After a minute or twoa spinning wait icon appears and the desktop reverts to being properly visible.

"12/10/2016 00:14 Application Error Faulting application name: VisHelper.exe, version: 0.0.0.0, time stamp: 0x57ea5656
Faulting module name: nvd3dum.dll, version: 21.21.13.7306, time stamp: 0x57f0081d
Exception code: 0xc0000005
Fault offset: 0x006c4da3
Faulting process ID: 0x1e48
Faulting application start time: 0x01d2240ca2ffd3f9
Faulting application path: C:\Program Files (x86)\MediaMonkey\VisHelper.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3baaab0007230109\nvd3dum.dll
Report ID: bcdf8885-7561-4479-bf07-aa85bd6e8f20
Faulting package full name: 
Faulting package-relative application ID:
"

System is

Windows 10 64bit
NVidia GTX 970 (driver 373.06)
16GB Ram
i7-4790k

Re: Milkdrop 2 MediaMonkey Port

Post by mstrange » Thu Oct 22, 2015 10:31 am

wytch_weigh wrote:mstrange,

First, apologies for taking so long to respond as I've only just gotten the time to troubleshoot this and see your reply. Second, my previous comment was directed at someone else (who duly deleted their post). So please don't take offence.

It was a system issue. I finally tracked down the instability to an updated Intel VGA driver (10.18.14.4206) where, it surfaces, there are one or two known bugs. The Motherboard Manufacturer is yet to release the latest generically available driver, so I've rolled back to the previous one (10.18.10.3920) and all is now well again.

TY


No problem, thanks for the update.

Re: Milkdrop 2 MediaMonkey Port

Post by wytch_weigh » Thu Oct 22, 2015 10:25 am

mstrange,

First, apologies for taking so long to respond as I've only just gotten the time to troubleshoot this and see your reply. Second, my previous comment was directed at someone else (who duly deleted their post). So please don't take offence.

It was a system issue. I finally tracked down the instability to an updated Intel VGA driver (10.18.14.4206) where, it surfaces, there are one or two known bugs. The Motherboard Manufacturer is yet to release the latest generically available driver, so I've rolled back to the previous one (10.18.10.3920) and all is now well again.

TY

Re: Milkdrop 2 MediaMonkey Port

Post by mstrange » Thu Sep 24, 2015 11:54 pm

wytch_weigh wrote:What's that about? It was a civil request. What's your problem?


Forum didn't send me an email for some reason so I only saw this now.
I tried to repro this bug with 4.1.8 on Windows 8.1 and I am not seeing any issues with the keyboard controls in either native or VJ mode.
Can you give a more explicit set of steps to reproduce the error on your side? Either I am misunderstanding your problem or the issue is specific to your configuration or system.

Re: Milkdrop 2 MediaMonkey Port

Post by wytch_weigh » Fri Jul 17, 2015 12:06 pm

What's that about? It was a civil request. What's your problem?

Milkdrop 2

Post by wytch_weigh » Fri Jul 17, 2015 6:34 am

A request to fully integrate Milkdrop 2 natively into MediaMonkey.

I'm aware of http://www.ventismedia.com/mantis/print_bug_page.php?bug_id=12119

Thank you.

Re: Milkdrop 2 MediaMonkey Port

Post by wytch_weigh » Sat Jul 11, 2015 7:55 am

Can someone at MediaMonkey please comment on this. VisHelper.exe appears to have been modified by you and is probably the reason why the plugin is faulting when the vis and console windows are merged. Does the plugin need an update to function properly?

Re: Milkdrop 2 MediaMonkey Port

Post by wytch_weigh » Fri Jul 10, 2015 6:56 am

Hi

I've been using this brilliant port without problems in MediaMonkey version 4.16 for some time now. I've updated to version 4.18 of the main program and now I can only use the console elements in VJ mode. Attempting keyboard shortcuts integrated with the visualisation causes a freeze/crash in Milkdrop images. The native version of Milkdrop v1.04 doesn't have this problem. Anything I can do?

Specs: Windows 8.1
i5 haswell refresh processor
Integrated HD 4600 graphics with latest drivers

Re: Milkdrop 2 MediaMonkey Port

Post by auralarch » Mon Dec 01, 2014 2:22 pm

That's fantastic! Thank you!!!

Top