Corrupted Package

mrantarctica
Posts: 26
Joined: Sun Feb 23, 2020 12:01 am

Corrupted Package

Post by mrantarctica »

Hi Rob,

I tried to download the latest eDrumin Control Software 1.3.2.19 and I get an error message saying that the digital signature is invalid. I am, however, able to install an earlier version of the software. I had previously had 1.3.1 working in Big Sur. I have rolled back my system to Mac OSX El Capitan to use my audio interface. I am also unable to drag and drop any presets that I had saved on my earlier setup now that I am using 1.2.0.15. Can you advise whether there is a fix for this issue?
User avatar
Rob
Site Admin
Posts: 4716
Joined: Sat Aug 01, 2009 2:04 pm

Re: Corrupted Package

Post by Rob »

I'll double check that there are no issues with the build 19 installer, but I think I would have heard something from others by now.
User avatar
Rob
Site Admin
Posts: 4716
Joined: Sat Aug 01, 2009 2:04 pm

Re: Corrupted Package

Post by Rob »

I'm not seeing an issue with the installer. I don't have El Capitan to test with. Can you provide a screenshot of the issue?
mrantarctica
Posts: 26
Joined: Sun Feb 23, 2020 12:01 am

Re: Corrupted Package

Post by mrantarctica »

Screen Shot 2021-01-09 at 12.21.15 AM.png
Screen Shot 2021-01-09 at 12.21.15 AM.png (1.2 MiB) Viewed 1176 times
perceval
Posts: 313
Joined: Sat Aug 06, 2011 4:59 pm

Re: Corrupted Package

Post by perceval »

I would update at least to 10.14.

10.11 is quite old, and there have been multiple security fixes added to the OS since then.

No need to go to 10.15. I did, and I wish I hadn't. 10.15 introduced a lot of pain to developers, and there are still a couple of apps I have that do not work in 10.15 and above yet.
User avatar
Rob
Site Admin
Posts: 4716
Joined: Sat Aug 01, 2009 2:04 pm

Re: Corrupted Package

Post by Rob »

He's got no choice because there's no driver support for his hardware beyond El Capitan.

I'm sure there's a solution. I spend some time searching tonight.
User avatar
Rob
Site Admin
Posts: 4716
Joined: Sat Aug 01, 2009 2:04 pm

Re: Corrupted Package

Post by Rob »

This appears to be a bug in Apple's codesign application in Big Sur. Apparently there's a workaround. I'll look into it next week.

Rob
User avatar
Rob
Site Admin
Posts: 4716
Joined: Sat Aug 01, 2009 2:04 pm

Re: Corrupted Package

Post by Rob »

Here's Apple's official explanation:

“This is expected behavior, you will need to produce two different packages that are signed with different hashes if you want to support older OSs"
mrantarctica
Posts: 26
Joined: Sun Feb 23, 2020 12:01 am

Re: Corrupted Package

Post by mrantarctica »

perceval wrote:I would update at least to 10.14.

10.11 is quite old, and there have been multiple security fixes added to the OS since then.

No need to go to 10.15. I did, and I wish I hadn't. 10.15 introduced a lot of pain to developers, and there are still a couple of apps I have that do not work in 10.15 and above yet.
Rob wrote:He's got no choice because there's no driver support for his hardware beyond El Capitan.

I'm sure there's a solution. I spend some time searching tonight.
Consulted the Resident Audio website again, and it would appear that they say don't upgrade to Mac OSX 10.15 Catalina. This would appear to suggest their hardware works up until Catalina. I will try to get either High Sierra or Mojave installed today and see if the eDrumin installer runs. However, based on Apple's explanation, it would seem that the problem still exists as it is an older OS.

Have thought about just scrapping the Resident Audio T2 but to be honest, the performance is actually better than with just the native Apple Sound card etc. Unfortunately there aren't many good cheap Thunderbolt Audio interfaces around and Resident Audio seem to refuse to just generate some drivers that work with newer OS's

I will see if anyone has managed to get the Resident Audio devices working on Big Sur and see if I can get it working too.
User avatar
Rob
Site Admin
Posts: 4716
Joined: Sat Aug 01, 2009 2:04 pm

Re: Corrupted Package

Post by Rob »

I'm pretty sure the issue will not be present on 10.12.
Post Reply