I have my project using dynamic link from PPro. So, as it is transcoding my BR project, I get this winfile.cpp-758 error. I then let it debug and it will continue, but the output BR file just has video, no audio. Any ideas? I found nothing on this on my search.
It's never a good sign when the top two hits on Google are your post! doesn't look like a common error.
No idea, but when faced with an uncommon error, that persists after a windows restart and Encore close/open, I start testing with a new simple project, then elements of the problematic one.
I've started experimenting with looking at windows error logs to see if they add some info about what is happening.
For CS4 you must update the Roxio component http://forums.adobe.com/thread/400484?tstart=0
More on Encore and Roxio http://forums.adobe.com/thread/528582?tstart=0 or direct to
Plus, Long File Names or odd characters Cause Crashing http://forums.adobe.com/thread/588273
And #4 Here http://forums.adobe.com/thread/666558?tstart=0
And This Message Thread http://forums.adobe.com/thread/665641?tstart=0
An Encore Tutorial http://www.precomposed.com/blog/2009/05/encore-tutorial/
I just got the same error.. First time I've ever had it.. This is disc 3 of a 5 disc set I'm doing, none of the others have come up with this error.. I'm burning to DL DVD.. Will try again now, see what happens..
Unusual error combined with works on one disk, not another = Do Over. That is what worked for him this time anyway.
Dual layer requires running as administrator, but again, your other ones worked.
In any event, I suspect corrupted project, and would work through these if it is a complex project and a do over is difficult.
Troubleshoot damaged projects in Encore on Windows
I've got a little further information on this.. It hasn't helped, but it's further information - there doesn't seem to be anything out there..
Maybe Adobe can start putting pieces together..
I've cleared the cache..
I've started a new Encore project (via dynamic link in Prem) and tried to burn a basic 1 menu, I button/link disc..
This failed - right at the end..
I tried the 'transcode now' feature in Encore - it worked on the very short timeline, but the main timeline which is about 1h:45m long failed right at the very end..
I'm currently trying another disc (project) to rule out an issue with the computer/software.. Tomorrow, I'll be trying this failed one on a mate's Mac (I'm on PC).
I REALLY don't want to have to re-do this project..
OK.. So.. Disc 4 worked - so it's definately a problem with Disc 3 - and I don't think the problem is with Encore as this project didn't work even with a completely new menu...
Currently trying the 'locate file' step of the above troubleshoot doc, a lot of the things on that list don't apply to me (no subtitiles or moving menu etc etc).. But yea, I believe the problem is in Premiere and Encore is just having trouble because of this (as I'm using Dynamic Link)
I have noticed I've been getting a critical error sound when Prem & Encore open with this project, no message comes up, just the sound..
Anyway.. shall try this 'locate file' step, then failing that I'll clear all cache - then failing that, will have to re-do the whole thing..
Will keep you posted.. I realise this is an old thread, but it's a current problem which really seems to have no answer, and not a lot of information - so I figure I'll put up what I know as I experience it in the hope that somebody might be able to figure out just what's going on..
You want to export as MPEG2-DVD, with a size setting so that Encore will not retranscode.
If your timelines are the same length as other disks, you can look at what Encore picked for them. Otherwise, use a bitrate calculator.
Awesome, thank you Stan.
You would not believe this but it just went to disc!! I just cleared the cache from within Premier (which I was a bit frightened to do if I'm honest.. last time I did that, the computer didn't like me very much).. Anyway, I'd tried clearing Encore cache to no avail, but once I'd cleared the Prem Cache it worked without a hitch.. So it was obviously a problem from within the Premiere Cache...
What a nightmare.. At least it's sorted now..
Thanks again for your input, as always, it's very much appreciated!
Theoretically, either cache should work (the cache is common), but...
Thanks for letting us know. It is always tempting to think the regular things won't work, and I'll bet that clearing the cache from PR is not one that is often tried.
Yea well that's what I thought, which is why it took so long for me to try the Prem Cache clean.. but hey, it worked.. The reason I thought of it is that I've had the same thing with 'Update' - if I update from Premier, it'll update the whole suite.. If I update from Photoshop it'll only update photoshop.. Bizzarre..
Either way, I'm transcoding the master of the problem disc right now, woohoo!!
Europe, Middle East and Africa