Shaun Gish
Well-known member
- Joined
- May 31, 2011
- Messages
- 57
- Reaction score
- 0
- Points
- 0
I've been trying to trouble shoot an issue with my Dragon and a QTake Light system (specifically a Nebtek Lightning). This may ultimately be an issue with the QTake/Lightning but I have done some tests that lead me to believe it's a combination of the QTake system AND the Dragon.
Any time I try to send an HDMI signal to the QTake the video signal flickers between multiple standards and frame rates (e.g. if the camera is set to 1080p23.98 the signal that QTake sees flickers between 1080p23.98, 1080p24, 1080i29.97, etc). While the standard flickers, the image in the QTake monitor also flickers on and off. If this same signal is sent to any other devices (Pix240, Flanders Monitor, etc) the signal shows up just fine (and the standard is locked solid). Trying to route the signal from one of these devices back into the QTake has the same flicker issue (device/monitor is solid, QTake flickers).
Full disclosure - the Lightning doesn't have an HDMI input so anytime I've tried this I have used an HDMI to SDI converter (I have tried several different ones including the Pix240 cross conversion, BMD converter, Atomos, even a teradek bolt HDMI transmitter paired to an SDI receiver - all have the same issues). I have also tried using an SDI DA to re-clock the SDI signal just to see if it could clean anything non-standard in the signal.
Here's the weird part - all of the other devices I have that can kick out HDMI (Canon 5Dm3, GoPro, GH4, etc) all work with the EXACT SAME setups that I've tried. In addition to this, a couple of non-pro HDMI monitors I have that work with these devices don't like the signal coming out of the Dragon either (but my SmallHD monitor is fine with it). So - this leads me to believe that there's something non-standard being kicked out by the HDMI output of the Dragon (perhaps it's a non-standard implementation of HDCP?)
The specific use case is that I want to be able to use my Paralinx Tomahawk (which is HDMI transmitter, SDI receiver) and know that I'll be able to reliably send a signal to video village for long tracking shots or aerials.
Anyone have any similar experiences? Or any ideas on what to try? (Obviously I should try another camera body at some point - just not sure when that will be possible).
Any time I try to send an HDMI signal to the QTake the video signal flickers between multiple standards and frame rates (e.g. if the camera is set to 1080p23.98 the signal that QTake sees flickers between 1080p23.98, 1080p24, 1080i29.97, etc). While the standard flickers, the image in the QTake monitor also flickers on and off. If this same signal is sent to any other devices (Pix240, Flanders Monitor, etc) the signal shows up just fine (and the standard is locked solid). Trying to route the signal from one of these devices back into the QTake has the same flicker issue (device/monitor is solid, QTake flickers).
Full disclosure - the Lightning doesn't have an HDMI input so anytime I've tried this I have used an HDMI to SDI converter (I have tried several different ones including the Pix240 cross conversion, BMD converter, Atomos, even a teradek bolt HDMI transmitter paired to an SDI receiver - all have the same issues). I have also tried using an SDI DA to re-clock the SDI signal just to see if it could clean anything non-standard in the signal.
Here's the weird part - all of the other devices I have that can kick out HDMI (Canon 5Dm3, GoPro, GH4, etc) all work with the EXACT SAME setups that I've tried. In addition to this, a couple of non-pro HDMI monitors I have that work with these devices don't like the signal coming out of the Dragon either (but my SmallHD monitor is fine with it). So - this leads me to believe that there's something non-standard being kicked out by the HDMI output of the Dragon (perhaps it's a non-standard implementation of HDCP?)
The specific use case is that I want to be able to use my Paralinx Tomahawk (which is HDMI transmitter, SDI receiver) and know that I'll be able to reliably send a signal to video village for long tracking shots or aerials.
Anyone have any similar experiences? Or any ideas on what to try? (Obviously I should try another camera body at some point - just not sure when that will be possible).