That's interesting. Are there any other reports on that incompatibility issue with Windows?
It seems to be a one off so far. I wouldn't be surprised if the PC drivers break at some point as well. At this point I just want an answer from Acces on what they will do about this. It's been two years.
Heads up, I've gotten a report via the Facebook group I admin that the latest Windows updates break the drivers on PC making the Virus unfindable.
https://www.facebook.com/group…4163516337019600/?__cft__[0]=AZWIakD34iTX9Vzy22h4QjMh6_0zApSnaLeN2DpUAniYj1zXEXaV_yzD3-XUYAqWwONgPY1VRjufScUn1FO8iD7wPWeBYN6nm1v-q9QgKMbmxwdM2upHmLhEhWCipjZmLQZyfDnFAqBcwHgExsXNDx8-&__tn__=%2CO%2CP-R
Which indicates the development resources are available…
They are, but they choose to ignore a significant portion of their user base.
Unbelievable, Kemper just announced a new beta 4 days ago which is iOS compatible and compatible with the latest Mac OS versions..................
Alles anzeigenYep.. It's still the same joblisting.
It makes you think no one wants to work for
a shitty company like Accessthem...But more likely Access probably doesn't even want the position to be filled..
Otherwise they would've put some more effort in it...
At the very least they could've put the joblisting on Indeed.com or jobscout24.
Now the listing is just hidden away on some website that's only visited by a few thousand people..
No, it's not. The Kemper site was advertising the same listing and has been taken down there and replaced by a different listing. They just didn't update the Access site.
Alles anzeigenIt's a software job. Here is Google's translation:
"We are looking for someone to strengthen our development team
Software developer
Your tasks include the further development and maintenance of our platform-independent software framework and the embedded and desktop applications for our products.
Your profile:
• You are fluent in C / C ++
• You have experience with larger software projects
• You have a good knowledge of at least one of the following platforms: Windows, Mac OS X, iOS
• You are a team player and ideally have a musical background
We offer an exciting job in the music industry, a friendly and creative working environment, as well as the opportunity to contribute your own ideas and actively shape the entire product development process.
If you want to become part of our team, send us your brief application using our contact form."
Wrong page, they posted this link on facebook: https://www.kemper-amps.com/jo…XMwCoYb8#a-job-software-2
And to clarify, it was the same listing back in September on the Kemper amps site as the one you posted just now from the Access site which hasn't been updated in eons..
Where do you see this? The job position is still listed here:
That's for a hardware development engineer. Previously it was for 'Software Developer Audio/DSP'
Looks like Kemper finally hired a new DSP/C+ developer. Hopefully this means an update will happen soon.
+1 We've been waiting since October 2019 at this point. I also bought a new TI2 last year based on the fact that they said they would update it.
Could you as a developer (Access) have foreseen this in the past? Not really. Now the task at hand to make it compatible with the ARM architecture makes it even more complicated than it was before and boy it would mean a full code overhaul. So I'll go on a limb here and guess that Apple knew what was coming and correctly scheduled it on their last intel branch models and quote 'security' as their main reason, taking away scrutiny from the M1 that would have caused the same issues and even on a lower architectural level.
As for my previous statement about Access not being at fault for Integration part, I stand by it. Also they do their due diligence by making sure the information is available on their site and forum that Mac currently has issues. The one part where I do agree with you, is that their transparency in regards to the future and a possible resolve, are sub-par.
I work for a developer/electronics manufacturer which uses both iOS and MacOS so I have background knowledge of how this works. Apple does release confidential memos notifying developers of upcoming changes in each OS version when they start to appear beta builds for SDK holders. These changes are known well enough in advance so that developers can make necessary changes to maintain compatibility. So that part of your argument is invalid.
Also, I am acquainted with Sean Costello who is the driving force behind Valhalla DSP. He recently posted that it took him a day to re-code one of his plugins for the new M1 platform - https://www.facebook.com/ValhallaDSP/posts/10158708762617226 He's also released M1 compatible builds of his commercial plugs for the new platform as well within a month of the new platform becoming fully available. So this is not the massive code overhaul you are describing, even with the simplistic GUIs he is using in his products.
So from my perspective based on my knowledge of how these situations work, Access/Kemper and Ploytec had MONTHS of advance knowledge of these forthcoming changes with Catalina. The problem I often find is that many developers either wait until the last minute to get their code compatible with new OS releases or don't do it until the new OS version is already released to the Public. Ploytec updated the drivers and passed them on within a reasonable amount of time so the fault for this lapse lies squarely with Access/Kemper.
I'm not sure who that comment was directed at "it's more than just some settings". Absolutely it's Apple who have made significant architectural changes - firstly the move to only supporting 64-bit (which is what this thread is about really) - and then the move to user-mode drivers going forward.
However Access have been completely non-comital around whether they are going to update their Mac software or not. That's unacceptable. Some of us would quite happily pay for them to work on an update.
Also I strongly disagree with your comment around the buyers of a new TI hardware being at fault and negligent if they don't research Mac compatibility. Access should be actively highlighting the Mac compatibility issue. If they aren't then it's Access that is negligent and at fault.
+1. I bought a new Darkstar last year thinking they would eventually sort this mess out.
Alles anzeigenNice idea, but NI have a pretty poor track record supporting their own computer integrated hardware, let along take on an offering from another company.
* I invested in Kore 2 for example - and this was abandoned by NI after a while.
* Similarly support for my Machine MK1 hardware has also been officially terminated (although there may be workarounds).
As with Access's support for the latest Mac OS's - all of this just puts you off buying hardware that relies on computer integration. It's not that cheap - and we've lost all trust in the vendors providing long term support.
The best solution would be a class compliant MIDI over USB only USB with a plug-in and new librarian app really. This would make the TI series future-proof
Nice work, I have your Vol 1 set and used them as templates for sounds I was after. I'll be picking up this one as soon as I can.
Post 159-ish in here:
https://www.elektronauts.com/t…-macos-big-sur/140193/176"The solution includes a brand new driver that moves away from kernel extensions which were deprecated with Mac OS Big Sur. Our new driver is made with modern technologies and makes development easier which in turn helps us to deliver a solution of higher quality."
Seeing as they were using the same driver as Access perhaps Access can license that code from them for the same compatibility.
For info, an Elektron guy's just posted on their forum. They're doing their own thing with their new driver and so are leaving Ploytec behind. So, they have a solution for their kit.
Care to link it?
I just bought a Darkstar new last August. As far as I'm concerned I've already paid for the update.
Definitely backward compatibility is not Apple's approach - but I do think they are constantly aggressively modernising because they think it's the right thing to do. From an IT perspective - it's simpler and better (from a security perspective and more) to remove historical baggage (painful as it is to users).
We'll have to agree to disagree on this point, I work in IT myself and while I am aware it's simpler to remove historical code I don't believe it's better from a sustainability/ethical standpoint.
Sorry - I don't for a minute believe Apple would remove the ability to support audio hardware via custom drivers. It's just it's a big step change for the vendors. And this isn't my area - but I am a software engineer - so I can research further.
This is the company that dropped Firewire which was a widely adopted standard in the audio industry with no prior warning.
This is the company that introduced a security chip which completely screwed up USB audio drivers for an extended period of time.
Apple has shown time and time again that they don't care about backwards compatibility or about being helpful towards existing users. They just charge forth and drop new tech and updates without giving a sh*t about the impact these changes will have.
and on the same page, further down, they state:
macOS Big Sur 11 no longer loads kernel extensions, it's not possible to provide an update for Big Sur. Still, we have plans to keep the driver updated for earlier versions of Mac OS X.
So, that’s the end of the TI on macOS.
Time for a MIDI Over USB only version then. Like we requested several years ago.
Does the Kemper system use the same kind of USB audio system? Perhaps dropping into that forum and asking a few questions might be useful to both sets of users?
No clue, but it still gets updates:
