Forum Replies Created
-
AuthorPosts
-
12 December 2025 at 9 h 33 min in reply to: Any update on discrepancies when using Link Metronome sync with Ableton Live? #7584
DanielAkerbergMemberHi Philippe. Now almost a year since you wrote “I promise that we will have a fix in a not so long time as it is something important…”. Any progress on this?
//
Daniel2 March 2025 at 16 h 15 min in reply to: Any update on discrepancies when using Link Metronome sync with Ableton Live? #7242
DanielAkerbergMemberPhilippe, now there has been a couple of months since last. Are there any updates on this fix? Thanks!
//
Daniel7 December 2024 at 13 h 17 min in reply to: Any update on discrepancies when using Link Metronome sync with Ableton Live? #6637
DanielAkerbergMemberHello!
I just now read the 6.1 Release notes and found this “Metronome / Looper: Fixed the link synchrinisation”. Does this mean that you have found a fix to the Ableton Link issue?
6 September 2024 at 15 h 18 min in reply to: Any update on discrepancies when using Link Metronome sync with Ableton Live? #6567
DanielAkerbergMemberOk, then I know you are still working on the issue. Thanks for the update. If possible, please keep me in the loop with the progress!
17 March 2024 at 15 h 29 min in reply to: Insert Looper actions NOT started on first beat of next bar with ActionAtNextBar #6417
DanielAkerbergMemberHi Philippe!
I am now trying the Metronome Master With Link together with Ableton Live with my latest Logelloop 6 version. When I have bpm 120 and record for 4 beats the loop should be 88200 samples long (since I am using 44100 as sample rate) but each time I record (with both Main Looper or Insert Looper) I get different lengths, either some number near 88080 OR some number near 88300. This means the loop will be slightly too short or too long and after a few rounds you can clearly hear it is no longer in sync with beat in Ableton Live. Is the sample length exactly 88200 on your computer? Thanks!
27 February 2024 at 21 h 01 min in reply to: Trim Main Looper/Insert Looper start and end point (not by selection) #6361
DanielAkerbergMemberI now found the issue. It was the Synchro = 4 setting on Insert Looper that gave the strange result above. I now set Synchro = “Free” and it works.
27 February 2024 at 17 h 06 min in reply to: Trim Main Looper/Insert Looper start and end point (not by selection) #6356
DanielAkerbergMemberHello!
I tried your proposal above and it works for all the cases where the SelectionIn = 0 and the modification is done to the SelectionOut. But as soon as I add a value in SelectionIn strange things are done that I do not understand. I think the strange thing happens during defining the selection. A have the below macro code
—–
InsertSendMessage fx1 1 SelectionIn 40000
InsertSendMessage fx1 1 SelectionOut {$Looper_fx1_rank1_current_length$}
WaitDuration 10
InsertSendMessage fx1 1 AudioMessages Copy
WaitDuration 200
InsertSendMessage fx1 1 AudioMessages Paste
—–Before Macro Length = 88000
After Macro Length = 66000 (I was expecting 48000 since we should have removed 40000 samples from the start)When I run the above macro without Copy and Paste to see what happens using SelectionIn/SelectionOut this is the values i see in the Insert Looper:
Begin: 22000
End: 110000
Length: 88000I cannot make any sense of the above values. Why is the Begin 22000 and not 40000? And should End really be able to have a value AFTER Length?
Thanks
27 February 2024 at 11 h 49 min in reply to: Trim Main Looper/Insert Looper start and end point (not by selection) #6353
DanielAkerbergMemberHello,
I was probably a bit unclear. I should not have used to TrackLoopBegin/EndAt variables since they are actually used for setting the selection of a loop, which is not what I am looking for. I am look for a way to actually modify the recorded file itself. So if the recorded file (or loop) has a length of 80000.0 samples I might want to trim it so that i ends 5000.0 samples earlier and the file (loop) has now got a length of 75000.0 samples. And from this there would be no going back of course. Is there such a function? Thanks
DanielAkerbergMemberThanks!
26 February 2024 at 10 h 51 min in reply to: Insert Looper Selection not updated by $Looper_fx1_rank1_SelectionIn_state$ #6349
DanielAkerbergMemberYes, of course. I don’t know why I suddenly forgot about this… Thanks!
DanielAkerbergMemberApparently this is connected to if the specific FX 1-5 is connected to the Inserts 1-5 as per your picture above. If for example Fx 1 is not connected to an insert this Insert Looper does not get “stuck” in a selection
DanielAkerbergMemberNow the triggering of Insert 2-5 works fine! However, I have found another strange behaviour that I cannot explain. When I have red marked/selected only “Slices” the selctions are swithcing in main looper in accordance to Slicer settings. In this case the Insert Loopers should not be affected at all by the Slicer (because no Insert 1-8 have been red marked), but what happens is that at the moment when Slicer is started all Insert Loopers get “stuck” in one selection from where the current playhead is located. This is very strange since nothing should happen to the Insert loopers. Any ideas?
DanielAkerbergMemberOk. Thanks!
20 February 2024 at 19 h 03 min in reply to: How can I retrigger Matrix Macro so new Case Branch triggers? #6318
DanielAkerbergMemberThanks!
I will look into the above.
One thing though. You write that a RepeatWhile Loop cannot be stopped from the outside. However when I trigger the below CaseBranch from a second matrix (where I set the same Global variable $rndSliceActivated$ used in the first Matrix RepeatWhile statement) then the loops selection is reset and the RepeatWhile loop in the first Matrix is stopped and I can trigger another CaseBranch. To me this means that the RepeatWhile CAN be stopped from the outside, right? Or am I misunderstanding something?
—–Second Matrix—–
CaseBranch 1
Set $rndSliceActivated$ = false
MidiSend “Launchpad MK2” 150 106 5
WaitDuration 500
TrackLoopReset trk_all
InsertSendMessage fx1 1 SelectionReset
BreakCaseBranch
——–31 January 2024 at 15 h 39 min in reply to: Loopers will not reset In and Out selection within Matrix Macro #6277
DanielAkerbergMemberSure. Below is the full Matrix Macro:
—Start—
Declare Local Once boolean $firstTime$ = true
Declare Local int $itemID$ = 0
Declare Local int $itemSize$ = 56
Declare Local int $verticalPosition$ = 1Declare Once boolean $rndSliceActivated$ = false
If { $firstTime$ }
$firstTime$ = false//Sleep 300
SendData thispatcher itemamount 2Sleep 200
SendData mainWindow setsize 463 {30 + ($itemSize$ * 1)}
SendData item 0 fontface regular
//SendData button 0 fontsize 40
SendData item 0 bgcolor 0. 0. 0. 1.;
SendData item 0 bgoncolor 0.773 0.145 0.196 1.;
SendData item 0 bordercolor 0.2 0.2 0.2 1.;
SendData item 0 borderoncolor 0.2 0.2 0.2 1.;
SendData item 0 textcolor 0.827 0.827 0.824 1.
SendData item 0 textoncolor 0.827 0.827 0.824 1.;SendData thispatcher basicdisposition
SendData MacroInitialized
MacroStop
EndIf// Which Case is it ?
Message { “Button, Dial or SVG number ” + currentCaseValueString() + ” : ” + currentCaseOptionValueFloat(0)}CaseBranch 1
Set $rndSliceActivated$ = false
MidiSend “Launchpad MK2” 150 106 5
Sleep 500
TrackLoopReset trk_all
InsertSendMessage fx1 1 <>
BreakCaseBranchCaseBranch 2
MacroStartIfNeededOnSlot 49
MidiSend “Launchpad MK2” 150 99 16
BreakCaseBranchEndCaseBranches
Sleep 500MidiSend “Launchpad MK2” 150 106 0
MidiSend “Launchpad MK2” 150 99 0
—End— -
AuthorPosts