PSR Keyboards (11 Boards) > PSR-E Series

Does anyone know how Sound Controller app works?

(1/4) > >>

hikari:
Since YAMAHA has discontinued Sound Controller app for PSR-E3 series keyboard. So PSR-E3 series keyboard cannot have pitch bend or modulation wheel by connect a iOS device to it.

So does anyone tried to sniff into USB line to get the command that iOS device send to the keyboard to adjust pitch bend or modulation wheel?

I knows that I can send a local off command to the keyboard and create a loopback between MIDI IN/OUT on this keyboard. And send pitch bend or modulation wheel MIDI command to the keyboard by a microcontroller. But it still is pain in the *** cuz I can't easily change the panel voice of this keyboard.

Since I can't get Sound Controller app so I don't really know how YAMAHA implement this app. Does anyone know how to send pitch bend/modulation wheel, even change effects setting or panel voice via USB-MIDI for budget YAMAHA PSR-E series keyboard?

pjd:
Hi --

Welcome to the Forum!

There isn't any magic, really. The Sound Controller app sends standard MIDI messages to the target keyboard. This is accomplished by sending MIDI over USB.

The PSR-E series keyboards respond to the XG Lite subset of MIDI messages. Yamaha didn't bother to document these in the Data List PDF.

You should be able to send these messages from the MIDI Designer app on IOS. I built a MIDI Designer template for the SHS-500 Sonogenic which has a similar tone generator as the PSR-E series:

https://sandsoftwaresound.net/sonogenic-voice-editor/
https://sandsoftwaresound.net/shs-500-sonogenic-midi/
https://sandsoftwaresound.net/sonogenic-ui-midi-flow/
http://sandsoftwaresound.net/customizing-the-sonogenic-voice-editor/

Unfortunately, I've never found a way to select panel voices. Yamaha's internal architecture treats the keyboard as separate channels distinct from the incoming external MIDI channels.

Hope this helps your exploration.

-- pj

pjd:
By the way, Yamaha apps do sometimes generate "magic" undocumented MIDI SysEx messages.

I have monitored them in MIDI Designer. I've sometimes been able to monitor these messages by splitting out the messages from the MIDI stream and sending the messages to a MIDI monitor like MIDI-OX or even MIDI Designer.

It takes a lot of experimenting and faffing around, but it can be done!

-- pj

pjd:
I hooked up Sound Controller to Genos1 and monitored the outgoing MIDI messages.

When Sound Controller starts up, it sends the following set-up messages:

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               
 000B0BCE   2  --     F0  Buffer:     2 Bytes   System Exclusive     
 SYSX: F0 F7
 000B1051   2  --     F0  Buffer:     2 Bytes   System Exclusive     
 SYSX: F0 F7
 000B18A0   2  --     F0  Buffer:     6 Bytes   System Exclusive     
 SYSX: F0 7E 7F 06 01 F7
 000B18BE   2  --     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 43 50 00 00 07 01 F7
 000B1C90   2  --     F0  Buffer:     6 Bytes   System Exclusive     
 SYSX: F0 7E 7F 06 01 F7
 000B1C9B   2  --     F0  Buffer:     8 Bytes   System Exclusive     
 SYSX: F0 43 50 00 00 07 01 F7
 000B1C9E   2  --     F0  Buffer:     9 Bytes   System Exclusive     
 SYSX: F0 43 73 01 52 26 02 02 F7


F0 7E 7F 06 01 F7 is the standard MIDI identity request messages. BTW, if no keyboard is connected, Sound Controller will loop and send this message over and over again until it receives a response. This is how Sound Controller detects a connected and supported keyboard.

-- pj

pjd:
I monitored Genos1's responses to the Sound Controller app:

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               
 00002D38   2  --     FE    --    --   --  ---  Active Sensing       
 00002E00   2  --     FE    --    --   --  ---  Active Sensing       
 00002EC7   2  --     FE    --    --   --  ---  Active Sensing       
 00002F8F   2  --     FE    --    --   --  ---  Active Sensing       
 00002FDD   2  --     F0  Buffer:    15 Bytes   System Exclusive     
 SYSX: F0 7E 7F 06 02 43 00 44 42 1C 0A 00 00 01 F7
 00002FEA   2  --     F0  Buffer:    16 Bytes   System Exclusive     
 SYSX: F0 43 50 00 00 07 02 07 00 47 65 6E 6F 73 00 F7
 00003057   2  --     FE    --    --   --  ---  Active Sensing       
 00003120   2  --     FE    --    --   --  ---  Active Sensing       
 000031E7   2  --     FE    --    --   --  ---  Active Sensing       
 000032AF   2  --     FE    --    --   --  ---  Active Sensing       
 00003378   2  --     FE    --    --   --  ---  Active Sensing       
 000033CD   2  --     F0  Buffer:    15 Bytes   System Exclusive     
 SYSX: F0 7E 7F 06 02 43 00 44 42 1C 0A 00 00 01 F7
 000033D8   2  --     F0  Buffer:    16 Bytes   System Exclusive     
 SYSX: F0 43 50 00 00 07 02 07 00 47 65 6E 6F 73 00 F7
 000033EC   2  --     F0  Buffer:    42 Bytes   System Exclusive     
 SYSX: F0 43 73 01 52 26 02 03 20 01 02 03 04 30 31 32 33 20
 SYSX: 21 22 23 24 25 26 27 00 00 00 00 00 00 00 00 00 00 00
 SYSX: 00 00 00 00 00 F7
 00003440   2  --     FE    --    --   --  ---  Active Sensing       
 00003507   2  --     FE    --    --   --  ---  Active Sensing       


F0 7E 7F 06 02 43 00 44 42 1C 0A 00 00 01 F7 is the Genos1 reply to the identity request. It says "I'm Genos 1".

Good luck discovering what these SysEx messages do!

-- pj

Navigation

[0] Message Index

[#] Next page