MIDI Feedback

[hepiyellow]

Does this module provide MIDI feedback for toggle buttons, and fader/knob amount?

If not, is it feasible?

[yastefan]

Hey,

the module does not have feedback built in. I have thought about it for a long time but have not found a satisfactory solution. Firstly, there is the problem that grandMA3 only provides feedback via the sequence number and not via the executor. This is sufficient for many things, but if you have changing sequences on the executors, you can no longer differentiate between them via OSC. The other problem I see is the reliability of sending OSC via grandMA3. I have often had problems with grandMA3 using the port exclusively, even when it is only supposed to send via the port.

If you only trigger the executors or sequences via Chataigne, you can set the midi input for the toggle buttons to toggle and simply send a midi note On to your controller when an On event occurs. This way you also get visual feedback.

Cheers
Stefan

[hepiyellow]

OSC output Connectivity

Yeah I do seem to also encounter issues with receiving MA3's OSC output. Sometimes it works. Need to investigate How MA3 bind the output port.

Feedback Solution

MA3 Side
I can written MA3 plugin, that when initialized, it goes over all Executors, and sends out an OSC message for executor's mapping:
[Object address] [page] [exec number]
e.g.
/13.13.1.6.2 page 1 exec 201

if an object has more than one executor assigned to it, it will send a list of executors, e.g
/13.13.1.6.2 page 1 exec 201 page 1 exec 202

• The plugin would also listen for changes in the executor's Object , and resend the mapping when it changes
• The plugin would also listen on new executor assignment, and send the new mapping
• The plugin would listen for deleted executor assignments, and send the relevant new config, e.g:
  /13.13.1.6.2 (Means that this object is not assigned to any executor)

Chataigne Side

We can expand the grandMA3 module (or write a new one), that will receive OSC from MA3.
If the first argument is "__EXEC_MAPPING" (This is an arbitrary unique identifier I just made up), then it means it is an exec mapping, and the following arguments are the executors. It will update it's own state, a map with ObjectAddres->ExecList

If the first argument is other, then it is a Value message. It will look up the object address in the Exec Mapping, then find all States with mappings that have a grandMA3 module output of the relevant executor. Then it will look at the input of these mappings, and send feedback to the appropriate Input "Values" (e.g. Midi Channel 1, CC1, 70%)

Do you want to do it?
I'll do the MA3 side, you the Chataigne side?

[PixelLighting]

So For the Side of Ma3 i had Something Ready to use i Added the Feedback for the Active Page becasue i found this but with the Plugin saying Page1 always No matter which site you are on

local function main()
Printf("Get Fader Value and send OSC from grandma3 to TouchOSC")
local mypage = CurrentExecPage()
Echo("Page_index: "..mypage.index.." Page_name".. mypage.name)

executor_table = {201,202,203,204,205,206,207,208,209,210,211,212,213,214,215}

function Read_Fader_Send_OSC_nn(executor_nr)


local FaderDataStructure = {}
FaderDataStructure.value = FaderValue
FaderDataStructure.token = "FaderMaster"
FaderDataStructure.faderDisabled = false

my_ex_obj_1 = GetExecutor(executor_nr)
if my_ex_obj_1 == nil then
Echo("Executor not assigned")
else



local fader_current_Value = my_ex_obj_1:GetFader(FaderDataStructure)

Echo("Exec_nr: ".. my_ex_obj_1.index .." Executor: ".. my_ex_obj_1.name .. " Value: " .. fader_current_Value)

local exact = fader_current_Value * 2550.0 / 1000
local osc_value = tonumber(string.format("%.1f", exact))


Cmd("SendOSC 3 \"/Page" ..mypage.index.. " /Fader"..executor_nr..",i," .. osc_value  .. "\"")
end

end

for i, name in ipairs(executor_table) do
Printf (name)
Read_Fader_Send_OSC_nn(name)
end


end

return main

in Chataigne Comes the Massge

/Page(Current) /Fader(FaderNr) : Value(0-255)

Maybe there would be a way to teach th Chataigne Plugin to Read this Value ?

A Nice addon Would be Some kind of loop for The Plugin Where you Entering Values Like LoopTimes or LoopDelay if You Triggering it how Often it should Read out the values and Send an OSC maybe would be an Crazy thing to add an Active FaderReadout

As an extra the Page Thing can be removed aswell and it will send ut correctly

[hepiyellow]

Hi,

I see you have release a new version with new feature.
So you are back developing this. I am happy.

I decided to make a POC for my suggested solution (Above).
I think it's better NOT to send redundant OSC from MA3 to Chataigne at fixed intervals.
Instead, to use the built in OSC output that MA3 has, which is Sequence based (not exec based).
And do the resolution (seq->exec) in Chataigne.

I am working on it.
I'll let you know when it's ready.

Is it ok If I contact you directly (via email) instead of here?

[PixelLighting]

Hello i think its a bit better to write here to change out Progress which will be visible for all the other people too if you want to Highlight an Code you need to type

'''Ruby
'''

The ruby is for coloring the Single parts of an Code its the ' Symbol

Im not directly coding i can a bit of coding like only the basics but the Codes i used are from others or i changing Existing ones with my knowledge. This Code i got from the ma3 forum and changed it a bit.

I think the exec one is better for midi Feedback because of the simpel Thing of motorized fader Feedback so if you change pages you could make on an bheringer x Touch compact a nice setup where you even have 16 instead of 8 faders. Because on the compact are 2 banks split up so if you would had 2 of These you would have 30 faders because on both Banks it has difrent CC values and Buttons values i use the bheringer xtouch mini as an executor area becauee it has 16 Buttons and 8 rotary knobs that endles spin,but have Hard value with led Level, its the exact sich as the x Button area

For sequnce mapping you just need to add an readout in chataigne because basic fader values are send with sequnce names and Adress as i understand a sequnce is 13.13.1.2.(sequnce)

Compact mini Bank A is 0 to 100 Bank b is from the middle so lets say -50 to 0 to 50

[hepiyellow]

Hi,

I am happy to say that the POC works !
I will organize it a bit and make a PR som time in the following week.

[PixelLighting]

Hi,

I am happy to say that the POC works !
I will organize it a bit and make a PR som time in the following week.

Hey
What you mean with POC ?

I think as said it makes more sense to bind a midi to a executor and not a sequnce because if the name changes or the setup you would map all New and to trigger a sequnce there are options or move the fader independat for an sequnce instead of an exec.

I use an akai apc mini mk2 and a bheringer xtouch mini at the moment in near time i will get an xtouch compact for motorized fader Feedback and the Layout is nearly the same like on consoles you have encoder fader and Buttons nearly in the same Layout so the x Touch line is nice for midi/osc+ma3. I have like already 3 ist talking i even use the Streamdeck mapöing from Fiets.

[hepiyellow]

POC is Proof Of Concept. I wrote a MA3 plugin that sends OSC messages to Chataigne, so that the grandMA3 module will know the mapping between sequences and executors. And the plugin syncs grandMA3 module whenever there is a change in the mapping.

…

On Thu, Sep 14, 2023 at 12:25 AM PixelLighting ***@***.***> wrote: Hi, I am happy to say that the POC works ! I will organize it a bit and make a PR som time in the following week. Hey What you mean with POC ? I think as said it makes more sense to bind a midi to a executor and not a sequnce because if the name changes or the setup you would map all New and to trigger a sequnce there are options or move the fader independat for an sequnce instead of an exec. I use an akai apc mini mk2 and a bheringer xtouch mini at the moment in near time i will get an xtouch compact for motorized fader Feedback and the Layout is nearly the same like on consoles you have encoder fader and Buttons nearly in the same Layout so the x Touch line is nice for midi/osc+ma3. I have like already 3 ist talking i even use the Streamdeck mapöing from Fiets. — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQLRIWL36JNOJPYC77X5XTX2IQGNANCNFSM6AAAAAAZ7JKG2E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[PixelLighting]

So you added an sequnce Feedback and an Feedback on change for exec and sequnce did i understand corectly ?

I think you Integration the one i send and added the sequnce and change notice Part am i correct ? If you send the lua Code i could check if it would work on my system to had sometimes an copy paste problem becauwe a little Syntax changed once

[hepiyellow]

@PixelLighting Hi, I am sorry I am having difficulty understanding your English.
Please read my previous explanation:
#7 (comment)

But in short:

• You can keep using the grandMA3 Chataigne module's "Move Executor Fader" command in your Chataigne mappings.
• When a fader is move in MA3, then MA3 sends an OSC message with the Sequence-Number and fader vale.
• The NEW grandMA3 Chataigne module will have a sequence-2-executor-map it uses to resolve a Sequence-Number to the Executors that it is assigned to. And update the MIDI values that are mapped to those executors.
• And MA3 Plugin will use Hooks (to follow exec changes) and Send OSC messages to the grandMA3 Chataigne module, with information that allows it to build the sequence-2-executor-map.

It sound complicated.
But I made it all work yesterday.
That was the POC (Proof Of Concept)

[PixelLighting]

Hey @hepiyellow ,

Now i understand what you want to Do but why sending an sequnce out of ma3 to map the exec, why just not use the normal get value from the executor itself this makes much more sense just like i swnd the code for the ma plugin where it just sends the Active Page Number+Values for fader mapping.

I dont want to map my sequnces i want to map my MAexec to my faderexec so i can rebuild myself the ma Layout on an midi controler. That i can save no matter the sequnce Nr or macro or speedmaster what is not an sequnce to a midi Position that will be updated if its on an fader.

A midi Feedback for light up Buttons you just ned to send midi via chataigne and then Invert so it stay light up and dimms when pressed.

[hepiyellow]

@PixelLighting

Immediate Feedback

The reason to use the built-in Sequence based OSC feedback is in order to get immediate feedback (around 10 mili-seconds).
With a Plugin that sends the current executor's value, this plugin need to send ALL the values in some fixed interval, which will probably be around 0.5 a second if you don't want to overload the system. And still it is a LOT of redundant traffic.

Mapping MIDI Controls to Executor

I wrote it several times,
My solution includes mapping MIDI controls to executors NOT to sequences !

[yastefan]

Nice to hear that the feedback feature is taking shape. In the current version, the feedback for the sequences already works very well. If you activate the OSC input and the checkbox "Learn from oscInput" in the plugin, then the plugin creates a sequence container in the values with all signals that were received. If these values are changed in Chataigne, then the plugin sends the new values directly to GrandMA. Direct mapping between the values and sequences should work without problems.

@hepiyellow I find the solution of sending an executor/sequence map from a grandMA3 plugin via OSC very elegant and think that this is the way to go :)

If you write a grandMA3 plugin which sends via OSC a JSON string with the executor/sequence map, I extend the plugin that there is also an executor container beside the sequence container. The map would then also have to contain the handle assignment, since the sequence sends the commands (MasterFader, SpeedFader, GO+, etc.) directly

[PixelLighting]

@hepiyellow can i ask for what excatly you need this extremly highspeed Feedback? In my head would be for an good midi setup not enough to have an interval refresh and a refresh when changing pages beacuse its lesser traffic Overall.

And sorry you talking for the ma side always in sequnce instead of executor that was confusing.

[hepiyellow]

Well, during the show, if the user wants to change a page, then make a quick move of one of the feeders, and then go back to the previous page. It could be annoying if there is latency when an exit page is changed. Also, I want to develop a Plugin for fader presets that when you load a preset, all the relevant feeders go into the new position. I don’t there to be any latency when loading a preset, because the user might want to immediately change one of the faders. On 2023. Sep 14., at 12:15, PixelLighting ***@***.***> wrote: @hepiyellow can i ask for what excatly you need this extremly highspeed Feedback? In my head would be for an good midi setup not enough to have an interval refresh and a refresh when changing pages beacuse its lesser traffic Overall. And sorry you talking for the ma side always in sequnce instead of executor that was confusing. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>