Morten MosgaardRE: https://mastodon.social/@fuimadane/116456257715692097
Hey #LinuxAudio (and others), say hi to my fellow dane @fuimadane, who I recently discovered just released a special granular plugin for Linux!
Ercanbrack
fuimadane@ercanbrack @mosgaard hiii :)) You're very welcome! Glad to be here
DRMR@fuimadane @ercanbrack @mosgaard Cool that you are using DPF, but why the hell did you put your code inside the examples folder? :P
I might "fork" and restructure this into a more "proper" repo ..
@dreamer @fuimadane @ercanbrack I didn't see an examples folder while installing, so it took me a little to notice there was a Github fork.
I feel in big risk of wanting to learn C++ with all these cool projects!
@dreamer @ercanbrack @mosgaard
Haha, fair point 😄
It started out as an experiment inside the DPF examples folder while I was learning and prototyping the plugin, and then DrumCloud just kept growing from there. So yes — it’s definitely more “it evolved there” than “this was the master plan from the beginning”.
I’ve since moved the active work into a cleaner worktree/branch, but I agree that it would make more sense as a more proper standalone repo structure.
:)
@dreamer @ercanbrack @mosgaard
So if you fork and restructure it, I’d actually be happy to see that
@fuimadane A bit austere still though, build with `make -C plugin`
@dreamer
DrumCloud started as a rough DPF experiment while I was learning and trying to build the kind of granular drum-loop tool I had in my head, so seeing someone take it seriously enough to rebuild and restructure it into a cleaner standalone repo means a lot to me.
I’m genuinely very grateful that you took the time to do that. It’s both flattering and motivating, and I really appreciate the credit back to my original repo too.
This honestly makes me really, really happy.
DrumCloud started as a rough DPF experiment while I was learning and trying to build the kind of granular drum-loop tool I had in my head, so seeing someone take it seriously enough to rebuild and restructure it into a cleaner standalone repo means a lot to me.
I’m genuinely very grateful that you took the time to do that. It’s both flattering and motivating, and I really appreciate the credit back to my original repo too.
This honestly makes me really, really happy.
@fuimadane Of course I'd also be happy to transfer ownership of this. Or just show you how to do this so you can keep it on your end ;)
In this case I started with `git subtree split -P examples/DrumCloud/ -b DrumCloud` which pulled all of your changes to the root of the project (removing all of DPF and its history). So that could be a starting point for you here as well.
@dreamer @dreamer Wow, thank you — that honestly means a lot.
That’s incredibly kind of you. I’d really love to learn how to do it properly on my end as well, so I can understand the process and maintain it myself going forward.
And thank you for sharing the git subtree split approach — that sounds like exactly the kind of starting point I was missing.
I’m genuinely very grateful for both the restructuring work and the offer to help. It means a lot to me.
I tested your version locally and I really like the cleaner repo structure.
At the moment though, I noticed that the LV2 build in REAPER cannot browse/load samples from the UI yet, while that part is working in my current stable version.
So for now I’ll probably keep my current release as the main/public one, but I definitely think your restructure is interesting and valuable.
@fuimadane Oh I barely did any testing on this. Just to make sure that it builds. I did later notice you had a separate branch, while I was working from your main branch. So maybe that has the missing commits that are needed.
@dreamer
thank you again for taking the time to restructure D-Cloud
I really appreciate the cleaner repo structure you made. Since then, I’ve continued working on my side and added newer fixes and features, including the newer sample-loading and UI-related improvements.
I wanted to ask: would it be okay with you if I reuse parts of your cleaned-up repo structure and combine them with my newer fixes in future D-Cloud updates?
I just wanted to ask you, I really appreciate the work u put into it
thank you again for taking the time to restructure D-Cloud
I really appreciate the cleaner repo structure you made. Since then, I’ve continued working on my side and added newer fixes and features, including the newer sample-loading and UI-related improvements.
I wanted to ask: would it be okay with you if I reuse parts of your cleaned-up repo structure and combine them with my newer fixes in future D-Cloud updates?
I just wanted to ask you, I really appreciate the work u put into it