INTERACT FORUM

More => Old Versions => JRiver Media Center 23 for Windows => Topic started by: Helibaby on March 14, 2018, 02:02:29 pm

Title: MC 64-bit crashes clicking the "Display" window
Post by: Helibaby on March 14, 2018, 02:02:29 pm
Hi Folks,

MC 23.0.103 64-bit (Windows version) is crashing immediately when I'm right clicking on the Display window (independend whether minimized or as Screen) or clicking on the Extras icon top left of the Display window.

Regards,
Helibaby
Title: Re: MC 64-bit crashes clicking the "Display" window
Post by: Hendrik on March 14, 2018, 02:03:59 pm
This usually happens when you have a visualization plugin which is incompatible with MC. MC by itself certainly isn't doing that here.
Title: Re: MC 64-bit crashes clicking the "Display" window
Post by: Helibaby on March 14, 2018, 03:06:49 pm
Quote from: Hendrik on March 14, 2018, 02:03:59 pm
This usually happens when you have a visualization plugin which is incompatible with MC. MC by itself certainly isn't doing that here.

Hi Hendrik,

I uninstalled the Soundspectrum visualizers Aeon, G-Force and WhiteCap and everything is fine now!
As they can be installed with the 64-bit version of MC, I thought they were compatible. Obviously they aren't!
Thanks for your advice.

Regards,
Helibaby
Title: Re: MC 64-bit crashes clicking the "Display" window
Post by: iFlip92 on March 21, 2018, 09:50:16 pm
Quote from: Helibaby on March 14, 2018, 03:06:49 pm
Hi Hendrik,

I uninstalled the Soundspectrum visualizers Aeon, G-Force and WhiteCap and everything is fine now!
As they can be installed with the 64-bit version of MC, I thought they were compatible. Obviously they aren't!
Thanks for your advice.

Regards,
Helibaby

I had this problem when version 6.8 came out for Whitecap too. Install the previous 6.7.1 version and it will work again but obviously no x64 MC support as only 6.8 is meant to be doing that. I have raised a ticket with SoundSpectrum but they seem to have other priorities and they are only a small team. In other words no idea when this will be looked at. Can you please raise a ticket with SoundSpectrum as well so that they get more pressure to fix this?