16.08
Reaper 6.81
Windows 10, VST3 x64 (16out version)
MSuperLooper chops the last bar off of the main loop in sync mode now.
1. Add MSuperLooper to track
2. Enable Sync. Set Default bars to off.
3. Press play on Reaper's transport
4. Press record.
5. Play 4 bars. During the 4th bar, press record again to stop recording.
6. Observe the last bar being chopped off as the loop finishes.
It works fine if you set Default Bars to a number; only a problem when Default bars is "off."
Cannot replicate in 16.07.
Incidentally, in 16.07 and before (?), there was a minor visual glitch when using MSuperLooper in Reaper. An 8 bar loop, for example (pick a number), would function properly, but the text would sometimes incorrectly display it as 9 bars. No big deal
16.08 MSuperLooper is messed up in Reaper?
-
- KVRAF
- 1791 posts since 17 Sep, 2002
You do not have the required permissions to view the files attached to this post.
-
martin-meldaproduction martin-meldaproduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=583716 - KVRist
- 273 posts since 6 Oct, 2022
Dear funky lime,
the visual minor glitch issue was resolved in 16.08, right observation.
Regarding the sync length problem, I have finally reproduced it with different sync/signature settings, different than my default. It was a rounding problem. For instance with tempo 120, signature 4/4 and SR at 48000, buffer size 128 problem is not reproducable.
Thank you for finding this, will be fixed in next version.
the visual minor glitch issue was resolved in 16.08, right observation.
Regarding the sync length problem, I have finally reproduced it with different sync/signature settings, different than my default. It was a rounding problem. For instance with tempo 120, signature 4/4 and SR at 48000, buffer size 128 problem is not reproducable.
Thank you for finding this, will be fixed in next version.
Martin
MeldaProduction
MeldaProduction
-
- KVRAF
- Topic Starter
- 1791 posts since 17 Sep, 2002
edit: I think you edited your message while i was typing, i guess you can disregard this message 
thanks!
This happens in with a blank, fresh project. 108 BPM, 4/4 time. Only two tracks: Track 1 has MSuperLooper, and Track 2 is a guitar track sending its audio to Track 1. It also happens with my larger template projects where MSuperLooper is saved; I am traveling but I can send you an RPP file in a few days (it's at least 15mb though). However, I already rolled back to 16.07 last night after posting, since that version is much more reliable for me. (i haven't tried doing a full cleanup on the uninstall, not sure if that would even help)
It happens with the default MSuperLooper/global settings, or with my own custom settings.
Arturia Minifuse 4, 48khz sample rate, 256 buffer. I've tried many BPMs, and several x/4 time signatures like 4/4, 5/4, etc.
aside: MSuperLooper sync has never worked with x/8 time signatures here (e.g. 6/8, 7/8), only x/4 ... gotta double the tempo as workaround (otherwise it thinks bar 1 lasts forever)
It happens in all instances:
Again, all these methods work perfectly for me (even when used in tandem to control the same instance) in 16.07 and earlier.
Thank you for your assistance!
thanks!This happens in with a blank, fresh project. 108 BPM, 4/4 time. Only two tracks: Track 1 has MSuperLooper, and Track 2 is a guitar track sending its audio to Track 1. It also happens with my larger template projects where MSuperLooper is saved; I am traveling but I can send you an RPP file in a few days (it's at least 15mb though). However, I already rolled back to 16.07 last night after posting, since that version is much more reliable for me. (i haven't tried doing a full cleanup on the uninstall, not sure if that would even help)
It happens with the default MSuperLooper/global settings, or with my own custom settings.
Arturia Minifuse 4, 48khz sample rate, 256 buffer. I've tried many BPMs, and several x/4 time signatures like 4/4, 5/4, etc.
aside: MSuperLooper sync has never worked with x/8 time signatures here (e.g. 6/8, 7/8), only x/4 ... gotta double the tempo as workaround (otherwise it thinks bar 1 lasts forever)
It happens in all instances:
- clicking the "Record" button via mouse
- using MIDI notes (through MSuperLooper's MIDI system) to trigger "Select and record" or "Record"
- using MIDI CC through ReaLearn (i.e. not using MSuperLooper's MIDI system) to trigger "Select and record."
Again, all these methods work perfectly for me (even when used in tandem to control the same instance) in 16.07 and earlier.
Thank you for your assistance!