Forum Replies Created

Page 85 of 149
  • Bouke Vahl

    January 12, 2010 at 11:03 am in reply to: Audio Sync Problem – Sampling Issue?

    Steve,
    Your therory is wrong. Sample rate could be anything without affecting the duration.
    (Although by changing the sample rate a tiny bit you can change duration…)

    How was it recorded and ingested? Perhaps the recorder drifts a bit over time on playback.

    You can change sample rate in any audio package. You even can open the audio in QT pro and export to 48 Khz.

    Easiest way of getting rid of the sync problem is cutting out small pieces here and there. (assuming you have to cut anyways)
    If you can’t cut, you can change the duration of the audio in an audio editor. Do use ‘pitch shift’ (or whatever it’s called in the package you use) if you can. This will be fast, unnoticable for the audience and leaves you with the highest quality.

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pro’s

  • Bouke Vahl

    January 11, 2010 at 10:53 am in reply to: Canon 7D 24p footage sync problem

    What happens:
    You shot video @ 24 fps. Now you play back as 23.976 fps.
    That is a different speed. So if you don’t compensate, you’ll loose sync.
    As mentioned in a thread just below this one:
    Restamp the audio files as 48.048 Khz. Then FCP will not use the new sampling rate, but just change duration and you’re sync again.

    There are a lot of (free) utils out there that can do this.
    hth

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pro’s

  • Bouke Vahl

    January 10, 2010 at 3:23 pm in reply to: Timecode mismatch on FCP export to quicktime

    Matt,
    You are right, no DF in 23.976 (i refuse the term 23.98 cause it is incorrect and has caused enough trouble already)

    Nevertheless, the difference is a typical DF / NDF difference.
    It’s a nasty bug then…

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pro’s

  • Bouke Vahl

    January 10, 2010 at 3:20 pm in reply to: Stitching Files Together

    Francis,
    Go to the link YOU provided and read:

    QuickTime Reference Movies
    The FS-100 uses the FAT32 disk format, allowing up to 2GB of recorded video per clip. While recording, the FS-100 automatically creates a new clip when the 2GB limit is reached, ensuring that no frames are dropped. Depending on the length of your recording, you may have multiple 2GB clips.

    After your recording is complete, you can go to the FS-100 Utilities menu and create a *QuickTime reference movie. This movie acts as a pointer, referencing your multiple clips to form one movie. This feature makes clip management more efficient, especially when editing—your NLE will import the reference movie as one clip.
    *Because the QuickTime reference movie points to your original 2GB clips, the clips and the reference movie should always be archived together.

    Now this is EXACTLY what i expected and wrote in my other reply.
    (and it is exactly the same as what my app. does)

    As for quality, remember that DV qt has a quality flag that defaults to ‘horrible’.
    That does not mean the file is bad, only that it is displaying bad looking to ensure the playback rate is met.
    (You can alter that flag also with my QTchange app.)

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pro’s

  • Bouke Vahl

    January 10, 2010 at 2:21 pm in reply to: Stitching Files Together

    You could put them all in a single QT ref file.

    I had some code laying around and made you something:
    This util does it for you in batch:
    https://www.videotoolshed.com/?page=products&pID=46

    But i would think that a decent recorder would be so smart to do the same…

    Let me know if this works for you.

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pro’s

  • Bouke Vahl

    January 10, 2010 at 1:18 pm in reply to: Canon 7D Audio Synching

    BJ,
    Sorry to have been so harsh.

    It highly irritates me that very often people don’t read / understand the questions and start giving the wrong advice based on assumptions / ideas that have nothing to do with the subject.
    (And i must admit, I’m guilty as well every now and then.)

    The internet is full of wrong information,
    and no-one seems to care to make clear if what they write is an opinion, guess or proven fact.

    And last:
    Business is doing great.
    As for how i treat my customers, i haven’t had a single complaint yet.
    (But yes, i’m not political correct. I’m not into politics, i’m a normal human being with a strong opinion.)

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pro’s

  • I’ll have a swing at this:

    [Trevor Fernando] “My question is…is this the best way to prep H.264/7D Footage for editing? “

    There is no best way. There are several ways, you decide what’s best for YOU.

    [Trevor Fernando] “I did a test of this workflow and it took 30 minutes to encode a 1.5 GB/4 Minute clip into ProRes, and the final file ended up being 4 GB. Does it normally take this long? I have about 305 GB to convert, so I want to know if this is the fastest way to do it. “

    I just ran a test on an old quad.
    Using just a QT pro export, takes slightly more than 3 times the duration to transcode.
    But, the machine still runs about 50% idle. Thus if you have an application that is smart enough to max out the CPU power you should be able to double that speed.
    Experiment a little.
    You can always export your synced clips as QT refs to feed them to another transcoder.

    As for file sizes, if that bothers you, you could also transcode to XDcamHD. Will get you about the same file size as the H264. After you’re done, you could always relink to the originals and transcode again to any other codec you like.

    Same goes for the H264. If you start editing without much effect work, you could start out working with the originals and transcode just the rough edit when you get to the heavy work.
    H 264 ‘ not an editing codec’ just goes for the heavy work. For plain editorial making choices, it is just fine.
    Again, toy with it. If it’s workable for you, no need to transcode everything before starting the edit.
    (Why spoil horsepower on long takes that never will be used anyway?)

    For syncing before or after the transcoding, i don’t think it will make a difference.

    Now one thing i do think is important, get timecode!
    If you export from FCP timelines, all clips end up with the same timecode. Not handy for dupe detection / organizing your files.
    You can download “qtChange’ from my site and batch add TC to the originals, but i’m not sure how that will work during transcoding after you synced. So i would first add TC, then transcode (or don’t transcode), then sync.
    You end up with unique clips that are easier to organize.

    hth,

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pro’s

  • Tom,
    The OP uses Plural Eyes to sync. Nature of the beast to do it in a timeline..

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pro’s

  • Bouke Vahl

    January 9, 2010 at 3:00 pm in reply to: Timecode mismatch on FCP export to quicktime

    check the old and the new timeline
    I bet one is drop frame, the other is not…

    Bouke

    https://www.videotoolshed.com/
    smart tools for video pro’s

  • Bouke Vahl

    January 8, 2010 at 11:56 pm in reply to: Canon 7D Audio Synching

    [B.J. Ahlen] “Good points if this was indeed a one-off, but considering the less than clear communication I don’t think we know that.”

    How stupid / narrow minded / lazy are you?

    Read the original post:
    13 files in total – #13 is 1k reference tone.

Page 85 of 149

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy