Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bob]

Apple recently made a change that broke application support.  Catalina now requires apps to be "notarized" by default.

MC Mac is already signed with a distribution key supplied by Apple, but it is not currently notarized. This will require modification of our build process.  We are working on that at this time.

In the meantime, after installation you can open a terminal (from Utilities) and enter the following:

Code: [Select]

xattr -d com.apple.quarantine /Applications/Media\ Center\ 25.app
And MC will run as expected.

Reference:

https://apple.stackexchange.com/questions/366542/install-spotify-cant-be-opened-because-apple-cannot-check-it-for-malicious-so

[aileronguy]

THANK YOU! Thought I was going nuts.

[bob]

Working on the notarization process, getting there but it's a lot of monkeying around...

[bob]

Build 25.0.114 which is notarized is out now. Please check the 25.0.114 release post in this forum.

[JimH]

25.0.115 is now available in a thread at the top of this board.

[mikemcmann]

MC 25 will not open after installing Catalina (Nov. 11th)
I tried the terminal fix to no avail. I have a late 2012 MacMini
MC 25 tries to open but just flashes home page and cuts out.
All help appreciated

[bob]

MC 25 will not open after installing Catalina (Nov. 11th)
I tried the terminal fix to no avail. I have a late 2012 MacMini
MC 25 tries to open but just flashes home page and cuts out.
All help appreciated

Can you try 25.0.117 from the top of this forum please?

[mikemcmann]

Hello, the 117 is what I was trying to download. Have tried another 4 times and still a no go.
Opened up fine on my MacBook pro (mid 2012) though.

[mikemcmann]

moved to .115 and it's working thanks Bob

[bob]

moved to .115 and it's working thanks Bob

That's odd, the 2012 Mac mini is what it's built on.
If you get a chance could you try turning logging on in 115 then try installing and running 117 to generate a log and email it to me?
After the crash, the log will be in your User directory under Library/Application Support/J River/Media Center 25/Log.txt
bob (at) jriver (dot) com.
Thanks.

[sunrisepmm]

same problem here with late 2012 MAC mini Core i7 16GB Ram 1TB SSD with Catalina 10.15.1 - MC25 .115 works except of playing DVDs, meaning Video_TS is not recognized or found on library search, every other videofiletype is found and playable; even .ifo files not playable, only the single .vob files - very frustrating - but .117 is worse - it crashed immediately like mikemcmann posted; but no log.txt after crash in Library/Application Support/J River/Media Center 25/Log.txt;
attached error message of Apple report

[Hendrik]

MC25 .115 works except of playing DVDs, meaning Video_TS is not recognized or found on library search, every other videofiletype is found and playable; even .ifo files not playable, only the single .vob files - very frustrating

IFO files have never been supported by Media Center for Mac, sorry about that. The reason is a bit annoying, namely that on Windows we use a Microsoft-provided component to play DVDs, which of course is not present on a Mac (or on Linux for that matter)

[sunrisepmm]

Just to be sure: does that mean, that I am generally not able to play normal Video-DVDs on MACs or Linux-PCs with MC25, but only on Windows-PCs?
Or is the answer only related to .ifo files in the Video_TS directory.
Dragging the Video_TS directory to the MC25 header bar, releasing and clicking "Play" works well on my Windows-PC, but doesn´t work in MAC-Version .115.
Will make a check with Linux Mint 19.2 soon.

[Awesome Donkey]

Yes, IFO files won't work on Linux or Mac, just Windows because it depends on a Windows component to play them (DVDs).

[bob]

Just a quick note, the issue with the crashing Caps-Lock key press when MediaKeys are enabled is either in the Mac 10.15 SDK or Xcode 11.
Making a build in Xcode 10.1 on High Sierra produces a MC that doesn't crash when Caps-Lock is pressed.
There is a bug fix in Xcode 11.2 that may be what's causing the issue. We'll know later today...