Potential issue #1
Comments
|
Once you compile it, you'll need to use the dotnet runtime to run |
|
Amazing!
I can see that it is working, although I'm not sure what the channel map is.
So if I map it to Universe 1 and start at channel 1 does that mean that the
channel map is as follows?
PIXEL 1:
1 - Intensity
2 - Red
3 - Green
4 - Blue
Pixel 2
5 - Intensity
6 - Red
7 - Green
8 - Blue
and so on?
Thank you so much!
…On Tue, Nov 29, 2022 at 8:11 PM Kai Malcolm ***@***.***> wrote:
Once you compile it, you'll need to use the dotnet runtime to run dotnet
path/to/MagicHomeArtnet.dll --universe <universe> --channel
<first-dmx-channel>, replacing <universe> with the 0-based index of the
universe you want the program to listen on and <first-dmx-channel> with
the channel to listen on. This program has 4 channels - intensity & RGB,
this parameter designates the first one like you would do on a "real"
fixture.
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN3HLZTRIC5K2UNTY7ROFD3WK2SSTANCNFSM6AAAAAASO3N77Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Channel map is commented in the code: https://github.com/velocity23/MagicHomeArtnet/blob/master/MagicHomeArtnet/Program.cs#L8-L42 Unfortunately a limitation of the protocol is that you can't control individual pixels apart from with the presets (which are also documented above) |
|
I see that now, thank you. Understood.
That's too bad, but it could still be useful for adding a few lights around
the house to use with my more granular artnet drivers.
I assume that to control additional lights you simply run the script again
and it will ignore endpoints that are already discovered.
Thanks so much for making this!
…On Thu, Dec 1, 2022 at 2:45 AM Kai Malcolm ***@***.***> wrote:
Channel map is commented in the code:
https://github.com/velocity23/MagicHomeArtnet/blob/master/MagicHomeArtnet/Program.cs#L8-L42
Unfortunately a limitation of the protocol is that you can't control
individual pixels apart from with the presets (which are also documented
above)
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN3HLZX27PFYUED3VOATPNLWLBJRHANCNFSM6AAAAAASO3N77Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Unfortunately not... it just takes the first set of lights it can find on the network because there's no real with to differentiate between them (they don't expose an ID or similar) |
|
Well it's awesome that you made this and someday I will use it to timecode
my house!
I wonder if there is a controller that can switch between simple standalone
use with presets and full pixel control via artnet (without having it
constantly in artnet mode with a bridge running elsewhere).
…On Fri, Dec 2, 2022 at 1:16 AM Kai Malcolm ***@***.***> wrote:
Unfortunately not... it just takes the first set of lights it can find on
the network because there's no real with to differentiate between them
(they don't expose an ID or similar)
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN3HLZVMX3ASJQ4SJDGAQ2LWLGH3HANCNFSM6AAAAAASO3N77Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
What an excellent idea. This would be so useful to me if I could get it to work. I'm not a programmer at all. I compiled this in Visual Studio 2022. When I run MagicHomeArtnet.exe a CMD prompt window flashes on the desktop and vanishes. Perhaps it's an issue with my firewall or Microsoft cloud scanning it or something. I will keep an eye on the project!
The text was updated successfully, but these errors were encountered: