Hippotizer 3.2

in general, it doesn't matter what parameter name you choose. it's all a question of you remembering how you called it. what matters a bit more is which category the parameter is in, as it receives a timing that way and might complicate your life when recording presets.

i don't know hippo's timecode function. is it not a regular user-set parameter, but does it need to receive specific data from the console?

in general, it doesn't matter what parameter name you choose. it's all a question of you remembering how you called it. what matters a bit more is which category the parameter is in, as it receives a timing that way and might complicate your life when recording presets.

i don't know hippo's timecode function. is it not a regular user-set parameter, but does it need to receive specific data from the console?

Here is a showfile with the Hippo 3.2 fixtures made on the console which you can merge with you current showfile to get them added to you favourites.

This is already on the list of fixtures to be made but it was too late to be added to 2.0 software so it should be added at some point in the future.

With the fixtures in this showfile there are some edits to the attributes names as they are not currently in the desk.

I only created the fixture but I haven't heard back about any major problems so I believe its ok. if not it will give you a starting point.

Here is what has changed:

Master
Invert - Spin
Warp A Select - Warp
Warp B Select - Warp 2
Warp Mix - Effect Parameter 3
Video Map Mix mode - Video Map
Mix Morph - Transition Type
Map Select A - Video Source
Map Select B - Video Source 2
Region Mapper - Visual Mode
Timecode Shift - Timeline Position

Layer
Advance Colour Enable - Colour Mix Mode
Media Pause - Generic Control
Live Input - Proj Input
De-Interlace - Opacity
Generator Level - Gen Para 1
Gen Para 1 to 8 - User 1 to 8
Text Direction - Text
All other text channels - Layer Mode 1 to 11
Audio Sync - Sync Mode
Time Code Channels - Controller 1 to 4