I’ve been working on a Tracker Interface for Ardour for the past 6 years, reminiscent of SoundTracker software coming from the Amiga.
See (DISCLAIMER: this is ALPHA software).
It is already functional but slow and has a number of missing features, quirks and imperfections.
Here is the purpose of that message: I need help.
I’ve been working alone on this for too long, with a job and a family I do not have enough spare time for it, so I need people to join me to finish it sooner (and frankly merrier too, cause working alone isn’t fun).
I’ve meant to ask for help a long time ago, I wanted to do that after my branch would have been merged to Ardour’s master, but various bugs are always moving the goalpost, so I’ve decided to throw my “message in the bottle” now.
What do I need:
first and foremost I need developers
second and centermost I need testers
third and backmost I need documentation writers
fourth and allmost I need souls
So where to go from there? I’m thinking perhaps of setting up a weekly or monthly jitsi meeting where I could walk anybody through the code, take suggestions, etc. All that is really to be determined and that is also the purpose of this post.
So if you feel the call, join me in that crazy endeavor and together let us create a beautiful tracker
i’m not actually a coder, but a DevOps and a long-time tracker user (renoise, milkytracker, ft2, openmpt etc). I’m really excited for your initiative, since i asked for tracker interface within ardour (the event list editor reminded me of tracker, and i suggested that perhaps it would be possible to have a tracker interface - derived from that?)
What we would do would be up to you. But certainly upon request I could demo the tracker interface, provide assistance to those who wants to compile it, walk anyone through the code, receive feedback, etc. And if nobody shows up I’ll just work solo on it.
The next meeting would be Jan 24. Hope to see or dream you there!
you should receive email with access to the dropbox video. Let me know if this does not happen soon.
question i forgot to ask yesterday:
How does keyboard focus work? Is it like - whenever tracker editor is open - it has primarily the keyboard focus, or you have to click between editor and tracker editor to change focus?
(in short: do copy/paste (ctrl/cmd+c/v) shortcuts work within tracker editor?)
Regarding keyboard focus, it’s bad, I know more or less how to pass through the tracker interface shortcut keys that are not recognized but it’s very flaky. Another item that belongs to the to-be-polished category. And Ctrl+c/v is not supported.
Wow, this looks promising! List editors are always inducing this question: why is this not on a grid, like a tracker?
But you @ngeiswei actually follow through! Well done.
If I find only a little bit of time, I will try to contribute. But I can not make any promise. I just started learning C++, so not much wisdom coming from there either. In any case I will check out the fork today and try to build it.
If you need more traction for this project, I suggest posting a call for help and the video over at
There are a lot of open source and tracker enthusiasts over there.
Last Monday meeting went well (except I was unintentionally muted most of the time), a good soul joined the call to cheer me up while I was hacking the code. I did not record the call (maybe I should have).
@GenGen, If you’re a C++ noob it’s perfect because then you have the added motivation to learn C++ (and you may benefit from the feedback of a veteran C++ dev). If you can you’re super welcome to join the call and I can walk you through the code. Thanks for the forum link BTW.
Sorry I couldn’t make it. Time is sparse between family and full time job. 5 pm UTC is just about dinner time in our household. I will try to make it next time though, they can do without me every now and again
Hey @dspasic! Things are slowly but steadily moving. I’m still doing my weekly coding session on Jitsi Meet at 5pm UTC, and sometimes people join to cheer me up :-).
I haven’t updated the Arch package because I’m still working on my next change (support effect automations, not just instrument’s) which involves lots of refactoring. As soon as it is ready, I’ll push that on the tracker-editor-wip branch and update the Arch package.
Let me provide a little update. I’m finally done refactoring the code so that I can add the last important feature which is to be able to edit automations of effects, not just synths. I don’t know how long that is going to take me. The refactoring took me almost 8 months, and I would probably have estimated that to 2 months (the 4x rules seems to apply). So well, maybe another 8 months! That’s why I ask for help
After that I’ll update the arch package, test, test and test, and I hope you, the interested community, will do too. I want to be sure it does not crash Ardour before considering merging it upstream. Then, there will still be a massive amount of optimizing, improving, polishing and skinning to be done, but hopefully, being upstream will facilitate that.
The really nice thing, is that the midi engine of the upcoming Ardour 7 is considerably better than that of Ardour 6 (which is actually why I didn’t really care to merge it until recently, because with the Ardour 6 midi engine, the tracker editor is too much pain to use due to its explicit tick-scale precision). In other words, the two endeavors, awesome midi engine and tracker editor, are converging really nicely.