Bill-
First off, I want to say I mean no disrespect to you or your product and really appreciate your insight. I was merely sharing my experience with the device which was limited to a 3 day period through which I frantically tried to implement the client's
vision without any prior knowledge or experience with your product. The only reason I posted about it here was because I quite honestly had trouble finding people who had any sort of experience with it all. The science project comment might have been taken a
bit out of context. Given the Pi's heritage as an experimental device I was trying to imply that it is frequently employed in random areas where a computer might prove useful, I'm sorry if it offended as that was not my intent.
I received the
HDMI to
DVI adapter from the client which came as a part of a kit that was supplied with the artwork. I don't know who that company was, which was part of our confusion in finding information about the product. We also spent a decent amount of time on the phone with tech support, but she had to keep checking with another tech to help us through troubleshooting the device. It was a "let's get this working ASAP, the client's on a deadline" rush to get the device to output and interface with our lighting controller. She also supplied her own
projector, so I couldn't verify if it was an output issue from the ImageCue vs. an issue with the
projector itself. Assuming the supplied
DVI connector was approved by you all, I think we can safely blame the
projector for that one.
We use LightFactory which is very capable at handling intelligent lights and I had to write a
profile for this device. I did run into the problem with the "
snap attributes" as you said and learned that LF doesn't have a way to program that into the
fixture profile which is unfortunate. What I ended up doing was creating a
channel group for each "scene" I needed and then applying that into the appropriate cues. The
channel groups allow for
DMX entry as well as
snap to at both full or zero. Once I got that working I was able to
build the looks like the client wanted for the most part.
Where I ran into trouble was in how the media was arranged on the flash drive versus what the client's expectations were. The sample
cue list they supplied had several looks for each scene, including fades and lighting transitions. I thought I saw something about the
ETC Express, but I might've been mistaken. Again, working on a deadline with unfamiliar tech, just trying to get it running for the show. I didn't have time to figure out how to incorporate all the proper cues into each scene and they didn't all apply to how she wanted to set up the show, so I ended up cherry-picking scenes using her notes and the
cue sheet.
With your added information that seems to be where the trouble began and continued. I tried using the
fade option (can't recall which
fixture channel controls that) with some success, but I figured out that it had issues with some of the videos which also included their own fades. What ended up happening is the video would
lag behind the lights. We didn't have time to trouble shoot that issue, but I suspect it was either in when LF was "snapping" the ImageCue's channels or an issue with how the
fade on the ImageCue was interacting with some of the videos with fades built in.
My frustration there was that we typically use
QLab for media control, and with a GUI-based controller it's easier to see what the video is doing by itself, being able to rule out the lighting controller as a cause of the trouble. I couldn't remove the lighting controller from the troubleshooting chain because it was the only way to interface with the ImageCue. With the way this is setup I would've had to removed the flash drive, taken it down stairs to my computer, load the videos,
etc. Granted, if the client followed the documentation (or shared it with me initially) it would have been a different result altogether. I suspect if she supplied with the
cue sheet first and I built the show around that it woudl've work out. But, you have to understand, I knew nothing of this product and had no references beyond your website to go on. Assuming the device was struggling to render the video was not a stretch given that information at the time. I didn't have time to spend on tech support at that
point.
If I were given all the tools from the beginning with just a
bit more than 3-4 hours of lead time before the
first rehearsal, and we were using the media as the company intended I think it would have been quite a different story. The client downloaded the media she wanted to use from what she said was a dropbox account linked to her. She then put it on her own USB in the root folder, which obviously didn't work. I found the supplied USB which she didn't know about and went from there. We did have an issue with the USB drive where it would not load anything other than the default
image library, but their tech support helped us fix it by resending the files.
Reading your notes, this seems like a lot of misinformation from the client who had an idea of what she wanted for the show, but didn't read the documentation (nor supply me with any of it). I'm still in the
QLab camp at this
point, simply because that's how we've set up our rig and it works well for the typical shows we run. But I will follow this product with interest now. Thank you for sharing your insight and again, I apologize if I caused any offense.