-
Notifications
You must be signed in to change notification settings - Fork 13
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
ASID support #28
Comments
Maybe we can snoop around in the source codes for other editors to see how interfacing with HardSID is done? I believe GT2 has support for it. |
HardSID also supports SIDBlaster which I have, so I can help out testing it. |
This is a task migrated from workstreams in Slack. |
Someone on facebook asked for ASID support, seems to be some sort of protocol which is used by different machines with real sids in them?
|
Hi! Recently answered in the Facebook thread, but saying hi here as well. Let me know if you are interested to implement ASID and if I can help out in any way. Having a plugin in Deepsid would also be awesome. Maybe should write a ticket about that as well? |
For completeness - I just added ASID support to DeepSID and will create a pull request in a few days. Ticket and demo video here: Chordian/deepsid#22 |
PR #178 has been created as a basic, but working proof-of-concept of the ASID support. At the moment it only reads the MIDI port from the configuration file, but a UI in the editor could be added in the future. Using compiled-in RtMidi. |
Please remove the hardSID from the title of this ticket when you are going to pursue ASID. Those two are not compatible since there are no MIDI drivers available for the HardSID for modern computers. It's a dead device because there is no documentation / specifications available for addressing these devices. |
It may not seem important to us, but it should probably still be considered since a lot of users in the Facebook group actually requested it.
The text was updated successfully, but these errors were encountered: