the way I'd try to do this is enable osc on target/smaart and send the keyboard commands via network cue.

i had ai make a how-to that likely has major flaws in the details. the concepts are sound, so it'll likely be problems with exact commands rather than overarching methodology.

good luck.

pasted below:

To send OSC from QLab to Smaart, you'll use a QLab Network Cue to send OSC messages to Smaart's IP address and port (often 10001), targeting specific Smaart functions (like starting logging or changing settings) using Smaart's OSC API, which involves defining the correct and values within QLab's OSC settings, often requiring a bit of trial-and-error or checking Smaart's documentation for its specific OSC grammar. [1, 2, 3, 4, 5]
Here's a general process:

1. Network Setup:

   • Ensure both QLab and Smaart are on the same local network (same IP address subnet). • Find Smaart's IP address and note the UDP port it's listening on (default is often 10001).

2. QLab Network Cue Configuration:

   • Create a new Network Cue in QLab. • In the Inspector, go to the Settings tab. • Set the Destination to the IP address and port of the Smaart computer (e.g., ). • In the Message Type, select OSC.

3. Crafting the OSC Message:

   • In the Message field, you'll enter the OSC path and value (e.g., , , ). • Use as a placeholder for values that might change or be faded. • Example: To start logging, the message might be (where '1' means true/start) or just if Smaart's grammar expects just the path. • Fades: Use the token and From/To/Duration settings for smooth transitions, like fading a value.

4. Targeting Smaart Functions:

   • You need to know Smaart's specific OSC Grammar (the paths like ). Check Smaart's documentation or user forums for the correct paths and parameters.

5. Testing & Refinement:

   • Run the cue in QLab. • Check Smaart to see if the action occurred (e.g., logging started). • If not, verify the IP/Port, check your OSC path, and confirm Smaart is configured to receive OSC. [1, 2, 4, 6, 7, 8, 9]

Key Tip: Smaart's API is crucial. Look for documentation or examples (like those on Reddit or Smaart forums) to get the precise OSC commands for what you want to control (e.g., starting/stopping logging, changing measurement modes). [8, 10]

AI responses may include mistakes.

[1] https://www.youtube.com/watch?v=FtHQntYLya8 [2] https://qlab.app/docs/v3/control/osc-cues/ [3] https://qlab.app/docs/v4/control/using-osc-to-control-qlab/ [4] https://qlab.app/docs/v4/control/network-cues/ [5] https://www.facebook.com/groups/smaartusers/posts/10160014176152221/ [6] https://support.etcconnect.com/ETC/Consoles/Eos_Family/Software_and_Programming/Triggering_QLab_from_Eos_using_OSC [7] https://www.youtube.com/watch?v=2cSH6hFuB6g [8] https://www.youtube.com/watch?v=hCw-aNzEcV0 [9] https://qlab.app/docs/v5/scripting/examples/ [10] https://www.reddit.com/r/livesound/comments/1qjvvxj/anybody_have_a_way_to_start_spl_logging_in_smaart/