Modular looper bug report

[Pacocreative]

#1
Hey, here’s something which looks like a bug to me.
When I try to use macro to change a group of a looper under Korpus, it seems to ignore the message.

Steps to reproduce:
1/ Setup Korpus in Data Plugins
2/ Load a few loopers into fx1/1 fx2/1
3/ Send a command InsertSendMessage fx1 1 Group 2 to put the first looper into some group
The looper does not react.

#2
Korpus looper UI bug:
In the extended properties of the modular looper, there’s a field for note ref.

   Ref 
[  60  ]

The problem is that it does not react to mouse dragging over when the mouse is on the number.
It does react when the mouse is on the sides of the rectangle
Other controls in this section seem to react properly

https://www.dropbox.com/scl/fi/uxdmceuniey9eppkk24a3/UI.jpg?rlkey=0emgypreu0u2r0q3tlb8uqtrp&dl=0

minor thing, but I thought I’ll share

[Philippe]

hi Patrick,
I cannot confirm the first one.
Could you try again please?
Or maybe there is something missing in your steps to reproduce ?
For example this macro work perfectly here :

InsertSendMessage fx1 1 Group 2
InsertSendMessage fx2 1 Group 3

WaitUserAction

InsertSendMessage fx2 1 Group 2
InsertSendMessage fx1 1 Group 3

***

I confirm the ref field issue, and it is fixed for the next one.

Thank you for the report.
Best,
Philippe

[Pacocreative]

The first one seems to be way more complex.
In a few cases the test macro worked, and my macro to put 4 loopers on 4 channels worked.
But in most cases it does not. I have no idea how to isolate it or where to look into.
No errors in the console.

[Pacocreative]

Here’s what I figured out:

InsertSendMessage fx1 1 Group 1
WaitUserAction 
InsertSendMessage fx1 1 Group 2

This always works.

But this is where it seems to break
1. Set a random group (ex 5.) via UI dropdown
2. InsertSendMessage fx1 1 Group 1 – works
3. Set a random group again (ex. 3)
4. InsertSendMessage fx1 1 Group 1 – does not work anymore, as if it remembered it’s still in group 1
5. InsertSendMessage fx1 1 Group 2 – this will work again, because we’re setting a different group than the last one via macro

The specific case I’m working on is writing a macro that will put 4 loopers into one group after they were manually assigned to different groups

Current workaround that works to set 4 loopers to group 1:

	InsertSendMessage fx1 1 Group 2
	InsertSendMessage fx2 1 Group 2
	InsertSendMessage fx3 1 Group 2
	InsertSendMessage fx4 1 Group 2

	InsertSendMessage fx1 1 Group 1
	InsertSendMessage fx2 1 Group 1
	InsertSendMessage fx3 1 Group 1
	InsertSendMessage fx4 1 Group 1

[Philippe]

Hi Paco,
Thank you so much for the perfect explanation.
Yes, you are right, there is a bug if you ask again the same group after it was manually changed.
This is fixed for the next release.
Thanks again.
Philippe

[Pacocreative]

Hey,

Here’s a bit of a behaviour discrepancy I discovered.
Korpus recording, via UI & built-in midi mapping:

Press Rec - stars recording
Press Rec and hold - cancels recording and clears the buffer

This works as expected.
However when I try to mirror this in macro scripting:

// Record seems to work better via bult-in midi control
CaseBranch "K Rec"
//    Message "Record"
	// Record current looper / group
	InsertSendMessage dt1 1 Record
	BreakCaseBranch

CaseBranch "K Rec_longpress"
//    Message "Record Clear"
	// Clear current looper / group
//	InsertSendMessage dt1 1 Record // optional, tried to fix the issue
	InsertSendMessage dt1 1 Clear
	BreakCaseBranch

It does not bring expected behaviour.
It seems that Record status (in sync mode) goes from 0 -> 2 -> 1, and while trying to clear buffer in state 2, it does not really work as expected, I can’t stop and clear the recording, while it’s in blinking mode. Also not sure if I should be stopping rec additionally on clear. I tried, but it did not seem to help.

Is there any specific routine I need to do to mirror the built-in behaviour, or we arrived at some limitations?

[Philippe]

Hi,
Ha, I forgot this case ! Thanks for reporting.

In the next release you will have the ability to add “long” as argument after record to force clear.
It will do exactly the same as if the long record is trigged by a Midi command

// This message will force clear in every situation
InsertSendMessage dt1 1 Record long

Philippe

• This reply was modified 2 weeks, 6 days ago by Philippe.

[Author]

Posts