VAS

NEW: Ambient | NanoLockit

42 posts in this topic

Hello,

 

My question is about powering. What is the input range for DC on the USB connector and or the Lemo? If capable of receiving external power from a camera/battery how might this effect the internal battery if it is powered 95% of the time this way?

 

Is the internal Li-Ion battery replaceable in the future if it degrades?

 

Thanks

 

Stuart

Share this post


Link to post
Share on other sites

I've been thinking about adopting the ACN for some time now and these Nano's seem like they could be the ticket to sign the deal. Shug great minds think alike. What's the on set practical range of the ACN?

Thanks

Bill

Share this post


Link to post
Share on other sites

I am disappointed, that there is no scratch mic build in the nano lockit. One of the main reasons to go for a relay small timecode device is, that you do not want to put more stuff on the camera, than needed. For me it is a reason to go for a tentacle, which is very sad, because I have 2 tiny Lockit's and one ACL 204. A nano lockit would fit very good in to my timecode family. 

The thing is, that not all post pro people can handle audio timecode well. As far as I know, and pleas correct me, if I am wrong, only Avid can read Audio Timecode. If you are working with Adobe or Final Cut you need additional software. A lot of editors prefer a reference audio signal instead of audio timecode to sync it later with plural eyes. And since the post workflow is not always clear, and full of misunderstandings it is always the best, to give them both opportunities. 

Share this post


Link to post
Share on other sites
The thing is, that not all post pro people can handle audio timecode well. As far as I know, and pleas correct me, if I am wrong, only Avid can read Audio Timecode. If you are working with Adobe or Final Cut you need additional software. A lot of editors prefer a reference audio signal instead of audio timecode to sync it later with plural eyes. And since the post workflow is not always clear, and full of misunderstandings it is always the best, to give them both opportunities. 

To be fair, PluralEyes is also additional software.
There used to be an AuxTC add-pn for FinalCut, not sure if that still exists. Then there is the Tentacle software, which isn't free (unless you already have a Tentacle), because it can sync AudioTC as well as regular TC...

Share this post


Link to post
Share on other sites

Davinci Resolve also reads and can sync based on Audio-TC and is free, and because more and more projects are shot in log and/or very big files it's often used since it's one of the nicest programs to create color corrected proxies.

Share this post


Link to post
Share on other sites
2 hours ago, Herbert Verdino said:

I am disappointed, that there is no scratch mic build in the nano lockit. One of the main reasons to go for a relay small timecode device is, that you do not want to put more stuff on the camera, than needed. For me it is a reason to go for a tentacle, which is very sad, because I have 2 tiny Lockit's and one ACL 204. A nano lockit would fit very good in to my timecode family. 

Maybe a good business idea would be to sell a cable with a small scratch mic built into it...

Share this post


Link to post
Share on other sites
12 minutes ago, jhharvest said:

Maybe a good business idea would be to sell a cable with a small scratch mic built into it...

Haha! But wait...  That sounds like quite a nifty idea :-o

Share this post


Link to post
Share on other sites

I was thinking along similar lines - making a Y cable with a cheap lav at one end...

If it was built into the TCbox one could use the battery there and make it work for cameras without plug-in power too though.

Share this post


Link to post
Share on other sites

I didn't think about it at first but it looks like if they had added the proper power into the boxes they could have made sales with "NanoLockit+TinyMike combos" (simply adding a connection on the box).
I really like the Nano though. If I hadn't buy Mozegear and Tentacle these last years I would certainly have plunged. :) 

Share this post


Link to post
Share on other sites

RE: Microphones into timecode units

A month ago, we had an issue here, almost tragedy. A colleague, did a television series with DSLR's, Tentacles and Sound Devices 633. Tentacles at DSLR's, one channel TC, one channel scratch track from Tentacle microphone. The whole programm played at air (broadcast) with the sound from Tentacle microphones; only the parts without spoken dialogue. Spoken dialogue was synced. The rest was from Tentacle microphones. Of course, mistake comes from the editor, but the colleague almost fired (explained to production what was the issue).

So, thanks to Ambient, Timecode Systems, Denecke and MozeGear not putting microphone into the timecode units. A lot of misunderstanding can be happen with that combo. By the way, I am huge fan of not putting audio inputs into cameras (by camera manufacturers); only TC.

Share this post


Link to post
Share on other sites
35 minutes ago, VAS said:

RE: Microphones into timecode units

A month ago, we had an issue here, almost tragedy. A colleague, did a television series with DSLR's, Tentacles and Sound Devices 633. Tentacles at DSLR's, one channel TC, one channel scratch track from Tentacle microphone. The whole programm played at air (broadcast) with the sound from Tentacle microphones; only the parts without spoken dialogue. Spoken dialogue was synced. The rest was from Tentacle microphones. Of course, mistake comes from the editor, but the colleague almost fired (explained to production what was the issue).

So, thanks to Ambient, Timecode Systems, Denecke and MozeGear not putting microphone into the timecode units. A lot of misunderstanding can be happen with that combo. By the way, I am huge fan of not putting audio inputs into cameras (by camera manufacturers); only TC.

But with the right amount of TC bleed into the audio track, you can have 2 ways of syncing and less chance of the wrong audio making into broadcast ;- )

Share this post


Link to post
Share on other sites
1 hour ago, VAS said:

Of course, mistake comes from the editor, but the colleague almost fired (explained to production what was the issue).

So, thanks to Ambient, Timecode Systems, Denecke and MozeGear not putting microphone into the timecode units. A lot of misunderstanding can be happen with that combo. By the way, I am huge fan of not putting audio inputs into cameras (by camera manufacturers); only TC.

ouch, sounds tough. On the other hand, I wonder who gets fired if the TC is not readable and there's no scratch track on camera and the editor has to do some weeks of lip reading to synch things up...

Share this post


Link to post
Share on other sites
1 hour ago, daniel said:

But with the right amount of TC bleed into the audio track, you can have 2 ways of syncing and less chance of the wrong audio making into broadcast ;- )

That's why I am saying; not audio inputs for cameras. Only proper timecode connection.

31 minutes ago, chrismedr said:

ouch, sounds tough. On the other hand, I wonder who gets fired if the TC is not readable and there's no scratch track on camera and the editor has to do some weeks of lip reading to synch things up...

I have not understand yet, how this was passed through QC from broadcast. If there is any.

Share this post


Link to post
Share on other sites
1 hour ago, daniel said:

But with the right amount of TC bleed into the audio track, you can have 2 ways of syncing and less chance of the wrong audio making into broadcast ;- )

Oh you're such an optimist. Wait...pessimist. No, optimist.  :-)

Share this post


Link to post
Share on other sites
28 minutes ago, VAS said:

That's why I am saying; not audio inputs for cameras. Only proper timecode connection.

Yeah, but it would be easier to facilitate a DSLR workflow using TC or scratch audio if the TC box at least passed audio or had a built in mic. These days some projects go through various scales of post, including quick, on set edits for social media (where an audio scratch for sync may be more viable than a TC solution) and inclusion in to large scale projects later, where a double system without correctly time stamped media would make things very laborious. But, to be fair this is only an issue for camera's with both audio I/Ps on 1 connector. Eg the minijack on a DSLR.

CurrentIy I would settle for a something simple which would let me 'squirt' a second or 2 TC at the beginning of each take into the single channel wireless camera hop I use with my DSLR clients in lieu of a box sending TC and audio (ERX).

Share this post


Link to post
Share on other sites

I don't want a mic in my timecode gear. Why bother wasting so much time and effort for low-budget DSLR workflows. 99% of jobs I do shooting on DSLR they don't have a clue about timecode and they certainly don't want to pay extra for a slate or lockits. I either don't touch them at all or feed them a decent mix with a G3 (which works perfectly btw). 

 

Back to the nanolockit... Klaus, is there some way to ensure that your lockit setup doesn't get inadvertently hijacked by other lockits that might be in use by another nearby crew?

 

like Zaxcom uses a group code for  Zaxnet. Some kind of unique lockout password

 

 

 

Share this post


Link to post
Share on other sites
37 minutes ago, daniel said:

Yeah, but it would be easier to facilitate a DSLR workflow using TC or scratch audio if the TC box at least passed audio or had a built in mic. These days some projects go through various scales of post, including quick, on set edits for social media (where an audio scratch for sync may be more viable than a TC solution) and inclusion in to large scale projects later, where a double system without correctly time stamped media would make things very laborious. But, to be fair this is only an issue for camera's with both audio I/Ps on 1 connector. Eg the minijack on a DSLR.

CurrentIy I would settle for a something simple which would let me 'squirt' a second or 2 TC at the beginning of each take into the single channel wireless camera hop I use with my DSLR clients in lieu of a box sending TC and audio (ERX).

Maybe a second "proper" input (3.5mm). One for microphone and one for timecode. Doesn't take so much space. I am not afraid of gear fialure; but for user failure (which happens a lot today).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now