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

MIDI Implementation and more #53

Open
StanleyHottek opened this issue Aug 23, 2024 · 2 comments
Open

MIDI Implementation and more #53

StanleyHottek opened this issue Aug 23, 2024 · 2 comments

Comments

@StanleyHottek
Copy link

  • make the fasttracker 2 complete and please also implement MIDI output. preferably with a few more functions, such as MIDI CC.
  • separate tracks audio input (with MIDI out) and output with multi-channel sound cards
  • live rendering

... I can think of more... I would even pay more for your work!
I think it's great that the FT2 has not been forgotten and is being rebuilt for new technology.

but at the moment I'm working with the old fasttracker 2 because it has MIDI out.

@JoNilsson
Copy link

JoNilsson commented Aug 23, 2024

... I think it's great that the FT2 has not been forgotten and is being rebuilt for new technology.

but at the moment I'm working with the old fasttracker 2 because it has MIDI out.

I share your sentiments regarding full MIDI implementation. But beyond that some of the features might not be welcomed by the developers because of the fact that they are outside of the original functionality and scope of a true original DOS FT2 clone. But the code is open for forking and there is nothing stopping another development team from taking on the task. It's not going to be cheap in the ways of man hours though. Some of those features would require major rewriting of core functionality. Also, piling multiple issues into a single Git issue should be avoided because it reduces clarity, makes the core issue harder to manage and track, complicates code reviews, and can lead to disorganized version control, whereas keeping issues separate allows for better focus, easier prioritization, and cleaner resolution of individual problems or features. If you want to get something done I would recommend following the advice above.

I do agree that it would be wonderful to have parity when it comes to MIDI features though, but it might not ever happen here. SDL MIDI kind of sucks. I'm also still using the good old DOS executable for my music projects that require MIDI outputs.

@8bitbubsy
Copy link
Owner

What do you mean by "make the fasttracker 2 complete"? It's a clone of original FT2, and I think it's (kinda) complete as it is. It doesn't try to be a modern full-fledged DAW. That is outside of the project's scope, and there are other alternatives out there for that.

Anyway, MIDI out is not that easy to implement in a realiable and timing-stable way when dealing with high (ish) audio buffer sizes. FT2 on DOS could get away with a smaller audio buffer size because it runs in a realtime OS, but I have heard some people say that MIDI out had some smaller timing precision problems even then. I also do not have a way of testing MIDI out because of no MIDI gear, so yeah, it's not going to happen. Sorry...

Paying also doesn't help; I don't want this to become a job - that would suck all the fun out of it, and I would feel stressfully obliged to finish the request.

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

3 participants