Hello !
I have one USB RGB 16 channels controller and i have the C# Program, i wanna try to make Plug-in for Vixen can someone tell me more about creating plugin's, if i make the plug in the full board and program i will post on this page 😉
Thanks !!
Do you mean 48 channels (16 RGB - 3x channel) or 16 channels? If the latter, you may want to go with 15 or some multiple of 3.
budude wrote:Do you mean 48 channels (16 RGB - 3x channel) or 16 channels? If the latter, you may want to go with 15 or some multiple of 3.
Yeah 16x3=48 Channels the max of the board on 1 USB using PIC18F2550 and 3 TLC5940 Chips this board i was used for Country Competition of electronic but i only have program in c# that control's each RGB LED separately and source code the program looks like http://prntscr.com/5j5lfb and the output is in real time.. and here is video of the controller
The user ctmal has created a series of videos showing how to write plugins for Vixen2, and perhaps he has done the same for Vixen3 modules. Use the search feature (either the forum feature or perhaps google) to find them.
Edit: Here are the tutorial videos for Vixen2.
When i'm done with college i will try to make it 🙂
In vixen 3 we call them modules, not plugins. but its basically the same thing. This would specifically be an output controller module. One of the reasons for the name changes is because we prefer for them all to be distributed in the main package rather than having disconnected plugins floating about. This is primarily because that once its installed and used in a user's profile, it then becomes required for any of that profile to load from that point forward. So its better for them all to be distributed together in one package.
Controller modules for vixen 3 are quite a bit more complicated than vixen 2, because the controller plugin has more responsibilities in v3. But all of the v3 source is open and available on github. The exact link is in the developers menu on the majn vixen website. You can look at the existing controller modules to pattern yours from. If you need more help on v3 development start new posts in the V3 development section. Most of the devs monitor that subforum.
-- Jon Chuchla --
Sent from my iPad using Tapatalk
jchuchla wrote:In vixen 3 we call them modules, not plugins. but its basically the same thing. This would specifically be an output controller module. One of the reasons for the name changes is because we prefer for them all to be distributed in the main package rather than having disconnected plugins floating about. This is primarily because that once its installed and used in a user's profile, it then becomes required for any of that profile to load from that point forward. So its better for them all to be distributed together in one package.Controller modules for vixen 3 are quite a bit more complicated than vixen 2, because the controller plugin has more responsibilities in v3. But all of the v3 source is open and available on github. The exact link is in the developers menu on the majn vixen website. You can look at the existing controller modules to pattern yours from. If you need more help on v3 development start new posts in the V3 development section. Most of the devs monitor that subforum.
-- Jon Chuchla --
Sent from my iPad using Tapatalk
I don't know if a am able to make one of these classes http://prntscr.com/5jag6k because all this is important to work the controller ;(
Edit: I know how to do it ;))
P. Short wrote:The user ctmal has created a series of videos showing how to write plugins for Vixen2, and perhaps he has done the same for Vixen3 modules. Use the search feature (either the forum feature or perhaps google) to find them.Edit: Here are the tutorial videos for Vixen2.
Hey my program is using .NET 4.0 how to use NET 4.0 in Vixen 2.1 ?:(
