![]() ![]() If you experience this, we recommend either removing some automation, or reducing the ‘Output Rate’, this can be set per Source in the Source Manager. Exceeding these limits for long periods of time may result in the console ‘buffering’ control data and slowing down the perceived speed of movement. This table is designed to provide a rough estimate of how many Sources can be simultaneously manipulated, based on the connected hardware device. This icon pack includes icons to use when building your QLab Stream Deck profile. This results in different limits for the number of Sources that can be safely moved at any one time. So if there are 16 Speakers placed on the panner, moving a single Source will result in 160 messages being transmitted every second (1 Source x 16 Speakers x 10 fps).Īs we have tested panLab Console with external hardware, we have observed that different hardware models cope with varying quantities of control data. By default, these output levels are updated 10 times a second. When a Source is moved, a new output level will be computed for each Speaker on the panner. Moving an object within panLab Console can result in a large volume of control data being sent to the connected hardware device. Innovate Audio is not affiliated with with Figure 53, LLC and macroLab has not been reviewed nor is it approved by Figure 53, LLC. Most macroLab features work with QLab 3, but compatibility is not guaranteed.įigure 53® and QLab® are registered trademarks of Figure 53, LLC. MacroLab is fully compatible with QLab version 4 or higher. The free version of the software allows for the use of 4 macros, and there is a small In App Purchase which unlocks an unlimited number of macros. As well as remembering macro configurations between app launches, macroLab includes the ability to save banks of macros to a file, which means your macros can be shared between usersĪll features included in macroLab are available completely free! The only limitation is the number of macros which can be accessed at any one time. If you ran TouchOSC on an iPad, that could act as a touch surface for firing macroLab macros If you own a Streamdeck for example, you could use its physical buttons to trigger macros. For example, set a macro to create a new MIDI Cue, preset the channel and byte 1, but define byte 2 and the cue name when the macro is fired MacroLab has many powerful functions built in, here are some examples:Īutomatically discover all QLab workspaces on the network via Bonjour, and connect with a single clickĪbility to define specific values when the macro is fired. Increment the value of MIDI byte 2 over all selected MIDI cuesĬreate a new MIDI cue in a cue list called ‘LX Cues’, with a defined device ID and cue number Select all cues which are on an infinite loop Action: Select all cues with a name containing ‘Understudy’ Select all cues which have audio routed to an output called ‘Subs’ Here are some examples of macros which could be created in macroLab: Selection: There are over 130 unique parameters built into macroLab, which you can use to build your macros. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |