Srgtfury

Dear Hon. Senator Mike, Fury can tell you that I had an oscilloscope on the ERX TCD and got somewhat over 1/2 of the dialed output. Thank you very much Fury

Hi Jon, FWIW, 5.2.28 has been very stable, as regards TC. Also, the in camera DC/RG4 is pleasing, for its designed target. Nevertheless, always flip PVC's, when changing any firmware, mid stream...but that Tc is a thing of beauty, at 23.98, as much as most inanimate objects can be. Thank you very much Fury

Lotta wowsas... Thank you very much Fury

This is valid, fro Zaxcom's ERX TCD to Dragon @ 23.98!! Thank you very much Fury

See Fury's post, as it relates to the successful transmission of 23.98 Tc to Dragon, with Zaxcom ERX!!! This requires, at the date of this missive, Dragon firmware 5.2.28 AND a 2 volt output or> setting on the ERX. Enjoy... Thank you very much Fury

Fury is happy to relate that he has successfully synched TC, from ERX TCD, ver 1.33 to RED Epic Dragon @ voltage output 2.0 or >, from ERX. Voltage output of 1.0 gives intermittent connection only and then only after first synching at 25 or> and stepping down. Subsequent cold boots of either or both pieces gives no joy at that voltage. All this after new Dragon Firmware 5.2.28 - no previous version was successful @ 23.98. Fury can also relate that the 2.0 volt synch maintained for, at least, several minutes, before the celebration began... Thanks Howy and Glen, from Zaxcom and Mark, et al., from RED. There is now joy in Mudville and as they say... "...Oh, somewhere in this favored land the sun is shining bright; The band is playing somewhere, and somewhere hearts are light, And somewhere men are laughing, and somewhere children shout..." For finally the Code of Time has been found out. Thank you very much Fury

Now see this: http://audiodeluxe.com/products/izotope-rx3-advanced-includes-insight Rx 3 Advanced + Insight for $749.00, if interested. Thank you very much Fury

Thanking you Hon. Senator Mike... Thanking you Marc... Well, Fury did go to RED, with a newly developed ERX firmware, by and from Howie and Glenn (can't say enough about their interest and efforts here), and RED stated that they did not want to do any further testing at this time, as they were close to a fix, on their end. FWIW, The Fury Dragon (which has to go in for servicing and is therefore not reliable as a reliable test apparatus, at this point) did NOT synch at any frame rate below 29.97 (everything higher was fine), with this new firmware attempt, from ERX's TC to Dragon. BTW, Howie is really trying here. Gotta luv his perseverance. This time he had some sort of low pass filter treatment. Stay tuned... Thank you very much Fury

It has been much more than "banter," BTW. There have been players, who start with, shall it be called-inappropriate-comments, which are thinly veiled intimidations to the umpire, that no one will publicly out. Thank you very much Fury

The League prolly has at least as much concern, regarding the Playas stepping on something else... BTW, has anyone established a Zaxcom water resistant/proof, transmitter solution that they are happy with? Thank you very much Fury

Hi Hon. Senator Mike! Copy that. Fury has it on first hand information, that RED has acknowledged the problem is on their end. Having said that, Fury has also learned that Zaxcom (Howie) has NOT acquiesced just yet. He is going to try a rather intensive effort, with low pass filtration, etc., to modify the TC output and maybe that will yield a working accommodation, for RED Dragon and 23.98. It won't be Monday, however, so stay tuned... Thank you very much Fury

Hi Tony, Fury tried that in February, using the ERX Tc, available at that time-no joy on 23.98 or 24, as well as some others. With 1.30 also failed. 1.31. is next to try. Thank you very much fury

Hi Tony! With the current ERX TC generator, there apparently cannot be less jitter than is currently in the build just released, for non integer TC. What does seem a bit perplexing, is that although other camera issues occur, as regards TC, with Zax and OTHER devices, it is only now, all these months after Dragon was released (granted only recently in large numbers) that this TC issue has taken such prominence. Most be a lotta Dragon believers... Thank you very much Fury

Update, Fury uploaded the Beta 5.2.21, to RED Dragon and the 1.30 to ERX. Although it only happened once and for 2 seconds (approx.), the TC" went green on RED's display, then, sadly back to no joy at 23.98. Fury was alternately ebullient and crestfallen... But! seems as though progress is being made. Also, it seems that the issue relates to reading the incoming signal, from those devices that don't have a native generator , for the non-integer (23.98) TC, which has a tiny bit, albeit present of jitter added, to keep the time, so to say. Stay tuned... Thank you very much Fury

Fury reporting, First, thanks very, very, much too Glenn, for working on this accommodation, for the RED Dragon's issue. Way above and beyond. Using build 1.30, with ERX's TC out, still no joy @ 23.98, but all Green at 24 & >. Walking the code up and down, after synch, still no joy. Glenn is aware and taking another look...stay tuned. Thank you very much Fury

Well, Does anyone have a 100% reproducible method of connecting Tc at 23.98 or 24, from Nomad and/or ERX to any RED Dragon camera, using only those components and appropriate cabling ? If so, please list the method. Thank you very much Fury

This is oddly somewhat pertinent, but Fury believes that he has posted on this Epic Vs. Dragon TC difference, reviewed below, somewhere ion this forum. Several months ago, when Fury first reported this and was at RED Irvine, with a Dragon build 5.X.X, there was an EPIC X handy, with build 5.X.X. TC , from ERX failed on both. Fury suggested rolling back firmware, on the EPIC X first to an earlier 5.X.X, which gave no joy at <25 FPS. Then the 4.X.X was tried, after some research and joy, which persisted (synch 23.98 & 24), as sequential firmware was loaded on the EPIC X , up to the then current 5.X.X, that had previously failed. Fury was rabidly salivating, that the same process would likely flash something onto the Dragon, in moments and there would be joy. But alas, there was no joy in Mudville that day, for the Mighty Dragon had begun it's sneer with 5.X.X and 4.X.X, was but an anachronistic footnote, to Dragon . Still, hope springs eternal, in the human breast, and anecdotal successes, with, now, many other scenarios, lifts the dark melancholy of unrealized expectations and ...sound reasoning, otherwise dashed. Let's see what Glenn and RED come up with, waddaya say? Thank you very much Fury

Hi Justin, Fury remembers you... Actually Epic Dragon does have trouble with some Ambient boxes and other devices as well. To be sure, ERX and Nomad directly are within SMPTE spec. See post # 29 above. Again, it is VERY accommodating of Zaxcom to address this, in IF'sHO. Thank you very much Fury

Exactly what Fury said...No? What Zaxcom is doing is an accommodation, for RED Dragon owners, because of a RED Dragon related issue, which has been acknowledged, for many months. The particulars are now apparently quite well known and look for RED to produce a long term fix, whilst the Zaxcom accommodation hopefully allows a proprietary fix, as it were... Thank you very much Fury Thank you very much Fury

Hi Tony, Fury would look at Zaxcom coming to aid first. Howie has the matter, in sharp focus and something MAY be provided as early as this coming Monday, from Zaxcom that will obviate this vexation... You should have rented Fury's Carbon Fiber Dragon, BTW;-) Thank you very much Fury

Hello Dear Friends, Well, Great news! Fury finally got RED's head engineer and Zaxcom talking directly. Glenn, from Zaxcom, who has always been , as we all know,overly helpful, for any Zaxcom related questions, has confirmed to me that RED acknowledges that the issue is in RED's reader and is being addressed. Jitter, BTW, is not a player here and Zaxcom does not send it on all rates, in any case. The problem seems to be that the transitions are, while within SMPTE specs, not close enough, for the RED reader, as it currently exists, to reliably read them. That is a reason that we see anecdotal reports, of success, as one MAXX user described, in particular. OTOH, Fury did not ask Glen if the MAXX might be sending a slightly different output, but the Nomad to Dragon problem does seem quite reproducible. The fix, for this overall problem, including other TC devices outputs, to Dragon, is what RED is going to provide, as the RED reader is simply not able to reliably read the transitions, at this point. Having said that, Zaxcom is also trying to help out and is looking at changing their output signal, to better match the current Dragon TC reader. Let's see who wins the race. As Fury posted here and elsewhere, the 23.98 AND 24 TC's are have not been accepted, by Dragon, from Nomad or ERX, in nearly every case. Fury has been told that there has been some success, but sporadic and with sudden dropouts, with synching at 25 or> and walking down to 23.98, within the extended menu of the ERX, in particular, but Fury's attempts to do this have always failed, irrespective of voltage output settings or initial synch rate. Thanking you very much Fury

Hi Marc, Fury has called RED and been there several times, regarding the issue at hand. To be sure, this is not a voltage issue, as oscilloscope analysis of voltage outputs, from Nomad, ERX and sync able Lockit boxes are essentially identical, within the same output range-some less and some more, from ERX, of course. The threshold voltage, for synch is achieved and no joy., from ERX/Nomad The lead tech at RED pronounced it a hardware issue, at last check a week ago, but no resolution, from RED quite yet. Thank you very much Fury

Hello Marc, bwf, dear friends & Hon. Senator Mike! Fury has spent a fair amount of time, with RED tech and the determination is that the is a DRAGON hardware issue. To be sure, it is, at once, vexing and perplexing, to all. The above workarounds , while meritorious, are not facile enough, for routine field applications. Fury has been informed, by RED tech, that they continue to work on this issue, which admittedly has taken longer than all had hoped... In short, it depends... Fury shall report back, here, if new developments warrant. Thank you very much Fury

Hi Ryan! That would have been Fury. The issue, as protracted discussions with RED tech have revealed, is with the Dragon hardware, as regards 23.98, from several devices to Dragon (newly buildt or upgraded). Dragon does take TC, for example, at 25, 25.97 and from 23.98 via Ambient Lockit. Now the rollback firmware tests on Epic X, that were effective, on one occasion, involved the earliest 4.X camera firmware and then sequential upgrade to then current (three weeks ago or so) Epic X firmware. RED still working on this and they do realize that it is an important issue to address. Alternatively, has anyone, with either the EpicX or Dragon TC issue, comfortably used alternate TC (25, 25.97)and then ,manipulated the synched files in post? Thanking you very much Fury

There must be some software issue, wrt the Dragon versions, as none of the versions available allowed the ERX TC to pass. Took two Epics out and wouldn't take TC either (they were on 5.1.38). Fury suggested roll back to a 4.X version (only available for EPIC X)...TC passes. Upgrading EPIC X's to all the 5 versions thence allows TC to pass on those Epics. No joy on Dragon however. Nothing coming across from the 4 pin lemo (pin 3 hot). In any case, had already tried the 2 volt settings-no responses, excepting the 4.X flash, as noted above. After the Epic X's accepted time code, 0.4 also worked fine... Now, the oscilloscope did show; less than 0.4 volts out, when ERX was a set to 0.4, approx. o.5 volts, when set to 1.0 volts and 1.0 volts, when set to 2.0 volts. Mind you that was a fairly robust Motorola scope and repeated several times, after reboots. Some debugging next. Would really be helpful, if anyone can document time code from Zaxcom to Dragon successfully. Thanking you very much Fury