No announcement yet.

Error exporting to AAF

  • Filter
  • Time
  • Show
Clear All
new posts

  • Error exporting to AAF

    Hi everyone,
    I shot my footage at 50p.
    My project settings in edius was at 25p.
    After editing the footage I decide to export the project to send it to a friend (who is editing with Premiere)
    So I try the aaf export.
    The thing is that I am getting an error that the frame rate is not the same etc.and the aaf export is not feasible.
    Any idea how I'll make the aaf export work?
    I have already try to change the project settings to 50p or import the 25p sequence to a new 50p project, but none of them seems to work.

    Thank you in advance for every idea!

  • #2
    there is no solution other than to re-edit with matching frame rate
    Anton Strauss
    Antons Video Productions - Sydney

    EDIUS X WG with BM Mini Monitor 4k and BM Mini Recorder, Gigabyte X299 UD4 Pro, Intel Core i9 9960X 16 Core, 32 Threads @ 4.3Ghz, Corsair Water Cooling, Gigabyte RTX-2070 Super 3X 8GB Video Card, Samsung 860 Pro 512GB SSD for System, 8TB Samsung Raid0 SSD for Video, 2 Pioneer BDR-209 Blu-ray/DVD burners, Hotswap Bay for 3.5" Sata and 2.5" SSD, Phanteks Enthoo Pro XL Tower, Corsair 32GB DDR4 Ram, Win10 Pro


    • #3
      Thanks Antons.
      It's sad, but...that's also my feeling


      • #4
        Rather than linking to the clips get EDIUS to make new ones in a format the premiere Pro will be happy with like Prores. This will change all your clips from 50p to 25p but he would have a project with your clips in it. He could then I use this as a basis of matching up the originals to the timeline in premiere or just edit at 25p.
        EDIUS silver certified trainer.
        Main edit laptop: DVC Kaby Lake desktop processor laptop, 32GB RAM, 3.5Ghz i5 desktop processor, nVidia 1060, Windows 10.
        Desktop: 4Ghz 9900K processor, 32GB RAM, nVidia 1660TI GPU, Windows 10.
        Desktop: 2Ghz 12 core Xeon processor, 32GB RAM, nVidia 1060, BM Intensity Pro, Windows 10


        • #5
          Thanks a lot, I'll try it.