Start Channel Option

[GoogleCodeExporter]

It's occured to me that OLAOutput is currently unable to send DMX data that 
starts on a channel 
higher than 1. It might be good to have an additional inlet (and argument to 
set default) which 
specifies what DMX channel number should be asssigned to the first item in the 
list data which is 
inputted to the object. This way you could send data starting on higher channel 
numbers without 
having to send potentially hundreds of values below it.

Original issue reported on code.google.com by butler2710 on 24 Apr 2010 at 8:34

[GoogleCodeExporter]

Good idea. If I include this, can I ask for your support in testing it?

Original comment by [email protected] on 24 Apr 2010 at 5:36

• Changed state: Accepted
• Added labels: Usability

[GoogleCodeExporter]

I don't believe the job of data manipulation belongs in the olaoutput plugin. 
The underlying dmx devices have to 
send from the 0 index so there is nothing saved from the olaplugin down by 
starting at non-0.

Is there another max object you could use to offset the list data?

Original comment by nomis52 on 24 Apr 2010 at 5:43

[GoogleCodeExporter]

I can help test certainly.

Ultimately, this wouldn't affect the output. But it means that in Max, you 
don't have to attach a massive string of 
zeros at the beginning of your list. Imagine if you're dealing with only 12 
channels, but they are set starting at 
address 501. You would have to include 500 zeros in the list message to 
OLAOutput. This makes things 
unwieldy to deal with from a Max point of view.

Original comment by butler2710 on 24 Apr 2010 at 6:02

[GoogleCodeExporter]

Original comment by [email protected] on 8 May 2010 at 5:02

• Added labels: Type-Enhancement
• Removed labels: Type-Defect