Jump to content

Bouke

Members
  • Posts

    299
  • Joined

  • Last visited

  • Days Won

    13

1 Follower

Profile Information

  • Location
    Netherlands
  • About
    I'm a developer of software tools, both ''off the shelf' as custom work.
  • Interested in Sound for Picture
    Not Applicable

Recent Profile Visitors

2,642 profile views
  1. I don't recommend anything special, but I DO recommend you test. Since there can be delays close to everywhere (display, incoming / sending over Tx Rx, latency of an AD converter, silence before your clap sound etc), LTC convert accepts an offset (positive and negative) for everything. Mind you, LTC is more than frame accrate. As it has a specific start / end of the bits in one frame, its possible to sync up to some 2 milliseconds. The display / visual slate TC should be no more than a last resort. hth, Bouke
  2. For live broadast it makes no difference at all. DF is intended to know HOW LONG a show is. A show starting at (first frame 01:00:00:00) and last visible frame (Note NOT tc Out) at 02:00:00:00 in NDF (mark the absence of semi-colon) 29.97 or 23.976 is NOT an hour long, but 0.1% shorter. That makes planning / timetables difficult, hence DF. Thus, masters at 23.976 . 29.97 are expected to have DF tc. (In a way 24 and 25 are also DF, as the TC follows the 'time on the wall'.) On a side note: (Keep in mind I'm an Avid picture editor.) You can choose between dropping app. 1 frame every minute (hickup in the video), or live with going out sync slowly. Now, no clue what kind of show you are doing, but most of the time 'action' cams 'dash cams' are used as FX shots, close to never longer than 30 seconds. Getting out of sync is no issue for such a short shot, but syncing IS. My QTchange can help 'a bit' with that (I've added something for drone shots, to convert file creation time to NDF, could do about the same.)
  3. Leave it and let post deal with it. It's a slow down, NOT a standards conversion. Avid MC can do it straight out of the box, so can a lot of other NLE's. DF / NDF has nothing to do with the 30 slow down to 29.97 btw...
  4. Watch the 4th part of Four Rooms, Tarantino has a 15 min (or about) monologue. (Fun movie anyways.)
  5. Bouke

    Gps tracker

    Pff, no clue where you live. Over here, if you can pinpoint the stuff, NOTHING will happen, so you have to go in yourself, risking a fight with bad guys, and on top of that, a lawsuits cause it's illegal. I totally get the sentiment to get your stuff back. (I need to recover my 1500 euro MacBook), but I also know that the price to recover it will be HIGH, and probably not worth it.
  6. Bouke

    Gps tracker

    Invest in insurance. Even if you know exactly where your stolen equipment is, what are you going to do? (Really, you could march in with an axe and chainsaw, and get back what's yours, but when the shit hits the fan, you'll loose. Sadly, but this is the way it is, for reasons.)
  7. I know about speed change for 23.976 / 24 workflows. (Old style video to 35mm, I did work on Avatar, all rushes from Mocap, including 'not so' sync sound from BWF have been processed with my software, so I think you can trust me when I state that I do know what I'm talking about.) I also know about how Samples after Midnight convert to TC. I've spent WAY too much time on explaining that BWF DOES NOT carry TC, but a 'frame number' (Starting at 1, not 0, but that's too much into detail...) I did not intend to criticize your work in any way, I merely wanted to state that 1000/1001 (as the 0.1% math is often described) is to be preferred over 48048, as that refers to changed sample rate to do a speed change. I do have an attitude, not sure how long you have been around here, on on other lists, most people do know me a bit and do know that there is no real evil in it. (I'm a coder / used to be a video editor.) Sure, why not? I did not intended to start a war, hence the disclaimer in my offending message.
  8. You did, you use 48048 or 48000 to identify speed for your Samples to TC calculation. (Where the frames are missing btw...) I would use video FPS (Drop or non-drop) to give a preview about what the TC will look like. But lets agree to disagree.
  9. Thanks, found the issue and fixed it. (Bext chunk contains non-text where I expect text...) I'll make an update later today.
  10. There is no 'weirdness', changing the sample rate to get TC 'right' is weird, this might fuck up things big time. If you don't know what you're doing, step away and let the big boys take care of it. (Insults intended, sorry...)
  11. Eeh, I'm offering help just for debugging / fun. As a Pro, just trash the unit and buy something that is proven to work. Of course, all location sound stuff is HIGHLY overpriced, but what war do you want to win? Go with the flow, my rate only with my effort on your system problems makes no sense at all. TRASH the unit, get something that does the job, or post on a list / forum / site with people who like to have problems. ( Sorry to sound so harsh, I have my own issues at the moment.)
  12. Please send me the file from Logic, I know there used to be an issue with Logic files (some non-standard stuff), but I thought that was worked out. I did a test run with LTC convert, and it works fine. (But it does not really 'do' anything except reporting.) For fun, download this: https://we.tl/t-MVaRKTlPWx Drop it on the left side of LTC convert, enable 'expect breaks' and scan. When done, doubleclick on the filename in the interface, and it'll show you where the breaks are.
  13. My LTC convert can scan every frame and give a report on jumps / breaks, if there is a LTC track present. https://www.videotoolshed.com/product/ltc-convert-auxtc/ Just enable 'expect breaks'. (I must say I forgot how it reports, but it does do 'something'. It's late here, can't check myself now.)
  14. avid MC can do this, if you know what you're doing. I suspect PT to be a able to do the same, as well as Reaper, and others. It all depends on what you want. Setting a new Timestamp (FU, BWF does NOT carry TC) is not that hard.
  15. Check the difference between LTC and normal TC. I bet you won't see a difference. If the master LTC clock was sound, and sound has one long file, and video clips before and after are ok, there is something fishy with the video file. Check the file size and compare it with other files, see if there is a significant size difference to what should be expected. Try LTC convert to create a new clip. And, try LTC convert to re-stamp the BWF to match the video TC. If any of the two fail, send me the files.
×
×
  • Create New...