What does that mean.Jorgeelalto wrote:This is really interesting,but a pity it's synthedit .
Kirsty
What does that mean.Jorgeelalto wrote:This is really interesting,but a pity it's synthedit .
That seems wrong. Maybe a bug?AutoMotto wrote: I have FL Studio 12.2 And the current version of this plugin and NONE of the modules move, not even ones in use and there is NO WAY to delete or move unused modules. Perhaps in your DAW it works, but not FL.
Sorry, I meant that this project is interesting, but I don't really like synthedit. Even so, I'll follow this topickirsty roland wrote:What does that mean.Jorgeelalto wrote:This is really interesting,but a pity it's synthedit .
Kirsty
?Jorgeelalto wrote:Sorry, I meant that this project is interesting, but I don't really like synthedit. Even so, I'll follow this topickirsty roland wrote:What does that mean.Jorgeelalto wrote:This is really interesting,but a pity it's synthedit .
Kirsty
(If I'm not mistaken, I've seen that this modular is made with SynthEdit. I could be wrong :p)
I know, I've been using SynthEdit plugins for some time. I'll give it a try. It's that SynthEdit plugins usually consume more CPU than non-SE plugins. Maybe it's my computer that is very underpowered, or maybe it's me, sometimes I'm a bit mad about itpottering wrote:?Jorgeelalto wrote:Sorry, I meant that this project is interesting, but I don't really like synthedit. Even so, I'll follow this topickirsty roland wrote:What does that mean.Jorgeelalto wrote:This is really interesting,but a pity it's synthedit .
Kirsty
(If I'm not mistaken, I've seen that this modular is made with SynthEdit. I could be wrong :p)
Seems you are a Reaper user, x32 synthedit stuff loads just fine in Reaper x64.
SynthEdit is just the framework that has been used. Kirsty coded ALL modules himself if I'm not mistaking. CPU usage is remarkably low!Jorgeelalto wrote: I know, I've been using SynthEdit plugins for some time. I'll give it a try. It's that SynthEdit plugins usually consume more CPU than non-SE plugins. Maybe it's my computer that is very underpowered, or maybe it's me, sometimes I'm a bit mad about it
Well, in that case, I'm very interested in this! Thank you.Nielzie wrote:SynthEdit is just the framework that has been used. Kirsty coded ALL modules himself if I'm not mistaking. CPU usage is remarkably low!Jorgeelalto wrote: I know, I've been using SynthEdit plugins for some time. I'll give it a try. It's that SynthEdit plugins usually consume more CPU than non-SE plugins. Maybe it's my computer that is very underpowered, or maybe it's me, sometimes I'm a bit mad about it
Most likely is a bug, sadly the Dev doesn't seem too interested to offer a reply. But never mind, there is always Sonigen modular and Kamioooka to use. I would prefer to donate money to a Dev who cares about what people want, not based on the size of their own monitor and assume everyone has the same.Nielzie wrote:That seems wrong. Maybe a bug?AutoMotto wrote: I have FL Studio 12.2 And the current version of this plugin and NONE of the modules move, not even ones in use and there is NO WAY to delete or move unused modules. Perhaps in your DAW it works, but not FL.
I have a life so don't visit KVR every day. I'm sorry you feel this way.AutoMotto wrote:Most likely is a bug, sadly the Dev doesn't seem too interested to offer a reply. But never mind, there is always Sonigen modular and Kamioooka to use. I would prefer to donate money to a Dev who cares about what people want, not based on the size of their own monitor and assume everyone has the same.Nielzie wrote:That seems wrong. Maybe a bug?AutoMotto wrote: I have FL Studio 12.2 And the current version of this plugin and NONE of the modules move, not even ones in use and there is NO WAY to delete or move unused modules. Perhaps in your DAW it works, but not FL.
Her opinion to me is - "screw those who don't have (or can't afford) a bigger screen"
Not very proffesional, even for a free plugin IMO.
So you prefer that people who developed some nice stuff for their own needs doesn't release this to the public? I currently working on a vst-looper and made some design decisions based on my needs (e.g. all loops are mono), when I read such a comment as yours I think that it is maybe better just to use it for myself instead of investing the time into writing a manual etc..AutoMotto wrote: Most likely is a bug, sadly the Dev doesn't seem too interested to offer a reply. But never mind, there is always Sonigen modular and Kamioooka to use. I would prefer to donate money to a Dev who cares about what people want, not based on the size of their own monitor and assume everyone has the same.
Her opinion to me is - "screw those who don't have (or can't afford) a bigger screen"
Not very proffesional, even for a free plugin IMO.
No, you didn't have understood what I am saying. I have already released something in the past as Open Source (an extension for Reaper/Mackie Control: see http://forum.cockos.com/showthread.php?t=81818). I totally disagree with your demand for any sort of support, and for sure if someone started to rant in a way to doing this here, for sure I would not react to this person or try to help him. Luckily I have never seen this behavior before.AutoMotto wrote:@Klinke - I understand what you are saying, I have developed my own VST based on the Roland Jupiter 4, I have no plans to share it just like you have no plans to share yours, we all do what we want to do sir, but when a dev shares a plugin, they must be prepared for feedback (good or bad) if they cant take the feedback, don't publish the plugin, simple as that!
Brilliant job on this synth and the GUI rewrite. Thank YOU so much, for this.kirsty roland wrote:I have a life so don't visit KVR every day. I'm sorry you feel this way.AutoMotto wrote:Most likely is a bug, sadly the Dev doesn't seem too interested to offer a reply. But never mind, there is always Sonigen modular and Kamioooka to use. I would prefer to donate money to a Dev who cares about what people want, not based on the size of their own monitor and assume everyone has the same.Nielzie wrote:That seems wrong. Maybe a bug?AutoMotto wrote: I have FL Studio 12.2 And the current version of this plugin and NONE of the modules move, not even ones in use and there is NO WAY to delete or move unused modules. Perhaps in your DAW it works, but not FL.
Her opinion to me is - "screw those who don't have (or can't afford) a bigger screen"
Not very proffesional, even for a free plugin IMO.
I've made it clear from the start that I made Patchwork for my own use and am happy to offer it for free to anyone else who would like to use it.
It does all the things that I want but I am willing to make some changes (even if I'm personally not interested in using them) to help other users out.
But I am not going to customize it beyond my own needs.
My PC is an Asus Laptop at 1366x768 but I code on a HD monitor. If I reduce the entire GUI again I will probably get some posts from people with 4K monitors complaining that its too small.
I've spent some weeks rewriting the GUI code to accommodate advanced skinning.
With this new method any user can fully customize the GUI. Not by simply changing the graphics but also repositioning the GUI elements anywhere on a module.
So if anyone doesn't like my graphics or layout they can make their own.
You can...
Reposition the knobs, input/output plug holes switches and displays.
Re-skin every module background and the entire synth background.
Rewrite any module or control text.
Re-sizable GUI will probably come at some time in the future but I can't please everybody.
It's not just simply skinning. This is dermatology
In the meantime, if you don't like the synth I am giving you for free I too would recommend Sonigen.
Kirsty
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement