[Tim Kolb]

Since your AMD GPU card is not on the compatible list at this time (6750M and 6770M in MacBooks are currently supported), I’m certain you’ll get no hardware GPU help.

In an iMac, you’d need an NVIDIA card…

As I said earlier, even though the AVCHD material is not decoded specifically on a compatible GPU, the GPU picks up a lot of slack in other areas to enable the CPU to allocate more torque to decoding.

All the H264 decoder operations I’ve seen in general use are typically single-threaded (I think Adobe may be distributing the task across CPU cores by frame to get better efficiency), so I’ve found that clock speed on a CPU seems to trump pure core count, at least for H264 DSLR material…AVCHD may be similar in that respect.

CineForm will certainly help…and CineForm Studio is a free download from the GoPro website, so it costs nothing to install. I know the free version of the software loads and transcodes GoPro and other DSLR material, but I’m thinking you may have to use Prelude (available in CS6) to convert AVCHD…

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

No.

Encoding a file makes (exports if you like) a video file in the location of your choice…then you upload that file to YouTube.

…piece of cake.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

If Premiere Pro is launching the project, but not asking you to point it at the preview files (the project should know that they’re missing), then there is something funky about how this process is happening.

When you launch the project, does the project ask you where a bunch of files with long, nonsensical names are?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

When you exported the file, you compress it to whatever the preset you picked is set for… YouTube presets are H264 (MPEG4).

What export preset did you select?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

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

[Tim Kolb]

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

[Tim Kolb]

Well…Adobe can only trim what they have access to, and in most cases, if it’s a file format from a camera that can’t be “written” by a computer (you can’t render RED raw or ARRIRAW out of After Effects for instance), then the necessary access to “trim” the file probably isn’t available either.

RED can do whatever they want in their own software, but they have to make access available in the SDK for someone else to get that capability of course…

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

If it was a media file that was good enough to make it through the import process, but was corrupt enough to crash the app, I would think that Erik would notice that he’s “touching” the clip in question every time he crashes…it should be pretty obvious.

Erik, have you tried to launch PPro and just make some color bars and black and see if they can be placed on a sequence and played? That way you initially eliminate media altogether…

Then I might try import one clip…try it on a sequence…if that works, save the project…make a new project, try a different (preferably a different format) clip and see if that works…etc.

There are a couple of possibilities here…

You’ve done a clean install and tried to run the system with only CS6, otherwise I would have said that the most likely scenario was another application in conflict with PPro…several versions ago I had to change anti-virus programs because PPro would crash whenever I tried to create a sequence (?!)

As it is, if the issue is not tied to a media file, then it’s obviously some fundamental thing, and I’d look to things like the status of the targeted cache file disk…is it full? Possibly display card drivers…other system drivers, etc.

While we’ve seen Mac users with issues, there are Mac users who seem to be functioning reasonably well. Unfortunately I’ve been away from Macs as my primary platform for a decade, so troubleshooting system-level stuff on Macs isn’t really my thing these days.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

Good info Walter…does Motion install the legacy codec?

This sheltering of ProRes by Apple is getting even more frustrating than it has been in the past.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

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