Posts by djantimatter

Quote from serano

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.

Quote from hugol

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.

Quote from hugol

Nice 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.

Display More

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.

Quote from ChrisCabbage

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.

Quote from ChrisCabbage

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.

Quote from hugol

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.

Quote from hugol

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.

Quote from oliAtBass

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.

Display More

Time for a MIDI Over USB only version then. Like we requested several years ago.

Quote from ChrisCabbage

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:

https://www.kemper-amps.com/fo…1877-8-0-2-22186-release/

Quote from OneNationAbove

I don’t need to disconnect the power, I can leave it on or in standby without a problem, but if I want to use it outside of Logic I have to remove the USB cable for some reason or I won’t hear a single sound.

According to Access Support this is because it’s a class compliant issue, and according to them, normal.

This was their reply:

“We cannot answer this to be honest, but we can only assume that this might be caused by the TI not using class compliant Midi drivers due to the Total Integration, which other device use, since there it is only for Midi I/O.”

But I don’t know what I should think of that.

Display More

This an issue with Local control. Both of my TI units do this. Go to the config mode and look for Local Control and turn it on, problem solved.

Note: You'll have to do this every time you start up your TI.

Looks like Kemper and Co can't get their sh*t together to even give us a basic update. It's been almost two years since the last firmware update. Since then 2 new versions of MacOs have been released and Apple is currently making a major hardware platform shift. And yet, somehow we still have no update.

This is RIDICULOUS.

For YEARS, forum users here have been requesting a future proof MIDI over USB only version of the Virus Control VST/AU plugin and Access/Kemper have steadfastly REFUSED to do so over and over again. Meanwhile, they've left their Synth line in the dust in favor of their Amp line.

Access - MAKE this right and make it right NOW!!!!!!!!

Quote from ChrisCabbage

Not long now 'til the Anniversary of Marc's Oct 8th 2019 announcement on Catalina incompatibility!

Party time?

We're still waiting, poor show Access.

I've recently bought a new Darkstar as part of my mobile rig so my ageing 2005 Polar can be retired from travel and gigging work next year. I've done this in spite of any updates on Access' front as the Virus has been a core component of my sound for a decade now. I seriously hope they will get their act together and fix this soon.

We really do need an answer and a timeframe from Access on when they will get this resolved and if they plan on doing an end of life for the TI series. It's very poor on their part to maintain radio silence for so long on this matter.

Quote from oliAtBass

ok, just as an experiment:

- Remove all the preset bank files

- Check start time

- Then add them one by one or in groups

- Check start time for each addition

Sounds tedious, but it should give an indication whether the problem is related to the number of preset files or maybe even a certain (faulty) one.

Display More

No difference, removed all but one with no change.

Quote from oliAtBass

That's a lot.

Try to divide them into sub folders.

Done, no difference.

Quote from oliAtBass

How many preset bank files are in your local personal preset folder?

195

Quote from skittb123

I don't know what's causing your Logic Pro X to become unresponsive but the 10 minutes ''boot time'' of the Virus TI AU plugin is normal. This only happens when you open the plugin for the first time.

This is happening repeatedly so it's not the first opening.