Thanks for sharing these info, I was having a long test session for LibreArp today, and indeed there's a a good glimpse of that big to-do list...alefunguju wrote:First off, there will be much more coming in the future versions. Consider the first version a proof-of-concept.
If you're interested in what's on the to-do list (it's already quite a lot and more items are being added), you can take a look at the issue tracker on GitLab (link on the official page).
Before I give my feedback, I will reply to the below QAs
To phreaque:
to be considered before moving to MacOS
Why would I do that before moving to macOS? The codebase is cross-platform as-is, someone just needs to compile it, which I can't do, personally, simply because I don't have and currently don't plan on getting a macOS device. I see no reason to postpone macOS community builds (that is: done by someone else than me) until more features are done.
You're right, I didn't realize that, but when I checked the website, read the guide I realized the development for mentioned platforms is identical somehow.
1. Color based keynotes to determine the key sorting (e.g. blue = 1st note, orange = 3rd note, grey = root note etc.)
I'm not exactly sure what you mean here. If you mean some visual representation of which note is which number in from the input, that's already on the to-do.
You got me right, and it's great to know that you're planning to implement this in future release.
2. Ability to add markers and to define Midi CC to jump through different arp variations.
I rather plan on having the ability to add multiple arp patterns and a song-wide timeline of when each pattern is supposed to play. The plan is to add this feature on version 3.
Well, I'm not quite sure what those patterns would like like, but my idea was to allow having variety of basslines for example across let's say 8 bars, and each bar represent a midi-triggerable zone... But I sense that you're into the same thing, perhaps we just use different terminology.
3. Adding a midi out feature so it gives ability to sort certain key notes to be sent to a specific midi channel..
I can add this, sounds like a reasonable idea.
That's very good
if the VST is a freeware
It's not. It's free open-source, point of which is that it can be a collaboration of volunteers who contribute to the codebase - anyone can see the source, edit it, send changes back to me, create their custom version etc etc.
why not to make a payware version of it with such capabilities. It will make a huge benefit for us.
I won't be doing that, I'd much rather keep it open-source. Trust me, you wouldn't benefit from that - I'm a comp-sci student doing this in free time and making a paid version wouldn't magically create more free time for me to work on it.
Honestly, that's the spirit, we learn, gain experience, share and hoping to get rewarded by whichever way... Surely your efforts are getting noticed and being appreciated, and that will lead you to further challenges, which I'm sure will bring you the knowledge you are aiming for...
--------------
My feedback after a deep examining of LibreArp:
* Tested it in FL Studio 20, the 32bit version wasn't fully functional inside the FLS 64 bit host btw. (The GUI for example wasn't able to resize)
* When I added two LibreArp instances, the 1st one caused a sustained notes (stuck notes) and couldn't be muted unless (refresh the VST).
* Relocating the (Red Loop Marker) can make more sense if it can be dragged from the (Scroll area - where the bar numbers are), just to avoid clicking notes by mistake while dragging the marker within the grid region.
* Grid region: Good color theme, really it's inspired by FL Studio piano roll.. I feel an urgent need for velocity and other CC parameters to be added as well
My overall evaluation for this arp (as is): 6/10 - once the mentioned planned features added, I think it would easily reach 9/10
Anyhow, I'm grateful to test it, and I believe it will be a unique tool.
Good luck & looking forward to see the upcoming updates...
