Let's continue working on this
@ryukau I just wanted to say I'm sorry for what happend. I want us to finish this wonderful synth.
I'm OK with it.
I probably also said something bad because of my lack of understanding of language. If you felt my tone was inappropriate, I'm sorry for that.
However there's one condition must be met: use of JUCE or VST 3 SDK.
It's not about DPF, but because of the problem on my current environment. I kind of stuck in Windows environment for now, because my Linux environment freezes quite often. DPF is nice on Linux, but not so much on Windows (it requires MinGW, if I understand correctly).
I'm currently working on another synth, so if you are OK with the above things, I'll work on DigiDrie after finishing it.
That's great news!
Feel free to chose any environment you want. Sorry to hear about your freezing linux.
I'm looking forward to working together again!
The another synth is mostly finished. So I'm ready to start working on this repository.
I'll focus to port previous code. Target is VST 3 SDK, because it requires least amount of code to port. It will take time because I have to remember many things. When porting is finished, I'll open PR.
Great, congratulations on the other synth! Where can I find it?
If you are on NixOS, then it probably has to be built from source code. It's on PluckSynth branch of VSTPlugins reposiroty (link).
If you are on Windows, macOS, or latest Ubuntu, download link is available at here.
Could you enable discussion on this repository? So that topics which is not related to DigiDrie development can be written there.
I looked into Insights->Community, then clicked Set up discussions but it opened 404 page. Probably I don't have permission to enable the feature.
OK, thanks for the link, I'll check it out when I have some time. Discussions are enabled now.
Thanks for opening discussion. 😀
Migration to VST 3 SDK is done. Checkout vst3migration branch.
Build commands are updated in top level README.md in vst3migration branch. I haven't tested the commands on Linux. If it's not working please let me know.
I found that I forgot the interaction of macro, lfo, and envelope to internal control signal. 🤯 Would you possibly write a how to style documentation? For example, I couldn't figure out following workflow:
- Get a lowpassed output.
- Apply release to master gain.
It can also be a recipe recipe section of the user manual.
It has been almost a week and there's no response to my last commit. I leave this project indefinitely.
Hey, I was just trying to build it. Sorry for taking so long!
I'm running into issues, I get:
-- Checking for modules 'pangocairo;pangoft2'
-- Found pangocairo, version 1.50.7
-- Found pangoft2, version 1.50.7
-- Checking for module 'fontconfig'
-- Found fontconfig, version 2.14.0
CMake Error at vstgui4/vstgui/uidescription/CMakeLists.txt:200 (message):
Generating editoruidesc.h failed: No such file or directory
-- Configuring incomplete, errors occurred!
I'll put a bit of information here, but I won't continue development further. I have other things to do, and I can't afford the context switch between projects. I understand that you are probably just busy on your work, but I feel that it's better to split the way here.
As I said, I'm planning to fork DigiDrie and make my version at some point. This synth has some nice ideas, but for me, it's faster to port everything to C++ and debug on there.
The error says editoruidesc.h on VSTGUI is lacking, so I suspect submodule initialization is not done properly. If you haven't, try the following command under DigiDrie directory, on vst3migration branch.
git submodule update --init --recursive
CMake version must be 3.20 or higher.
This is probably not related, but to make sure, package requirement for Ubuntu is listed on the link below. See Package Requirements under For Linux section:
https://steinbergmedia.github.io/vst3_dev_portal/pages/Getting+Started/How+to+setup+my+system.html#for-linux
VSTGUI can be built on Ubuntu, Fedora, Arch (Manjaro) and Mageia (reference). So if the build command is correct, the error is specific to your environment. I can't help much beyond this comment.