MSuperlooper, lets discuss where we are

[TVbene]

The guys from Plogue say that VST2 supports syncing tempo TO a plugin by the way. (see last paragraph:
https://www.plogue.com/bidule/help/ch03.html)
Would be the easy solution but that's probably not supported by any main stream DAW...

[AisD]

We are at the point where Melda prioritizes to push new software instead of adding very important features that people ask.
Just check how many views get Tempo and Feedback topics, I know it's really hard and time consuming to develop and fix the bugs of so many plugins. Anyone from melda could you answer me, why msuperlooper cannot get feedback? Or send Tempo to DAW?

[MeldaProduction]

Not really pushing new software, btu there's like an infinite todo list of FRs people are asking for, so there's a priority list... And honestly I only read KVR once in a few weeks and go through it quickly, so no long topics. If you have something specific, please use a contact form.

I'm not sure what you mean by that - plugins are following the DAW's tempo, not the other way around. I guess there could be some weird way to do that in some rare hosts such as Bidule, but we need to focus on the major players. I don't follow about the "feedback".

[Dirk Diggler]

I think they're talking about visual midi feedback with lights.
Which of course depends on the controller. And most use custom sysex, so there are no standards.
The only way I have found to make midi feedback work both ways is with Bomes.

[Sampleconstruct]

I have been exploring Superduperlooper recently and I'm getting erratic dropouts in almost every recording I do (un-synced, individual loop lengths), I tried all the settings but the problem persists, is this a known issue, anybody else? Also when recording a second loop on e.g. track 2 and exceeding the length of the loop in track 1 it always seems to record another full cycle of the loop in Track 1, even if I stop somewhere totally else and set an end marker (yes, I have "All Loops Same Length" deactivated). I had planned to use this live on stage but with the constant dropouts this makes no sense.

[Sampleconstruct]

I see, it's by design.

The first loop that you record is very special, it is called the "main loop" and it affects everything that happens afterwards - every loop that you then record will need to be the same length or a multiple of it. This way all tracks will always be in sync.

[Dirk Diggler]

No dropouts here, win10. Check the latency on your interface perhaps?

And your second loop issue is to be expected. You exceed the length of the master (1st track) do you expect it to erase where you missed the end loop?

[Sampleconstruct]

No dropouts here, win10. Check the latency on your interface perhaps?

And your second loop issue is to be expected. You exceed the length of the master (1st track) do you expect it to erase where you missed the end loop?

Latency in my DAW is set to ma (1024 samples), CPU meter hardly moves, that's not the problem.

Actually on stage I would just like to use this plugin as a multiple tape recorder with different FX per recorded loop, so the special role the "main loop" has is actually getting in my way here, I'll look for something else.

[tonycore]

have the same issue, although there is a "workaround" that i've discovered, i'll see if I can recall it and let you know. Vojtech has answered me with his reasons for having it the way it is. Meanwhile, I'm sending you a DM with a suggestion of another plugin that I use instead, though planning to change it all to MSL eventually.

[zerocrossing]

No dropouts here, win10. Check the latency on your interface perhaps?

And your second loop issue is to be expected. You exceed the length of the master (1st track) do you expect it to erase where you missed the end loop?

Latency in my DAW is set to ma (1024 samples), CPU meter hardly moves, that's not the problem.

Actually on stage I would just like to use this plugin as a multiple tape recorder with different FX per recorded loop, so the special role the "main loop" has is actually getting in my way here, I'll look for something else.

I’ve never had any drop outs with MSuperLooper, and I’m using a 128 sample buffer. What’s your RAM like? Are you using a lot of sample based instruments that’s using a ton of memory? Are your internal levels all good?

[Sampleconstruct]

I have 32 GB of RAM and Logic displays 2.5 GB used in Activity Monitor. It sounds like the loops are stalling from time time which makes no sense if they are recorded into RAM.

[zerocrossing]

I have 32 GB of RAM and Logic displays 2.5 GB used in Activity Monitor. It sounds like the loops are stalling from time time which makes no sense if they are recorded into RAM.

Hm, that does sound wrong. Have you submitted a bug report? I’m on Windows 10, with Bitwig’s latest as my DAW.

[Sampleconstruct]

I have 32 GB of RAM and Logic displays 2.5 GB used in Activity Monitor. It sounds like the loops are stalling from time time which makes no sense if they are recorded into RAM.

Hm, that does sound wrong. Have you submitted a bug report? I’m on Windows 10, with Bitwig’s latest as my DAW.

I'll make a video and send it to Vojtech tomorrow.

[Dirk Diggler]

Ah you might want to mention which Mac OS, newest ones seem to be problematic.

[Sampleconstruct]

Ah you might want to mention which Mac OS, newest ones seem to be problematic.

The problem occurs on two machines I tested -> Mac Pro running 10.15 (Catalina) and a Laptop Pro running 12.6.1 (Monterey).