Jump to content

Sound

Members
  • Posts

    336
  • Joined

  • Last visited

  • Days Won

    2

Profile Information

  • Location
    Germany
  • About
    It's a great community.
    I am just starting with audio and have a low budget audio bag
    (Zoom F6 and Sony uwp-d) and I am very thankful for all this great advice!
  • Interested in Sound for Picture
    Yes

Recent Profile Visitors

1,723 profile views
  1. I have no Idea what you are talking about, but I am glad if it helps you.
  2. If its still interesting for you, I could recreate the file from logic. I dont need it to work as I dont have to check logic-files, but maybe it helps your software. https://we.tl/t-heGlQ4ZbLM
  3. Thanks, the new version seems to work! If there would be a batch-function it would be even greater. Right now, my ffworks-workflow is faster when I have to edit about 50 or more files.. Thanks a lot for your help, dont get me wrong, I am very grateful for your time, and your tool works. I will definitely use it to double check the files that seem to cause problems. I was thinking about buying something else all the time as this hast cost me LOTS of my time for weeks now. Before I had the Mixpre 10 ii and i regret having sold it, as i never hat any issues with it. But its a lot of weight if you use it on location and have to to a lot of things at the same time. So its not a question of money: At the moment there is no other recorder with six xlr-inputs and six track knobs with this size and weight. Especially fully powered, as you can use it all day with just one NP-F Battery and dont need an external powering solution. Mixpre 6 II could be fine, but only 4 xlr and one minijack input and only four track knobs... I just hope the new firmware has fixed ist, just have to test. For anyone who is interested. Here is a test file. Zoom F6, Six channels recorded in 24bit, 48khz until max filesize reached. https://we.tl/t-K1rOSFVFdA If its still interesting for you: https://we.tl/t-K1rOSFVFdA
  4. I am afraid I have deleted the logic-file already.. But its not necessary for testing as your file works. From my first test using the ffworks method I had a maximum shift of two frames between the original and the cut off file ends. I dont know exactly why there should be any shift at all as there is no audio drift when the tc output is connected directly to the audio input.. and its the same file synced to itself.. But LTC convert didnt detect breaks either on the original corresponding file, so it should be fine. But anyway, two frames for me is not a sign for an audio jump. I will continue testing.
  5. Thanks, looks good! Do you think its practical to scan 50 files with about 40 minutes each this way? Can you see the breaks in a 40 minutes file as well?
  6. Right now there is no easy way to find audio jumps on the mac. This is the fastest way for me: I feed Timecode from the output of the f6 to audio input 1. Then I record for hours or days... with 256 gb I can record about 80 hours in 24 bit - 6 channels. Then I have to compare file tc with the audio TC at the end of each clip. If audio jumps there should be differences between file tc and audio tc. The fastest way for me was to use ffworks for Mac to batch cut off the last seconds of every file. (Apply the "trim" effect to one file and copy it to all the others). Then export (FFworks deletes file tc on export as all other tools - unfortunately). Then I sync those files to the originals via audio-tc, export an xml for final cut (or any other preferred editing software) and compare the END of the original clips and the trimmed clips on the timeline. If they align at the end, then the file-tc (or the audio-tc, depends on the way you sync) at the start of the original file and the audio tc of the cut out version (from the end of the original file) are identical. Its a few steps but it takes a few minutes only - much faster than recording with two devices and listen if they are in sync. Another option could be to use "LTC Convert" with "expect breaks", but I couldnt test it for myself - first I have to find a file with audio jumps. Maybe I will let the recorder run for three days powered via usb-c - if I cant find any jumps then the update should have fixed the problem..
  7. Right now there is no easy way. The fastest way for me was to use ffworks for Mac to batch cut off the last seconds of every file, then export (without file tc unfortunately). Then sync those files to the originals via audio-tc, export an xml for final cut and compare the END of the original clips and the trimmed clips on the timeline. If they align at the end, then the file-tc (or the audio-tc, depends on the way you sync) at the start of the original file and the audio tc of the cut out version (from the end of the original file) are identical. Its a few steps but doesnt take too long. At the same time I will try LTC Convert with "expect breaks", especially when I find differences.
  8. Thanks for your help! It looks like a great tool, but I am afraid it doesnt exactl copy the file tc and audio tc is off as well.. According to the tool, the exportet file should start at 1:40:03 but it starts at 1:40:09 when I read it in tentacle sync.
  9. Maybe this could work to test if there are dropouts, will test it.
  10. Thanks again Bouke. I could install the newest (demo) version and could find the button. To try it out, I edited the file in logic and cut out a piece in the middle. But it doesnt recognize the file and is stuck with the status "please wait while files are scanned". No matter if "Expect breaks" is selected or not.. Tentacle sync finds a timecode and if I select "scan in the middle of file" it even show a different timecode from the edited part..
  11. Thanks again!! You are great! i am trying to find an easy way to detect audio jumps in the Zoom f6. Timecode output and file timcode of the recorder counts on but the recorded audio jumps. So if I feed Timecode output to an audio track of the recorder and the recorded audio jumps somewhere in the file there should be a difference of ltc and file tc at the end of the track. But most of the time LTC is converted at the beginning of the file, I cannot set it to read it at the end. So I thought I could just cut off the end of the file and then compare ltc and file tc.
  12. Ok I thought in single mode t least it works
  13. Its fine. the post is quite old, so no problem anymore.
  14. I am looking for an easy way to trim an audio file while keeping tc information. Lets say the file starts at 00:00:00 - I want to edit out the part from 00:10:14 to 00:10:60 and the starting tc of the new file should be 00:10:14. Is there an easy way to do it?
×
×
  • Create New...