David Cherniack
Forum Replies Created
-
[Tim Kolb] “since you can’t open multiple projects at once, I am assuming you simply copy to clipboard and open another project and paste?”
That’s correct.
I haven’t tried it with a timeline that includes subtimelines yet. If it works it’s also a way to consolodate a project from a timeline by pasting into a new project.
Remember to copy from the project window.
David
-
This JUST may be an important discovery. Then again it may be old news that I’m not aware of but I just discovered this tonight with my editor.
It appears on our preliminary testing that you can copy and paste sequences and bins from one project to another. If the source material already exists in the receiving project, and is in the same place as in the donor project, it will be accessed by the sequence. If it doesn’t exist it will be imported.
This works well with DV material. With HDV material on my Axio the sound wasn’t present in the pasted sequence until I did a match frame in each track.
It would appear that Adobe has put the hooks in PPro2 for importing timelines and bins in PPro3. There may be some gotchas in the process but it sure can be useful.
-
[Tim Kolb] “FCP deals with QuickTime of course and that would be the one thing I’d wonder about”
Yeah…should be possible to fool it by exporting from PPro as QT and batch renaming them to avi’s to match the original file names.
Still…reading the AutoDuck forum it seems that the workflow back to AE is limited and then there’s the question of how solid is the AE>PPro workflow. With a whole whack of stills that need to be animated in this edit, it seems to me that I should be thinking PPro all the way.
David
David
AllinOneFilms.com -
Thanks, Tim.
I’d enjoy working with you but the way the film is funded requires payment to a Canuck for tax credit purposes, and specifically an Ontarian ( so I don’t have to duplicate paperwork for another province.)
My email is davidc@AllinOneFilms.com
A question that occured talking to a FCP editor about a possible workflow:
It’s an HDV project that I’ll be onlining on the AXIO for it’s realtime magic. I’ve ingested the material with scene detect (AXIO does that even though Adobe doesn’t) and sorted it into bins by scenes. I’ll batch convert the the clips into DV files (see https://forums.creativecow.net/cgi-bin/new_read_post.cgi?forumid=132&postid=856145 for my workaround of the lack of a render que in PPro) with matching timecode (I tested and that works ) and put those on a portable drive. At this point I’d hand the project and drive to a PPro editor but if I can’t find one that’s suitible a FCP editor might work if the Automatic Duck plugin will take the AAF file exported from the Axio (it’s just clips and bins – no timelines.) On the way back it would be an edl – worst case scenario – or best case scenario – using the AutoDuck plugin to export the FCP project as an AE project, and then into PPro for the online and finishing.
Have you or anyone else tried this workflow? or at least the first leg PPro’s AAF to FCP? For the second leg maybe I’ll also post in the AutoDuck forum.
David
David
AllinOneFilms.com -
Adobe make a dumb decision? Surely not.
We now return to manipulating clips in the delightful Project Manager.
David
AllinOneFilms.com -
[Arlen Bell] “I understand the next release (maybe a “dot” release) of the suite will include 64 bit support.”
My guess is that Adobe will provide a 64 bit version of PPro as their brilliant solution to the horrific memory management issue. In other words, those of us who do large projects with large graphics will have to throw together new systems (maybe) with multi-GB of ram (a certainty). The mind boggles at the potential incompatabilities.
David
AllinOneFilms.com -
You didn’t give much info about your project but, generally speaking, your situation shouldn’t be as bad as you describe. PPro has a serious memory management issue but unless your project is huge you should be able to get around it most of the time.
First, reduce or eliminate subtimelines within subtimelines. Just go one level deep.
Second, if using large graphics, work with smaller proxy files.
Third, PPro 2 will use 3 GB of ram. Adding ram helps.
Fourth, consider splitting up your project, if possible.
Fifth, let Adobe know about it! They should have provided a better fix in 2.0 and chose to concentrate on other things. We should not have to wait 18 months for them to fix a problem which should have never been in the software in the first place.
David
AllinOneFilms.com -
[Mark Palmos] “do you mean keep it to one sub-timeline depth, or to have only one layer of source on a sub timeline?”
I mean one sub-timeline in depth ie no subtimelins inside sub-timelines. That Helps PPro’s speed and memory management issues with long sub-timelines. It also allows relatively efficient trimming of projects. Unfortunately, with my double system sound in this project, I couldn’t do that. My 17 hours of interviews became 17 hours of subtimelines.
Alpha canals? They can be more painful than root canals.
David
AllinOneFilms.com -
Hi,
Sorry for the delay in answering. I’ve been wrestling with the monster (PPro) and am writing this while the project is re-loading for the 4th time today. (it’s 10am)
Victory, I’m editing on an Axio running an HP 9300 with dual-dual 275 Opterons and 3 gigs of ram. It’s a smoking system and I hate to think what shape I’d be in if I was on anything less. The issue is the memory management architecture of PPro, nothing else. Adobe is well aware of the problem but has chosen not to completely fix it yet – I guess because it only effects those with really large projects or who are running lots of large graphics.
I can only re-iterate – if contemplating a large project proceed in a way that you can easily break it up. I began my project in 1.5 assuming that the memory management was so poor Adobe would fix it in 2.0. While they did improve it, it is no way completely fixed as my numerous restarts attest. As I’ve pointed out elsewhare Matrox provides a utility to monitor memory usage by PPro. I can usually see when I’m about to hit the wall and restart before PPro crashes.
They really have to fix this if they expect to be taken seriously by long formers. Would the time I save by Axio’s real time be worth the frustrations of PPro? I’m not sure but I have my doubts. The frustartions at this point in my project are immense and are starting to get me down.
David
AllinOneFilms.com -
[VINCE BECK] “Premiere does have issues with large projects”
Hoo Haw.. Some of us working on large projects have come close to slitting our wrists. In a related vein, Avid has very robust media management. PPro’s is rudimentary in comparison.
David
AllinOneFilms.com