-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using set_values #47
Comments
Found another reference where set_values seems to be working.
Im wondering, whats the best way of handling that the light actually recieves the command to shut off? await channel doesnt seem to do anything when using set_values, but if I use await asyncio.sleep(1), then the light hits the target values which were requested. I was more or less hoping everything needed would be to use channel.set_values([255,255,255,0,255,0]) and channel.set_values([0,0,0,0,0,0]) and it would do it, but then again, im not a developer |
When you create a node you specify with Awaiting an object waits for all Fades to complete. So the most easy solution would be to set a fade with maybe 0ms duration. and just call |
Hi,
Probably not an issue with the project but just wanted to check if im doing something wrong trying to set an explicite value and not a fade.
For reference, I have a PKnight Artnet4 - Cr041 (probably one of cheapest artnet controllers avaliable :D)
the fade function works as intended as shown in your example. If I on the other hand try to use the set_values function towards a device, nothing seems to happen. Changing the fade time to 0, seems to do something along the lines of what I want, it just feels wrong when there is a specific function to set the value directly.
I had a look in the issues list and found another reference of a person having issues using the set_values function. The example below does not seem to do anything.
Have I misunderstood how the set_values function should work?
The text was updated successfully, but these errors were encountered: