Batch encode and source range max question
 

I hope this hasn't been asked before(did do a search) but here it goes:

1. When you have alot of movies and you need to do a prediction of them it could be usefull to have a batch encode option or a multiple instance option so that you can start cqmatic more times.

2. I know the source range should be uniticked, the problem is when you do a full encode the source range isn't set, and tmpgenc wouldn't know the movie length.
With normal encodes a source range is always needed because tmpenc would otherwise see a 90 min movie as a 4 hour movie :P
So the question is will it know the total normal of frames with a full encode so that you won't get a oversized movie?

Re: Batch encode and source range max question
 

That's hopefully wrong. TMPGENC always find the correct length and you need source range only when you don't want to encode all the movie.

I don't know where is your problem, but there is something wrong on your PC.

Well i have all the corect codecs(ace pro codec pack 5.93), and it hapends with all the movies so far..
Gonna try with a new xvid movie to see if it predicts the lenght ok(most of the others were divx3 and divx5).

/EDIT: seems to be ok now(same movies), dunno why but i did install this new codec pack yesterday mayb it was that klite codec pack that had some old codecs :P

When I say always, it's ALWAYS, whatever the source type !

Yeah but if the system has a b0rked codec it would be giving the wrong info right?
Thanks for the help :)
Now i only hope for a batch encode feature to make the encoding a piece of cake ;)

Do you use an avisynth script ?

Note: with ACE you should remove old DIvx version and keep only 5.05 one (that's what I do); That is nothing to do with you problem but 5.05 is better to handle all divx, included 3.11 and 4.12.

I usually do prediction only, then add the project to tmpgenc batch list. And procees to the next job I have to do. After this I launch the batch process of tmpgenc. It's better than nothing.

Yep i do the same first the prediction then add it to a batch job @ tmpgenc.
But sometimes a prediction takes 1 hour(sometimes 15 minutes depends on the settings) and it would be handy if it could do all the predictions at night without any user interaction and save it in an text doc with project/file name :)
I make a avisynth script at moviestacker(only change the res and fps there) then load it on a frameserver with virtualdubmod.
Then i add the vdr to tmpgenc and save the project as text.
That's what i do with most of my movies lately because some of them give errors with tmpgenc(illegal floating error or index out of range at random %).

!!!
That's is where you loose the length info (even if it's strange).

Why don't you open the avs directly in tmpgenc ? There is no need of frameserving !

Change your tmpgenc version ! I didn't have this since a very long time (I use 2.520).

But i still got the got the errors without frame serving and with it the errors are gone :?
Will try to encode a movie without the frameserving tonight to see if it gives any errors again :)
I am running TMPgenc plus 2.521.58.169 is this version ok or should i try the 2.520?
This also a fresh tmpenc install btw, already read the faq on tmpenc errors and changed the directshow priority a while ago.

Trust me : you shouldn't have this so othen. Change you tmpgenc version and update your avs version to 2.5.3 :!:

I never went to this version but I don't think it is worse than 2.520 so you can keep it.

Thanks will try with avs 2.5.3 and post the results 2morrow :)

/EDIT: Used avs 2.0.8(without frame serving) and the movie encoded fine, btw it was the same movie that always failed with those tmpgenc errors. :D