Sounds good. Considering I have 12GB of memory, the more it can use the better.
That's gooodda news! While they are at it will they be kind enough to see if there is anything to be done about the following annoyances?
PPro defaults to "entire project" while exporting. I almost 95% of the time I find myself exporting the "work area bar." The rest of the 5% I am capable of extending the work area bar to cover the entire project, so that I don't include anything that might be lying on the 'workbench' beyond the 'entire' project time line. May be it's just me.
But when you install CS3 (and CS4) master collection, After it takes half an hour (?) to install the first DVD it will sit there asking for DVD #2, very politely. But you have to keep watching the grass grow to know when it will ask for the next DVD. If you are on another computer with a KVM switch, you have to constantly switch back to see if it's time. A Nero program I bought from the computer show for $3 (older version) will eject the disc when it asks for the next to be put in, which helps me even if I am in the other corner of the room. And it will detect the next disc and go on with the project without me clicking "OK", which you must in CS. Isn't it a computer? Doesn't it have the capability to eject and detect the new disc? It has, only if the Adobe engineers will let it. If it's easy for a $40 prog like Nero to implement it shouldn't be hard for a $2500 program. Then I am thinking that may be Adobe is protecting me - if the DVD tray opens up and lies there may be the kids or the dog might bite it. But we don't let the dog around when we are installing the master collection.
Another one - When you search for help from PPro it may come up with something relevant (mostly it wont), but when you refine the search, now it's telling you there are 45 related stuff in inDesign! But I am NOT asking about InDesign, I was in PPro! It has already switched my search to InDesign. Sigh!
May be the engineers are trying to help me automate the search.
Bala, are you using CS4? Because it defaults to exporting the work area. In fact there is not even a setting to choose. Your report is confusing.
> Sounds good. Considering I have 12GB of memory, the more it can use the better.
Pr CS4 already makes use of the extra RAM. What is being improved according to this report is releasing the mem when its done.
Thank you for the report. All I need is a new system, and it sounds like it's time for me to finally upgrade to CS4 via 4.1.
>Your report is confusing.
It's a copy/paste "rant" from another thread. Doesn't really belong here.
Sounds like we have to wait until May...
Gabba gabba hey! I can't wait! :)
Thanks for the report, although before NAB would be better.
If they have already tested the above updates and its not going to be out by May, I would assume that there would be other additions / fixes as well.
What's the purpose of the link? It does not have any updated information.
I think it was just to enforce that his contact is a real person.
Is Dynamic Link fixed?
At least we know it is coming, and since it is almost 5 months since 4.0.1, there are going to be a LOT of fixes.
I guess to put in perspective, once 4.1 comes out, it will have been only 1 year since 3.2
No, to put it in perspective, we have all worked for Adobe for free for six months to beta test their shoddy work that should never have been released in October!!!
(With still no guarantee that there will be fixes, only new problems)
Oh boy! Let's feel happy...:-(
i No, to put it in perspective, we have all worked for Adobe for free for six months to beta test their shoddy work that should never have been released in October!!!
And some wonder why Adobe reps don't show up on this forum more often...
>And some wonder why Adobe reps don't show up on this forum more often...
Only a part of it is a copy/paste rant.
You may be right, CS4 does it differently. I removed it so can't remember. I will reinstall when 4.1 comes around. I was thinking about CS3 when I wrote it. But the other things are still CS4 annoyances hopefully being fixed in 4.1.
CS4 is not a $79 application. Major releases of expensive software that has been around as long as Premiere ought not be released in the condition 4.0 was released in. Period.
If stating that bothers Adobe reps, or some users here, so be it.
However, Adobe will never be any more responsive than they now are with PPro as long as users pony up the bucks and get concerned when other users complain about the obvious. That certifies for Adobe that there will be little consequence to premature releases.
I have thoroughly tested CS4 and in its present state there is no way I will buy it. Maybe 4.1,if its significantly improved.
I've had no major issues with CS4 and would definitely buy it. I find it already much improved over 2.0 and CS3.
That 24p fix better be in there..............
They said after cs4.01 that there wouldn't be a new update until NAB.
"4) Premiere Pro CS4 is the least stable of any release version dating back to, oh, 5.0 (i.e. crashes often for many, often apparently random, reasons)."
Are you saying he admitted to this? and this:
"5) Premiere Pro is a resource hog, needing AT LEAST 4gb of RAM."
ALSO what exactly does this mean?:
"Premiere now has 64 bit memory management for 64 bit Oses( OSX & Vista64/Win7 64)" I don't understand your saying they'll be native 64 bit?
It sounds like there will be some added features also.
DH said he will be doing a video to show of the 4.1 update.
I would be genuinely interested to know if they solved the problems with stuttering and freezing playback and low CPU utilization that plagued CS4 on some hardware combinations. The program was unusable on a 3.5GHz quad core with 4GB on Windows XP SP2. After a month of seeking solutions, I finally had to revert to CS3, which is running okay.
I recognize many of the problems addressed, plus the playback freeze indicated by Mark Weiss. That one's a real misery maker, since it brings editing to a screeching halt.
It appears to follow a swift succession of relocating the position on the time linee and/or (more likely) expanding or contracting on-screentime linene timeline range.
Much as I appreciate the problems apparently addressed, this one is my currenNUMERORO UNO.
The stuttering/freezing, huh? I thought it was just me.
I can't complete a multicam sequence without crashing at least 5 or 6 times. I just figured it was buggy. I always submit the little crash report that comes up, so hopefully they're getting the idea. Usually I'm just scrubbing or playing back as normal. DV footage, no effects, nothing fancy.
Good to know I'm not the only one with stuttering/freezing problems. I have gotten very quick at reloading the application, though...I suppose that might be a positive thing. ;)
What's your setup Christian? I've had no major issues with DV, and it seems a lot of folks having issues are using GOP media.
Same here, no problem with DV, but it hates high bitrate M2TS on a 2.85 Quadcore with 8 gigs ram.
Ive had some funcky stuff happen with DV in Multicam. I think the are some general multicam bugs.
Yeah, multicam has always been "pretty good" in its implementation, but for whatever reason, it never likes to go more than 5 or 6 minutes without reminding me that I haven't hit CTRL+S lately.
- DV footage...sometimes downconverted HDV footage, sometimes 24P, sometimes 24PA and every once in a while 30P. At any rate, the files themselves are generally DV AVI type 2.
- Windows Vista Ultimate x64
- Intel Core 2 Quad 9550
- 8 GB RAM
- Quadro FX 1400
- Files and OS on multiple 7200 RPM SATA and eSATA drives (let's see, there's a 750 GB drive, 1 TB drive, 2 TB RAID 5, 160 GB drive, etc)
- Asus mobo....I forget the model...P35 Intel
- Webcam (don't ask....well, unless you have a credit card. Do you have a credit card???)
At any rate...multicam is the only big problem-maker I've run into in an average edit, and it seems to be consistent regardless of how complex or minimal the sequence nesting is.
Actually, when I think of it...there's only one multicam I've done lately that didn't crash even once, and it was using MPEG-2 and WMV files. Huh, go figure.
That is a good news about updates. And I hope they will include a Scene detect for HDV HD capture as well as HD preview during the capture. Those features exist in DV but feels like this part of the software was never finished.
I have never had a playback problem like you guys describe above. My pc is Quad Q6600 cpu 4gb DDR3, dual nVidea 8800 with 640Mb ram on each video cards and 3tb of HDD space. Using Win XPPRO SP3. I have all the drivers up to date, and even updated BIOS for motherboard before installing CS4.
Few problems I encountered, when you scrabbing a video and then clicking back before the point on the time line where you start scrabbing, the premiere may freeze for few seconds and then come back or may crash with core importer error message.
Another problem I found is during the export. When audio filters are used in audio mixer for track and one clip has its own filter that clip will be out of sync after export. But as soon as that clip finished playing everything come back to normal. And the most interesting part is, does not matter how you set audio tracks to output thru a submix track to the main or all to main it is still gives the same error of rendering clips with filters with out of sync.
I have submitted a bug report few times will see what happens.
Other then that I did not have any other problems with CS4.
Also I have noticed that the Show Frames feature on time line shows the preview on the time line with a lot less quality then CS3 or CS2.
>it never likes to go more than 5 or 6 minutes without reminding me that I haven't hit CTRL+S lately.
Improved memory management giving RAM back sounds good if it works with Vista 32bit too. We wait to see...
Any new news on the arrival of 4.1. I guess there wan't any announcement at NAB? Anyone drag any info out of Adobe reps?
Don, I guess you do not read the forums completely, there is a thread on NAB 2009 which has all the information
Yes, I have been here very little lately--been up to my ears in it on a huge project that keeps me up until 2 every night to make a deadline