Anacreon Synthesizer | Anacreon 2.5 Released
-
OBSOLETE160530 OBSOLETE160530 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=160530
- KVRist
- 179 posts since 19 Sep, 2007
-
- KVRist
- Topic Starter
- 237 posts since 24 Jul, 2020
Hey thanks crickey! I'm feeling pretty good - Anacreon will never be completely be abandoned, but there will be long periods of time where I can't work on it. I wish I could promise a more consistent schedule, but I'm just not a consistent enough person right now. I will say that I feel engaged and that I'm not feeling discouraged about the issues I'm facing with Anacreon currently. Usually what kills it for me is a ridiculous bug that never resolves!crickey13 wrote: Sun Oct 10, 2021 8:41 am Good to see you back in stride, Erich. It's always sad to see softsynth projects being abandoned or stranded, so it's nice to see Anacreon being still developed.
BTW, I've been recently reading a book about Ancient Greece and I came across Anacreon at one point, instantly thought of your synth.
Anacreon was a pretty cool guy. I like his character a lot - nice to know Anacreon synth is living in your head rent free lmao! Hope you're having a great day.
-
- KVRist
- Topic Starter
- 237 posts since 24 Jul, 2020
Falk,falkTX wrote: Sun Oct 10, 2021 10:53 amI would say to try to remove the dll exports, since that is something that I know makes this work on linux.Erich.Pfister wrote: Sun Oct 10, 2021 4:56 am BTW I saw the debug variable and set it to true, but it's still not catching the entry point...
Just delete the whole "Set plugin symbols to export" section on https://github.com/DISTRHO/DPF/blob/dev ... ns.mk#L114 and relink.
If windows works like linux on this, you will get debugging symbols.
Thanks for your help! I'm planning to make the "set plugin symbols to export" section conditional based on whether or not DEBUG is set to true. Is that something that I should submit a pull request on after I've done it or is this too specific to my use case to be a library feature?
Thanks!
-
OBSOLETE160530 OBSOLETE160530 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=160530
- KVRist
- 179 posts since 19 Sep, 2007
-
- KVRist
- Topic Starter
- 237 posts since 24 Jul, 2020
Hey Falk - in your experience, is there anything preventing a plugin from having non-sequential parameter ids across the platforms you've implemented with Distrho? I'm planning to use bitfields to encode a 31 bit hierarchical addressing system for parameters so that I can add and remove parameters more easily without breaking between updates.
Edit: And that address is stored as a uint32 parameter id.
-
OBSOLETE160530 OBSOLETE160530 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=160530
- KVRist
- 179 posts since 19 Sep, 2007
-
- KVRist
- Topic Starter
- 237 posts since 24 Jul, 2020
Believe me - I've thought of putting the new ones after the old ones, but I'm doing a bit more than I said in my previous post. I want to allow a variable number of each module (osc, filter, etc) type via config file, and I want any patch made in Anacreon to load on any config that has at least the minimum number of the different modules required, and I want all automation saved by the host to match up perfectly so that people (like me) who don't use presets but use whatever the DAW provides for saving stuff.falkTX wrote: Sun Oct 17, 2021 5:24 pm For VST2, VST3 and LV2 this doesnt matter at all.
DPF (from your provided info when creating the plugin) assigns a dedicated symbol to each parameter. So saving and restoring state is pretty safe when it comes to parameters additions/removals.
But automation is not, so something to keep in mind (LV2 is always fine though, as the spec dictates to always use symbols to refer to parameters, never indexes)
If you want to be extra safe, reserve some parameters and just don't set the attributes to make them automable on the host, calling them "unused" or something.
It is not good practice though. Preferably if you add new parameters often the best is to put them after the old ones.
EDIT: I can think of a few different ways to achieve this with a continuous block of parameters.
-
OBSOLETE160530 OBSOLETE160530 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=160530
- KVRist
- 179 posts since 19 Sep, 2007
-
- KVRist
- Topic Starter
- 237 posts since 24 Jul, 2020
falkTX - it is a general problem but your help definitely provided a constraint that I wasn't initially aware of, so thanks for clarifying that!falkTX wrote: Sun Oct 17, 2021 5:51 pm Well I guess this is more of a general problem rather than be something specific to DPF.
You just need to find something that works well enough.
-
- KVRAF
- 1586 posts since 7 Jun, 2007
Hi Erich, sorry I've been away from here so long. Had a quick read to catch up. I like the concept of the synth components being configurable regarding numbers of each module etc, but I forsee a massive frustration if one tries to open a 7 osc 4 filter preset sound and anacreon doesn't because it's not currently configured that way. I believe the synth should open all presets regardless of structural configuration.
Otherwise you get that disgruntled annoyance like when u can't open specific IK Amplitude presets because u don't own all the gear it needs.
I just think that's a way to piss users off. And it only kinda makes any sense if there are in-app purchases to get. But hopefully anacreon will be a store-less synth.
Still looking forward to seeing the progress. Wishing u strength in ur coding dungeon!
Otherwise you get that disgruntled annoyance like when u can't open specific IK Amplitude presets because u don't own all the gear it needs.
I just think that's a way to piss users off. And it only kinda makes any sense if there are in-app purchases to get. But hopefully anacreon will be a store-less synth.
Still looking forward to seeing the progress. Wishing u strength in ur coding dungeon!
-
- KVRist
- Topic Starter
- 237 posts since 24 Jul, 2020
Hey Xalama Qo,
I'm not interested in selling DLC for this thing, please don't worry about Anacreon becoming that. What I want to do is make a customizable layout / component count and design the presets so that, if you've specified enough oscillators and filters and such, you'll open the preset just fine. Maybe it will tell you what you're short on so you can just load up more oscillators or filters or lfos or whatever you don't have enough of - that's literally just a settings tweak or loading a different layout file, which I plan to release for free. Other people might decide to sell layouts or presets for Anacreon, but that's their intellectual property at that point, I don't dictate what others do. The main reason I want this synth to be hackable is because, 10 years from now when everyone is running faster computers, the number of components can be increased without changing the source code. I'm trying to future proof by not assuming how many of each module people want, but the modules are all included and free. I hope that clarifies!
As far as coding goes, I'm still in a rut - my mental health issues are preventing me from working on my hobbies. Just don't have the mental energy to program! I always come back to Anacreon though, been programming this thing on and off for a long time. It won't be abandoned, just in a slow period. Sorry about that everybody!
I'm not interested in selling DLC for this thing, please don't worry about Anacreon becoming that. What I want to do is make a customizable layout / component count and design the presets so that, if you've specified enough oscillators and filters and such, you'll open the preset just fine. Maybe it will tell you what you're short on so you can just load up more oscillators or filters or lfos or whatever you don't have enough of - that's literally just a settings tweak or loading a different layout file, which I plan to release for free. Other people might decide to sell layouts or presets for Anacreon, but that's their intellectual property at that point, I don't dictate what others do. The main reason I want this synth to be hackable is because, 10 years from now when everyone is running faster computers, the number of components can be increased without changing the source code. I'm trying to future proof by not assuming how many of each module people want, but the modules are all included and free. I hope that clarifies!
As far as coding goes, I'm still in a rut - my mental health issues are preventing me from working on my hobbies. Just don't have the mental energy to program! I always come back to Anacreon though, been programming this thing on and off for a long time. It won't be abandoned, just in a slow period. Sorry about that everybody!
-
- KVRAF
- 1586 posts since 7 Jun, 2007
Thanks for the reply Erich. Hoping your health improves, hang in there!
It's great to hear your plans don't include in-app purchases. I didn't actually think that was the case, was just using Amplitube as an example of "computer-says-no" frustration in the middle of trying to be creative and not lose the flow.
I still think having presets with large component numbers should open "automagically", or perhaps warn the user of incompatible configurations and ask if the user would like to go ahead and open the potentially CPU heavy preset anyway.
Obvs I don't know how simple/complex your vision of config file change would be, or if anacreon would need to be reloaded in the DAW for changes to take effect, etc.
All I know is the simplest and least disruptive method is always best, because user experience is so important these days, and many musicians aren't coders or even computer-tinkerers. The fewer hoops to jump through the better.
Just my 2c
Wishing you strength again, and I still think you have a very strong and intriguing synth here with a big dose of mojo juice
It's great to hear your plans don't include in-app purchases. I didn't actually think that was the case, was just using Amplitube as an example of "computer-says-no" frustration in the middle of trying to be creative and not lose the flow.
I still think having presets with large component numbers should open "automagically", or perhaps warn the user of incompatible configurations and ask if the user would like to go ahead and open the potentially CPU heavy preset anyway.
Obvs I don't know how simple/complex your vision of config file change would be, or if anacreon would need to be reloaded in the DAW for changes to take effect, etc.
All I know is the simplest and least disruptive method is always best, because user experience is so important these days, and many musicians aren't coders or even computer-tinkerers. The fewer hoops to jump through the better.
Just my 2c
Wishing you strength again, and I still think you have a very strong and intriguing synth here with a big dose of mojo juice
-
- KVRAF
- 1586 posts since 7 Jun, 2007
Ok, I've just reread your reply, and the OTHER main factor in the config file is the GUI layout. I kinda glossed over that.
A config file does make sense if a customized GUI is involved too.
I was still picturing your original GUI with a mostly horizontal layout of modules iirc, and thought that to generically add modules they could just be slotted in next to the existing ones. The GUI window could get wider with each new module added, or stacked vertically.
I was imagining a more generic free-form arrangement of modules. But now I think I see where you're coming from. Gonna let that sink in
A config file does make sense if a customized GUI is involved too.
I was still picturing your original GUI with a mostly horizontal layout of modules iirc, and thought that to generically add modules they could just be slotted in next to the existing ones. The GUI window could get wider with each new module added, or stacked vertically.
I was imagining a more generic free-form arrangement of modules. But now I think I see where you're coming from. Gonna let that sink in
-
- KVRist
- Topic Starter
- 237 posts since 24 Jul, 2020
Xalama Qo,
Exactly - you've got it! Layouts will be completely freeform with custom GUI elements available. I'll probably release a few horizontal-type configs/GUIs with different component counts so that there's always a free option that has enough of each module, and I expect that people who like to tinker will adjust for themselves or maybe share what they make?
I know the sound of my synth is good - just want to make it so that the visuals / layout can be updated as styles change. Since I also plan to release Anacreon in a lot of plugin formats, I'm hoping that the custom layouts plus the different formats means that the plugin will live for a while on the internet.
Thanks for sending good thoughts / strength my way! I'm getting treatment for my issues, so I'm expecting to make good progress on health improvement in 2022.
Best Regards,
Erich
Exactly - you've got it! Layouts will be completely freeform with custom GUI elements available. I'll probably release a few horizontal-type configs/GUIs with different component counts so that there's always a free option that has enough of each module, and I expect that people who like to tinker will adjust for themselves or maybe share what they make?
I know the sound of my synth is good - just want to make it so that the visuals / layout can be updated as styles change. Since I also plan to release Anacreon in a lot of plugin formats, I'm hoping that the custom layouts plus the different formats means that the plugin will live for a while on the internet.
Thanks for sending good thoughts / strength my way! I'm getting treatment for my issues, so I'm expecting to make good progress on health improvement in 2022.
Best Regards,
Erich
-
- KVRist
- Topic Starter
- 237 posts since 24 Jul, 2020
Hey everybody - I'm back!
Todo:
- Debug existing bugs
- Unbug future insects
- Rebug spiders
- Relearn C++
- Unexpose patch cables as parameters (certain DAWs can't handle so many parameters)
- Attempt to implement a structured document format for GUI skinning.
- Improve FX section and make modulation work as expected.
- Find a way to make patch cables easier to follow.
Todo:
- Debug existing bugs
- Unbug future insects
- Rebug spiders
- Relearn C++
- Unexpose patch cables as parameters (certain DAWs can't handle so many parameters)
- Attempt to implement a structured document format for GUI skinning.
- Improve FX section and make modulation work as expected.
- Find a way to make patch cables easier to follow.