[Tim Kolb]

I think part of the issue may be platform differences as well…Windows vs Mac as well as the difference in drivers for FCP which have only needed some bug fixes over the last four years vs PPro, which has taken such massive steps in the last four years that the hardware drivers have had to make large changes…multiple times.

Also I suspect it’s easier to run a driver for a strictly QT ecosystem than for PPro, which has had to “work around” QT for the last two releases to accommodate all the native format support, etc.

As I’ve said in other threads, I think FCP users in migration need to remember that the CS5 major release is just over a year old and the 5.5 upgrade is a couple months. Third party developers (particularly for solid SDI I/O)are faced with a pretty stiff task.

I realize that doesn’t solve today’s problem, but I think it’s important if you choose to compare third party hardware support…to go back to a similar moment in FCP’s release cycle to evaluate where third party vendors were with feature sets and dependability.

It will get there.

As a long time PPro user, I’d also say that most third party vendors have been spending most of their time over the last 5 years focusing on FCP.

Premiere Pro was a bit of a second-class citizen for most of these manufacturers. (look at how many PPro stations were in these booths at NAB vs FCP…even in 2011!)

Now that FCP users are switching, maybe we can get the attention that Premiere Pro needs to bring third party hardware support up to the level of legacy Final Cut.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

You may want to try switching the sequence to “audio units” in the top right corner of the timeline panel. It changes the audio tracks in the timeline to be able to be cut/manipulated in samples or milliseconds, but also does change how the audio plays back on some systems.

2x might be more fluid then…

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

So…are you designating the second monitor as an external monitor?

Instead of that…have you tried simply dragging the program panel to the second monitor and filling the screen with it?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

I guess what I’m saying is that importing an FCP project and altering its settings are two different animals entirely. PPro doesn’t alter the settings on PPro sequences…

The workflow in PPro is to create another sequence if you need to alter framerate/size settings, etc. Once a sequence is created, those settings are committed.

Importing an FCP XML undoubtedly requires PPro to interpret things like framesize/framerate, but hardware settings inside FCP are likely so different that I just don’t see a proper conversion being possible, say from AJA FCP-to-AJA Adobe, without some work from the hardware company as the hooks, the interface, the options and the drivers are different.

Copy/Paste (as you noted) into a new, properly configured sequence is a relatively small leap to otherwise maintain the edited FCP timeline.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

I have 4 displays. I have since CS3…PPro runs fine.

What display cards are you using? Is this a Mac or Windows machine?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

[Erik Naso] “I would use AE but AE has no waveform so I don’t know if my adjustments are legal. I need that.
“

This is a major issue with the CS system right now. AE has color management…but PPro has the scopes.

This is a situation that has been pointed out to Adobe by those of us who have been here a while. It’s an important workflow gap that needs addressing.

I have reason to believe that it is front and center in the development priorities.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

For a maximum vertical view, i find myself using the tilde key “~” to make the timeline full screen and then toggling it back. However, I have multiple monitors.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

[Erik Naso] ” I have a bunch of CC to do and was hoping to use Ppro to do it.
I did a XML out from FCP7 and opened it in premiere without a hitch until I tried to playback with AJA card. Original sequence has settings baked in so I had to copy and past into a new sequence to see playback with AJA card. Not a big deal but still a workaround.”

I’m not sure that expecting a 64 bit program designed and released in 2011 to read the third party hardware settings from a 32 bit program with only minor structural changes since 2007 (when Adobe was current as CS3 with no multiple sequence settings within a single project) is a realistic expectation.

I understand that Premiere Pro loading FCP projects is hugely helpful for FCP users who have decided they need to migrate, but Adobe has had 4 drops (CS3, CS4, CS5, CS5.5) since FCP was last really structurally upgraded. (Apple did not really present the 2009 changes as a major version upgrade and most of my colleagues who used FCP didn’t think of it that way either…)

PPro does some things differently than FCP…that’s a given.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

Now that we know what products they were selling in the hardware line…

Mac workstation sales were driven by the printing/graphics industry (largely Adobe software), the video industry (Avid, Media 100, Adobe After Effects/Photoshop…etc), and the audio production industry (ProTools now part of Avid, Sample cel, Midi instrument software, etc.).

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

[Chris Cea] “Your thinking that maybe having 7 installed might allow Premiere to work with this codec?”

I need to be clear…I am reaching beyond my direct experience…but knowing how old the DNxHD codec is, how hard Adobe had to work to get old QuickTime to be useable, and the new Media Foundation is…really new…it couldn’t hurt to check I guess.

But…I’m troubleshooting at this point.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor