Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility issue #1

Open
silveruniverse opened this issue May 2, 2015 · 8 comments
Open

Compatibility issue #1

silveruniverse opened this issue May 2, 2015 · 8 comments

Comments

@silveruniverse
Copy link

Hey,
Would it be possible for this to work on win 7 64bit and/or a PS3 Rock Band 3 keyboard?
I've tried and tried for hours and MIDI-OX does output random instrument change events, but doesn't do anything if I press the keys, only the buttons.

@martinjos
Copy link
Owner

Hi silveruniverse,
I've just tested it on a Windows 7 64-bit system and it works with the Wii
version of the keytar (inc. key events). My guess is that the PS3 version
is incompatible. Sorry :-(
On 2 May 2015 10:44 pm, "silveruniverse" [email protected] wrote:

Hey,
Would it be possible for this to work on win 7 64bit and/or a PS3 Rock
Band 3 keyboard?
I've tried and tried for hours and MIDI-OX does output random instrument
change events, but doesn't do anything if I press the keys, only the
buttons.


Reply to this email directly or view it on GitHub
#1.

@tonysidaway
Copy link

tonysidaway commented May 2, 2015 via email

@martinjos
Copy link
Owner

That's a good idea, I might think about doing that.

@tonysidaway
Copy link

silveruniverse, I apologise for referring to you in the third person there. The comment was intended to be a private communication. I didn't know my email would end up on this website.

The idea is to see if it's possible to debug your setup by looking at what the app sees from your variant of the keyboard. It could be a quite simple variation that could easily be accommodated by a small change in the code.

@silveruniverse
Copy link
Author

Oh no worries, I'm more than happy to help with this, although I lack any knowledge on how to record the data output by the dongle.

But I tired anyway with software called USB analyzer:
https://drive.google.com/file/d/0B3uKvpRVJBDIMUFCMDA1cWpTeTQ/view?usp=sharing

Is what it recorded happening when I enabled the rb3_driver application, but even when pushing the buttons and keys the code there seemed to be the same.

If there's anything I can do and if you wish to add PS3 keyboard compatibility, then I'd be happy to help.

@tonike
Copy link

tonike commented Apr 25, 2016

Hello, has there been any progress on this matter? I also own PS3 keytar and I would love to help in anyway possible.

@trustmeimanengineer
Copy link

Hi folks,
Great project!

I also have a PS3 keytar. I'm looking into it. I can see output for all the buttons in the debugger but nothing from pressing the keyboard keys.

The packet size is still 27 bytes, although the format is a little different from the doc for the Wii version.

I wonder if the PS3 version could use a different endpoint for the keys, or if there is some other difference?

Cheers,
Richard.

@trustmeimanengineer
Copy link

On the PS3 keytar, packets from endpoint 0x80 look like this:
00 00 08 80 80 80 80 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 02 00 02 00 02

Byte 0:
bit 0 (1) - square
bit 1 (2) - x
bit 2 (4) - circle
bit 3 (8) - triangle

Byte 1:
bit 0 (1) - select
bit 1 (2) - start
bit 4 (10) - playstation button

Byte 2: directional pad, 8 = inactive, 0 = up, increasing clockwise

Remaining bytes always static as above, no response to keyboard keys or modulation slider.

Endpoint 0x02 reads out 9 byte values, all 0. Haven't found any other responsive endpoints. Bit of a mystery. Maybe there is a configuration step required?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants