Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy prores 422(LT) with 48khz audio still requires rendering

  • Nick Meyers

    June 11, 2018 at 4:39 am

    it’s all very strange.

    FCP can play AIFF and WAV quite happily
    simple mis-matches, like a 16bit audio file in a 24 bit sequence would NOT require rendering.

    you could trash your FCP preferences and see if that helps.

    otherwise, i’d say there;s something wrong with the files from Ableton.
    I have no experience with Ableton, so can’t help there.

    one more thing to check: what is your sequence preset?
    does is have the same frame-rate as the material you are working with?
    it helps if it does, especially with audio sync.
    however, again this would not cause your audio to need rendering.

    as i can’t help too much getting to the bottom of the problem, as an alternative i would suggest:

    set the appropriate sequence preset.
    delete all audio or start a new project.
    re-import the 24bit files
    batch export them from FCP to AIFF or WAV
    then bring those new files into FCP.

    nick

  • Michael Gissing

    June 11, 2018 at 5:28 am

    FCP sequence uses 32 bit float for audio processing so that is normal for the sequence settings. It isn’t the cause of the rendering. There must be something else about those files that FCP doesn’t like and it is possibly in the metatdata coming from Abelton.

    Are you sure it is the audio that needs rendering? Does it beep when unrendered? It has been a long time since I needed to use FCP7 and rarely did the audio need rendering.

  • Raju Bhai

    June 11, 2018 at 2:39 pm

    yeah, the only differences i could see in the settings was
    1) the 32 bit float (thanks Michael for confirming that this is ok!)
    and
    2) the data rate difference btw the imported audio and the video clip audio (still not sure if this could be a cause for rendering issue or if it is normal)

    SO, yes Nick, this is weird indeed. And Michael, Nick, I know it’s not an issue with Ableton. The reason being is that i’ve used Ableton audio files before in FCP7 and never had an issue. The only difference betw then and now is that then my video clips were full 1080 frame size and now the video i am using is small 640×360 frame size, and while i had transcoded to prores 422 in the past, this time, since i am using lower quality video, i transcoded to prores 422 LT instead. But my sequence settings are fully setup to match the new video. So i really don’t see where the issue could be.

    Nick I like your suggestion to trash preferences, but i watched the Larry Jordan video where he said only trash them if it really is an issue. I’m not sure in this case, but perhaps it’s worth a shot?

    And yeah, Michael, the sequence only needs rendering when i drop the ableton audio file in. When i import it into the timeline, 2 red render lines appear at top.

  • Nick Meyers

    June 11, 2018 at 11:04 pm

    [raju bhai] “the video i am using is small 640×360 frame size … But my sequence settings are fully setup to match the new video”

    ok , i sont think this is a standard FCP sequence setting,
    so that *could* affect RT [performance, but i would guess only for the video.

    try changing your sequence settings to oe of the offered ones, see what happens.
    my guess is it will remain the same.

    [raju bhai] “Larry Jordan video where he said only trash them if it really is an issue.”

    a little alarmist perhaps.
    you just have to re-set your preferences.
    make sure you have things like keyboard layout saved if you have modified it.

    [raju bhai] “the sequence only needs rendering when i drop the ableton audio file in. When i import it into the timeline, 2 red render lines appear at top.”

    why 2 lines i wonder?
    that would imply video and audio renders required
    are you getting the audio beeps that Michael asked about?

    nick

  • Raju Bhai

    June 12, 2018 at 1:35 am

    [nick meyers] “ok , i sont think this is a standard FCP sequence setting,
    so that *could* affect RT [performance, but i would guess only for the video.

    try changing your sequence settings to oe of the offered ones, see what happens.
    my guess is it will remain the same.”

    I don’t know which standard setting to select, it seems none of them match my video clip properties. For instance there is nothing in the standard FCP seq settings that is prores LT and 640×480 frame rate. I also tried changing the aspect ratio in seq settings to standard NTSC 3:2 and that didn’t work either. Additionally, when i dropped the video in it says there are no matching sequence settings so it creates the sequence with the matching setting for me.

    As far as the audio beeping, yes it is beeping. And when i checked again it isn’t 2 red render lines but 1 red line and 1 that is either purple or blue or grey (hard to tell the exact color of that other render line).

  • Shane Ross

    June 12, 2018 at 1:44 am

    FCP 7 was designed to work with broadcast standard formats. 640×360, even as ProRes LT…does not fit any broadcast standard. Your best option would be to convert that to 720×480 DV…or 720×486 ProRes.

    Yeah, you are working with a web sized video in an edit app not designed for cutting web sized video…

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • Nick Meyers

    June 12, 2018 at 1:45 am

    [raju bhai] “when i dropped the video in it says there are no matching sequence settings so it creates the sequence with the matching setting for me.”

    exactly, so FCP is working outside of it;s comfort zone.

    chose a sequence preset that matches your clips quite close.
    same frame rate of course,
    and try 1280×720 as that’s sure pixels e your video is.

    nevertheless i doubt this will change things, and i suggest that the files from Ableton are at fault for whatever reason.
    to test, make a new sequence of ANY flavour, and drop the audio in.
    re-procesing the files thru FCP or compressor should be tried, just see if it works/

    [raju bhai] ” red line and 1 that is either purple or blue or grey”

    either the default great line meaning no rendering requited
    or the steely blue-grey line which means there is some slight mis-match, but FCP can deal with it, and play back a “full quality” image.

    nick

  • Michael Gissing

    June 12, 2018 at 1:50 am

    My thought is the sequence settings are not a standard pixel aspect that FCP is happy with hence the rendering. The audio just makes it worse. I’ll bet the audio files are fine in any FCP broadcast standard sequence. The non standard sequence is the issue.

    When transcoding to ProRes, a standard pixel size needed like 720 x 486 to be chosen as Shane has pointed out.

  • Nick Meyers

    June 12, 2018 at 1:55 am

    and try 1280×720 as that’s square pixels, same as your video is.

    (couldn’t edit my typo in orig post)

Page 2 of 2

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