-
This program is written by monkeys on drugs!
Ive just spent 2 hours waiting for premiere to put a credit roll into my project, it has continued to crash and freeze throughout.
Got the edit done though!
be nice if i could add some credits to it without wasting my friday night due to your crap, poorly written 15 year old software.
Learn to update code, srsly.
thx adobe for screwing up my weekend! Appreciate it.
~Peter Berthet
Sydney, Australia -
9 Replies
-
Do you want help here, or are you just bitching?
If you’d like help, let folks know which version of PPro, what your machine specs are, etc.If you just need to rant, I guess that’s ok too. But not terribly productive.
cheers,
Jeff -
i agree, totally agree.
But it needed to be said. Or got off my chest.
If im working on an hour and a half project in DV thats not terribly out there as far as edits go, and the system constantly hangs, crashes and generally makes my friday night miserable.. theres clearly something wrong!
Next time im just going to use final cut, if not for my sanity then to save from going completely grey in a short timespan.
In fact id encourage anyone at adobe to go out with 4 cameras, film ANYTHING for 2 hours.
Throw them in a multicam timeline and do an edit.. doesnt matter where.. just make a whole bunch of cuts for an hour and a half – 2 hours and watch the program turn into a lumbering beast.
Ive seen it on so many systems now i cant accept its anything but the software.. these are pretty high end systems too. Its DV for christs sake, why should it take me 20 hours to render a dv timeline to a dv .mov ? Final cut does it in 20 minutes!~Peter Berthet
Sydney, Australia -
[Peter Berthet] “If im working on an hour and a half project in DV thats not terribly out there as far as edits go, and the system constantly hangs, crashes and generally makes my friday night miserable.. theres clearly something wrong!”
Premiere on the Mac is in its early days, so I can’t compare that to our PC versions, but I can tell you that it is very stable on our system.
[Peter Berthet] “Ive seen it on so many systems now i cant accept its anything but the software.. these are pretty high end systems too. Its DV for christs sake, why should it take me 20 hours to render a dv timeline to a dv .mov ? Final cut does it in 20 minutes!”
I7 920s here. A 20 minutes DV timeline takes me a few minutes minutes to render to DV, quite a bit longer for other formats, depending on compression and quality settings. Usually less then realtime however.
As far as I know, FCP doesn’t take advantage of multi-processing yet, so render times certainly aren’t going to improve.
Vince Becquiot
Kaptis Studios
San Francisco – Bay Area -
Peter – everyone has had moments of doom no matter the software. The occasional rant does feel good, but the whole point of a forum is to get responses from others.
Doing much of anything in Premiere 6.5 was pretty challenging, so it has been exciting seeing it evolve to CS4, which is pretty stable and feature rich in most cases.
I would agree that the multi-cam feature leaves things to be desired. I usually do a multi-cam edit not using the multi-cam feature.
But seriously, what is your question and your system specs. Sometimes a seemingly serious problem has a simple solution.
Mike Cohen
PS – I like monkeys and drugs.
-
I like drunkeys and mugs…..
Peter, this is bar none, the least inter-comptible software I have ever encountered. I have had 4 computers, 2 HP, 2 Dell and the software is currently working fine on my Dell XPS aside from the minor fact that YOU CAN’T EXPORT ANYTHING to ME or even DV out.
I believe this happened because of either a Flash update or a Windows update…the only 2 things I have ever allowed on this brand new computer specifically purchased to work with this software.
It’s an absolute life wasting Bear at times and I never had any trouble with 6.5
…. HOWEVER, once you get it running it’s quite stable and amazing. It uses 8 cores, it really rocks.
It is my feeling that Adobe knows they blew it on this one but they needed the $$$ so they released it early. My guess is that the next version will be more compatible and easier to install.
I hope they got the message….these posts are everywhere….. It’s a great program when it’s running. Adobe needs to realize that not every editor wants to be a software troubleshooter…. that is why Apple rules the roost for video editing to this day. Apple is for people who dislike troubleshooting and that’s why they pay 4x as much for their computers.
It’s good once you get it running. Now someday when I’m not editing 16 hours a day I’ll have to figure out how to fix that export problem.
Good luck.
Best,
Todd
Canon XH-A1’s and Vixia V30’s. Dell Studio XPS, i7 8 core 2.4gig, 6 gigs RAM soon to be 12, 5TB can’t remember video card, Pioneer Blue Ray Burner.
-
Vince wrote:
As far as I know, FCP doesn’t take advantage of multi-processing yet…
Final Cut has taken advantage of multiple processors since the days of the Power PC G4-450 systems with dual processors about 9 years ago.
Today’s Final Cut 7 takes full advantage of Apple’s Grand Central Dispatch in Snow Leopard and may move to complete 64-bit process in version 8.
What you do have problems with are the plugins. Many of those will only use one processor core. Not too long ago I tried to do some compositing with Toon-It and they were just on the cusp of releasing a version that would work in multiple cores.
I think Apple’s current low-end has two cores and a 64-bit capable processor. I have their current high-end (Dual Quad Nehalem just shy of 3GHz). Haven’t run the latest FCS on it but that will be coming shortly. Then we’ll see if I need more than 8G of system RAM.
What if there were no hypothetical questions?
-
So you mean that a straight export, with any color correction or levels adjustment etc., will render on export with all cores?
I do mean export, I know that you can work along side other apps and use all needed cores.
I don’t recall seeing that happen, but I should look into it again.
Vince Becquiot
Kaptis Studios
San Francisco – Bay Area -
Vince, when you have material that cannot be exported without rendering, the rendering engine uses all cores.
I have a tendency to do a fair amount of complexity on occasion on my timeline, which does need to be rendered before output.
As to whether or not FCP can play out multiple streams, that tends to be an issue of whether or not your hard drive array can keep up. If you have a slow array, you may need to render to avoid dropped frames. Apple doesn’t control your entire system like Avid does, so there are lots of “unknowns” in individual systems. Some are:
- What kind of card are you using for I/O? AJA? Blackmagic? etc.
- How is your array configured?
- What are you working in, SD or HD?
- How many simultaneous video streams are you trying to work with?
- Which Mac are you using for your work? Core2Duo? Single Quad Core? Dual Quad Core?
The way Avid configures systems (and pretty much guarantees results) is that they purchase fully-blown and tested CPUs, they only use their own proprietary I/O stuff (with the exception of their DS systems, which are now on AJA), they allow you only to use their arrrays and servers and they tightly control all equipment used. Add a third-party server or array and Avid will refuse to support your system.
And Premiere Pro is a lot like FCP in that respect. Adobe has no idea what kind of a system you’re using. There are certain standard systems that they can recommend but they’re not Avid. They cannot force anything on you.
Look at your timeline. If you have a green bar over all of it, you should be good to export and that goes for Avid, FCP and Premiere Pro. The way you get that green bar is by processing your stuff, which creates a render cache file that you’re reading from for those sections that had to be rendered. A render cache is one video stream.
If your system “thinks” it can play back something, it will place a green bar over that area. When I do graphics in After Effects, I export a full-resolution video file. If I import that into Premiere Pro, which is set to the DV (compressed) codec, I get a red bar over that section. Now, even though I have rendered it in AE to output it for Premiere, Premiere still wants to render it.
Output to tape should be from a timeline with a green bar.
If I do a project in Final Cut Pro and I work in Color or Motion, I’ll have to render the result in Final Cut. An 8-core system will render really, really fast because it’s using as many cores as are free. It won’t play back to tape without a render though.
What if there were no hypothetical questions?
-
Ditto on that brother!!!!!
I respectfully disagree with the other poster….I think it is very helpful to vent from time to time. If you want to talk about a waste of time, I’d say relying to the post saying it is “a waste of time to vent” is in fact….a waste of time.
These vents ARE important in posts, becuase they are searchable….and as a former developer, you can bet that Adobe sees these and cringes, and it has an effect.
Obviously you do not want the entre forum to become vents, but a few sprinklings here and there let others know that they are not crazy!
And yes….this is about the most unstable software that I have ever had the experience to work with. Simply no excuse. I’ve been trying to get through to Adobe phone support for 3 weeks, calling every few days, and the lines are JAMMED!
Let’s hope they have some major updates coming soon!
All in all, as you learn more and more, you find ways to “finese” your way through a project to get arround the many issues. The crashes are by far the biggest problem.
Cheers!
Reply to this Discussion! Login or Sign Up