the production thread

Unbroken1

…yeahman!

303abuser

Unbroken1 Cheers, sent you a dm.

Mad_Cyril

303abuser
On hols today, if you want some layman’s feedback!

303abuser

Mad_Cyril Link is in your dms, thanks.

Mad_Cyril

303abuser
Finally grabbed it.

Thanks!

Dubman

I’d love to give it a listen

303abuser

Dubman Link is in your dms.

erik

303abuser yep, sure 👌🏽 🤙🏽

303abuser

erik Thanks, sent you the link.

Along_the_Wire

I’ve got a M-Audio Keystation Mini 32 keyboard which worked fine on my old MacBook with Live 11. I’ve since got a new MacBook running OS14 and upgraded to Live 12 and now the keyboard doesn’t work at all - it doesn’t register as an input at all in Ableton. I can’t find anything at all online - has anyone had a remotely similarly miserable experience? I’ve spent a lot of hours trying to resolve.

I see it it in the MIDI Studio app

Henry

Along_the_Wire I have had a few minor weird things happening in 12. None of which are show stoppers. But just enough to annoy me at the time. Have you still got 11 installed?
Failing that. the current build is still only 12.0.1. So there should be an update soon, which might (or not) fix it.

303abuser

Along_the_Wire This might be a dumb question, but if you’ve upgraded to the latest osx version, is it possible that m-audio doesn’t support it yet?

** looks like you sorted it out, at least it was something simple

Unbroken1

…any new drivers on the M-audio site?

Along_the_Wire

Unbroken1 nope

Along_the_Wire

Henry It’s doesn’t work in 11 either, but I’ve found some things that don’t work it you have both 11 and 12 open at the same time.

I found something in Audio MIDI Setup where I can test if the actual MacBook can see the keyboard and it can’t. My other keyboard works fine, so it’s the old mini one that’s simply not supported anymore. Annoying - be worried about buying another one and having the same problem - checked compatibility of some of the better ones and looks like there isn’t a driver for OS 14 yet. What a fucking pain in the arse.

303abuser

Henry I have had a few minor weird things happening in 12. None of which are show stoppers. But just enough to annoy me at the time

I’m thinking about installing 12 this week after finishing a couple of lingering tracks in 11. Is it stable or worth waiting yet? I’m really interested in roar and some of the midi tools, nothing super urgent though.

Henry

Along_the_Wire That’s a right pain the hole. Not moved to OS 14 yet and dreading the day I have to, as something will deffo not be right. And Apple will not give a shit.
I would be tempted to take the hardware down the the Apple Genius Bar in the Bentalls, laying all of the kit out and causing a scene.

On a plus note for Ableton 12, Push 2 has now had an upgrade. Which has miraculously fixed the bug in the hardware where it would loose all of the display. The same bug that I have been asking Ableton support to fix, but they have failed to recognise even existed. Strange that.

Along_the_Wire

Jesus wept - out of desperation, I changed the cable at it was pretty much the only think I hadn’t tried (I was using the original cable that came with it) and it works absolutely fine. How absurd. Sorry to be a pain fellas.

Henry

Along_the_Wire I was going to suggest that (No 2 I.T. thing to check) but held back and I didn’t want any abuse!

Along_the_Wire

303abuser This might be a dumb question, but if you’ve upgraded to the latest osx version, is it possible that m-audio doesn’t support it yet?

It’s never needed a driver and the MacBook could see it, it was just greyed out on the MIDI audio app. Annoying, but glad it’s sorted!

Henry

303abuser My experience of M-Audio support was phoning them about 15 years ago for support on my sound card. I ‘spoke’ with a Glaswegian gentleman, and I could not understand a word he was saying. And it didn’t help because he was eating something at the time. From the poor quality of the audio call I came to the conclusion he was probably at home eating his dinner.

Along_the_Wire

Henry it’s never worked as an option in my life! Wish you had, I’ve been at it for hours and hours.

303abuser

Along_the_Wire At least it was simple. Getting into a chain of soft/firmware upgrades to fix this stuff is a total pain.

« Previous Page Next Page »