Msuperlooper development stopped, why?

[AisD]

Hello Melda
I see new plugins added..
Lots of updates for them, but for msuperlooper development stopped for the past two years, why is that? Only some minor bug fixes every half a year...
Is it that hard to update MSL too? Perhaps person who develops MSL got fired?
MSL lacks crucial functions
I will name just a few..
Stop All
Tempo warping(change tempo by just one bpm and msl cant handle that),
Feedback(There is no way to know if you record something or it has something recorded, waveform position within the sample)
Instant record with sync enabled
(Now MSL waits a bit before actually recording, InstaLooper3, Augustusloop solved this issue and it works)
Shorter loop length 1/8B, 1/4B 1/2B(Why minimum 1bar?)
MPE support
One shot loop


I know Melda is profit seeking organization, you update and create stuff for masses to use, and ignore stuff that do not generate profit, I get it!
There are not many loopers in the market, why you are not adding these features to the looper, and grabbing that N.1 position and actually making it SUPER LOOPER? By doing so you will definitely going to generate more profit Im sure of it!


People who use MSL please take your time and help Melda to understand what Im trying to say here.

[Dirk Diggler]

Several of your requests are already best handled by your DAW, not MSL natively.

MPE support for MSL?????
What would be point of that?

[smadger]

Hello Melda
I see new plugins added..
Lots of updates for them, but for msuperlooper development stopped for the past two years, why is that? Only some minor bug fixes every half a year...
Is it that hard to update MSL too? Perhaps person who develops MSL got fired?
MSL lacks crucial functions
I will name just a few..
Stop All
Tempo warping(change tempo by just one bpm and msl cant handle that),
Feedback(There is no way to know if you record something or it has something recorded, waveform position within the sample)
Instant record with sync enabled
(Now MSL waits a bit before actually recording, InstaLooper3, Augustusloop solved this issue and it works)
Shorter loop length 1/8B, 1/4B 1/2B(Why minimum 1bar?)
MPE support
One shot loop


I know Melda is profit seeking organization, you update and create stuff for masses to use, and ignore stuff that do not generate profit, I get it!
There are not many loopers in the market, why you are not adding these features to the looper, and grabbing that N.1 position and actually making it SUPER LOOPER? By doing so you will definitely going to generate more profit Im sure of it!


People who use MSL please take your time and help Melda to understand what Im trying to say here.

I see a few things here. Firstly I recognise your frustration, I'm not saying the features you want are all justified or should be expected, I'm just saying I know the feeling of a loved piece of software not doing that "one little thing" that would make it amazing.

Secondly, as I understnad it, the Melda plugs run from the same core, or kernel. I don't know precisely how interleaved everything is, but you need to understand that development, at any level, is not easy. There isn't a single piece of code in the world that hasn't had to be changed because of a bug somewhere, and all of this takes time and resources to test in your own studio, let alone when it's released in to the wild. So it's not always as easy as "just" updating one thing, by adding a feature in one product it may inadvertantly effect the stability of another, which needs testing, fixing, supporting etc. Then take in to account the number of variants of products that share the kernel, and you begin to understand that time and resources are pretty limited, and not everything can ever be accomodated.

Now look at it from a different perspective, you knew what you were purchasing and were happy with it at the time eith the features it had and anything since then has beena free bonus, no? You've had at least one major update the kernel (v16 presuming you purchased more than a few days ago) that includes fixes for bugs and other improvements under the hood that will affect you positively, for free. I know plenty of other devs that would either a) call it a "v2" and charge you for that, or b) just wouldn't do anything at all.

MSL specifically has had a feature added or bug fixed in 5 out of the last 6 releases, I think it's a little unfair to say it's not being actively developed when other plugins have received no updtes at all. And to throw shade because those fixes or features weren't the ones you wanted is a bit off. Again, I absolutely understand the frustration, but there's no need to do it.

Melda does listen to feedback, he is active in this forum as I'm sure you've seen. By all means submit a post as a feature request detailig what you want, and explain how it would help and why, and make it easy for Melda to understsand what you're asking - help him to help you. Who knows, perhaps other people can offer suggestions for workflows to achieve what you want that you hadn't thought of before, these tools are extremely deep and powerful.

Lastly, please, please please, when you are asking a developer to do something NEVER take this approach and say something like "Is it that hard to update MSL too?" You obviously have no idea of hard is to maintain a large codebase and the complexities that surround it. It's ignorant, demanding and a little offensive at best from the developers perspective and sure as hell isn't going to get you anywhere.

So again, I get it, I understand, just maybe think a little more and change the approach and you will have a better chance of getting somewhere.

[AisD]

Several of your requests are already best handled by your DAW, not MSL natively.

MPE support for MSL?????
What would be point of that?

MPE could be really useful by controlling multiple parameters like volume or loop number combined with other MPE plugins.
Please give me some examples of these best handled things?
You are probably talking about stop all right? What else?
In some cases i want to stop only MSL instead of stopping rest of the plugins.
If you use MSL on screen and only melda plugins i guess it's not that bad, but when you start digging deeper and begin to write script automations for lets say 10 plugins on each track, things get really complicated really fast, when there is no feedback for your actions.

[AisD]

I see a few things here. Firstly I recognise your frustration, I'm not saying the features you want are all justified or should be expected, I'm just saying I know the feeling of a loved piece of software not doing that "one little thing" that would make it amazing.

Secondly, as I understnad it, the Melda plugs run from the same core, or kernel. I don't know precisely how interleaved everything is, but you need to understand that development, at any level, is not easy. There isn't a single piece of code in the world that hasn't had to be changed because of a bug somewhere, and all of this takes time and resources to test in your own studio, let alone when it's released in to the wild. So it's not always as easy as "just" updating one thing, by adding a feature in one product it may inadvertantly effect the stability of another, which needs testing, fixing, supporting etc. Then take in to account the number of variants of products that share the kernel, and you begin to understand that time and resources are pretty limited, and not everything can ever be accomodated.

Now look at it from a different perspective, you knew what you were purchasing and were happy with it at the time eith the features it had and anything since then has beena free bonus, no? You've had at least one major update the kernel (v16 presuming you purchased more than a few days ago) that includes fixes for bugs and other improvements under the hood that will affect you positively, for free. I know plenty of other devs that would either a) call it a "v2" and charge you for that, or b) just wouldn't do anything at all.

MSL specifically has had a feature added or bug fixed in 5 out of the last 6 releases, I think it's a little unfair to say it's not being actively developed when other plugins have received no updtes at all. And to throw shade because those fixes or features weren't the ones you wanted is a bit off. Again, I absolutely understand the frustration, but there's no need to do it.

Melda does listen to feedback, he is active in this forum as I'm sure you've seen. By all means submit a post as a feature request detailig what you want, and explain how it would help and why, and make it easy for Melda to understsand what you're asking - help him to help you. Who knows, perhaps other people can offer suggestions for workflows to achieve what you want that you hadn't thought of before, these tools are extremely deep and powerful.

Lastly, please, please please, when you are asking a developer to do something NEVER take this approach and say something like "Is it that hard to update MSL too?" You obviously have no idea of hard is to maintain a large codebase and the complexities that surround it. It's ignorant, demanding and a little offensive at best from the developers perspective and sure as hell isn't going to get you anywhere.

So again, I get it, I understand, just maybe think a little more and change the approach and you will have a better chance of getting somewhere.

Thanks, I appreciate you writing and explaining, I have MSL almost 2 years now and using it everyday, not a single thing was implemented since I asked, all I got is low priority on todo list... where is that list? How many more plugins they will develop before reaching that low priority?
I might sound disrespectful by asking or telling, but you know I respect the time and effort they put developing all these tools for me to use. My projects uses MSL, I spend hundreds of hours developing techniques to utilize Melda plugins specially MSL, and it feels really sad that after so long nothing really changes.

[Dirk Diggler]

I've been using it since it was released.

Handling it in the DAW, yes stop all and tempo warping to start with.
If you want instant record with sync, it can't happen. That's what the sync does, it waits/quantizes till the next bar I thought. Shorter than a bar? How about change the time signature?

It seems your workflow is very different from using it as a live performance tool.
I'm not seeing a lot of me too responses, so perhaps that might be a clue.

It makes no sense for devs to spend time and effort on a single use case. I've learned to work with existing tools and learn what they can and can't do, and not expect the world to conform to my personal workflow. Some tools stay, some I work around, others drift out of usefulness for me.

It certainly never hurts to ask, the Mdevs here are very responsive. I'm all for keeping things updated.