Posts by RikBerkelder

BECOME PART OF THE COMMUNITY - Sign up here

    Hey Everyone,

    Today I wanted to use a touchscreen laptop with OnPC and a 2port node to run a very simple show. I've ran into an issue where keyboard shortcuts assigned to executor buttons seem to be behaving quite weirdly.

    Steps to reproduce:

    - open GrandMA3 OnPc 1.9.7.0 Clean Start

    - Assign Sequence 1 At Exec 101

    - Store Cue 1 thru 20 At Sequence 1

    - Set the exec 101 button function to Go+

    - Enable keyboard shortcuts

    - Press Ctrl+F1

    What happens (on my machine) is that every time i use Ctrl+F1 to Go the sequence it jumps multiple cues ahead. When i use the virtual playback buttons in the playback screen using my mouse it triggers the next cue as expected. using the DEF_GO shortcut (space) also works as expected. This behaviour also happens on other exec locations, and the XKeys. It also happens when i set the key function to GO-, <<<, >>>

    Assigning a Quickey with the DEF_GO to one of the execs and triggering that using the keyboard shortcut does work as expected.

    I have not been able to test this on another machine yet.

    Hey everyone,

    I'm trying to call macros from a layout view, but every time i touch the macro on the layout view only one step executes, then pauses. touches after that trigger one next step every time, as if the lines were set to "wait=go". All of the lines are set to follow. The macros work fine and execute all lines at once when triggered from the macro pool and form the CLI using "Call Macro 100" and "Go+ Macro 100", so it only goes wrong when triggered from the layout view.

    Edit: this only seems to happen when i call the macro in the layout view on another PC/Console in the network (i'm running my PC as master and a touchscreen laptop as touchscreen in MaNet. It worked fine and can't (easily) reproduce this after restarting MA3 on the laptop, so this might just have been a weird one-off hiccup

    Hi, I've been using MA3 OnPC with a 2portnode 2k and a MIDI controller. I'm converting the MIDI inputs into OSC for use with MA3. This setup is working great, but not all settings in the In & Out OSCData lines get saved. Name, Destination IP and Port are working just fine, but the FaderRange, Receive, Send, ReceiveCmd, SendCmd EchoInput and EchoOuput settings are reverting back to their default after each restart of the software.

    Steps to reproduce:

    - Menu > In & Out > OSC
    - New OSCData
    - Change FaderRange, Receive, etc.

    - Save showfile

    - Shutdown MA3

    - Restart MA3

    - Menu > In & Out > OSC

    - OSCData line is still there, settings listed above have reverted to default.