Artnet Trigger Column

[ossmac]

With the auto mapping feature being gone in Arena 6 (at least I can't find it), how do I setup a DMX shortcut to Trigger Column like was in Arena 5?

[drazkers]

When you go to DMX mapping mode a small arrow suddenly shows up beside the columns and each layer. When you select that and map to a dmx channel the value of the channel is the column. This also works in midi.

Picture attached.

[Arvol]

When you go to DMX mapping mode a small arrow suddenly shows up beside the columns and each layer. When you select that and map to a dmx channel the value of the channel is the column. This also works in midi.

Picture attached.

Just setup a client last weekend with this method, Something I really would like to stress here is to patch a "Generic LTP" fixture in your desk using "RAW DMX" values.
A lot of desk's will use a logarithmic wheel (meaning the faster you turn it, the more numbers it skips), so when you turn your wheel, you're going to go from clip 1 to clip 6 or 7, then onward to 15ish. It really sucks..... you have to be suuuuuuper slow when moving your wheel.

If you patch a dimmer channel, rather than the LTP RAW DMX, you're going to go from 0-100 in percentages (meaning, you will go from 1 to about 15 or so) your logarithmic get's even more coarse, rather than fine, when adjusting you're wheel. Where as a LTP RAW DMX uses dmx values from 0-255 ( a little more fine than coarse)

The happy middle ground I found is patching a fixture as a (you guessed it) LTP RAW DMX, and then entering in the value manually (lot's of desk's will have a button next to the wheel you are turning, press that button and enter a value) so when I enter in "3" I get clip 3, and when I enter in "55" I get clip 55 to play.
What's weird is, I can move the wheel to clip 3 (even when turning it slowly) and it will play clip 6-7... very weird, so by manually entering the value, this problem goes away.

Hope this will help save some headache in the future for you.

[ossmac]

Thanks You! That is working great.

[drazkers]

When you go to DMX mapping mode a small arrow suddenly shows up beside the columns and each layer. When you select that and map to a dmx channel the value of the channel is the column. This also works in midi.

Picture attached.

Just setup a client last weekend with this method, Something I really would like to stress here is to patch a "Generic LTP" fixture in your desk using "RAW DMX" values.
A lot of desk's will use a logarithmic wheel (meaning the faster you turn it, the more numbers it skips), so when you turn your wheel, you're going to go from clip 1 to clip 6 or 7, then onward to 15ish. It really sucks..... you have to be suuuuuuper slow when moving your wheel.

If you patch a dimmer channel, rather than the LTP RAW DMX, you're going to go from 0-100 in percentages (meaning, you will go from 1 to about 15 or so) your logarithmic get's even more coarse, rather than fine, when adjusting you're wheel. Where as a LTP RAW DMX uses dmx values from 0-255 ( a little more fine than coarse)

The happy middle ground I found is patching a fixture as a (you guessed it) LTP RAW DMX, and then entering in the value manually (lot's of desk's will have a button next to the wheel you are turning, press that button and enter a value) so when I enter in "3" I get clip 3, and when I enter in "55" I get clip 55 to play.
What's weird is, I can move the wheel to clip 3 (even when turning it slowly) and it will play clip 6-7... very weird, so by manually entering the value, this problem goes away.

Hope this will help save some headache in the future for you.

I just made a lua script that asks for the fixture number and start and end column to create the cue stack.That or just multiply by .4 in your head. I don't use the encoder for clips anyways.

[Arvol]

When you go to DMX mapping mode a small arrow suddenly shows up beside the columns and each layer. When you select that and map to a dmx channel the value of the channel is the column. This also works in midi.

Picture attached.

Just setup a client last weekend with this method, Something I really would like to stress here is to patch a "Generic LTP" fixture in your desk using "RAW DMX" values.
A lot of desk's will use a logarithmic wheel (meaning the faster you turn it, the more numbers it skips), so when you turn your wheel, you're going to go from clip 1 to clip 6 or 7, then onward to 15ish. It really sucks..... you have to be suuuuuuper slow when moving your wheel.

If you patch a dimmer channel, rather than the LTP RAW DMX, you're going to go from 0-100 in percentages (meaning, you will go from 1 to about 15 or so) your logarithmic get's even more coarse, rather than fine, when adjusting you're wheel. Where as a LTP RAW DMX uses dmx values from 0-255 ( a little more fine than coarse)

The happy middle ground I found is patching a fixture as a (you guessed it) LTP RAW DMX, and then entering in the value manually (lot's of desk's will have a button next to the wheel you are turning, press that button and enter a value) so when I enter in "3" I get clip 3, and when I enter in "55" I get clip 55 to play.
What's weird is, I can move the wheel to clip 3 (even when turning it slowly) and it will play clip 6-7... very weird, so by manually entering the value, this problem goes away.

Hope this will help save some headache in the future for you.

I just made a lua script that asks for the fixture number and start and end column to create the cue stack.That or just multiply by .4 in your head. I don't use the encoder for clips anyways.

There's some thinking out of the box for ya
I had to make this really dummy proof for this client though lol. This is a person who still prefer's 5 pin over artnet, because they don't understand artnet lol