Hi everyone, I have little problem with led par, it's not mine but I must use it. This is Led Par 64 (no name, don't have any descriprion, even on buttons...) It has 24Led's, RGB 1W.
Channel 1 is BLUE
Channel 2 is GREEN
Channel 3 is RED
Channel 4 is ... from 0-125 it's dimmer, from 125-195 it's shutter and from 195-255 it's auto color mix (Fast to Slow)
Can anyone check my files and tell me what is wrong ? I was trying few times and always on my dimmer channel is everything, and I wan't only dimmer so CH4 values from 0-125 and nothing more. Shutter can be on second wheel.
My desk is Pearl Tiger.
Here are my files
http://www.fileserve.com/file/tjta7BA
Led Par, dimmer + shutter + macro on one channel
Moderator: Moderators
-
- Posts: 1089
- Joined: 02 Jul 2010, 10:29
- Location: Siegen, Germany
- Contact:
As Nic has stated, there is not much you can do. Either you try that reduce thing, but loose shutter and colour mix. Or leave it like it is, and try to avoid flashing. I believe I'd go for the reduce action.
Classic Pearls need R20 files, d4 files are not supported. However, you can use d4 files to open them in Personality Builder, and then export R20. But in particular those range adjustments usually need to be applied manually. Essentially, Classic software doesn't allow for such split/mixed ranges - as soon as a channel is assigned to a wheel, this wheel fades through the whole range. No way for functions like in Titan, e.g. virtual functions, conditions etc.
Sebastian
Classic Pearls need R20 files, d4 files are not supported. However, you can use d4 files to open them in Personality Builder, and then export R20. But in particular those range adjustments usually need to be applied manually. Essentially, Classic software doesn't allow for such split/mixed ranges - as soon as a channel is assigned to a wheel, this wheel fades through the whole range. No way for functions like in Titan, e.g. virtual functions, conditions etc.
Sebastian
Under modes, set the virtual attribute to have no channel offset and then point the 'Virtual Attribute' field of attributes that you want mastered to this attribute.
Which sounds ridiculous.
So, in a typical example:
Attributes = Dimmer, Red, Green, Blue.
Mode:
Red [channel offset = 1] [virtual attribute = Dimmer]
Green [channel offset = 2] [virtual attribute = Dimmer]
Blue [channel offset = 3] [virtual attribute = Dimmer]
Dimmer [channel offset = <leave blank>] [virtual attribute = (none)]
Virtual dimmer is only available in Titan. When exporting r20 the dimmer channel will be ignored here.
Which sounds ridiculous.
So, in a typical example:
Attributes = Dimmer, Red, Green, Blue.
Mode:
Red [channel offset = 1] [virtual attribute = Dimmer]
Green [channel offset = 2] [virtual attribute = Dimmer]
Blue [channel offset = 3] [virtual attribute = Dimmer]
Dimmer [channel offset = <leave blank>] [virtual attribute = (none)]
Virtual dimmer is only available in Titan. When exporting r20 the dimmer channel will be ignored here.
Who is online
Users browsing this forum: No registered users and 26 guests