calyx
13th September 2004, 00:32
Although this encompasses several programs, many of which have their own forums here at Doom9, I've decided I'll go ahead and post here.
So today I get up and open up each folder to view the logs for a bunch of batch encodes I did last night, and for some reason it didn't have logs for each movie, only 2 out of 5 actually. I know I checked to make sure that save to log was checked on each project - perhaps this new feature isn't working so well for batch encodes?
Next I opened the rebuild.ecl files in CCE SP 2.67. A few of them opened up fine and I was able to view what Q value for the encode is. And a few others gave me the "Frame size 852x56 is not supported. Supported rame size is up to 720x576." type error mid-way through.
I repeat this a few times, on a couple of the movies they even end up going away on. On 2 of them they always repeat in the same place.
When viewing the movie (vov/ifo format) with WinDVD, I have no problems, the movie looks great and plays all the way through without errors.
I also opened up each of the problem avisynth scripts created in the D2vAVS folder that would not load into CCE, and they played fine in Windows Media Player, and when I opened them up in notepad, they had the same lines as in the scripts that had loaded fine.
So basically, my end product looks great, all of the avisynth scripts seem to be correct, and then open up fine in Windows Media Player. Only CEE has a problem with them.
I've went over what versions of all software I have, what .dll files are stored where, etc. Everything looks good. Only thing I noticed is somewhat of a discrepancy, maybe one of the mods can help me with this.
I started out using CCE 2.5 when first using DVD-RB, and have since switched to 2.67. So the entire time I have been using 2.67 I have had the AudioDub(BlankClip()) option checked, and according to the DVD-RB Settings FAQ, it says:
AudioDub(BlankClip())
This option is a work around for a bug in some versions of CCE. It is only needed if you are using CCE 2.5 and running a AMD Thunderbird or Duron processor. See the CCE FAQ Q 14.1 and Q 14.3 for details.
So would this be a likely culprit for the problem? It doesn't seem to have caused any problems in the final encode, but something is freaking CCE out.
And I also just noticed that it said its only necessary on an AMD Thunderbird or Duron, and I have an Athlon XP Barton. So really, I never needed to use it for CCE 2.5 either.
Sorry for the long post, thanks for taking the time to read it if you did :) And I appreciate any input anyone can offer.
calyx
So today I get up and open up each folder to view the logs for a bunch of batch encodes I did last night, and for some reason it didn't have logs for each movie, only 2 out of 5 actually. I know I checked to make sure that save to log was checked on each project - perhaps this new feature isn't working so well for batch encodes?
Next I opened the rebuild.ecl files in CCE SP 2.67. A few of them opened up fine and I was able to view what Q value for the encode is. And a few others gave me the "Frame size 852x56 is not supported. Supported rame size is up to 720x576." type error mid-way through.
I repeat this a few times, on a couple of the movies they even end up going away on. On 2 of them they always repeat in the same place.
When viewing the movie (vov/ifo format) with WinDVD, I have no problems, the movie looks great and plays all the way through without errors.
I also opened up each of the problem avisynth scripts created in the D2vAVS folder that would not load into CCE, and they played fine in Windows Media Player, and when I opened them up in notepad, they had the same lines as in the scripts that had loaded fine.
So basically, my end product looks great, all of the avisynth scripts seem to be correct, and then open up fine in Windows Media Player. Only CEE has a problem with them.
I've went over what versions of all software I have, what .dll files are stored where, etc. Everything looks good. Only thing I noticed is somewhat of a discrepancy, maybe one of the mods can help me with this.
I started out using CCE 2.5 when first using DVD-RB, and have since switched to 2.67. So the entire time I have been using 2.67 I have had the AudioDub(BlankClip()) option checked, and according to the DVD-RB Settings FAQ, it says:
AudioDub(BlankClip())
This option is a work around for a bug in some versions of CCE. It is only needed if you are using CCE 2.5 and running a AMD Thunderbird or Duron processor. See the CCE FAQ Q 14.1 and Q 14.3 for details.
So would this be a likely culprit for the problem? It doesn't seem to have caused any problems in the final encode, but something is freaking CCE out.
And I also just noticed that it said its only necessary on an AMD Thunderbird or Duron, and I have an Athlon XP Barton. So really, I never needed to use it for CCE 2.5 either.
Sorry for the long post, thanks for taking the time to read it if you did :) And I appreciate any input anyone can offer.
calyx