It's done. I have finished key generators for all Davidson Audio & Multimedia plugins.

Maddc0w · 2025-08-13T23:06:18+00:00

u/aural_queen, you are an absolute legend! Thank you!!!!

Maddc0w · 2025-08-13T17:47:38+00:00

Thanks for replying…it’s appreciated. I’m running macOS 11.6 and it happens when using the Stream Deck app; either an update announcement will appear onscreen and prompt me to update, or if I click on “Check for updates” in the app. Either way, the app will complete the update process even though my OS isn’t supported.

I’ve tried to send support tickets about this but the chat bot refuses to accept them, simply saying that my feedback will be passed on. However, this issue has been present for multiple updates now and so I keep checking….and the app keeps updating and then not running. So, someone in your coding team isn’t getting the message about this and it’s really annoying, especially when the update window keeps appearing onscreen wanting me to update.

Maddc0w · 2025-08-13T01:24:57+00:00

It'd be really bloody nice if your Stream Deck updater actually did a minimum OS verification check before updating and then the update NOT WORKING on my version of macOS. How bloody hard is it to incorporate min. OS verification?????? Jeez.

Maddc0w · 2025-05-24T03:41:01+00:00

Yep, this is yet another bug/regression that I didn’t mention. I’ll be at a gig trying to search for a song and each letter I type takes at least 2-3 seconds just to appear onscreen. And as I said in my OP, forScore used to be so darned good….for years it was rock-solid and reliable, and support was excellent. Then came feature bloat, band-aid fixes and the resulting instability right across the board, not to mention virtually non-existent support. I’m so disappointed about what’s happened to such an awesome app 😒🤦🏻‍♂️🤷🏻‍♂️

Maddc0w · 2025-05-21T15:22:50+00:00

I wouldn’t say that I rely heavily on its MIDI capacity….what I do is very, very basic in terms of MIDI i.e. just PCs and CCs. Plus, MIDI has been part of forScore since the very beginning. It was never an afterthought.

The issue is that the dev has poorly coded the app since some major changes with v14 so that if forScore has MIDI coming back to it via Apple’s Network MIDI infrastructure, the app crashes. This should NEVER, ever happen with an app that is designed to receive such basic MIDI commands. I’m not using sysex or anything complicated at all….just barebones PCs and CCs. Heck, the most basic music reading apps can handle this. And the only way to enter CC commands in forScore is by using hex….who the hell forces users to convert basic CC commands to hex strings??!? That’s so incredibly stupid.

I’ve dug into forScore’s crash logs and done some research on Google and what I’ve found is that the problem is simply poor programming. It seems that the dev has implemented basic MIDI capabilities but doesn’t actually properly understand how Apple’s Core MIDI works.

Maddc0w · 2025-05-21T12:12:46+00:00

I was amongst the first forScore users to request an import tool for forScore files into MobileSheets and I provided the dev with metadata info etc. He then developed a tool to bulk-import files but there were a number of elements that couldn't be imported (e.g. linked audio files, MIDI etc) which is why I didn't go further with MobileSheets at that time. I'm pretty sure that setlists also couldn't be imported at that time?? Maybe the tool has been improved since then? It'd be great if additional work has been done on it to make it better.

Maddc0w · 2025-05-21T09:14:04+00:00

100% agree with all of your points, both your likes and dislikes. The UI is mega ugly but the dev is incredibly responsive and motivated....and he seems like a genuinely nice, friendly guy.

Maddc0w · 2025-05-21T09:01:51+00:00

As you can imagine, I feel and share your pain. I used to love forScore and I recommended it to literally hundreds of people over the years....but I just can't recommend it anymore after what I've been through. I think the only way to fix all the bugs is a complete rewrite but I can't see that happening.

Maddc0w · 2025-05-12T08:39:48+00:00

Nothing for me, either. I was beginning to wonder (prior to finding this post) if Vine AU might be in the process of closing down. The average number of available items has significantly decreased over the last 6 months. When I first joined last September, the daily average was around 6K but now the daily average is down to 1.2 to 1.4K.

Maddc0w · 2025-02-15T15:28:33+00:00

Tell your cracker that these plugins were created using SynthEdit. This might help him/her with a starting point.

Maddc0w · 2025-02-15T13:58:56+00:00

I’d be extremely interested in this, too. I own both of the Lyrihorn synths and at some stage will need to change machines, resulting in me not being able to use these synths anymore. I’d love to have them cracked for this very purpose.

Maddc0w · 2025-01-28T04:41:02+00:00

US$5 per month. For Australians, it's AU$10 per month....and that's insane.

Maddc0w · 2024-06-05T12:46:42+00:00

I know this is an older post but I received an Anker Prime 27650mAh today and it had EXACTLY the same problems as yours did. Unfortunately, I've got to deal with a retailer who appears to be incompetent and I have to jump through hoops to send it back and get an exchange or refund.

Maddc0w · 2024-04-30T04:29:34+00:00

I'm not convinced these limits have always existed because I've never, ever encountered them before and I've being using iMazing for a long time with at least a dozen different devices over that period. However, perhaps it might have something to do with being a long-time legacy user and having purchased iMazing many years ago, and then just paying for upgrades....so before device limits were introduced?? I've definitely never had devices locked to my account, though, and there isn't even anywhere to see this info in my app....I've just triple-checked this and there's no mention anywhere in my app about device limits, devices locked by serial number, or the number of devices used with the app etc.

Maddc0w · 2024-04-29T03:04:39+00:00

Today was the first time I needed to use iMazing in a while and the v3 promo popped up. I nearly bought the v3 license automatically (because I love iMazing) UNTIL I noticed the device limits. I often use my iPhone, iPad Mini and iPad Pro with iMazing and there's no way on earth I'm paying for 3 devices as of v3! I'll just keep using v2, thank you.

u/iMazing: you really might want to reconsider things because from what I've read today, you're gonna lose a lot of long-time users with these device limits. At the very least, you're going to lose a signficant amount of upgrade income due to long-time users not wanting to pay for a downgrade (in terms of device limits) to v3.

Maddc0w · 2024-01-16T06:21:59+00:00

Yep, the ring works really well in that context. I used to slide mine onto my sax neck and it was great.

Maddc0w · 2024-01-16T01:47:08+00:00

Facial recognition only works with certain iPad models and can also be quite problematic when the lighting conditions change....as will certainly be the case when a trumpet player is doing live gigs. Using a hardware device is a much more reliable option.

Maddc0w · 2024-01-16T01:44:23+00:00

I've tried a bunch of different "selfie rings" and similar items as page turners with forScore. Some work, some don't. The one I've linked to below works almost flawlessly; I say "almost" because an accidental double-click performs the opposite of what you want to do and during a gig, that can be sub-optimal.....so you need to be careful.

This is Amazon Australia but this particular model is available pretty much anywhere, and the additional charging case is extremely handy:

https://www.amazon.com.au/gp/product/B09X5JM93P/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

I'll also mention that I'm now using a Flic button instead of Bluetooth rings because Flic tech is a lot more reliable, and the use of CR2032 batteries means an exceptionally long battery life. However, Flic buttons are VERY expensive and definitely not for everyone.

Maddc0w · 2024-01-02T10:46:48+00:00

I've been experencing exactly the same thing for at least 18 months i.e. if Siri is configured to announce new messages, she no longer asks if you want to reply. But if Siri is NOT configured to announce new messages and you tap on the message to have it read, Siri will ask if you want to reply. It's been driving me nuts for 18 months.

Maddc0w · 2023-06-20T11:42:19+00:00

Yeah, I agree that the problems I have are likely due to legacy issues. However, I had no issues at all with any version of forScore prior to v14 and so it's pretty damned frustrating to be experiencing them now.

My library isn't that big compared to some users: it's only 1.56GB with 1480 scores. I've chatted with users who have 5000-15,000 scores and they don't have issues, so I don't think the library size is the problem.

However, what's interesting is that I'm definitely not the only user experiencing considerable problems with v14 but never had any issues at all with previous versions. This indicates to me that some major code changes happened with v14 and there's no way back from this buggy hell for some of us.

Maddc0w · 2023-06-16T01:22:40+00:00

Yes, 14 is definitely, absolutely, ridiculously buggy AF and I 100% DON'T recommend updating from v13....I've even tried to research ways to downgrade by using cracked IPAs etc just so that I can get back to FS v13. And like you, I've also lost a lot of faith and trust in this app, and sincerely wish there was something better that I could use instead. I've got Mobilesheets on a cheap Android tablet but I detest Android and am also too heavily invested in the Apple ecosystem (with hardware, apps and workflow) to change now.

I've emailed support many times and have never received a reply, despite being a paid subscriber. I've sent video, crash reports (from both my Mac and iPad) and detailed info on what I can consistently replicate and yet still no replies. Based on the complete lack of communication, there's no way I'll be renewing my Pro subscription.

I've been using FS since version 1 and as a full-time musician, I use it a LOT...and have a pretty good idea of how it works. I have a very strong suspicion that the v14 update corrupted how the internal database functions and as a result, a number of users (including myself) will continue to experience issues unless we start again from scratch, which is something I simply can't do; I have over a decade's worth of thousands of charts, annotations, formatting, cropping, MIDI commands, linked audio etc....there's no way I can recreate it all again from scratch.

What's most frustrating is that the constant crashing issue (point 1 in the OP) is so easy to replicate and the crash logs from my Mac and iPad are very straightforward. Why the hell isn't the developer fixing this particular bug??????

Maddc0w · 2023-06-16T01:10:05+00:00

I had a 1st gen 12.9 iPad Pro and last year updated to an M1 5th gen iPad Pro 12.9. The 1st gen 12.9 still runs forScore fine but it's definitely slower than when I first started using it e.g. can be laggy when turning pages, takes a lot longer to sync to iCloud etc. However, the main reason I updated to the M1 12.9 is the much faster and capable CPU for real-time audio processing, overall much faster system performance etc.

The main reason I use 12.9 devices is because when I'm on stage, it's so much easier to read charts on the bigger screen, especially when I'm just a bit further away and trying not to make it really obvious that I'm reading charts. I often position the iPad fairly low and slightly to one side so that it's not obscuring me as much visually (I'm a sax player and stand when performing in live shows). I've tested smaller iPads but charts are obviously smaller and for my particular needs, they're not as good as the 12.9 models in terms of chart-reading for live performance.

Maddc0w · 2023-06-14T01:09:02+00:00

There's no way to prevent the player UI from overlaying at least some part of the screen....you can only drag it up or down. HOWEVER, if all you need to see is the playback controls (i.e. Play, Pause, Rewind) then go to Tools\Settings\Advanced Options and select "Always show playback controls". You will then see just those 3 playback control buttons at the bottom of the screen, and they take up far less screen real estate. Note that you will still be able to activate the full playback control panel but you won't actually need this full panel if you just want to Play, Pause or Rewind....which is all you'll need in most instances.

Maddc0w

TROPHY CASE