Daniel Frome
1
COW Coin
Forum Replies Created
-
There’s no doubt that Edius is the fastest editing software out there. Not many people truly realize this.
-
No, FCP7 has had ‘range based markers’ since 7.01 I think. FCPX’s implementation is better, but same concept.
Avid’s easiest comparison would simply be making subclips. You can rename the subclips and they will always remember their link back to the master clip, so it serves the same purpose.
-
In your export settings, check on the “use marks” option.
-
Have you updated to 6.01?
Also, are you on Windows 7, or OSX?
-
We’re doing a show that shoots 15 hours of C300 footage per day. We consolidate (not transcode) with relative ease. We can consolidate 1 shooting block (40-50 hours of footage) in one day.
Don’t transcode… DNx36 isn’t that much smaller than the full rez (50mbps) material. Waste of time.
-
Apple is welcome to come film me. I will tell them what I think of FCPX ^^
-
Hi Dave —
I’ve also edited plenty in Premiere, but part of the issue is the enormous amounts of WMV and AVI files on the timeline. Although I can read these files, I fear the fact that these aren’t native formats on mac OS (I require 3rd party software to use them), I am suffering from an extra layer of code that’s contributing to the problem.
I fully realize that such a poorly organized project, combined with windows-native formats/codecs, is basically setting Premiere up for failure. I am sure that if I installed Windows 7 on my system and ran CS5.5 that way, this edit would easily see more stability and probably better performance too.
As a side note – it also shows you the downsides of a “native everything” NLE. The possibilities for error rise significantly.
I’m not sure which way I’ll go at this point.
-
Other editors actually tried to get the project converted XML. But when you’ve got complex sequences with WMV’s and DSLR footage (stuff that FCP sucks at) then even getting the entire complex edit transferred over (hardly realistic) you’re going to end up with a bunch of footage formats that don’t jive with FCP.
Trust me, the drive is littered with FCP XML files.
I finally got these projects to open on my laptop, but performance is very slow. Half the time the viewer isn’t even responding when I scrub around the timeline. If I render the timeline, then it’s not bad at all… so … rendering is what I’ve got to do.
-
While I’m at it, is there a way to insert material from one sequence to another WITHOUT nesting? I remember Ppro was missing this feature before…and now I’m really hoping it has it…
-
The “show” was not supposed to be a show initially. It was a web series produced by an ad agency. Shot mostly on DSLR (but fairly good production value). Now the idea was spun to turn it into a half hour TV program, and several editors have passed on this job because “it’s Premiere.” As ungrateful as that sounds, that’s the truth of how it ended up in my lap. The idea is to take the existing webisodes and create a proper half-hour from them.
I have some bad news though — the project looks like it was handled terribly from a media management standpoint. I’ve got multiple 5D shots with the same filenames (and it forced me to manually relink when opening the project…. not knowing which file is correct) – and it even uses plenty of WMV renders, which appear to be mixed down from other edits. There’s also plenty of “sequence within sequences” – which I also hate (but that’s probably the Avid editor shining through).
My workstation at home (8 core Xeon, 16GB RAM, CUDA supported videocard) was able to open up this project OK. But my laptop (quad i7, 8GB RAM, non CUDA card) has frozen 3 times already after opening up the project. It seems to get stuck on all the conforming jobs.
I’m already having a bad feeling about this, and might end up having to pass on the project simply because I already have a daytime editing job, and can’t fix this + finish the job in my spare time on schedule.
This is sad because I truly like Premiere… and I’ve used it on plenty of smaller projects. This is the stereotypical issue(s) that plague Premiere on every large project I’ve seen.
I’ll report back if the situation gets better.