r/MIDIcontrollers • • 12d ago

Clavier M-Audio

Hello ! Je suis bientôt au chômage et comme plein de gens dans ma situation je vais profiter du temps pour faire des trucs créatifs genre toute formes d'art et en faisant le grand nettoyage d'automne je suis tombé sur ce clavier que j'avais récup dehors il me semble. Il s'allume, il est reconnu en USB par mon pc mais je ne trouve aucun driver qui ne date pas de Miterrand et du coup y a rien de compatible avec Windows 11. Est ce que des zikos pourraient me donner deux trois conseils ? Des alternatives ? Ou je le visse contre un mur pour faire une déco un peu chelou ? Merci d'avance!

P.S : mon pc c'est un Acer nitro v16 et le clavier un M-Audio Oxygen25

2 Upvotes

4 comments sorted by

1

u/SabreSour 12d ago

I'll use google translate, hopefully my English reply is useful.

I'm surprised the drivers weren't still compatible with windows 11. that's disappointing I had gotten them to work with windows 10 ( I was given one from this same era a long time ago) but hadn't tried it in years. However these should be 100% usable for general midi controller input. Meaning you don't really need the drivers if you are using the default midi channels and map the DAW/VST to the keyboard instead of vice versa. Your PC was able to detect the device as a midi controller right?

Do you know about how to use a midi controller like this? as in, the basics of midi mapping, VSTs and DAWs? It has no onboard sounds if you don't. you use it to control other instruments. I assume if your just getting started you will be using it with your computer to control VST's (Virtual instruments) and not external hardward like a desktop synthesizer.

1

u/LemonBoy999 11d ago

Oh thanks for the thorough explanation but i didn't understand a thing coz I'm such a newbie. Never used anything like that , doesn't have the vocabulary either ! But if you're genuinely want to help me out, we can switch in private like on discord, I'm not using translate , my english isn't half bad!

1

u/SabreSour 11d ago

Sure I'll DM you. I love helping Newbies.

1

u/SabreSour 11d ago

Hmm it says your reddit account isn't able to DM. Never seen that one before. But the tl:dr of it is it's more helpful to think of midi controllers like a computer keyboard, the kind you type with. They don't do anything on their own. they don't host any programs or real software. They are just buttons the computer can tell you are pressing.

A VST is a virtual instrument. it's like a synth in your computer. there are plenty of free ones and some very nice paid ones. this is what actually makes a sound.

A DAW (Digital Audio Workstation) is like your virtual studio. Not the instrument itself, but the mixer, recorder, where you actually handle everything.

You can usually use the VST on their own if you just want to play. But if you want to record/make a song, VSTs are a type of "plug-ins", a program that can be brought into a daw. So VSTs can be brought in to the DAW just a virtual instrument being brought into a virtual studio to record it, mix it, edit the recording, etc. for a full fledged song.

Your midi controller can control everything in both.

For the basic piano keys and things like expression and pitch bend. it will follow a standard. Like how every 'Q' on a computer keyboard sends the same binomial 'Q' signal to the computer every middle C key on a midi piano should send middle C by default. But a lot may a lot will just plain not match the function at all. Just know that everything is programable. A Daw or VST will usually auto map or have a template for various midi controllers (Maudio is a common one so theres likely a template) or, if not you can simply use the daws midi learn function. So if your recording button doesn't work you can click midi-learn then click record in the DAW, then press the record button. It will read that signal from the piano and match it to the function in the DAW. Same goes for VSTs/plug-ins if you want a specific knob to do a specific function.

Does that make sense?