Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Pc to Mac prores issues

  • Pc to Mac prores issues

    Posted by Emiliano Aguirre on November 5, 2012 at 9:46 pm

    Hi, im working on my PC on premier CS6 and my boss has a mac whith final cut. Im editing the first cut and the idea is that he will be able to do the final adjustments on his mac. The footage its a quick time avc1 H264 codec. The problem is that i dont need to convert my videos to edit them but he has to transform them to prores. So when i export an xml from premier he can open the proyect on final cut but the performance of the computer its bad becaues its not a prores footage. How can I fix my workflow problems?

    Sorry for my english and sorry if its not clear my problem.

    Thanks!.

    Emiliano Aguirre replied 13 years, 6 months ago 3 Members · 10 Replies
  • 10 Replies
  • Tim Kolb

    November 5, 2012 at 11:09 pm

    This is a challenge…FCPX is better with some of these native codecs, but FCP previous versions really do need to prep footage.

    Unfortunately you can’t convert to ProRes on a Windows system, and whether or not the xml export from Premiere Pro would allow Final Cut to relink to the footage properly after a trip through log and capture is a question I can’t answer.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Emiliano Aguirre

    November 6, 2012 at 1:02 pm

    Thanks for you answer Tim. Ok i will ask my boss tu upgrade his FCP to FCPX. The other solution we tried is to use his premier pro (the mac version) but a problem whith the sequence appears

    “the project contained a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type”

    Im editing in a xdcam sequence but i tried other kind of sequence and the problem persist.

  • Tim Kolb

    November 6, 2012 at 3:17 pm

    XDcam preset? XDcamEX?

    Is this XDcamHDEX footage (from a Sony EX-camera?)

    If so…it’s actually MPEG2 footage wrapped in an MP4 wrapper (yes, I know it sounds insane, but this is how Sony decided to do this).

    I’m not sure if FCPX will handle XDcamEX footage natively…I assumed you were dealing with AVCHD or DSLR when you mentioned H264…

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Anhtu Vu

    November 6, 2012 at 4:22 pm

    I exchange big sessions between PP mac and PC all the time. If you’re careful about how you media manage your workflow, it should be pretty painless.

    I just finish editing/online 10 documentaries, shot in various format and codec. All the footages are duplicated on two different Raid, one residing in my studio and the other on my Peragus R6 along with my portable rig. I can edit at my client’s house, send the PP session directly to my studio’s rig via ftp and open the same session for finishing.

    On a side note, XML between PP and FCP is not bad at best. Unless, you only do straight cuts, there’s way too much information that does not carry across properly.

  • Emiliano Aguirre

    November 6, 2012 at 4:27 pm

    The sequence its a SONYHDCAM HD422 1080i/p. Maybe than codec its the problem The footage its from a canon 5d (maybe this is my mistake working whith a canon seq in a sony seq, foolish of me). Now im traing new seqs and premier sugest an ARRI cinema sequence.

    this is my footage:
    General
    Complete name : E:TRABAJO GUIDODOBERMAN100CANONMVI_7557.MOV
    Format : MPEG-4
    Format profile : QuickTime
    Codec ID : qt
    File size : 651 MiB
    Duration : 2mn 1s
    Overall bit rate : 44.8 Mbps

    Video
    ID : 1
    Format : AVC
    Format/Info : Advanced Video Codec
    Format profile : Baseline@L5.0
    Format settings, CABAC : No
    Format settings, ReFrames : 1 frame
    Format settings, GOP : M=1, N=12
    Codec ID : avc1
    Codec ID/Info : Advanced Video Coding
    Duration : 2mn 1s
    Bit rate : 43.3 Mbps
    Width : 1 920 pixels
    Height : 1 080 pixels
    Original height : 1 088 pixels
    Display aspect ratio : 16:9
    Original display aspect ratio : 16:9
    Frame rate mode : Constant
    Frame rate : 25.000 fps
    Color space : YUV
    Chroma subsampling : 4:2:0
    Bit depth : 8 bits
    Scan type : Progressive

  • Tim Kolb

    November 6, 2012 at 4:37 pm

    Ah…OK.

    You need a DSLR sequence setting…not XDcam.

    That footage should travel to FCPX without much problem as it IS MP4 (h264)…but the XML portability is probably the issue. You may be faced with saving the project as FCP XML and use a conversion tool on the Mac side.

    However, if the version of Premiere Pro is the same (if the Mac version isn’t older than the PPro version you are using), the project should travel and load…but I would say you would want to get rid of any preview files as it sounds like that may be the hang up.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Emiliano Aguirre

    November 6, 2012 at 5:08 pm

    I will trie now the dsrl sequence. We have the same premier version CS6, the problem is than he has fewer options of sequence to chose i dont know why. Thanks a lot for your help

  • Emiliano Aguirre

    November 6, 2012 at 5:11 pm

    Now I start whith the questions that confirm than i am an amateur. When you mean the media manage your workflow you are talking about FC?. Becaues in my pc I have my previews and cashe files in diferent discs than my footage. This could be a problem?

  • Tim Kolb

    November 6, 2012 at 5:26 pm

    For Premiere Pro, I think there are still components that complete the installation that have to be installed as downloads from the web…don’t know if maybe that has yet to be done on the Mac?

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Emiliano Aguirre

    November 6, 2012 at 8:08 pm

    DSLR sequence worked just great!!! thanks a lot!

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