Paul King
Forum Replies Created
-
Hi Alex
For me all the source is used in the project. They are mostly PSDs so there is no excess footage.
Thanks
Paul
-
Hi Richard
I do not have a name for you, all I can say is that I can confirm what you are seeing. I wouldn’t worry about pushing them on this as I know the OEMs will do it for you. They’ll take to the right people and will come up with a resolution.
However the good thing is that you know when it’s time to say and restart as you get prior warning. As far as I can remember Premiere would always take a long time to open large projects. I agree that it’s too long at the moment but I think they have definately taken a large step in the right direction. We can at least use PSD files in Premiere without a memory problem with them (the current problem seems to be there whether PSDs are used or not – as confirmed by Bill who’s project is using thousands of video files). I currently have a project with 2,000 PSD files imports as multi-layer PSDs.
And again I am really curious to here from those who have seen large projects on other systems to let us know what those systems are like.
Paul
-
Hi Bill
How much did you pay for Adobe tech support? Here in Australia I think we pay $3.00 a minute to have someone read the manual back to us. I suppose this teaches peaople to read the manual (not that it helps with these issues).
Have a look at RAM usage when you get the low system resources message, I’ll bet it’s hovering just under 2GB despite the 3GB switch.
As you said things are a lot better since v2. Does anyone know what other NLE apps are like with large projects?
Paul
-
The 3GB switch is fine but you will still get problems with RAM. The extra GB will do nothing for Premiere, in fact it may make things worse.
I am running an Axio with 2 and can see the same problems, what appears to be a lockup which then comes back and large project files (mine is currently 43MB) and they take about 5minutes to open. However they are more stable than they were with 1.5 and like Bill, I can now work on projects that I couldn’t do under 1.5 (I had to split them up).
However despite the amount of RAM Premiere gets, there is an underlying problem with another aspect of memory allocation that is causing the crash warning message. I can not discuss this issue here but I would recommend lobbying Adobe at NAB.
Paul
-
How much RAM do you have? 4GB? Hopefully not because it could be the root of the problem.
Paul
-
None of the filters are multithreaded in Premiere. However the media encoding is. I wish they would improve rendering speed, they seem to have been ignoring improving performance of Premiere when it comes to filters. If you have used Vegas (which I really hate) you will have noticed how fast and efficient it’s rendering is. I could never understand how one of the bottom end NLEs could have the best rendering engine – even better than Avid.
Paul
-
Ask Adobe, yes. But actually no. You wont see much benefit with Premiere alone. However Axio functions are fully multithreaded.
Also it’s not parallel processing, it’s multi-threading which is a bit different and gives better results for content creation.
Paul
-
What Larry said was correct but you need to be on the same font. The character map is the rightr place to start. Easiest way is to use it to copy then paste in titler.
Paul
-
Not sure that this is supported, I get the same error.
Wait till version 2 of Axio, it will make Canopus Procoder redundant as the Matrox encoder is super fast anyway.Paul
-
I think the Toshiba LCDs look better.
The JVC range of professional CRTs are a good buy too.
Thanks
Paul