Jump to content

Klaus

Members
  • Posts

    81
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Klaus

  1. Correct. Basically, you can't sync an app (or software for that matter). "Sync" as we refer to is a hardware level process which needs a constant, clocked connection. Neither the "host" platform mobile phone nor the source, Bluetooth allow for this. Instead, the process we are looking at her e with these implementations is actually a TC jam where the timecode value is aligned at the begin of recording. On from then the jammed unit is running completely on its own internal clock speed. From a professional perspective it is pretty much like having TC but no genlock - and we all know how "good" that works with even higher profile BMD, Canon, or Sony cameras. So, draw your own conclusion for flaky-shaky sensors, encoders and engines on a mobile phone. While the same would go for the F2 and TrackE, given the record of Zoom's F8(n) and particularly even more so with Tentacle we can just asume the accuracy of F2 and TrackE good enough for the intended application. Bluetooth again actually consists not of just the radio (IEEE802.15.2) but also so called profiles. "Official" BT profiles however, as all package based netowrk protocols, are not suited for meticulously time critical transmission (otherwise we would see this a widely available feature with e.g. all various BT speakers playing in sync). Thus, TCS (and also Tentacle for that matter) have introduced their proprietary protocol to achieve frame accurate jam which is utilizing the network stack IEEE802.15.2, Bluetooth operates on. Again, without consideration of native timecode devices such as the UltrasyncBlue, overall system accuracy will also depend how time critical the global BT software stack is implemented on the "receiving" end and the app can pipeline the custom protocol. Just saying as Apple has a good record of throwing curve balls accessing the hardware directly. Just to be clear enough that it may give workable results and for sure is better than going totally without, but no matter what you do a mobile device as recording platform cannot be "synced" in a literal sense.
  2. Suggestion accepted, thank you. We surely can look into making it smaller now and I will bring that up. Still it needs to be large enough for any radio, not just SSM and surely rigid enough so it doesn't move or hit the boom, so, not sure how much we could practically shelf off. To explain the indisputable clunky design of our current offering: Quicklok is completely optional, but on a wireless boom most likely want to have it in place, and if so remove Windshield with the radio attached. This again needs to be so rigid it , while at the same time supporting whatever windshield/Mic combo you might want to use (816 with soaking Rycote anyone?) and giving it enough room to position as required. This much why the extra section AFTER the Quicklok and I don't see the product as is change too much. So, most likely we would be looking at an additional product.
  3. Quite opposite, thank you, @LarryF for putting my attention to it! I was baffled as it is the same convertor we used in the UMP II and this had better life time on the CMIT. So I checked and found there were lines shifted in the spreadsheet and 6hrs were the time it ran on the maximum allowed current draw of 10mA Again, we'll be working on a table that should be available soon. @RadoStefanov, I can surely get that on the road, meanwhile there's a video showing them side by side on SoundSummit YT channel and it is the same size as the current Lockit.
  4. We prefer under promise and over deliver than the other way.So, deliberately tested the worst case scenario with an old NON Lectro NP-50 rated at 650mAh The one supplied (oh and a USB charger cradle, too) is reasonable quality, rated 750mAh and will last longer, considerably longer if people opt for the Lectro/Panasonic batteries (which we have been finding only few people invest into on quopting). Also, acording to our experience 4.4mA @48V seems a tad on the optimistic side. But we have had other mics running for days. Again, bare with us while the run time tables are still in the works.
  5. Working on it. We had a Schoeps CMIT running for 6hrs +, so that's the short side of the spectrum.
  6. The long wait is finally over, we are happy to finally announce shipping of the UMP III has begun. https://ambient.de/en/product/ump-iii-universal-microphone-power-supply/
  7. bump https://ambient.de/en/product/ump-iii-universal-microphone-power-supply/
  8. Step after step We found most of the people we talked to that would fall into the target group of smaller teams, individual shooters, also mostly industrial/image/investigatory/documentary related projects actually do work on premiere and then FCP X. Especially Avid is comon in larger, dare I say professional productions with a larger team and such a dedicated script supervisor to take notes. Oh, and I forgot to mention our API is open and free and the logs can easily be extracted from every Nano (including all units shipped since 3 years)... as such we actually are in communication with a programmer of an asset management tool that reached out to implement this into his product and a member of our LockitTimecode user group has benn provided a sample json to create an importer for Reaper.
  9. Final Cut is definitely on our radar. We have even put that as our first stretch goal as being the second preference platform in use for the targeted user base. As soon this feature has gained enough traction we will have look at it.
  10. Hi everybody, Ambient has recently kicked off a campaign to extend the application of our trusted NanoLockit beyond the use as a timecode synchronizer. This exciting feature will allow you to read out a log file of button presses and use them as markers, cue points, you name it using an additional panel for Adobe Premiere (the platform in use for most of the productions it is targeted at). We had this spinning in our heads for quite a while and actually the reason the Nano shipped with 3 buttons and a lanyard since day one. Now that we finally found opportunity to evaluate it's usefulness it on our own productions in house there is no way for us to keep the handbrake fastened. The Kickstarter campaign we chose to promote this outside of our filter bubble basically has two pledge levels: one is just the panel (for current owners of our NanoLockit) but also a soft- and hardware bundle. The clue herein is the unit included is a regular NanoLockit, offered at 90,- EUR off our regular list price with the only differerence being the "Logger Edition" having the minijack cable swapped against a promo code for aforementioned panel. So, if your interest has been triggered on the logging feature or you just on the chance to extend your existing timecode setup on a bargain, feel free to check out our campaign on Kickstarter: https://www.kickstarter.com/projects/ambientrecording/nanolockit-logger-mark-good-and-bad-takes-while-on-set Disclaimer: the decision to go Kickstarter with this down to the core is mainly for the sake of crowdfinding rather than crowdfunding, but we strongly believe in that feature. So, albeit the pledges can only be sent out on succesful funding chances are you will see this panel as an upcoming optional addition no matter.
  11. Understood, will bring that suggestion in on the next meeting.
  12. Most of them are stocking already, QP5130 and 5150 incoming, so ready to accept orders. Depends on the construction of the cup, but yes, possibly. Agreed, I noted that as well and already talkedto our content team. what do you mean by stats? Also, while we only will carry little stock on certain QXS models and both QP, this might end up confusing if including anything aside current production lines QP S5 and QS.
  13. thanks for putting to our attention, will put our web design team on it.
  14. 34mm, all tube diameters are pretty much like on the QXS. However, this is an all new tube construction making this range much more rigid, on a level of the QP. yes, absolutely. It comes in the exact same lenghts than the QXS ppluss adding the QP5150. Yes, QS is still our premium/feature film boom, for those preferring less shells, lower diameter (30mm) and do not care about the length when collapsed. You're referring to the QAPL? Yes. Also, the new end pieces will fit the older boompoles (you'd need either to put on amini XLR, or solder the XLR direct, though)
  15. Hello everyone, some already might know from Sound Summit 2020 and have waited ever since for us to release our brand new boom pole range, the Quickpole Series 5. So, today is the day and I need to express how proud we are what our "team boom" achieved once more by going above and beyond leaving the treaded path. Building our booms to last, we understand most of you already owning an Ambient Quickpole presumably will not be in straight need for a new boom. Still, you might want to check it out: https://quickpole.ambient.de/
  16. Why would be that? If you dive inbto a TC based workflow with dual system sound, video and audio clips will be aligne dby jammed tc - the source doesn't play a role here. However, and that's the thing as per IronFilm: while SoundDevices has proven it can build good timecode generators and their units are tight on reference, sytem cameras are completely differen, so unless you run the MixPre "slaved" to the HDMI out of your camera with permanently attached cable, you won't get around an external TC sync box for it. Only this way you can asure all takes at least* starting at the same time over the day - and REALLY save on some post work. (*Disclaimer: this tc onto audio track will keep your back covered for takes up to 15 - 30 minutes, anything beyond is simply not feasible with gear without native support for external sync).
  17. Might be just a tad early to ask with the year just freshly started, if I'm allowed to say
  18. @johngoochWould 100g (including battery) @ half the size of Kortwichs sound tempting?
  19. Did you? can't find one, which address didd you use (using the web form it should be addressed corretly to support@ambient.de) Anyway, there have been made some changes along the way to best comply with the changes Lectro did when introducing their servo BIAS inputs. So, Clearly 1 & 2 are newr "servo" models, while 3 & 4 are the older hardware. Updtaing them is not really feasible as disassemble basically destroys most of the case and the pcb needs swapping - that's the prob with building products to last.
  20. Thanks! Now, since the OP has happily settled on the JB-1 I feel I may throw this in as no-plug info: ACL204 has been discontinued and replaced with the ACN-CL Lockit which brings everything known such as in a form factor comparable to the JB-1.
  21. Which basically rules out the vast majority of camera manufacturers - unless they start to consider implementing our module Nettime, not GPS but, like this?
  22. Well, the momant you sync, a 23/29 TC will slowly drift behind the continuously running real world time with a speed of - .1% roughly, which means after 1000 frames (or 42 seconds) you are already lagging 1 frame. So, say such super easy camera set to 23 (which, btw, is every Sony set to "24") comes on at 9:00 AM to for the day, and a second device fires up 10 minutes later, both units will already be 14 frames out of sync. This gets worse with every battery swap, scene rebuilt or similar. Well, one could possibly compensate for the timebase diversion of 1000ms to 1001.001001.... via PLL (what we did) and additionally try to approximate "NTSC real time" by recalculating the current lazy saturn time from 00:00 real world on reception, but if one unit has reception the other one doesn't and you just rely on this things will get hairy very rapidly. All I'm trying to say is the benefit of "not having to think about it" would not last longer than the first day you work which such a setup (if ever) until you get a phone call from post. But there's always proof to the pudding and as per @Bouke other time beases that are supossedly as accurate (NTP/network time etc.) If soemone has the ability to compare 2 timecode sources (e.g. with one of our Lockits with display on6.xx) just download a free app suhc as LTC Timecode generator for Android, launch it on 2 phones and compare the "real time" timecode on the headphone output - you will notice a considerable difference even on straight framerates. So,let me asure, we are not only in the position but we pursue this very actively. Actually we do have a software based solutionalready in the drawer but we definitely won't release anything that raises false expectations and does not live up to the quality standards that we are appreciated for just to compromise the bad reputation tc has already
  23. I had a lengthy conversation with Ari Krupnik, the guy behid "Dish" on our booth at NAB about GPS as your sole source of time and clock reference. And while he is clearly aware of the challenges and drawbacks, his system is clearly not meant for us, the pro-media people but rather the system camera filmer. Just to remind, we already offered a GPS solution since the mid 90s (funnily never sold too many of them) until we had to discontinue the ACC controller. So the idea is far from new to us. But, while GPS is a good reference to calibrate a system the idea of having this as your only set reference to rely on is not only ruled out as a majority of locations will leave you without reception, but also half of the world (read every region that shoots on 23.98/29.97) is left in the cold as GPS counts in real time (more or less, as per @Bouke) while NTSC lags behind, so there is no such ting as realtime over GPS in these regions and powering on equipment atr a different time of day will inevitably lead to a TC offset. As a result, "Dish" (at least at the time speaking) is concetped to output fixed time of day @ 24FPS, btw.
  24. That mirrors our experience witht eh Cantar - basically you're completely fine with jamming one Nano/Lockit once a day, press the green button to jam the others, and do not worry the rest of the day. If you want it all comfortable and absolute confidence, just leave the new Lockit permantently connected to your Cantar, once jamed via cable and set to master it will not only automatically c-jam all other ACN devices but constantly report the abberation (if any) to the source it was jammed from. This should be the closest to your initial request.
×
×
  • Create New...