Looking for testers of Picard build for macOS 10.15 Catalina

Tags: #<Tag:0x00007ff14a7bb220> #<Tag:0x00007ff14a7bb0e0> #<Tag:0x00007ff14a7bafa0> #<Tag:0x00007ff14a7bad48>

This is for all of you using Picard on macOS: Since macOS 10.15 Catalina there are new security restrictions in place requiring all apps to be submitted for a malware scan to Apple. Trying to start current Picard releases there for the first app shows a big security warning. While it is possible to manually circumvent these warnings, this is not obvious for most users.

I have now integrated the necessary steps for letting Apple aprove the app into the Picard build process. So far it is looking good, but I can only test on a single machine myself.

Hence the question for help: If you are using macOS 10.12 or later it would be great if you could try running the app MusicBrainz Picard 2.3.0.dev1_osx_xcode11.2_20191108234016 macOS 10.14.dmg.

I am specifically looking for the following:

  1. If you use macOS 10.15 Catalina, does the app start and run without showing the security warning?
  2. If you use macOS 10.12, 10.13 or 10.14, does the app start and run? I am especially interested in whether this app still runs on macOS 10.12 and 10.13.

If you test the app please let me know your results and the version of macOS you are using.

Please note: This is a development build and might contain bugs and not full completed features. For this specific case I am mostly interested in whether the app runs or not, so if you just test opening the app and see if it runs in general this is fine. Of course you are also welcomed to test and experiment this development build in general, but do so at your own risk.

Thanks a lot for your help.

2 Likes

Just downloaded and ran the 2.3.0 version, launched fine with no warnings. Will test it out for operation shortly.

iMac, Late 2015, 32 GB ram, Catalina 10.15.1 3.3 gHz, i5 quad core

1 Like

2019 imac
72GB at 2667MHz DDR4 RAM
3.6GHz 8_Core Core i9 CPU
Catalina 10.15.1
running fine tho did give me warning that it was downloaded from the web and asked me to hit ok or cancel
did test on one album to be on the safe side seams good

1 Like

Have run Picard 2.3.0 on Catalina with no issues yet, it has converted several albums perfectly and quickly, tagging files and renaming files with no errors.

Late 2015 5k iMac, 32 GB ram, i5 3.3 gHz quad core, 10.15.1 Catalina.

:+1:

1 Like

Have run Picard 2.3.0 through several hundred MP3 files and it has worked fine for me, determining the file names from the acoustic signatures in nearly all cases.

My comment is that right clicking to show file in containing folder, while helpful might be better as an “edit in” type - I make use of Fission to edit MP3 files, splitting where necessary. It would save several clicks/steps to be able to edit in directly from Picard.

No crashes, no errors, no problems… Catalina 10.15.1, iMac late 2015, 32 GB Ram, 3.3 gHz i5 quad core

Thanks a lot for the testing, this helps a lot and confirms that we have this working. I still hope somebody can test with maybe 10.12 or 10.13, because those are the releases I currently don’t know whether the “notarized” build will still work on. Unfortunately it is not surprising that people willing to test out development builds also usually have upgraded their systems to the latest version quickly :smiley:

Yes, I forgot to mention this. This will of course always happen and is perfectly normal, at least if you downloaded via browser. But this is really just the file getting a “downloaded from internet” flag set if you download it and macOS telling you this fact once when opening.

2 Likes

There is also “open in player”, which will open the file in the configured default application for this file type. There is a feature request to allow selecting the application used here in Picard (PICARD-1487), I think this would solve the issue. Apart from this I think another “edit” action in addition to the existing opening the folder and opening in another application would be best put into a separate plugin.

2 Likes

Duh!!! :slight_smile: Thanks for pointing that out, once I changed my default player all is good.

1 Like