Klaus

Not exactly. The system is designed as reference as accurate as possible and as such it does notfollow the "clock" of an external source even more so of unknown accuracy 8actually we only can pull so far from absolute reference. TRX mode is rather a single jam after which the system runs on it's own reference whcih may lead to abberation to the ajmming source depending on its absolute accuracy - witht hat being said, in the intended applications (playback/ remote roll on short takes) this is not an issue. What would be your application?

Well, not retuning exactly, it's more an instant re-clock

All true, but it also depneds wchich "ARRI" you are exactly referring to. Alexa "Classic" (which basically boils down to everything but Amira and AlexaMini - MiniLF to be seen, as this is a weird hybrid of Mini and LF (A.K.A "purchasable-65", so "Classic"): TC menu "Jam Sync" will, as Bouke said, "learn" TC and adjust internal reference - this requires a low jitter TTL TC signal and the better the signal the quicker the "learn" or "tune" (TC will blink while adjusting). As this will also drive the internal reference it is as good as having genlock as long the camera stays on. TC Menu set to "Regen" however, will regenerate the internal reference clock constantly clocked by incomming TC - so this literally is a "genlock by TC" Which means the signal must be constantly present like genlock, too. Again this may work unreliable with imperfect TC signals and put out errors. Alexa "CAP2" cameras (Amira, Mini and possibly MiniLF): TC Menu as above. Usually "Regen" does the job, due to the quality of circuitry. But as the Amira was initially designed towards the ENG market it also was planned to accept separate external sync and they merged it by giving the additional option in sytem/sensor menu to reference clock the sensor as per Wandering Ear to TC in and even Genlock (still, (by default, the sync In BNC is not connected to any electronics, btw.). Selecting TC In on top hardlocks the whole system witht he same effect as on the "Classic" range. Oh, and whoever really does need video sync: another contender of genlock spitting boxes was just announced at NAB

No, but we do support C-Link Still, there is no app to control sound devices recorder but a interface running on the webserver of MasterLockit - the Lockit does not have this webserver nor WiFi or Bluetooth, so it's not feasible. And whatever we do in the future will consider Scorpio support as well which is beyond the capabilities of that tiny box.

After more than a good 2 decades we finally decided it was time to give our trusted warhorse a small facelift and washed it a bit too hot.... find out more at https://mailchi.mp/ambient/long-live-the-lockit?e=[UNIQID] And, of course see it live in action in Las Vegas!

Hi, can't see the video but I would gather we should have a look at it here, be aware though that stock on quite some parts for the ACD301 has been depleted due to obsolescence and we cannot fix everything anymore. In that case we offer special upgrade conditions as per repair.

Ups, that's an interesting one. The fun fact is, that we saw quite some support inquiries that did so (apparently with display equipped larger Lockits) and complained about a "TC offset" between the displays. Refusing the expalnation of the obvious, that a camera primarily is a video capturing device with less priority on displaying frame accurate TC and the latency of ANY kind of display in general I had to console one team actually by proofing with a controller the TC was identical - we haven'T seen such complaints ever with the Nano. Still, we wre discussing the very isue in terms of future products. Currently we would be leaning towards an app, though. What's your take on this?

It might be a different cable that (temporarily) scared the gremlin away. I was chasing his brother once and the actual problem is in fact within the recordewr, a blown choke on the TC ground path, to be exact. If a cable is wired without the shield connected on both sides (which is the technically correct way, as it eliminates ground loop, btw.) there is no ground connection and no siognal - whiich wpould explain the working slate. If a cable has connector to shield on both ends, the chassis will take care of signal ground and tc in will work. This may also be the case if signal ground is established in any other way e.g. a common power supply for recorder and TC box, which seems plausible in case of a Pulse (hey, am I actually doing TCS support here? )

Rec roll is on a different pin of the SYNC port, so you can use both with the adequate cable. RED carries an accessory that splits up the 3 signals, TC, genlock, and roll, to 3 BNCs (http://www.red.com/store/products/3bnc-to-00-lemo-sync-cable) a well equipped rental that carries RED cameras should be able to supply. We also started to supply a special cable that uses SYNC and CTRL on RED DSMCs for TC and metadata and links remote roll trhough one BNC. Oh, and the upcoming PowerLockit will loop that signal as well. Still I wonder why ARRI takes TC input without making use out of it neither looping it through... cameras, a different world...

As you know, not with 23.98, 29.97, and 59.94 ... so, you never ever want to switch between even and odd framerates (leave alone drop and non drop) without a rejam - otherwise you'll be losing (or, actually, completely running out of) sync. This may sound a stupid thing noone would ever happen to do, but regarding that some particular camera brand will actually do 23 when set to "24".... Within "region" again you can even mix and match (cross sync) units synced to different framerates. Formerly that was done when editing on early mediacomposer systems that were only capable of 25FPS. So, (film) cameras were shooting @24 while sound was on 25 (here in Europe, that is and I can only guess it was 23 and 29 in US) Anyway, as Bouke already layed out, steam age technology... It seems to be comon sense lately that the framerate adjusts automatically on jamming from external witht hese boxes (AFAIK Tentacle has implemetned this with the SyncE and I recently read TCS with the USO as well but couldn't find the time to confirm this on ours). So one headache less. Oh, and let me help you out on this one: it's all our units - and they accept wireless sync (well they would even stay on with the Nano being charged after 10 minutes to run the rest of the day). (I'm not the shameless plugger, I'm the shameless pluggers son...)

Currently not through the LockitToolbox. However, if you jam with Time of day and set the userbits to MM.DD.YY.AD it wil acept the American Date scheme and set the RTC accordingly. Oh, and in Rome they use the EU scheme,IIRC

Backup cell is a LiPo, rated at 7.4V/800mAh

Side angled connector would stick out more prominent and might be mor susceptible to mechanical damage. Here the cable sneaks along the side. Not only can you adjust the position and/or orientation of the connector itself, you can also loosen the sleeve and "disknot" or unwind twists in the coiled cable what frequently happens on coiled cables and sometimes make it hard to collapse properly.

The idea, simply is to put the boom down to the floor on the bumper, not connector. Secondly, it also works for the straight cable option. Lastly, we also do offer a connector butt-end version. So, in the end it is all about options.

Oh, that must be a new breed then

Thanks everybody for the input. Range: well you won't find a specification even with radio mike systems as it is depending on so many parameters. 23m of what nagnila experienced is very low and usually we see doubler the range in typical environments (we had 50m at NAB showfloor and that is something) - Still, it's 2.4GHz and can be compromised by anything else in that band. The guide: Intentionally kept as instructive and compact as possible to keep the mandatory settings ready at hand but I admit it could carry more information - but then, who reads manuals? What is (also) not included is, that the Nanos automatically kick in a low noise ampplifier for better reception range when powered over USB. We will have a power adaptor from typical set level voltages to micro USB soon. The orange indicator to visualize a padded output was in fact introduced only after manufacturing and shipping the first batches and QSGs were printed - we have meanwhile included a separate sheet with revised LED blink patterns and eventually revised the whole QSG, ready for download at nanolockit.com. TC in on ring: stay tuned a little while and it will make much more sense. Bidirectional cables: we were indeed not aware that this would be an issue and will introduce the jam lock as on our bigger Lockits in an upcoming firmware. Auto power: same thing. While we still think it is a good feature and appreciated by a few productions equipped we understand it is not for everyone - but what's the LockitToolbox good for if not to introduce options and tickboxes? Again, we absolutely appreciate your feedback, feel free to post it here or on the Lockit Timecode User's group on facebook. @nagnila: It puzzles me one of your unit lost its RTC, there is a remeining capacity of a whooping 4% to keep that running. Please let it run completely empty and if the problem reoccurs apply for a service ticket, please.

@Jordan SyI know. Unfortunately, that's a hardware limitation due to the low power design. We are currently investigating all directions into improving this.

Point taken. We're still wrapping our heads around the best and most intuitive solution. So, probably it's just going to be an "Auto Power" tickbox where "On" does what it does now and "Off" requires manually starting under any condition.

It indeed is, however, and since this is a NanoLockit labelled thread, I think it is just fair to add a "displayless, one button Time of Day TC Jam sync", "automatic framerate adjustment on jam", and "jam and go by cable without menu acrobatics" with a "Yes" on Nano, oh, and a full metal aluminium enclosure that lasts a life time..... Well noted, without intention to make the Ultrasync One small - which it physically btw. is We decided against some features and pro others with simplicity of use in mind.

And here is what they do: (or me, to be exact as it is a blunt copy and paste to my email answer @thope) "the Nanos will come on automatically when connected and stay so in any condition. Very much like a mobile that’s on wouldn’t turn off after charging this is not going to change as they would otherwise shut down when powered externally while connected to camera. However, we are evaluating an option so they can be configured to power down after external power has been disconnected." Many productions use them with external power and a C-Jam Master - they just stay on camera and do not need to be taken care of in any way, not even power on/down. They come up with the camera and are ready to be synced, as soon you do, AC can do what they want - TC will always be there on spot. Have to power them down after charge is a trade off but cannot be avoided without risking they got shut off while on camera with external power and resulting TC inconsistencies. I know, you guys here are savvy enough to deal with LockitToolbox and take care of TC well enough - Still, the Nano was designed above all to also help and guide the even most inexperienced and intimidated by the daunting timecode task. Doing support and troubleshhoting on timecode and sync here at Ambient since 1994 I know that most problems originate from untis not being kept on camera or not being powered on accidentially. The ACN with C-Jam, auto framerate and autopower helps to eliminate these problems in the majority of applications.

@VAS: you beat me ;)Thanks for sharing!

That would be a Y - cable: TC and genlock DINs into 4 pin Sync socket - probably that's why not. But, you can use the 3 BNC split cable from RED.

@Derek H On from upcoming firmware 5.0 we improved immunity of ACN(s) so much, that 2 or more crews can bump into each other and all systems ar.e unaffected even when using C-Jam on the same channel. However, C-Jam Master is unavailable on the Nano due to complexity, and so a set of Nanos could theoretically be hijacked - but there's gotta be a reason to keep your Tiny s, 204s and MasterLockits, right? @Stuart: any typical USB compliant voltage between 4.8 to 5.2V. We will announce downcinvertor cables shortly. @Sound Intuition: Range, depends some what in between 60 feet through walls to 600 line of sight. Bear in mind, though, ACN doesn't rely on constant connection.

@edward chick @shug: Yes, absolutely. The Tiny (or ACL204 or MasterLockit) are perfect companions and Masters to a full horde of Nanos Also, we have done some changes to Lockit Firmware in 5.0 scheduled for release early May which makes using the Tiny as master even more easy - after powering on all you need to do is going to ACN in the menu and hit Master, you can then take the running TC or edit and satrt c-jamming right away. Another option was to one-time jam the Tiny from one of the Nanos RTCs and then enable C-Jam with TOD.

That'll be intersting to see, indeed. BT is just p2p and even more quite latency prone varying between 70-300mS , depending on hardware implemetation on both ends and limited range. Which is why we decided on 802.15.4 instead .2 and thus, no mobile device support. If they make this work reliably, hats off.