New Open-Source Con...
 
Notifications
Clear all

New Open-Source Controller for programmers

32 Posts
12 Users
0 Reactions
15.2 K Views
Posts: 24
(@viennaxmas)
Eminent Member
Joined: 14 years ago

One thought I keep crunching in my mind for a while is to use a video stream for storing the sequence information. Using an I-frame only format. It is pretty much a bitmap sequence. Each pixel in the bitmap would relate to a channel and with 8 bit you would get 256 levels per channel...

Just looking at what an average video editor can do on a normal computer...


Reply
Posts: 2168
(@djulien)
Noble Member
Joined: 19 years ago
Viennaxmas wrote:One thought I keep crunching in my mind for a while is to use a video stream for storing the sequence information. Using an I-frame only format. It is pretty much a bitmap sequence. Each pixel in the bitmap would relate to a channel and with 8 bit you would get 256 levels per channel...

Just looking at what an average video editor can do on a normal computer...

I was wanting to write "Vixen codec", but got distracted with other projects. The idea was to wrap the Vixen output plug-in API within a simple pass-thru video codec. Then *any* video editing or playback software could be used to run the sequence, and it would just send the byte stream out to the controllers and SSRs. The Vixen codec itself could be front-ended with some simple fx code. The minimum would be to just reduce the resolution of a rectangular region of the video down to a low-res rectangle - this would be suitable for driving pixel grids, and allow them (or other props, for that matter) to be driven by rectangular "windows" of the video. Of course, there could be fancier fx such as mirroring, etc to allow more flexibility in how the pixel grids are strung.

The nice things about this approach are that it can be used to sync video to the sequence (by definition, it already is synced), and the sequence is "self contained" within the video, as you stated above.

don


Reply
Page 7 / 7
Share: