Q Light Controller+

This is a very good fixture the Robin Pointe

http://www.robe.cz/fileadmin/robe/downl ... Pointe.pdf

This DJ party is fully equipped with this fixture.

Hi, is it different from the Robe Pointe product ?
https://github.com/mcallegari/qlcplus/b ... Pointe.qxf

i do not know. I took the time to watch and I'm telling you this

This definition is incomplete and does not follow the manual
Each turn.
Have you other hidden fixture?

pipolino419 wrote:This definition is incomplete and does not follow the manual
Each turn.

I admit, the Robe Pointe definition online is not that good. It's even missing one channel according to the DMX chart. I'll review it ASAP.

pipolino419 wrote:Have you other hidden fixture?

What do you mean ?

Before making a FIXTURE I verified if it does not exist in the program and on the forum. Is it done somewhere else to check?

pipolino419 wrote:Before making a FIXTURE I verified if it does not exist in the program and on the forum. Is it done somewhere else to check?

Nope. The only and official repository of fixtures is the one on GitHub: https://github.com/mcallegari/qlcplus/t ... s/fixtures
So I conclude Pointe and Robin Pointe are different products.
I'll review both definitions when I have some time.
Thanks

I'm not sure, but I suspect that Robe Pointe and Robe Robin Pointe is the same fixture.

Massimo you asked me to precisely meet the manuals. And the manual is written "Robe Lighting - Robin Pointe". Other software call "Robe - Pointe".
As you wish, but my definition of FIXTURE is good.

This fixture definition is ambiguous.
( Actually many fixture definitions in QLC+)

Can you tell me how QLC+ can associates these 2 channels together: How does QLC+ know to treat it as a single16-bit attribute?

I mean, I know that the Byte="1" tells it that it is the LSB, but how does QLC match the "Rot. gobo indexing and rotation - fine" channel with the "Rot. gobo indexing and rotation"?
Is it a name matching that looks for the "fine" string?

Thanks,
Erez (Hepi)

In fact, QLC+ currently uses 16bit only for movements (Pan/Tilt) and only in EFX in non-relative mode. It matches the channels by group and group byte.
In other words it searches for channels that both have group of "Pan" and one has group byte set to MSB/0 and one that has LSB/1.

I started to implement full support for 16-bit channels, but so far I only managed to update the definitions to explicitly add the relationship.
There's still long way to go, and most of the changes are deep in the engine, so potentially dangerous...

See https://github.com/janosvitok/qlcplus/t ... t-channels for current state.

Any update on 16-bit movement EFX? Right now I'm seeing Tilt LSB working but Pan LSB not working (stays at 0).

I posted a thread under Function Manager about it, but right now that thread is awaiting moderator approval.

Thanks!