Speaking of Melda... as I was writing this post I received an email from them. Looks like they must have caught some flack and they're sending out a mass mea culpa!

Moderator: James Steele
A lot of companies decide they don't have to be good, just not as bad as their main competitors.mikehalloran wrote:Reading the daily CNet reports on all the issues that users are having with Win10 and the auto-updates ... This has been going on over three years! Yea, I really want to switch to that.
For sure, IMO I've always thought the best solution hardware wise would be a high end MacBook Pro as a front end for a dedicated build your own PC running VEP or just MMC, MTC etc. Off load all the heavy duty plug ins like sample libraries etc. into the PC and use the laptop for the more real time stuff.James Steele wrote:Okay... they're hardly contrite, but looks like they took some heat. I didn't know the backstory that these guys have some sort of issue with Macs. On the other hand, I don't want to become so in love with a particular hardware platform that I ignore other options should they become viable and make more sense.
Sound Quest is frequently asked, which is better - Windows or Macintosh? This is our take on the two systems and why.
If you are interested in incorporating MIDI hardware editors into your DAW (Pro Tools, Cubase, Sonar,
Performer, Logic) using VST, AAX, AU, or any another plug-in system, the clear winner is the Macintosh. Hands down. No question. Why? The MIDI management system developed by Apple called CoreMIDI is
far superior in handling MIDI data and allows all applications equal and unlimited access to all MIDI ports.
This functionality is built into the operating system and is an incredibly important feature if you wish to
use AU or VST plug-in editors. The reason, both the DAW and the editor will function at their best when
both have equal access to the MIDI interface. This is what the Macintosh does.
Windows on the other hand, leaves the MIDI capabilities to the MIDI interface manufacturers. As a result,
there are many, many MIDI interfaces that only allow one application to access the driver at a time. This
means that if the DAW has the MIDI interface open, a MIDI hardware editor can't open the MIDI port to
communicate with the interface. To further confuse matters, some MIDI interface drivers will allow
multiple applications to access the MIDI interface but they must be separate processes. While there is a
workaround for these issues, it requires specific planning and you are forced to spend more time
considering the setup and configuration of your system. While these limitations are not true of all MIDI
interfaces, it is true for many of them.
Windows does have one advantage over the Mac. There is slightly more control over the output of SysEx
data. If you have a specific group of very old instruments from Casio (CZ and VZ series), Ensoniq (ESQ-
1, ESQm) or a few others which are not able to receive SysEx transmissions at full speed, it is possible
to reduce the transmission rate for effective communications. This is not possible on the Macintosh.
Even with this advantage, remember that with a Macintosh you can still install a virtual version of
Windows (Parallels, Fusion, etc) on a Macintosh and use it to communicate with these problematic
instruments.
This comparison between Windows and Macintosh is taken solely from the perspective of MIDI support.
There are certainly other reasons to choose one system over the other.
Prime Mover wrote: Users don't care about the complexities of what goes on behind the scenes between developers, but if they see one developer bitching about another... guess who ends up looking the fool? Yeah yeah yeah, Apple and Adobe are big evil megacorps... but I don't hear them shitting on you?!!
Urs wrote: To me there seem to be quite a lot of contradictory claims here.
Why would Apple invest in a notarisation platform for software which is distributed outside of their App Store, if their goal was to enforce selling through that App Store? They could have gotten that a lot easier by simply closing that system, or simply by abandoning package build, product build and codesign. And DMG with symlinks.
If 99$ a year sounds like a hell of a lot for a hobby developer, I wonder what hobby musicians think about plug-in prices.
If I was Apple and if I was keen on sanctioning software, the first person who I'd sanction would be the one who publicly posts an email that I had sent in private. My guess: Apple isn't keen on sanctioning software.
If I was a plug-in developer afraid of the whole notarisation process, I would not worry: Plug-in binaries do not need to be notarised. Applications, installers and DMGs do. So I'd distribute my plug-ins the olden way: In a zip, no installer needed - and no notarisation.
If I was a user of an operating system which has all my contacts, camera access, location services, a password manager, my credit card information and a photo library, and if I was living in a world where companies like Camebridge Analytica exist, where anything as stupid as a simple freeware game could harvest hundreds of millions of aforementioned data sources, where a well trained AI needs one photo from my home to suss out more about me than my friends know, I'd sleep a lot deeper if I knew that access entitlements for random software were somewhat managed for most of us.
Also, if it wasn't against forum guidelines I'd be happy to share a link to a certain warez site where certain Mac cracks for our products (and that of pretty much everyone else selling here) can be downloaded: Each with a great and convenient installer, which - conveniently for the guy who runs the site - also installs a crypto miner and possibly a full backdoor to the system, unbeknownst to the unsuspecting user of a platform which he thinks is free of malware. I really don't mind that to be over and done with.
I'm not worried, I have my towel.Michael Canavan wrote:Just because this is such a great summation of this recent Skye is Falling frenzy everyone is in, Urs from U-He on the issue in terms of the future.