Petros Kolyvas
Forum Replies Created
-
I think, and I could be wrong, but Dynamic Link is much more like placing a Motion project on the timeline than XML exchange.
Let’s say a motion graphics artist does a bunch of animation/lower thirds in After Effects. We’ll call that file L3.aep. Each “Lower Third” is a composition.
In Premiere you can import a AE project (L3.aep) and when you do so it will ask which compositions you’d like to link. You can use any you’d like, on the timeline just like you would use a Motion project on the FCP timline. It works almost exactly the same way with the differences being you have to import that AE project into the PPro project and can’t just drag a project onto the timeline. But as far as I can tell, that’s it.
In this case there’s one distinct advantage: One AE project can contain all the Lower Thirds and/or motion graphics you’d need for a given project; you wouldn’t need a massive folder full of Motion projects which can be overwhelming sometimes.
I’m sure others with more experience can chime in here but we’ve been testing CS5.5 out very heavily in the last few months on one of our three FCP workstations and for the most part has been a suitable replacement for FCP7 – it’s dramatically quick and just about as stable. It works well with Pro Tools for audio mixing/editing and so far the issues have been very minor.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
I’m not sure what the issue is, but AME has been very reliable for us in two edit suites, one running CS5 and one running CS5.5. There are some features we’d like to see added to achieve parity with other media encoders, and we’ve been submitting them to Adobe, but overall the solution has been a fast, predictable one.
It can, on occasion, take a while for the encode to start depending on the project length even in CS5/5.5. We recently rendered out a 1080p30 timelapse video (with some 2000+ 5MP stills on the timeline) and while it was only about 4 minutes long, it would take a while to “send/queue” to AME and then just a long to get started, this on a current-gen Mac Pro with 24GB of RAM and using fast drive arrays and SSD scratch/destination disks.
If you do wait, does it work or does it crash?
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
My suggestion:
Setup your own network between the two Macs until the IT/IS admins realise they’re being silly.
Requires:
– 1 Network cable (usually cross-over, but I’d be surprised if the ports weren’t autosensing MDI/MDI-X on modern macs meaning you could use any old network cable so if you have a network cable lying around try that first.)A rough sketch of what you could do:
– Connect one of the Ethernet ports on the Mac Pro to the Ethernet port on the iMac.– Setup each machine to be on the same nework. Use a static address for each (for example, 10.0.201.1 & 10.0.201.2 or use the more common 192.168.x.x. nomenclature) under the network perferences.
– Turn on “File sharing” under the “Sharing” pane in system preferences.
– The machines should be able to see each other at this point. (You should see them listed in the Finder sidebar or under the Shift-Cmd-K/Network location in the Finder with public/dropboxes listed)
– Create duplicate user accounts on both machines. IE. you’ll need to make sure a username/password for the two of you is on BOTH machines.
– Set the permissions on locations you’d like to share (preferrably using a tool that allows you to control the ACL/Access Control Lists on folders). Do some reading on ACLs – tools like Tinker Tool will help out with setting up inheritable permissions on shared folders. Why is this important? It makes sure that when you’re creating/adding/deleting folders/directories on a shared location the permissions are propagated correctly.
– Share those folders/directories (again under the Sharing pane.)
– Test it out (copy some files, open files, save files).
….profit? 😉
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Source format and H.264 target settings would be a start to help us diagnose the issue with you.
In Compressor were you using a preset or did you customize the settings?
We use AME to export h.264 (in an mp4 wrapper not mov – though it should make no difference) and are very pleased with the results; not to mention how much faster AME is than Compressor.
One issue with AME is that sometimes it tries to use a difference framerate than the source material (for example the Vimeo HD preset attempts to compress pictures at 29.97fps when our sources are most often 23.976.) Otherwise, it’s been pretty reliable.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
JB –
I should have mentioned both Mac and Lion more clearly. Your advice is sound – this was the very first time I’ve ever upgraded any system before a .2 or .3 release by Apple.
In our case, with the exception being the timecode overlay – the transition to Lion was relatively painless. Adobe was pretty quick on the uptake and there’s only one production system here actually running Lion.
The other two are still in 10.6 land. Even the Lion machine had it’s 10.6.x partition maintained so any projects or serious issues could be averted while we “tested” Lion out.
Best,
PK—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Thanks Todd.
I’m sure you fine folks will eventually get it sorted. It hasn’t stopped the Premiere train from rolling on in our little shop. Premiere Pro worked for about 10 hours without a crash today – it did eventually crash, but 10 hours is pretty spectacular in this day and age; I’m also pretty sure it was the Matrox player that eventually dragged it down…
So despite continuing little issues, thanks for all the hard work.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Wasn’t Timecode burn in listed as a non-working Lion issue – works fine under 10.6.8 but it was in Adobe’s original list of Lion issues… I’m not sure a new thread needs to be made:
https://forums.creativecow.net/readpost/3/915214
I was just surprised it wasn’t on the fix list and still doesn’t work under 10.7.1/5.5.1
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Thanks Todd.
It appears the Timecode overlay fix is not on the list and I can confirm it still isn’t working….
Out of curiosity, is this an infrequently requested feature? I don’t think a single edit has left here in a draft stage from FCP6-7 without a Timecode Reader overlay (sometimes multiple overlays TCR and TCG).
Other than that, I’ve found 5.5.1 to be massively improved with MXO2 performance and an overall good increase in stability. So here’s to hoping Adobe keeps listening….
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Hi Eric,
For some reason – when Adobe announced the PPro update – they noted it wouldn’t be available through the Adobe updater for a week or two. Not sure why….
I found the MXO2 equally flaky with AVCCAM. It’s better now, I was editing 1080p24 AVCCAM for the last couple of hours and the MXO2 didn’t quit on me once.
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger -
Quick question; have you installed the Premiere Pro 5.5.1 update? I just did, and while I’m on 10.7.1, the MXO2 is running better than it has in a long while. The MXO2 (mine also has MAX) used to simply not play out of Premiere most of the time, now it seems quite reliable (this after just one evening though so gains of salt and all that.)
https://blogs.adobe.com/premiereprotraining/2011/09/adobe-premiere-pro-cs5-5-update-bug-fixes-mac-osx-v10-7-lion.html for the update if you need it.
Adobe doesn’t mention Matrox specifically in this release, but Matrox did explicitly note Premiere Pro 5.5.1 in the latest MXO2 driver release (even though 5.5.1 wasn’t out yet.)
—
There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger