[Free Synth] Crypt 2 by Vitling

[Esteban Villanova]

Sound is excellent: https://www.vitling.xyz/crypt/

[Syphus]

Would be nice if you could save presets that you make - can't figure out if it has that function . . . .

 

 

Syphus

[Amberwolf]

Seems pretty useless to have something you can alter settings in but not save presets for, so I'd guess there must be a way.  If not, you might want to ask them why such a basic function would be left out.

 

 

But they might be like BabyAudio, where they don't think users should be allowed to have fine control over their plugins, and don't let you change most parameters, it's all buried "under the hood" so that some potentially really useful plugins are just left as useless garbage for anyone that wants that control and isn't just a "preset pusher".    

[Syphus]

15 hours ago, Amberwolf said:

Seems pretty useless to have something you can alter settings in but not save presets for, so I'd guess there must be a way.  If not, you might want to ask them why such a basic function would be left out.

 

 

But they might be like BabyAudio, where they don't think users should be allowed to have fine control over their plugins, and don't let you change most parameters, it's all buried "under the hood" so that some potentially really useful plugins are just left as useless garbage for anyone that wants that control and isn't just a "preset pusher".    

I Emailed developer and asked about the preset saving . . .   No saving of presets.   He suggested saving the plugin with the project.   I thought that in worst case, I could snip the the image and use that as a way to preserve settings - who knows maybe it will change after enough people ask about it.

 

Syphus

Edited Monday at 10:18 AM by Syphus

[Esteban Villanova]

What a major f*ck up... I emailed the dev too.

[Amberwolf]

Guess that's why it's free, doesn't have the most basic of functions. 

Or conversely, it doesn't save presets because it's a free version of something else?  (or is going to be?  I don't know this developer or their products)

[Esteban Villanova]

Had some back and forth with the dev. He got very offended because I said lack of presets makes it useless. I apologized and explained why they matter and he seemed open to the idea afterwards. He doesn't seem to be very experienced in production in general.

[Amberwolf]

11 minutes ago, Esteban Villanova said:

He got very offended because I said lack of presets makes it useless.

 

Something I used to call "programmer syndrome" but is better called "engineer syndrome":  almost always, the developer of a product (physical or digital) only ever sees it from the inside, and they don't actually look at the things in the way they are used by their intended userbase.  When that userbase responds by telling them how it ought to work to do the required job, the developer typically refuses to change it and sometimes explodes at the user, completely missing the whole point of the product, which is to be used by the user, and thus must do things the way the *user* wants them done, not the way the dev thinks they should be done.   

Often the problem is only a UI issue--the under-the-hood stuff works fine, but is not user-accessible in a useful way, or in a user-friendly or workflow-friendly way.  These issues usually get the hardest pushback from the dev, which is the most ridiculous part of it, since the dev should be making the User Interface for the user, not for themselves...but they make it the way the program internally works, not the way the user needs to access those features.   

I have almost never been able to get this across to devs.   The Bakers here have been the most responsive of all of the devs I've ever worked with, but even they have this syndrome now and then, prioritizing program design and operation over user interface and user-experience like any other dev.    

 

Sometimes it is because a dev thinks they know how a feature should be used...but it doesn't matter what they think--what matters is what the *user* wants to do with the program and they way they need to do that, *especially* with art creation, as an artist is not going to do things in some programmatical way, in most cases.   Each one has a way that works for their art, and the program must be adapted or adaptable to that, which is one reason presets and other UI customizability is so very important.  There are many such improvements in customizability in Sonar / etc., though from the posts I see around here some of them could stand some improvement in user-awareness-functionality, and in control accessibility / state-visibility.   

 

It's not easy to make a UI at all, much less one that does all the things a complex program (like Sonar) can, and it's impossible to make a single UI that does everything every user needs it to in the way the user needs it to...so complete customizability is essential for such complex programs.    Customizability is even harder to create flawlessly than a fixed UI...so anyone attempting to do it at all gets my congratulations and eternal thanks, even while I goad them on to continuous further improvements.    

 

But when a program (or device) foists a UI on user, especially an artist, it is at best unhelpful, and usually actively prevents a user from doing the things they want to do.

 

 

As much as I dislike most of the current usages of AI, I can't wait until AI is advanced enough to alter existing programs for me tell it to create the UI I need, as I need it.  Or even just to create a UI "over the top" of the program, so that when I need to do something, it lets me tell it what controls I need, and what information I need displayed, and then I tell it what to do with those and it makes me the UI I need to see for the stuff I am doing at that time, and refine it as I go. 

 

 

[Esteban Villanova]

4 hours ago, Amberwolf said:

 

Something I used to call "programmer syndrome" but is better called "engineer syndrome":  almost always, the developer of a product (physical or digital) only ever sees it from the inside, and they don't actually look at the things in the way they are used by their intended userbase.  When that userbase responds by telling them how it ought to work to do the required job, the developer typically refuses to change it and sometimes explodes at the user, completely missing the whole point of the product, which is to be used by the user, and thus must do things the way the *user* wants them done, not the way the dev thinks they should be done.   

Often the problem is only a UI issue--the under-the-hood stuff works fine, but is not user-accessible in a useful way, or in a user-friendly or workflow-friendly way.  These issues usually get the hardest pushback from the dev, which is the most ridiculous part of it, since the dev should be making the User Interface for the user, not for themselves...but they make it the way the program internally works, not the way the user needs to access those features.   

I have almost never been able to get this across to devs.   The Bakers here have been the most responsive of all of the devs I've ever worked with, but even they have this syndrome now and then, prioritizing program design and operation over user interface and user-experience like any other dev.    

 

Sometimes it is because a dev thinks they know how a feature should be used...but it doesn't matter what they think--what matters is what the *user* wants to do with the program and they way they need to do that, *especially* with art creation, as an artist is not going to do things in some programmatical way, in most cases.   Each one has a way that works for their art, and the program must be adapted or adaptable to that, which is one reason presets and other UI customizability is so very important.  There are many such improvements in customizability in Sonar / etc., though from the posts I see around here some of them could stand some improvement in user-awareness-functionality, and in control accessibility / state-visibility.   

 

It's not easy to make a UI at all, much less one that does all the things a complex program (like Sonar) can, and it's impossible to make a single UI that does everything every user needs it to in the way the user needs it to...so complete customizability is essential for such complex programs.    Customizability is even harder to create flawlessly than a fixed UI...so anyone attempting to do it at all gets my congratulations and eternal thanks, even while I goad them on to continuous further improvements.    

 

But when a program (or device) foists a UI on user, especially an artist, it is at best unhelpful, and usually actively prevents a user from doing the things they want to do.

 

 

As much as I dislike most of the current usages of AI, I can't wait until AI is advanced enough to alter existing programs for me tell it to create the UI I need, as I need it.  Or even just to create a UI "over the top" of the program, so that when I need to do something, it lets me tell it what controls I need, and what information I need displayed, and then I tell it what to do with those and it makes me the UI I need to see for the stuff I am doing at that time, and refine it as I go. 

 

 

Yeah, I get the same impression with REAPER devs, who don't use MIDI themselves... (Justin just records audio).

[Syphus]

I got another email from the dev - He stated that he is going to look into upgrading to allow preset saving since a few people have asked him about it - He stated he would let me know if anything changes . . .

 

Syphus