-
1. Re: Transcode problem in Encore after 5.03 patch applied to Premiere Pro
Andrey V Dec 14, 2010 10:53 AM (in response to Andrey V)Looks like no one really knows what could cause this?
I have reinstalled the hole Master collection ran updates, but it did not fix the problem. When 5.02 update was installed on Premiere Pro everyting was fine.
So I guess I will have to go downgrade to 5.02 and finght with disolves and other transitions wrong behavior when gpu is on.
Thnaks my favorite Adobe.
-
2. Re: Transcode problem in Encore after 5.03 patch applied to Premiere Pro
Stan Jones Dec 14, 2010 6:19 PM (in response to Andrey V)No idea. I haven't installed the 5.03 update yet, and was toying with the idea of trying a test before and after.
I have reinstalled the hole Master collection ran updates, but it did not fix the problem. When 5.02 update was installed on Premiere Pro everyting was fine.
So after seeing this problem after the 5.03 update, you reinstalled, updated 5.02 and had a success, then updated 5.03 and had the same problem?
Definitely file a bug report. If this were a common problem, surely we'd have heard more from other users. But that doesn't mean it might not be a bug.
-
3. Re: Transcode problem in Encore after 5.03 patch applied to Premiere Pro
Andrey V Dec 15, 2010 11:40 AM (in response to Stan Jones)Well, prior to 5.03 update I had everything working I had 5.02 update, and transcoding AVCHD to blue ray and DVD was just fine. I have done couple of projects with AVCHD format and also transcoded them to regular DVDs using Encore. Now since there was a problem with disolves and Adobe says that the problem with wrong transition behavior was fixed I wanted to update, so I did. But could not transcode, So everything was reinstalled but that did not fix the problem. So I looked into a project and I had on one spot of the Audio track used keyframes to increace level. Deleted those and was able to transcode to Blueray. Now I am trying to get DVD but it has been transcoding for almost 6 hours and still not done. CS4 transcodes the same project under 1 hour. So I dont know what is wrong.
I submited the bug report. I will create smal project with the same keyframes used, so then I will upload that to the web and post the link here. And hope if anybody will be willing to test that and post the result. Other wise I will have to roll back to 5.02.
-
4. Re: Transcode problem in Encore after 5.03 patch applied to Premiere Pro
Stupid screen name rules Jun 10, 2011 3:13 AM (in response to Andrey V)I'm having the exact same problem with transcoding stopping at same place each time when selecting Transcode now DVD. I have tested the same project on 3 very different Windows 7 64bit systems with the same results. Tested on two different systems running Intel i7 processors with 16GB non-ECC DDR3 RAM in Dual Channel and one Intel Dual Processor E5620 Xeon with 12 GB ECC RAM in triple channel mode.
I am convinced that it is not a hardware issue and after reading your post I suspect it has more to do with transcoding our H.264 code raw footage on this newer version of Encore CS5.1 with Premiere CS5.5. I also setup my Encore project with dynamic link to my Premiere projects sequences. I first open Premiere then I open Encore and try transcoding. I have also had the same thing happen with MediaEncodor. When first starting the transcode now process it runs my CPU at 100% for a good 5-10 minutes and the memory usage slowly climes from about 30% to about 70% and then all of a sudden my CPU usage drops to about 2-15% and my memory usage jumps to 98% and Windows 7 OS comes to a super slow pace that is borderline frozen. With enough patience I am sometimes able to close Encore down normally after waiting 20 minutes.
This never happened in Encore CS5.0 with Premiere CS5.0.
@Adobe - This is definitely a bug that needs fixed.
Thanks,
David
-
5. Re: Transcode problem in Encore after 5.03 patch applied to Premiere Pro
Harm Millaard Jun 10, 2011 3:19 AM (in response to Stupid screen name rules)David, it sure looks like your source material is at fault here. A clip that consistently causes this on different machines, where the only commonality is the same source clip. Try to remove the faulty clip and then try again.
-
6. Re: Transcode problem in Encore after 5.03 patch applied to Premiere Pro
Stupid screen name rules Jun 10, 2011 3:41 AM (in response to Andrey V)It is very unlikely that it is a faulty clip as I have tried transcoding all 4 of my Dynamicly linked sequences from Premiere and have the same problem with all of them. I also tried it on fresh footage with the same results. I am now reverting back to the CS5.0 products to test it out and if it is the footage I will know it.
I smell a CS5.5 bug.
-
7. Re: Transcode problem in Encore after 5.03 patch applied to Premiere Pro
Andrey V Jun 10, 2011 10:07 AM (in response to Andrey V)Well it seems like it is problem of a premiere CS5, because CS4 does not have this kind problem and it is installed on the same machine and using the same project it works fine..
-
8. Re: Transcode problem in Encore after 5.03 patch applied to Premiere Pro
Stupid screen name rules Jun 10, 2011 4:51 PM (in response to Andrey V)Update.
After uninstalling the CS5.5 Master Suite and running the Adobe Creative Suite Cleaner Tool I installed the CS5.0 Master Suite and opened up the same project file I was using in CS5.5 and same source video footage. Premiere CS5.0 detected that the project was from a different version and converted it then it conformed the source video files and all was good. So I opened up Encore and setup a new project the same as I had done previously with CS5.5 with the same transcoding settings on the dynamically linked sequence files from the Premiere project. Clicked transcode now and it has been transcoding at 100% CPU usage and 40-60% memory usage it has been transcoding for about 8 hours now.
However, it did have one instance where it did like I had previously described were the CPU usage sudenly dropped to about 5-10% and the memory maxed out for a good 20 minutes but then pulled out of it and has not had a problem since then.
In Windows Task Manager it shows that it is Premiere and not Encore that keeps sucking up all the memory when transcoding.
By the way we are using 1080p with a mix of both 23.97fps and 60fps footage shot with a Panasonic HDC-TM700K.
I hope Adobe can figure this out soon for us. I'm considering switching back to Final Cut Pro when the new version X comes out this month if it works better for me. Hopefully that will not be necessary. *hint hint nudge nudge*




