• Registered: 2026-03-03
  • Posts: 18

Topic: remote control 12micD with streamdeck

hello!

i'm trying to control the 12mic-D preamps with a streamdeck, with no luck so far.
osc, http post request etc... i can't get it to work.

I even tried the powershell commands explained here:
https://docs.rme-audio.com/12micd/150-1 … ew/#151-4C

and copy/pasting this command from the manual:
curl --header "Content-Type: application/json" --request POST --data '{"osc":{"schema":null}}' RME12MIC-D65432.local/api/v2/self

(replacing the 65432 with my 12mic-d's ID)
and even that gives me an error and doesn't work.

did someone managed to get a form of remote control from anything else than the web remote?
or maybe there is a workaround controlling "RME connector" in midi?
Thanks!

  • Max
  • Max
  • Moderator
  • Offline
  • Registered: 2007-05-09
  • Posts: 358

Re: remote control 12micD with streamdeck

Is HTTP Remote switched on?
What is the error you get?

  • Registered: 2026-03-03
  • Posts: 18

Re: remote control 12micD with streamdeck

i think i got it.

First the syntax they show in example in the manual will work only from a mac terminal.

Then, the manual is full of typos: they forget ' everywhere and put spaces everywhere.
For example:

TX:--data {"input": {"analog": {"4": {"p48": null}}}}

doesn't work at all, it should be:

TX:--data '{"input":{"analog":{"4":{"p48":null}}}}'

  • Registered: 2026-03-03
  • Posts: 18

Re: remote control 12micD with streamdeck

Then:
i tried to narrow down the problem by removing all switches and dante stuff and just connect directly my computer to the 12micD with RJ45

I don't know why but the link local adress auto negociation has a 255.255.0.0
so for example if my 12mic has this adress: 169.254.1.XXX
The computer may have this adress: 169.254.2.YYY

while the web remote from a browser works, the curl command don't.

So in link local mode, you need to identify the 12 mic D adress, and then manually enter the adress in the network manager:
If the 12mic has 169.254.1.XXX, your computer need 169.254.1.YYY

  • Registered: 2026-03-03
  • Posts: 18

Re: remote control 12micD with streamdeck

Then:

the commands that work in mac terminal do not work in windows cmd or power shell.
Syntax in windows is different and quite a pain in the ass.
For exemple on mac:
curl --header "Content-Type: application/json" --request POST --data '{"input":{"analog":{"1":{"p48":false}}}}' RME12MIC-D60C90.local/api/v2/self

Will need to be this in windows cmd:
curl --header "Content-Type: application/json" --request POST --data "{\"input\":{\"analog\":{\"1\":{\"p48\":false}}}}" RME12MIC-D60C90.local/api/v2/self

Windows cmd doesn't read the ' properly and they need to be replaced by "
and you have escape the interior quotes (") with \


I still can't get it to work in powershell for now.

  • Registered: 2026-03-03
  • Posts: 18

Re: remote control 12micD with streamdeck

wooho

it works from Companion with the pluging "generic http request"

in the field "url": http://RME12MIC-D60C90.local/api/v2/self
[obviously replace with your own 12mic id, and for some reason the "http://" is needed]

field "body": {"input":{"analog":{"1":{"p48":false}}}}
[here no need of the windows cmd funky syntax]

field "header input(JSON)": {"Content-Type": "application/json"}

drop down menu "content type": application/json

the rest can be default settings

  • Registered: 2026-03-03
  • Posts: 18

Re: remote control 12micD with streamdeck

and if you wnat to use it directly or streamdeck/streamdock app without companion,
with the plugin "web request" it works

the only difference is that in the "header" field, instead of 

{"Content-Type": "application/json"}

just type 

application/json

8 Reply by Max (edited by Max 2026-03-10 00:31:57)

  • Max
  • Max
  • Moderator
  • Offline
  • Registered: 2007-05-09
  • Posts: 358

Re: remote control 12micD with streamdeck

Glad you figured it out! Shell quoting in Windows is indeed different from linux/macOS, and we would document it if it wasn't already different between the various shells (cmd.exe, ps) in different Windows versions. Nowadays, you would probably just copy and paste the string from the manual into an LLM of your choice and ask it to "make this work on Windows". It would likely also highlight that Windows has issues with hostname resolution and the "http://" requirement that you found out.

full of typos:

Thanks for pointing out those missing quotes in that specific example. Corrected in the next release.

put spaces everywhere.

That does not make a difference, JSON allows whitespace between the tokens.

  • Registered: 2026-03-03
  • Posts: 18

Re: remote control 12micD with streamdeck

yep! sorry for the spaces, i tested it again and as you say, it doesn't matter!