Hi @MeldaProduction. I jumped in to try out MSuperLooper, but unfortunately have run into a few issues.
I'm on MacOS Mojave and in both Reaper and Logic with the AU plugin, if I use the 'Sync' mode I'm finding that (1) if the DAW transport is running, the Record will start immediately and not wait until the next bar, and (2) on playback, the loops will get stuck for half a second or so and you get a buzz/glitch sound.
The other issue I've faced is that if you stop recording on the first overdub, the volume of the initial loop is much louder in volume.
In Ableton Live, the AU version also has issues. VST seems to be ok for point (1) above, but still has the increased volume problem mentioned in point (2).
MSuperLooper issues: playback loops stuck and volume issues
-
- KVRAF
- 3017 posts since 8 Jun, 2018
i didn't try the MSuperLooper that deep, but when you change oversampling, also the speed of the recorded loops, gets multiplied.
i add it to this thread. so that all the "problems" are in the same thread.
i add it to this thread. so that all the "problems" are in the same thread.
Primoridal Music: sadà\exposadà - Indusrial & Expanding Your Mind Hurts: Sound Brut
-
- KVRist
- 71 posts since 26 Nov, 2017
loving the potential of this thing but I can confirm the above super looper on logic with au and it doesnt work in sync mode and record happens immediately.
in bitwig I have had trouble with 2 things
midi mapping only sees channel one even when I am on channel two, not a big deal just noticed it.
sync and all loops same length set to off
it works for the first loop on vst3 then is just kinda random for when the record will start and stop for the other tracks
then I tried the vst 2 and it worked but then I turned on surround mode and it stopped working and started being strange on the secondary tracks like vst3 version
with out sync checked it works well.
in bitwig I have had trouble with 2 things
midi mapping only sees channel one even when I am on channel two, not a big deal just noticed it.
sync and all loops same length set to off
it works for the first loop on vst3 then is just kinda random for when the record will start and stop for the other tracks
then I tried the vst 2 and it worked but then I turned on surround mode and it stopped working and started being strange on the secondary tracks like vst3 version
with out sync checked it works well.
-
- KVRAF
- 3729 posts since 3 Nov, 2015
This is certainly a very different plugin than all other Melda plugins, I mean at the technical level. This is the only Melda plugin that will crash every time something is done with it. I have a synth in Bitwig, then I add MSuperLooper. I press the big record button and play a few notes: plugin crashed. Every single time I tried it. Out of 100+ plugins, one that crashes: it's really a not bad ratio at all but, it shows that there's something technically very different with this one.
-
pervyinthepark pervyinthepark https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=378736
- KVRer
- 9 posts since 30 Apr, 2016
SUPER hard to program through MIDI to work on a footswitch bay. Using Bitwig.
Just using the Behringer FCB1010, I want to use midi notes from that to control the buttons in the looper while I play guitar. Like a guitar looper...
Took me over an hour to get anything really. I had to make a second track to eat the midi data and send that to the guitar track in bitwig. Thats bitwigs fault. But when I finally got it to send... the next button doesn't work. I can get it to hit record when I hit a button and turn it on and off, but for Next, I hit it once, it works, then it stops. I can only do 2 loops that way!
Just using the Behringer FCB1010, I want to use midi notes from that to control the buttons in the looper while I play guitar. Like a guitar looper...
Took me over an hour to get anything really. I had to make a second track to eat the midi data and send that to the guitar track in bitwig. Thats bitwigs fault. But when I finally got it to send... the next button doesn't work. I can get it to hit record when I hit a button and turn it on and off, but for Next, I hit it once, it works, then it stops. I can only do 2 loops that way!
-
- KVRist
- Topic Starter
- 30 posts since 4 Apr, 2020
My previous experience with Melda plugins are ones that have been around for years and obviously have all bugs worked out. But still, I was surprised that in just a few quick minutes I came across multiple issues that were show stoppers.
Really hoping they invest the resources to get these bugs sorted out quickly.
Really hoping they invest the resources to get these bugs sorted out quickly.
-
- KVRAF
- 10376 posts since 2 Sep, 2003 from Surrey, UK
^^^
I trust that you guys have reported the bugs to MeldaProduction, together with the steps needed to recreate the problem(s).
https://www.meldaproduction.com/about/contact
I trust that you guys have reported the bugs to MeldaProduction, together with the steps needed to recreate the problem(s).
https://www.meldaproduction.com/about/contact
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Thanks for the info folks! Working on it!
-
- KVRer
- 1 posts since 25 May, 2019
playback and glitch issues in au plugin sync mode persist to this day (November 27/2020). don't make the mistake I did: i did not try (enough) before buying. the au plugin in sync mode is useless until the issues are fixed. save your money, i wish i had.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Please contact me via info@meldaproduction.com and get me some more info.Rovan wrote: Sat Nov 28, 2020 7:44 pm playback and glitch issues in au plugin sync mode persist to this day (November 27/2020). don't make the mistake I did: i did not try (enough) before buying. the au plugin in sync mode is useless until the issues are fixed. save your money, i wish i had.
-
- KVRian
- 915 posts since 12 Sep, 2007
FYI I don't have the same issues on Win10 VST, that behavior was fixed with updates a while back, so it's perhaps MacOS or AU issue.
Dirk
Dirk