CCE and MA scripts problems
Every once in a while I run some tests with TMPG against CCE just to see the differences.
As I already mentioned here in the forum I have many problems running MA scripts with CCE 2.6x trials. As mentioned before it seems that the problem is related to high-res video (higher than 544x576) and MA scripts. Though, I already had problems with older MA and I never had problems with all static scripts I tested so far. Sometimes it encodes just fine some 1000 frames or so and sometimes it just gets crazy from frame 0. All my CCE encoded samples show "Avisynth caught and access violation at 0x100430a0 attempting to read from 0x0e7cf194" on the top of the screen in red font. I'm not quite sure but sometimes the message could be different in terms of the shown values if I change resolution or script. Else I just can see a black background with the cinemacraft logo on the right bottom which is ok for a trial. Right now my MA script looks like this: Code:
Mpeg2Source("D:\mymovie.d2v") Code:
function MA_Routine(clip c) { Code:
function AddAudioCCE(clip v1) { At least it went way over the first 1000 frames. I believe it was almost 6 minutes ok. |
Ola rds-correia:
as you can see in my post (in KDVD thread) about "error in CCE 2.67", I also got an error in my first test, but it was from the encoder. The error you get seems to come from avisynth itself, as CCE encodes OK but with an error message from avisynth. Don't you get the same error in TMPGEnc?, I guess not, but you could tell us. In my encode, I did the resize "manually", taking the parameters for bicubicresize() and addborders() from Moviestacker, why don't you try this?, cos I get errors from gripfit from time to time. But I'm not the best person to guve you clues, since I just did one encode... Boas Festas e Feliç Ano Novo |
Quote:
|
Hi guys,
Sorry to take so long answering but my internet provider had problems yesterday... Anyway I just wanted to let you know that I'm only curious why this happens because I really do prefer (as already mentioned before) using tmpgenc instead of cce. Even because tmpgenc doesn't have these problems :D I just like to see their pros & cons against each other once in a while. :wink: But thanks any way. |
Try one using the classic resizing syntax using FitCD or Moviestacker as mentioned by Dialhot.
|
Hi Guys,
I'm sorry but I feel like a complete newbie when I try to resize using the old methods through MS of FitCD. It's just that I never had to do it by hand since when I joined the community SansGrip had already built his master piece GripFit... I have tried it using some info I found with the search button but it seams it's not enough for me. Could you give me a hand or show me a very good thread? Thanks. |
Here is a Link to a FitCD Guide translated by Google:
http://translate.google.com/translat...language_tools Go and look at the mpeg resizing part As Moviestacker is totally build on the FitCD core you can just also use this for Moviestacker Edit: Seems that this shitty Google doesn't translate totally, so here's the german link to use with a www translation engine you prefer. http://www.tu-harburg.de/~saas0262/s...d/fitcdref.htm |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.