Hi there,
I have an Issue with the MIDI-Input on Windows10. My whole system worked just fine on mac. Now I have to switch to windows10. I work with the latest version of sonicpi (v3.2.2).
The app MIDI-OX recognizes the Midi-input data very well (midi-device: USB Midi Interface), but the Input-channel is not shown up in SP.
I tried to reset MIDI and also restart windows, but by no chance SP recieves any MIDI-Signals.
Does anyone has suggestions? Thanks in advance 
Sorry about this, it’s very strange to hear - I’ve not yet heard of a Windows user with issues with MIDI. It certainly works just fine on all my Windows 10 devices.
Would it be possible to share a copy of your logs? They can be found in .sonic-pi/logs in your home directory. That might help us shed some light on this matter…
Sure, here is what I found:
±-------------------------------------+
This is the Sonic Pi IO Server
Powered by Erlang “22”
API listening on port 51240
Incoming OSC on port 4560
OSC cue forwarding to {127,0,0,1}
on port 51235
±-------------------------------------+
Enabling cue forwarding
Switching cue listener to open network
Enabling cue forwarding
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -
[GUI] - {8c9db1c6-e218-4dd8-bea8-ad227374d4f7}
[GUI] - Discovering port numbers…
[GUI] - Port entry server-listen-to-gui : 51235 : 51235
[GUI] - Port entry gui-send-to-server : 51235 : 51235
[GUI] - Port entry gui-listen-to-server : 51236 : 51236
[GUI] - Port entry server-send-to-gui : 51236 : 51236
[GUI] - Port entry scsynth : 51237 : 51237
[GUI] - Port entry scsynth-send : 51237 : 51237
[GUI] - Port entry osc-midi-out : 51238 : 51238
[GUI] - Port entry osc-midi-in : 51239 : 51239
[GUI] - Port entry server-osc-cues : 4560 : 4560
[GUI] - Port entry erlang-router : 51240 : 51240
[GUI] - Port entry websocket : 51241 : 51241
[GUI] - Detecting port numbers…
[GUI] - GUI listen to server port 51236
[GUI] - port: 51236 [OK]
[GUI] - Server listen to gui port 51235
[GUI] - port: 51235 [OK]
[GUI] - Server incoming OSC cues port 4560
[GUI] - port: 4560 [OK]
[GUI] - Scsynth port 51237
[GUI] - port: 51237 [OK]
[GUI] - Server send to GUI port 51236
[GUI] - port: 51236 [OK]
[GUI] - GUI send to server port 51235
[GUI] - port: 51235 [OK]
[GUI] - Scsynth send port 51237
[GUI] - port: 51237 [OK]
[GUI] - Erlang router port 51240
[GUI] - port: 51240 [OK]
[GUI] - OSC MIDI out port 51238
[GUI] - port: 51238 [OK]
[GUI] - OSC MIDI in port 51239
[GUI] - port: 51239 [OK]
[GUI] - Websocket port 51241
[GUI] - port: 51241 [OK]
[GUI] - All ports OK
[GUI] - launching Sonic Pi Runtime Server:
[GUI] - Ruby server pid registered: 5880
[GUI] - hiding main window
[GUI] - initialising toolbar icons
[GUI] - setting up window structure
[GUI] - restoring scope states
[GUI] - creating status bar
[GUI] - creating info panel
[GUI] - creating shortcuts
[GUI] - creating tool bar
[GUI] - initialising documentation window
[GUI] - wait for sync
[GUI] - waiting for Sonic Pi Server to boot…
[GUI] - starting UDP OSC Server on port 51236…
[GUI] - UDP OSC Server ready and listening
…
[GUI] - Sonic Pi Server successfully booted.
[GUI] - waiting for Sonic Pi Server to respond…
…
[GUI] - Sonic Pi Server connection established
[GUI] - honour prefs
[GUI] - asking OSC server to start
[GUI] - cue port in external mode
[GUI] - update prefs icon
[GUI] - toggle icons
[GUI] - full screen
[GUI] - load workspaces
[GUI] - loading workspaces
[GUI] - load request Version
[GUI] Change Volume to 80
[GUI] - boot sequence completed.
[GUI] - asking OSC server to start
[GUI] - cue port in external mode
[GUI] - writing settings
[GUI] - stopping OSC server
[GUI] - stopping UDP OSC Server…
[GUI] - saving workspaces
[GUI] - UDP OSC Server no longer listening
[GUI] - asking server process to exit…
[GUI] - executing exit script
[GUI] - exiting. Cheerio
Clearing pids: []
No pids to clear
Started [5880] [-] “C:\Program Files\Sonic Pi\app\gui\qt\build\Release…\app\server\native\ruby\bin\ruby.exe” --enable-frozen-string-literal -E utf-8 “C:\Program Files\Sonic Pi\app\gui\qt\build\Release…\app\server\ruby\bin\sonic-pi-server.rb” -u 51235 51236 51237 51237 4560 51240 51238 51239 51241 [-] C:/Users/post/AppData/Local/Temp/sonic-pi-pids/5880
Started [9524] [-] “C:\Program Files\Sonic Pi\app\server\native\scsynth.exe” -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U “C:/Program Files/Sonic Pi/app/server/native/plugins/” -b 4096 -B 127.0.0.1 [-] C:/Users/post/AppData/Local/Temp/sonic-pi-pids/9524
Started [3248] [-] “C:/Program Files/Sonic Pi/app/server/native/erlang/bin/erl.exe” -noshell -pz “C:/Program Files/Sonic Pi/app/server/erlang” -s pi_server start 51240 4560 51235 [-] C:/Users/post/AppData/Local/Temp/sonic-pi-pids/3248
Clearing pids: [“3248”, “5880”, “9524”]
Clearing [3248]
– command “C:/Program Files/Sonic Pi/app/server/native/erlang/bin/erl.exe” -noshell -pz “C:/Program Files/Sonic Pi/app/server/erlang” -s pi_server start 51240 4560 51235
– removing C:/Users/post/AppData/Local/Temp/sonic-pi-pids/3248
– force killing 3248
– killed 3248
Clearing [5880]
– command “C:\Program Files\Sonic Pi\app\gui\qt\build\Release…\app\server\native\ruby\bin\ruby.exe” --enable-frozen-string-literal -E utf-8 “C:\Program Files\Sonic Pi\app\gui\qt\build\Release…\app\server\ruby\bin\sonic-pi-server.rb” -u 51235 51236 51237 51237 4560 51240 51238 51239 51241
– removing C:/Users/post/AppData/Local/Temp/sonic-pi-pids/5880
– unable to get ProcTable info for: 5880
– process: 5880 not running
Clearing [9524]
– command “C:\Program Files\Sonic Pi\app\server\native\scsynth.exe” -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U “C:/Program Files/Sonic Pi/app/server/native/plugins/” -b 4096 -B 127.0.0.1
– removing C:/Users/post/AppData/Local/Temp/sonic-pi-pids/9524
– unable to get ProcTable info for: 9524
– process: 9524 not running
Finished clearing pids
Device options:
Requested devices:
In (matching device NOT found):
Selecting default system input/output devices
Booting with:
In: MME : Analogue 1 + 2 (Focusrite Usb A
Out: MME : Lautsprecher (Focusrite Usb Aud
Sample rate: 44100.000
Latency (in/out): 0.013 / 0.091 sec
SC_AudioDriver: sample rate = 44100.000000, driver’s block size = 64
SuperCollider 3 server ready.
late 0.041894436
late 0.120266914
late 0.185588360
late 0.263961315
Booting on Windows
Boot - Starting the SuperCollider server…
Boot - C:/Program Files/Sonic Pi/app/server/native/scsynth.exe -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -U C:/Program Files/Sonic Pi/app/server/native/plugins/ -b 4096 -B 127.0.0.1
Boot - SuperCollider booted successfully.
Boot - Connecting to the SuperCollider server…
Boot - Sending /status to server: 127.0.0.1:51237
Boot - Receiving ack from scsynth
Boot - Server connection established
Studio - Initialised SuperCollider Audio Server v3.11.0
Studio - Resetting server
Studio - Studio - clearing scsynth
Studio - Studio - allocating audio bus
Studio - Studio - Create Base Synth Groups
Studio - Starting mixer
Studio - Starting scope
“C:/Program Files/Sonic Pi/app/server/native/erlang/bin/erl.exe” -noshell -pz “C:/Program Files/Sonic Pi/app/server/erlang” -s pi_server start 51240 4560 51235
Studio - Spawning o2m with:
‘C:/Program Files/Sonic Pi/app/server/native/osmid/o2m.exe’ -L -b -i 51238 -O 51239 -m 6
Studio - Spawning m2o with:
‘C:/Program Files/Sonic Pi/app/server/native/osmid/m2o.exe’ -t /midi:$n:$i:$c/$m -b -o 51239 -m 6 ‘Sonic Pi’
Studio - Initialised MIDI subsystems
This is Sonic Pi v3.2.2 running on windows with ruby api 2.7.0.
Sonic Pi Server successfully booted.
Server is exiting.
Shutting down GUI…
Goodbye
Exiting - shutting down scsynth server…
Sending /quit command to scsynth
Stopping OSC server…
Stopped OSC server…
Interesting - these all look good to me.
Do you happen to see files named osmid_o2m.log ,osmid_m2o.log and server_errors.log? If so, do they have any contents?
Yes, there are such files, but they don’t have any content.
I also reinstalled SP, and than shortly after installing, one moment, SP recognized MIDI, but only output-channels. After reseting MIDI, they disappeared again.
That’s really strange, so sorry you’re having issues. Unfortunately it’s not clear to me how to help at this stage - there are no issues in the logs so I have nothing to work from.
BTW, how are you resetting the MIDI? That button should only be visible on macOS as it’s not required on Windows.
Goog Morning Sam, there is a MIDI reset Button in the windows-version. At least, this it, what I meant:
I tested the USB-MIDI-Device on another Windows-PC - and it worked well So I decieded to reinstall SP a third time on my Windows-PC. magic happend! Now, it workes for some reason 
The whole thing shows me once again that all those hard- and software ensembles are to be understood as a mode of existence, which have their own indeterminacy, logic and resistance.
I thank you very much for taking the time to patiently walk with me through the strangeness.
All very strange, but I’m certainly glad you managed to get things working.
With respect to the button, I must have removed it recently in the latest code - it certainly won’t be there in the next release for Windows
Also, you’re totally right - hard/software ensembles are definitely a special mode of existence! I often feel like I have to slowly build a trust relationship with the technology I use for expression. It can take a long time, often be very frustrating but can be absolutely worth it
Good luck with things going forwards and thank-you so much for your patience and sticking with Sonic Pi.
