Bouke

Let me emphasize the fact that I don't know the Zaxcom workflow! I'm not going to milk Peter for the full amount on this one, but if I make changes, they better count and not clutter up the app as it is. Funny enough, I had a question just this week about AAC / MP3 output. It can do both, (and more), but some of you seem to be afraid of AAC, as clients demand Mp3. IMHO those clients are ignorant, but, well, they are clients... Feel free to spill comments, I'm open to suggestions! Bouke

You are right. It can, but compared to my software, it is 'crippled' (Like any other NLE.)

'When the battery has cooled, it actually delivers more electricity than was used to charge it.' This is totally impossible by our laws of nature. It 'should' read something: 'When the battery has cooled, it actually delivers more electricity than THE AMOUNT OF ELECTRICITY that was used to charge it.' The waste energy is added of course. Still a clever idea.

eeh, 12 volt times 5 amps = 60 watt? If in doubt, take a heavier one. (More amps, NOT higher voltage than indicated on the device.) Can't hurt. Just make sure you have the right fuse if needed. No clue what a 'bds' is, but any device has an indication of power consumption. (And do note that at 5 amps the loss in the cable will cause a voltage drop, so don't make the cable too long, or use a thick one.)

Hey Dalton, Something might be lost in translation, but I fear you're totally clueless about the issues at hand.

This is an understatement for 'some' of us. (Definitely for me.) Some of us (again, defintely me) already have issues with that, and getting shit on top of that does not help. Saying 'NO' to some requests / clients is the healthy thing to do, but that's not always (with understatement) easy, especially since most 'bad' things tend to be on a slope, where you'll find yourself in a situation that the issue is gallons over the last drop. I've learned this a long time ago. (I'm over 30 years in the industry.) But, I still struggle with it almost every day, even knowing exactly what is going on. Saying 'No' will increase your reputation, as it shows you won't do stuff that is 'not up to standard', but at the end of the month there are bills to pay. I have no answer, except that if your mental health goes down the drain you won't be able to do anything of value for anyone, especially yourself. hth, Bouke

And I'm not 🙂

Hmm. This is 'Auto Sequence' style. Nice eye candy, but I fail to see how this helps you. (And this looks like a demo image, not 'real world' production.) On a 10 hour shooting day, you don't have an easy / fast overview on what can / could be wrong. (And it's hard to know what 'is' wrong. Cam 2 could be missing sound on a clip, where that was perfectly OK since the sound guy took a leak and the DP decided to shoot a funny puking cat as wild take.) Then, in my experience as editor, start / stop times of sound / video are NEVER close. (Extreme example, I've worked with a sound guy who hit REC in the morning, and STOP when he was back in the van, while the cam had close to 100 shots.) I totally understand your wish to have 'some' feedback, but this is not 'it' IMHO. (Mind you, I've been an editor for over 30 years.) So, let's make a list with stuff to check and raise hell if a condition is not met: (And yes, I know Tentacle is reading this as well and steal the ideas (again).) (video) clips > X minutes MUST have matching sound. (It's probably an interview / presentation) Sound MUST cover at least X percent of video, if present (Or you get double warnings) ???? Thinking of it, the old version of LTC_convert had an option 'move no match BWF to subfolder', so the editor had a pool of 'wild / ambient' tracks. Perhaps I should bring that back.

You are missing a few essentials: The 'sync word', defines the END of a frame. Thus, you only know the TC AFTER it has passed. You can state that the sync word defines the beginning of a new frame, but that only works on continuous TC, and you still need to compensate for the duration for the sync word. Next, there is no checksum or whatever in the bits, so you need to do a bit of error checking and freewheel a couple of frames if there is a glitch. This all takes time that has to be compensated for to get a proper 'sync' display. (Let alone the latency in the display, and in the audio device.) That can all be done in (cheap) hardware, but it's not as easy as in a normal computer environment, and will only pay off on large volume production.

Just ask, and I'll alter it to have something like that! Currently, the lists do give you feedback though. It's not hard to make an overview of what is happening / missing / strange. I don't know how Tentacle software works, so I'm not sure what you would like to see.

my LTC convert lets you patch and output: https://www.videotoolshed.com/product/ltc-convert-auxtc/ It does not yet do XDcam, but I could add that. Well, I'm currently busy making a new version of BWF merge (that will replace the old, since that seems unreliable on some systems, and is just 32 bits). So far it can: split Poly to Mono (thus extract one channel from stereo is possible). merge Mono to Poly (where start does not have to be the same, so you can have multiple recorders that are jammed but don't have the same start time) Offset tracks with latency (Thus, if you have wired and radio mixed, you can get them in perfect sync again.) Work on files > 4 gig (RF64 capable, unlike Wave Agent) Still contemplating what more features I should add, but the above works already. Let me know if you want to toy with it.

Festool makes great tools (I have a saw) but is highly overpriced. The 'systainers' / packaging tools they use are not manufactured by them, but 'generic'. I saw exactly the same boxes in use by nurses in the hospital. So, perhaps some more googling will get you a better deal if you want to pursue this.

It should be possible, and perhaps a good time to finally build a Linux box and toy around. What is the screen resolution you want to use? Touchscreen? First things first, did any of you test it already? (The latest version, I forgot to put an 'about' in the menu, but if you see the option 16/24 bits, it's current.) If it does not sound good, what's the point? (Do test with / without the meters turn on, the meters work in between the chunks, in theory, that could introduce ticks every 10 msec.)

Hi Daniel, Yep! If you have time, please toy with it and let me know your findings!

If this thread is revisited in another 5 years, I've made a small simple (lossless, what goes in goes out) audio delay that can delay up to 10 seconds, in steps of 10 msecs. (Using any soundcard present.) It's free, and even brings it's own VU / Peak meters. Mac only at the moment, but I'll make a Win version when my Win box is powered up again. Download AudioDelay here

Just for fun I started to code a delay. (Well, that's done, now making an interface...) Any source in / any device out, adjustable delay as long as you want. It' quite easy to make, just store chunks of sound in a buffer, and read from that buffer. Only drawback, if you change the delay, it will skip parts of sound without any dissolve, in chunks of 1/100 of a second. No clue how that will sound yet. And yes, you need a computer with sound card, but it hardly will take resources, since it does not do anything except eating a tiny bit of memory to store the sound.

Can't you post a 10 sec vid of a funny puking cat? That would be WAY more interesting.

I know, wrong group, but nevertheless... I'm currently working on a video recorder for a MoCap studio, but perhaps it could be handy for you guys as well. At the moment it can: Record video from up to 8 Blackmagick devices (A cheap BM Mini Recorder is good enough for rock 'n roll.) Take sound from another device and marry it to the video on the fly. (So no need for SDI audio embedders.) Take LTC from another device or UDP for accurate TC. Apply some effects (currently flip / rotate as I work for MoCap, but I could add LUT's or alike.) Record in 'any' codec (It's FFmpeg based), including HEVC. H264 / ProRes / HEVC have build in presets, but you can make your own easilly. Display incoming video not only local, but on any computer on the network (Over UDP, sorta kinda NDI style) Easy custom or auto set file names Instant playback of recorded clips It's Mac only at the moment. A simple half decent Mac Mini or Macbook Pro can do two HD streams without an issue. (Probably more, but how to connect more than two BM devices? They don't have a daisy chain option...) For logging by scriptboys / girls, have a look at my LiveLog app. Link to LiveLog If needed, I'll integrate it. (Giving you XMP / ALE / Database metadata.) If you are interested, tell me what you want and I'll try to implement it if it's not already there. If you want to toy with it, let me know.

Have never worked with it, but since it's able to run Python, my code 'should' run on it. But why the hassle? Get a tablet running Win10 and run this: LTC reader It can act like a smart slate (Play clap sound and freeze display.)

For Mp4 / Mov, only the start frame is written as 'tc', as a frame number. The rest is calculated based on the frame rate. (And yes, you can specify a different framerate for the TC if you like, but it 'should' not be an issue, it's just math...) You don't know me, but I'm a coder, not a sound guy. (I used to be a video editor, but have seen little off speed files.)

Ah, my bad. I've overlooked this: But then the solution seems simple enough, set the cams to regular 29,97, and have post interpret as 23,976 (read, 1:1 frame relation.), as RunAndGun mentioned. Any half decent NLE can do this. Or am I still missing something? Having said this, if you can manage to put 23.976 LTC on an audio track, my LTC_convert can probably set 'correct' TC's on the files. (And if not, send me testclips and I'll make it work...)

I totally don't get this. This is NOT shooting slomo with an off speed, this is a speed change in post with a 1:1 frame relation. (And yes, that results in a 'slomo', since the frame duration is stretched, but I consider this 'pull down', as 29,97 is NOT an 'off' speed.) Are both set to drop / non drop alike? If not, that's your problem. Then, depending on how smart Post is, how is the new TC calculation done? If they are in sync in 29,97, they also should be in 23,976

Hi all, Since some (well, a lot) of you are responsible for Timecode: QT change has had a major update. It is no longer dependent on QuickTime being installed, and 64 bits (big sur / Catalina compatible.) And it now works also on Mp4 and BRAW files. Beside that, I've recently added an option to offload cards and set TC based on system time, but with a non-drop option. This was done per feature request from Top Gear USA. The logic behind it: They shoot 23,976, but have a couple of drones with no TC nor sound input. Thus the sound guy jams all cams, and the drones get their clocks set to the TC displayed at a given time. Example: Cams are jammed at 09.00 am. TC shown on sound shows 09:00:00:00, drone time is set to 09:00:00:00 In QT change, load all clips, set 'jam time' to 09:00:00:00, and the first clip recorded at 09:00:10:00 will get that as TC, but the clip recorded at 11:00 AM will get TC 10:59:52:20. Of course TOD is a last resort, but this will get you as close as a second or so. (And the offload / set TC in one pass routine will be quite handy. Thinking of it, perhaps I should add as second backup location.) Toy with it if you like, demo is free. https://www.videotoolshed.com/handcrafted-timecode-tools/qtchange/ Bouke

What has Metacorder over Boom recorder?

Whom's? If you mean my software, you have to be a tad more specific, as I can't mind read over this distance. Bouke