autom4tic

for all those that use Devices, I've a proposal for the next beta...

HOME position (that come from the Device Command) will never be recorded, neither as a DLink nor as in Sample or Chase.

why:
when you ask for HOME it's in general that you want a device to be clean in order to record a Palette, and you don't especially want the whole HOME stuff to be recorded in the palette.
moreover when sampling, you won't want the whole HOME stuff to be recorded within the Sample

in case of specific wanted HOME to be recorded, I can create a palette 0 (as HOME) that can be register in DLinks

your thoughts are more than welcome.

++

So what happens?

Call HOME.
Change some parameter.
Record DLinks: only changes will be recorded.

Call HOME.
Change nothing.
Record DLink: nothing will be recorded, device stays as before.

I agree!

Moreover it will be useful, in DLink editor windows, to select a device and to remove it.
Or to fix a DLink in a single step for a Device with 0 intensity. To fix an entire sequence could be catastrophic.

Thanks,

Carlo.

hey Carlo,
thanx for participating...

Call HOME.
Change some parameter.
Record DLinks: only changes will be recorded.

exact

Call HOME.
Change nothing.
Record DLink: nothing will be recorded, device stays as before.

nope,
device will go back to his previous state recorded in some DLink before.
are you agree with that?

if you use FORCE DLink, Home position will be recorded in the DLink

if you really want to use HOME for something, I've forced creation of palette 0 as HOME

Moreover it will be useful, in DLink editor windows, to select a device and to remove it.

in the DLink editor, use the dataBaseButton- for this purpose
enter the number of your device and hit the button


++

sl1200mk2 écrit:

Call HOME.
Change nothing.
Record DLink: nothing will be recorded, device stays as before.

nope,
device will go back to his previous state recorded in some DLink before.
are you agree with that?

I do.

if you use FORCE DLink, Home position will be recorded in the DLink

if you really want to use HOME for something, I've forced creation of palette 0 as HOME

That's fine for me.

Moreover it will be useful, in DLink editor windows, to select a device and to remove it.

in the DLink editor, use the dataBaseButton- for this purpose
enter the number of your device and hit the button


++

Good.

Thanks,

Carlo.

Hallo Nicolas,

some side note.

I think it could be good to reset (to Home) only selected parameters: if I'm in Focus window and I press, for example, cmd+Click the HOME applies to focus but everything else stay still.

I learned that if I click on the name of a parameter I can digit the value for every device selected (I can also use mouse to edit everyone). But If I have an attribute with coarse and fine (e.g. PAN) only coarse has been edit while "fine" becomes "0".

Last note: I attach the personality for Martins MAC Quantum Profile (basic). As said some days ago it has a 16bit gobo rotation parameter.
I prepared it with Attribute 8-Rotation and its definitions (converting 16bit in 8 bit) and then Attribute 9 as FINE. It Seems to work. The problem is that I can't see Parameter Fine in Effect Window. Why?

Thanks a lot again (forever and ever),

Carlo.

ciao,

I think it could be good to reset (to Home) only selected parameters: if I'm in Focus window and I press, for example, cmd+Click the HOME applies to focus but everything else stay still.

if you enter 0 (zero) in the command line and click on an attribut button, you can HOME this attribut

I learned that if I click on the name of a parameter I can digit the value for every device selected (I can also use mouse to edit everyone). But If I have an attribute with coarse and fine (e.g. PAN) only coarse has been edit while "fine" becomes "0.

if you mean using '@_level' shortcut to set a value, yes it's dedicated to the coarse

I prepared it with Attribute 8-Rotation and its definitions (converting 16bit in 8 bit) and then Attribute 9 as FINE. It Seems to work. The problem is that I can't see Parameter Fine in Effect Window. Why?

it's because until I found a good algorythm for handling graphical scrolling on Fine parameter, I've decided to not display FINE (for some parameters).
you'll find them back soon

Thanks a lot again (forever and ever),

u're welcome

++