Відео

I would need your Chataigne and MA3 files to check.

@@stefankrumm6709 I would love for you to check, can I send them to you somewhere?

Hi, not directly, but by macros. You can trigger a macro by midi notes that - for example - consists of a line like "goto 2". That would activate cue #2 of the "selected sequence". I have such a set of macros in my normal setup to fire cues for "Start Song", "Refrain", "Solo" etc. from the main cue of a song.

@@stefankrumm6709 thanks! i will give that a try!

In MA2 war es möglich, einen Playback Executor mit einem Midi Control change zu verknüpfen. Es war wohl auch möglich, eine Sequenz auf mehre Executors zu legen, die unterschiedliche Werte haben konnten. In MA3 bestimmt die Sequenz über die Playbacks. Das heißt, wenn man eine Sequenz mehreren Fadern zuweist, gibt die Sequenz den Ton an. Die Fader bewegen sich simultan. Auch ist es nicht möglich Fader ausser den Master-Fadern einem Midi-Input zuzuweisen. Deswegen der Umweg über OSC, da geht praktisch alles. Trotzdem ist die Midi-Steuerung nicht obsolet. Man kann Sequencen, Gruppen, Views, Macros, Plugins, Worlds und vor allem alle Masterfader (Selected, Speed, Rate ....) damit steuern. Ich habe inzwischen eine Commandwing am Start und nutze trotzdem den Midi Controller über Midi um Selected Sequence, diverse Speed- und Gruppenmaster zu steuern. Ich hoffe, das hilft ein wenig. Mehr Infos und lebhafte Diskussionen ob das Sinn oder Unsinn ist, gibt es in den MA-Foren. MA hat sich halt so entschieden.

Ach ja, es gibt eine Lösung. Aber etwas umständlich. Im Midi In/Out dialog kann man ein Midi event einem der 50 Playback Master zuordnen und diesem wiederum auf einen Playback Executor legen. Im Setting der gewünschten Sequenz kann man nun unter Playback den gewünschten Playbackmaster zuweisen. Nun kann man über den Umweg über die Sequenz den Executor steuern. Folge mal den beiden links hier: help2.malighting.com/Page/grandMA3/masters_playback/en/1.9

​@@stefankrumm6709Vielen Dank für die ausführlichen Antworten! Mein Denkfehler bestand darin dass ich dachte dass MA3 onPc anfangs noch Executor per Midi ansprechen konnte, dies aber mit einer neueren Version entfernt wurde. Dass dies aber von anfang an nicht möglich war, sondern nur bei MA2, hatte ich falsch verstanden. Vielen Dank für die Hilfe 😅

Hi, Ihre Frage ist hier unter dem falschen Video gelandet. Könnten Sie sie nochmal unter dem Teil 1 der anderen Serie posten? Ich antworte Ihnen dann.

Klar, vielen Dank!​@@stefankrumm6709

In principle, I agree with you. But I'm afraid my German accent and my bad English would make the video even worse. 😀

@@stefankrumm6709 I prefer any bad english above a robot voice.

Sorry, this is not possible. You need MA hardware for output.

Hi, does page #10 already exist in your show file?

Hi, the problem is caused by the GrandMA3-Chataigne module. For some reason, the number of pages is restricted to 9. You can easily fix it by locating the "module.json" file in the plugin folder. In a text editor open the file and search for the executor entries. In the line "Page": {"type":"Integer","min":1,"max":9,"default":1}, change "9" to the number of pages you need. On a Mac, the file lives in Documents/Chataigne/modules/grandMA3-Chataigne-Module-main. cheers Stefan

excellent and thanks for the quick response wow that was fast, one more question : I can toggle my cues saved on playback executors with my midi controller however lets say if I hit store or delete than a button on my midi controller assigned to an empty executor nothing happens, I want to setup a cue, press store and then press the empty slot on my midi controller to save, is this possible?

like I assigned my apc mini to 3.416 3.417 3.418 etc and they're all blank cues i want to press store than button 1 on my physical controller and have it store on assigned executor (lets say 3.416) the page is created and i have cues on 3.301-3.310 already made

@@lightinglizard7739 Hi, I am afraid that is not possible (but I will give it a try).

If you send me your Chataigne file I could check what‘s wrong.

@@stefankrumm6709 Sadly i have the same issues. What could i do ?

@@_pasi2996 Hi, did you set a filter/remapping? See video at 3:35. If you don't have success, please mail me your Chataigne file, I will try to fix it. tutorials@stkrumm.de

@@stefankrumm6709 yes, i had the remapping in there. I didn't saved the file so i just recreated it and now it works. i don't knew what i was doing wrong before. But Thanks :D

I would need a bit more information in order to help you. Can you mail me a screenshot of the command line history to ArtOfLight@stkrumm.de ?

@@stefankrumm6709 Im unfortunately getting the same error. Did you ever figure out why?

@@stephencassidy4127 Hi, did you configure and enable midi and OSC output? A screenshot of the system messages and the command line history would be helpful.

@@stefankrumm6709 Yeah I followed the steps just lots of illegal object errors when I run the script. Thank you for uploading all this btw. The tutorials are fantastic.

If you don't need syncing also TouchOSC, please just delete the line reading "Cmd("SendOSC 3 \"/Master" .. ",f," .. val/100 .. "\"")" nearly at the end of the plugin file. Or if you need OSC output, adjust "SendOSC 3" to your OSC output channel, e.g. "SendOSC 2". Sorry for me beeing so unprecise in the plugin and video. Stefan

Hi, could you please give me some more detail? Where does the not-on/off come from? From the encoder? Could you eventually send me a log from Chataigne, so I could check what is going on. You can set the range to fit your needs. Either or, better, both, in Chataigne in the filter/remap dialog and in the module.json. I will try to set this up at the weekend and will put a link here.

@@stefankrumm6709 im using a Xtouch mini and an Akai apc mini mk2 and on both if i make an Input any button it will always send an Note on and Note off signal to Chataigne and senden both of the times a clear

@@stefankrumm6709 If i hot a Normal Pad it will always send an Note on and a note Off and on both it will send the Comand on the remap 16:16:27 CustomLoggerUI Cleared. 16:16:28 X Touch mini Note On : 11, G#0 ( pitch : 32 ), 127 16:16:28 grandMA3 Send OSC : /cmd 16:16:28 OSCModule clear 16:16:28 X Touch mini Note Off : 11, G#0 ( pitch : 32 ), 0 16:16:28 grandMA3 Send OSC : /cmd 16:16:28 OSCModule clear

@@PixelPlayslLP I will check that. Just to be sure: you mapped a button on your midid device to send a command "Clear" in Chataigne and onPC receives a double Clear? As I said, I check that here.

@@stefankrumm6709 i recieved a double clear in ma too so its like 2 times sending a Single Clear

Good news for your APC40. In contrast to other brands, MA allows usage of midi, OSC, and DMX remotes without any MA hardware connected. The nodes are only needed if you want to send out real DMX values to the world. There is another video that deals with midi to OSC mapping. I feel this is more versatile, especially if you want to control faders and encoders in onPC: ua-cam.com/video/CzmEK2NEHFw/v-deo.html

I feel MA is going away from Midi and there seems to be a change towards OSC. Perhaps a midi mapper may be a solution. I am not perfectly sure but you could try "Chataigne" where you can have several midi devices as input. I route my single midi input (X-Touch compact) via chantaigne to OSC for onPC. Should be possible to route the inputs to Chataignes midi out module towards Grandma. Never tried it. benjamin.kuperberg.fr/chataigne/en

I am afraid my answer above was some sort of wishful thinking. Sorry. Chataigne seems to need a physical device for midi out.

As far as I know you can control sequences by midi directly. If it comes to cues and sequences on executors, you will have to translate/map midi to OSC. I am doing that with the free software Chataigne. A tutorial will follow in a couple of days. benjamin.kuperberg.fr/chataigne/en