-
Notifications
You must be signed in to change notification settings - Fork 4
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
Does this work with v4.0.0? (latest) #11
Comments
I'm not sure, I was wrapping up 3.x support when 4.x landed and I've not had the time lately to finish up the work. I apologize, but I have some time off where I can try to get this wrapped up. |
Don't apologise! My new Model:02 comes with v4.0.0 so it would be great to know if this project supports that I am looking to
It feels like m8-js should be able to do this, but I would love to know for certain Looking forward to testing! Best wishes |
Happy New Year :) Not trying to be pushy and I am sure you are busy, but wondering if there was any kind of timeline or roadmap for this. No probs if not. Best wishes |
Unfortunately, this is a personal project that requires me to do a lot of reverse engineering of the M8 binary disk protocol. I haven't had a lot of time to work on this lately, and I don't have a timeline. All that's left for |
No worries, completely understand, thank you
…On Fri, 24 Jan 2025 at 04:50, Jeremy Whitlock ***@***.***> wrote:
Unfortunately, this is a personal project that requires me to do a lot of
reverse engineering of the M8 binary disk protocol. I haven't had a lot of
time to work on this lately, and I don't have a timeline. All that's left
for 3.x is the MIDI Mapping support tests, a release and then I can move
to 4.x. I just need to make the time.
—
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACFFFML7KYC23UUSBI2ND2MHBAFAVCNFSM6AAAAABTN2BEDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJRGU4DANBUGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thank you :)
The text was updated successfully, but these errors were encountered: