3 ms·

You do bring up some great points. Yeah, I guess it is still FLOSS. It's just my personal opinion that having a paywall (or the appearence of one) for the majo

You do bring up some great points. Yeah, I guess it is still FLOSS. It's just my personal opinion that having a paywall (or the appearence of one) for the majority of your users is a huge barrier to success and openness, no matter how small that paywall is. Not that it's a bad business model, it's just one that I don't want to use for my projects. I don't want to sound like I'm downplaying the acheivements of Ardour. It is definitely impressive, and I look forward to the MIDI workflow improvements! It's just from a workflow perspective (especially from an EDM perspective), Ardour isn't quite my cup of tea. I personally want to create something with a workflow akin to Live/Bitwig/FL. Yeah, your article on time keeping was a huge inspiration in our time-keeping system. We would definitely love your feedback on this! Currently I've designed it in such a way where we can easily swap out the actual internals of the `MusicalTime` struct if we find that f64 is not good enough. I'm aware it will indeed be a challenge when it comes time to support automation of tempo, time signatures, swing rythm, etc. That's why I seperated it into its own repo to keep it focused on the pure algorithm. (The repo is in rusty-daw-timeline btw).

PaulDavisThe1st 5y ago
> Ardour isn't quite my cup of tea. I personally want to create something with a workflow akin to Live/Bitwig/FL. https://www.youtube.com/watch?v=EiwUN7hz6eU https://www.youtube.com/watch?v=EiwUN7hz6eU Scene launching started working yesterday (on top of clip launching). All of our music<->audio time conversion stuff now lives in its own library, called temporal https://github.com/Ardour/ardour/tree/master/libs/temporal https://github.com/Ardour/ardour/tree/master/libs/temporal It's likely that there will be a wholesale renaming of data types in here, because "int62_t" is a little too generic, and at least one of our long term devs is strongly against builtin-like names (eg. timepos_t) for things that are actually our own objects.
- BillyDM 5y ago
  Oooh, that clip launching stuff looks nifty! I'll have to try it out. I'll also take a look at temporal. You definitely have a point when it comes to avoiding mistakes of the past. Your help and guidance is appreciated!

PaulDavisThe1st 5y ago

> Ardour isn't quite my cup of tea. I personally want to create something with a workflow akin to Live/Bitwig/FL. https://www.youtube.com/watch?v=EiwUN7hz6eU https://www.youtube.com/watch?v=EiwUN7hz6eU Scene launching started working yesterday (on top of clip launching). All of our music<->audio time conversion stuff now lives in its own library, called temporal https://github.com/Ardour/ardour/tree/master/libs/temporal https://github.com/Ardour/ardour/tree/master/libs/temporal It's likely that there will be a wholesale renaming of data types in here, because "int62_t" is a little too generic, and at least one of our long term devs is strongly against builtin-like names (eg. timepos_t) for things that are actually our own objects.

BillyDM 5y ago
Oooh, that clip launching stuff looks nifty! I'll have to try it out. I'll also take a look at temporal. You definitely have a point when it comes to avoiding mistakes of the past. Your help and guidance is appreciated!