Bouke

Pff, I feel a rant coming up, but not sure if this gang wants to hear what I (being a seasoned editor) has to say about the subject.

Has anyone ever used LTC on a sound channel on an Arri shoot? Reason, for a custom project I've made something to destructively change the TC on .arx / .ari files. (And the wave files that come with it.) I'm currently building that into QT change (as well as BWF support), and I could also build it into LTC convert, but if no one will ever use it...

I know Marcel from a (coders) mailing list, he's indeed very helpful and a nice guy!

for fixing corrupt / bad files: https://www.videotoolshed.com/product/wavefix/ Deity should have made this though, not me. I can / will add more functionalty to taste,

On re-reading, it should say: THEN I know what I'm talking about. (At this point I have no clue what could cause drift, the Deity guys should know. I'll rant about that in my next post.)

Well, often, but close to never in PM. I can be harsh, but that is 'normal' for me. It is a bit the Dutch way, I master that art. Don't seek anything behind it, it's just words. To be honest and modest, that's an understatement : -) Fact is, and please: 'Whatever happens on JW, stays on JW.' I'm bi-polar. That means that from time to time I'm brilliant, but there is a horrible flip side.

Please, make it simple. Give me a few (at least two) timecodes (Or bwf timestamps) with the corresponding drift, and I know what I'm talking about.

Nope, then I have no clue... But I don't know how these thingies are working... How big is the drift, is it constant? Does the drift get bigger when the TC values increase? If so, by how much?

What happened on these files: The file size in the header was set to x00 00 00 00 (Read, zero.) Same goes for the size of the Data chunk. (As I expected.) This makes sense after a crash. The device expected a normal exit, then measure the file, then set the correct values. It's absolutely no problem to fix these files 'in place'. (If I find a bit of time today I'll build it in 'somewhere'.) The drift is something else. There is a normal BWF timestamp. Perhaps, but that's a VERY wild guess, that gets altered to a NDF format or alike on normal exit. (Where the normal clock runs in RT or so.) No matter what the trouble is, I bet it's a DF / NDF (0.1 % or 3.6 seconds per hour) drift. That's a golden oldie, also easy to fix.

Using my WeTranfer (here) I think the Data chunk is set to 0. Setting it to FFFFFFFF (if it's < 4 gig) should do the trick, or calculate the 'right' size. What happens with drift. If the timestamp is there, there should be no drift. I know that for Avid you can force the FPS. (Thus Avid won't ask how to interpret the timestamp.) That's an easy fix as well, in the Bext chunk, remove the Speed (pad with space) (Perhaps also comment out the iXML, if it's present)

Send one to me. If the data is there, I can fix it. Bouke

This is implemented now in the Mac version. (Win will follow.)

Does anyone have a mix conform to the Netflix loudness specs? (With the corresponding DIA stem.) Working on my 'Loudness change' app now, trying to implement a more open source speech gating than the free but not open source Dolby routine. But I don't have the means to test my work, so I'm looking for a test set with the measured values, to compare it with my work. (It won't be exactly the same, but I think I can get it within 0.5 LU, while Netflix allows for 2 LU difference.) Thx, Bouke

nice! And finally a 'how to' video that is not absurd long / annoying!

Perhaps in a DAW, but not so much in a NLE. Perf slip in MC exists, but not in all versions. In Premiere, no go afaik.

eeh, never owned a sound cart, but my friend has a HUGE one, and he has all kind of 19" drawers. (I had heavy drawer plates in my rack for easy access to beta / digibeta, could handle up to 60 kg or so, bit overpowered, but probably lighter ones can be had / made. Or buy 'off the shelf' drawer profiles that extend enough, and get a piece of thin plywood. Won't break the bank: https://www.meubelbeslagcenter.nl/ladegeleiders/standaard-ladegeleiders-20kg/

You're missing the point. Chances that the trouble is in the connector are very slim.

If cross talk would happen in a connector you all would be complaining about your headphones. It's way more likely to happen inside the electronics. I would not be surprised if the cams that suffer from this have automatic levels, and/or are fed with a way too high signal.

Why don't you share the original recording as stereo? I don't listen to it. I open it in an editor and I bet something pretty that the first thing I see is that your LTC channel is WAY TOO LOUD. This is your problem. Again, LTC does not need 'volume'.

Fair enough, I'll see what I can do. First things first, test the 'reverse' option. (For the others, that has been build in now, and I've fixed some bugs on Mono input.)

Y split takes one input, two outputs. No clue what you are trying to do then.

Why did you not PM me, I've missed this one! This is exactly why I made it. Capture multicam on a single system. (I must admit, I have no clue what it does on SD, thought that was phased out... I can definitely make it work, this thing started it's life for SD work on video assist for a major feature...) Paid version is available as soon as I have set a price (that's always difficult...) AND I have enough feedback that it does indeed work as advertised! PM me if you like, or mail me direct. bouke@videotoolshed.com I can have you up and running in no time!

Eeh, this is a mono mix. Keep the LTC volume low, -25 should be no issue at all. (In 24 bits even lower.) Get my LTC convert app (the free demo will do just fine) and do some test recordings to see how low you can go. LTC does not care about volume. Very low should still work. Test, make attenuation cables (resistors) if needed.

But Resolve can't do (subframe) offsets AFAIK, nor scan for longer time (if TC does not start at the beginning, some action cams have a fade in....). The devil is in the details. If all is perfect, it's fine, otherwise post gets expensive. (And Resolve is a sledgehammer if you just want to deliver files with 'correct' TC.)

I don't get it. What version are you running? If you select an unused track and hit Render, the app will show a warning, and nothing will happen. There is no need to clear the list. If you drag new files / select a new input folder, the list is cleared and the new files are selected. What am I missing here? Bouke