INTERACT FORUM

More => Old Versions => JRiver Media Center 24 for Mac => Topic started by: Paul S.A. Renaud on November 05, 2018, 09:00:50 am

Title: JRiver does not exit anymore properly since Mojave 10.14.1
Post by: Paul S.A. Renaud on November 05, 2018, 09:00:50 am
I am using MC 24.0.56. Since upgrading to Mojave 10.14.1 (from Mojave 10.14), JRiver does not close anymore. I need to do a Forced Quit before I am able to do a lockdown of the computer (Macbookpro).
Title: Re: JRiver does not exit anymore properly since Mojave 10.14.1
Post by: Awesome Donkey on November 05, 2018, 09:22:58 am
Might be a dumb question for me to ask, but is Media Server running?
Title: Re: JRiver does not exit anymore properly since Mojave 10.14.1
Post by: Paul S.A. Renaud on November 05, 2018, 11:42:31 am
Dumb answer. How do I know whether that???  I did not change anything, other than upgrading to Mojave 10.14.1
Title: Re: JRiver does not exit anymore properly since Mojave 10.14.1
Post by: chrisc on November 11, 2018, 09:22:47 am
Ticked - yes, unticked - no  (Tools menu)

(https://i.imgur.com/2F6jDw4.jpg)
Title: Re: JRiver does not exit anymore properly since Mojave 10.14.1
Post by: Awesome Donkey on November 11, 2018, 10:06:11 am
Actually, to check if Media Server is enabled go to MC's Options > Mac Startup and if the Run on Mac startup: option is set to Media Center or Media Server or Media Center and Media Server then that's likely why. If it says Nothing, then it's probably something else.
Title: Re: JRiver does not exit anymore properly since Mojave 10.14.1
Post by: RunHomeSlow on November 11, 2018, 03:20:47 pm
I am using MC 24.0.56. Since upgrading to Mojave 10.14.1 (from Mojave 10.14), JRiver does not close anymore. I need to do a Forced Quit before I am able to do a lockdown of the computer (Macbookpro).

i have already posted that, since Mojave release and with JRiver v53 and 56 in the download page of v56 here.
just revert back to .45 all is good there  :)
Title: Re: JRiver does not exit anymore properly since Mojave 10.14.1
Post by: Paul S.A. Renaud on November 15, 2018, 10:57:07 am
My problem seems to be solved. It was not the Media Server (wasn't running). It was in the connection to the NAS/DAS.