[Lucas Merino]

When I get back to the workstation I will try to mock something up that I can pass along. Also note, we are working with EXR sequences. I’ll see if I can make a gradient test chart of some sort.

[Lucas Merino]

Thanks for the reply.

Would you happen to know why the banding appears in the Davinci preview window, and not other software, like After Effects for example?

Have you experienced similar? I’m wondering if the preview image is lower quality so that frames per second/realtime is higher?

[Lucas Merino]

[Walter Soyka] “I would feel better about this if Apple had explicitly involved third-party developers (as they have done with iOS).”

I totally agree with you here, except remember there was no appstore when the iPhone launched.

But as I said about the precedent they set with the launch of fcpx, there was no mention at all about “modular design” and base systems where indies could get by with minimum addons and pros could buy all sorts of things (which really I feel this is exactly how it works now anyway… some people can afford/need Sapphire and Automatic Duck and some people cannot/don’t).

Had they presented the product this way, and also launched with 20-30 3rd party companies with plenty of “addons” ready to go, I think it would be a totally different forum right now. Kinda like when they roll out app developers on stage during a presentation.

[Lucas Merino]

[Chris Stevens] “If you want feature X, you will buy a third-party plug-in. “

When your 3rd party plugin doesn’t work, who are you going to call for support, Apple or the 3rd party? And when you call that person and they tell you to call the other company, then what?

And then what happens when Apple updates fcpx and it breaks the 3rd party plugin?

…And what happens if you are in the middle of a project and it’s an auto update from the appstore, just like when Quicktime gets updated when you don’t want it and it kills After Effects export.

If they are going for a modular 3rd party approach, Apple has set up a horrifying precedent with how they released fcpx.

[Lucas Merino]

[Paul Escamilla] “here’s a very scary thought. What if Apple buys Avid and Adobe and kills off Premiere and Media Composer? Then what?”

Open Source Editshare

As per Premiere on osx vs. Windows… at work I have a Mac Pro that I dual boot with bootcamp. I have the same versions of Premiere CS5 on both setups and it just clearly works better on the Windows side. This is the exact same hardware, being that it’s the exact same machine.

On the Mac side, when I try to rapidly zoom-in-zoom-out on the timeline (which I do a lot) it just drags. Also moving clips around on the timeline, for some reason seems more clunky on the Mac side.

The only reason I boot up into OSX is for FCP 7. If it weren’t for that, I would have every other application I use on the Windows side (adobe suite, avid, Cinema 4D, various compression software, etc.)

[Lucas Merino]

I know saying this on this thread is a needle in a haystack, but as a long time Premiere user, I want to tell people that it runs much better on Windows.

… and this is in no way simply being anti-apple for anti-apple sake. In my experience it has just run so much better whether scrubbing on the timeline or loading files, etc.

The one caveat that I think people will realize is that there is no built in “working codec” similar to Prores or Avid DNxHD. You can look at Cineform as a 3rd party solution, but IMHO if Adobe released some sort of Prores type codec (or built in Cineform by default) it would be a really fantastic tool. I think they choose to not include this because they want to be codec agnostic in a way, but the problem is they have no good codec to output when you project is finished. You have a choice between web codecs like h.264, or totally uncompressed… there is no good middle ground.

[Lucas Merino]

Here’s my guess… Apple knows it’s not a professional grade product, but they are gonna market it like it ‘might be’ until it’s released. They set a low price point at which all of us will willingly purchase it to try it out… who wouldn’t, you know I will for $299. Then we will all find out it’s not a product built to the level professional’s need, but at that point Apple will at least have made $299 from all of us to recoup some costs of development.

Some hissy-fits will be thrown and Apple will listen silently and decide what to do based on how we start using it. They may develop it further if people keep using it (which I feel they are not expecting) or they will decide to just keep it how it is or go the Shake route.

[Lucas Merino]

Having the exact same issue today. Have footage that was shot as 720p/60 and needs in be imported with pulldown removal… when the shot comes in, it plays choppy and audio cuts out in the middle of the clip.

If I select to NOT remove pulldown (in prefs) then the file comes in at 59.94 and plays fine as well as having full audio.

Unfortunately this needs to be cut along with Red footage that is 23.976. Why they did not shoot 24p-native on the HVX I have no idea.

Any clues or leads would be appreciated.

[Lucas Merino]

Unfortunately I cannot bring the video back in to Premiere because I need to export quicktime clips is non-standard resolutions (such as 200×400, etc.)

Do you have experience with this same audio problem of importing 4 mono MXF tracks into AE?

[Lucas Merino]

Here is a situation I ran into a few weeks ago, maybe this will help you out. We were shooting on an HVX200 into a Firestore (FS-1). We found that, for example, lets say we only shot 10 minutes of footage (call them “minutes_1-10”). If we then formatted or deleted those files from the firestore and shot another ten minutes (call them “minutes_11-20”), we were not able to use those 2 sets of files (the two 10 minute chunks) in the same Avid project.

We would have problems ranging from clips not appearing in the Media Tool, to even the name of a clip pointing to completely wrong footage. The only thing we could deduce was that some sort of meta-data in the mxf files was being re-written each time the Firestore was emptied. When those clips were brought into Avid, there was overlapping info between files and everything went downhill from there.

So, the only way we have been able work with the footage has been to create totally seperate Avid Project for each time we formatted the firestore and started recording new. Not only that, but we also have to have a seperate Avid MedieFiles folder for each time as well, and need to continually rename as we open each project accordingly (just so that Avid doesn’t read the files in the same project).

Luckily we do not need to use all the clips in the same project, otherwise I think we would have trouble.

I emailed Focus Enhancements about this and they said they new about a problem and were working on it.

In any case, if anyone else has had this problem, did you figure out how to fix it?