Re: NEW - PropController Project
Two more for the pile:
I have some older ArtNet code that I believe might still work but defiantly needs optimization.
I would also like to get the sACN code into its own object, the reason is so you can swap between network protocols by just changing objects (IE sACN to Artnet). At present part of the sACN code is in the parent object.
Re: NEW - PropController Project
Update: I've created an "unreleased" folder within drivers and posted some new code. This contains code that either needs testing or needs work. Once we have confidence that its working we can move it out of there.
New code includes ArtNet, GE Color Effects, Channel Driver /w some dimmer curve code. BAM and Renard are also in there because they both need testing and tweaking.
I've also added two enhancement requests under issues on the project site in regard to the Pixel drivers. I'm not sure if or how the rest of the info I posted should be captured on the project site. Wiki??
Also if you want to be added as a Project committer just PM your request to me.
Re: NEW - PropController Project
I'm going through right now rebuilding some of the E1.31 to DMX to suit my needs, adding a few features, taking a few out as i don't see them necessary.
Do you think we should create a template file for projects. It seems like the controller is mostly doing a Input, Process, Output (typical to computers huh?) which could be laid out. I'll put some stuff up in a bit to show what i'm talking about.
The channel patching feature you talked about is probably quite simple. Have a recieved buffer, a patch method, and an output buffer, each iteration of the loop, the recieved data goes in the first buffer, the patch moves the data around, and the output buffer is used by the output plugins.
Josh
Re: NEW - PropController Project
chilloutdocdoc wrote:
The channel patching feature you talked about is probably quite simple. Have a recieved buffer, a patch method, and an output buffer, each iteration of the loop, the recieved data goes in the first buffer, the patch moves the data around, and the output buffer is used by the output plugins.
It is easy the hard part is the configuration of the patch when there is no UI. I have patching code, just no way to configure it.
Re: NEW - PropController Project
DynamoBen wrote:Two more for the pile:I have some older ArtNet code that I believe might still work but defiantly needs optimization.
I would also like to get the sACN code into its own object, the reason is so you can swap between network protocols by just changing objects (IE sACN to Artnet). At present part of the sACN code is in the parent object.
When you say move the sACN code into it's own object, do you mean just copy the code over, or put it in a seperate cog then the "master"
Right now my ideal configuration would be
0: Master
1: Serial Configuration (calls functions in master)
2: sACN or Art-Net
3: Output1
4: Output2
5: Output3
6: Output4
7: Output5
Does this follow what you were thinking for a pretty basic "starting point"?
