Petros Kolyvas
Forum Replies Created
-
This won’t address your most important points – but I do think/agree media management in Premiere leaves a lot to be desired. Many of your issues are issues I wish there were answers to as well. Sometimes I have projects that rely on clips from 10 or 20 disk images and I too would like to copy the key clips out – clips imported into a project.
Regarding ProRes – it’s a $50 add-on. It’s called either Motion 5 or Compressor 4.
While, even without FCPX, I still find myself using those applications – the $50 to get ProRes alone was worth it. Plenty of companies charge a lot more for access to their codecs so even if you never plan on using them (one or the other will suffice) – you get ProRes 422 and 4×4 for use in CS5/5.5 – works like a charm!
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
We have and use the AF100 regularly and it’s probably some kind of combined issue with FCPs Log and Transfer window and possibly the AVCCAM codec.
Clips that would crash FCP7 worked fine in Premiere Pro CS5 – which is ultimately how we ended up getting them out as ProRes and back into FCP7 for cutting.
Our only guess after running into this issue several times, was that the AVCCAM import routine in FCP7 would crash when clips needed to be spanned.
I could be wrong about all this, but we’ve had an AF100 since they shipped and the behaviour in FCP7 is fine until clips span several files on media.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Todd,
That would explain why with CS5 we saw it and CS5.5 we didn’t (and not the retail vs. volume license link I proposed.)
Thanks!
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Are you asking about the version included in Production Premium or the Master Collection?
If so, then it’s in After Effects and attempting to apply it to a clip and view its interface should (grain of salt) get you where you need.
I recalled doing this on a retail copy of CS5, but the volume licensed versions don’t prompt the end user for the CF serial so I’m not 100% positive.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
One thing that is seems is a result of the app store distribution is that there is longer an “investment” in FCP licenses for freelancers/end-users.
It’s $299 for this version. It will be something in the ballpark for the next (probably) and there will be no “upgrade” path – as we’ve seen with all the Apple “app stores.”
So, if Apple does get features added to FCPX that makes it interesting for those who either a) weren’t using FCP to begin with (possible the current case for a lot of FCPX target users) b) people using competing products (probably not the case with 1.0) c) people who were using FCS but did not upgrade – it’s not like anyone looses by waiting.
As for Premiere as an option, if it’s not one now, it will become one.
Should part of one’s workflow involves Photoshop Extended, Illustrator and After Effects, it’s like you get Premiere and Encore for free. That’s how we got it, and that’s how we started experimenting with it. We were pleasantly surprised.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
[Gareth Randall] “Is it because they didn’t like FCP7 and were only sticking with it because of what they thought the next generation of the app would provide?”
I can only speak for myself and our small shop, but it’s not that we didn’t like FCP7, it’s just that if we had the choice between a Revolution (which at this time won’t work with any of our monitoring hardware or control surfaces) or an evolution that finally allowed FCP to address more memory (part of the 64-bit package), have better multi-threading/multi-cpu support (IE take advantage of the hardware more efficiently) along with a few tweaks and updates, we’d take the later.
I also think it’s reasonable to assume that over time – as many have said – FCPX will begin to develop support for all that 3rd party stuff. It’s still hot from the oven – and it’s only the first batch to boot.
However, CS5/CS5.5 is running a 64-bit engine (that’s very very fast) and can take advantage of large amounts of RAM (again to speed-up workflow) right now. It has also be able to edit many formats natively for some time. Finally, it also supports a fair amount of monitoring hardware – even if control surface support is lacking. We’ve been using CS5 alongside FCP7 for almost a year now and no client has ever cared if their project was “edited” on one or the other.
There’s still a lot we like about FCP7. It’s just that there’s as much to like about Adobe’s products.
And, as Gary mentioned, with all the promotional pricing, we’re planing on trying out MC5.5 too. In fact, FCPX and its advantages or disadvantages aside, it continues to be an exciting time for those involved in media production.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Thanks Alex, those look very good.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Hi Kevin,
Thanks so much for the pointers.
The systems have either 16GB or 24GB of RAM. I was trobleshooting on a system with 24GB of RAM. I has set it up with 4GB left for other apps (while not 25%, I had hoped that at this level of available memory I was covered), but no other apps were running; at least at then end of my troubleshooting, prior to finding the solution, I had rebooted several times and AE was all that was “active” in addition to OS/driver services.
It is, indeed updated to the most recent version – though I have found that after a short while returning it to focus from another CS5 app causes the spinning beach ball no matter how small the composition is.
As for the setting tips – I’ve bookmarked the link – many thanks for that. Part of the way I’m hoping to work is to, instead of having animators send over massive video files, simply collect the project files and assets so compositions can be rendered out as required – but that does mean I should have a handle on some of the technical issues so it will prove really helpful.
Again, thanks so much for taking the time to respond, it is greatly appreciated.
All the best,
Petros—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Turn out there seems to be a bug in the CS5 64-bit rendering engine. I had to turn of the “Render Multiple Frames Simultaneously” option and it worked fine. Took longer, worked fine.
Crazy, but at least there’s a solution if anyone else has this issue with Illustrator assets.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
One other note. I’ve reloaded all the footage, but the issue continues.
It’s like it’s rendering but missing media and not telling me so.
Another oddity is that whenever I close and open the project the composition looks like my faulty render. I reload all the media, and it looks fine, but then when I go to render I have the same issue.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger