I am (a joker) :lol:.
And I believe you as the same has happened to me :wink: it's true too.
Cheers

That will end up in a HELLL low speed of mencoder as RDS figured EXACTLY that out! It seems theres a bug in mencoder which drops down the speed of encoding to approx. 3fps! when doing this 8O

But you get your correct film pixel area encoded, without anything else :!:

Edit: I don't see any speed loss, at least the tests I did with MencoderME, which does exactly this :roll:

-kwag

@Kwag,
But, Karl, by loosing at least 30fps and going down to something like 2 or 3fps on my new AMD Athlon XP 2400+ :roll:
I don't see that as reasonable.
There's got to be a major bug there :!:
But yes, as soon as they take care of it, I would use that method too.
Cheers

Nope. Something is wrong Rui.
With the file generated by MencoderME, which does this (first line of temp.conf) : vf=yuvcsp,scale=::0:0:60,crop=0:0:-1:-1,unsharp=l3x3:0.6,hqdn3d=3:6:2,unsharp=l3x3:-0.7:c3x3:-1.5,noise=3th,expand=704:480:-1:-1:1

I get 6 FPS on my 300Mhz AMD K6, FreeBSD server.
I just made that test. So it must be some other issue :!:

-kwag

Maybe a build issue?
I encountered that too .... so which build are you using Karl? The latest from VM or the latest offered in the CVS Snapshot Thread?

I didnt updated it to the latest till now as RDS reported probs. when using Dshow Makeavis.

Ill keep an eye on that and will do tests again. :)

Hi Inc.,
It could be a CVS issue but remember that Karl is using it under FreeBSD :!:
That couldn't have been downloaded from OUR latest CVS builds :D.
But I'll try it again tonight with older builds and I'll compile the one from today and give it a run for it's money :D.
Cheers

I'm using MEncoder dev-CVS-040430-00:00-3.3.1 (On Windows)

On FreeBSD, I have:
-kwag

Version updated to 1.02.2

- read change log

;-) Inc.

Inc, can you please change your filname strategy ?

- always have exe named packshot.exe
- name the rar according to the release

This way we can archive the different releases in a download directory and don't have to change the link 'Packshot" in the start menu of windows to point each time to the correct version :-)

makes sense! Thanks for the hint ... next release it will be like that. :)

Hi Inc.,
With so many problems with folks trying to put makeAVIS to work with mencoder I think you could add a check box named "debug" that would add a "pause" as the last argument of mencoder.
And I don't think it will be useful for anything else but at least we'll track down other guys problems with Avisynth/makeAVIS faster.
Cheers

Perfect idea, Rui :!: :D

Hi Inc,

As I posted, I'm now involved in encoding a home-made video. It's a capture, and I'm trying to keep interlaced.

I remembered then some useful settings in mencoder for interlaced sources. Here I go: you could put a check-box in PackShot (something like "interlaced source" or "keep interlaced") for those who want to keep interlaced the film. And by clicking it, there could be applied some useful parameters in mencodings:
- in lavcopts you could add :ilme:ildct: (mencoder uses a specially designed motion estimation and dct algorithm for interlaced sources).
- in filter chain, you could add il=d: at the begining of filters and :il=i to interlace it back.

Well, just in case you find it useful, as I don't think this will mean changing too much things in your GUI.

New requirement : I don't know if Purebasic allow to set the priority of child subprocess but if it does, it would be nice to have a box where to set the priority (iddle, normal, high) that the command shell will have.

@ DigiDoc

I know the iDCT filter settings.

But there are some issues when using il=d,........,........,........,il=i
Some filters do not like deinterleave function, espaecially the hq3dn filter as it does not filter only temporal but also spatial and that causes strange effects when using il=x.

As you see in PackShot a checkbox for interlaced encoding is available but still disabled. The next days Ill find the right filter allocation for settet interlaced encoding OR the Mencoder filters will be switched OFF when doing a interlaced encoding ... as Im quite shure that avisynth still offers the best methods for treating/filtering interlaced material.

@ Phil
Its not that easy, I think it will be possible via API, but Ill look around how to get that option enabled.

Thank you :-). Don't spend too much time on this, that still can be done via task manager.

It's me again :-)

I want to make a poll about something : I'd rather to have the process.bat file that is generated into the target directory rater than into the mencoder one. And perhaps having the name 'targetname.bat' insteed of always be called 'process.bat'.

I don't know if others than me will find this usefull.

:arrow: All suggestions are welcome! ;-)

I offer you the following two options where a) is the most incomplicated, Ill explain you why:

a) The created bat file will have the specified target name, so youll have a collection of bats according to your done encodings in a new folder like "jobs" instead of generating it in the "engines" folder ... and from this "jobs" folder also then the bat files will be processed. :arrow: would be my choice as by this you will get by the time a collection of all your encoding settings in one "jobs" folder ;-) :!:

b) Its possible to put the encode.bat file into the target folder to where youll encode to, BUT (and here comes the problem) you would have to set the mencoder path in your system variables OR we do put generally mencoder in the Win sys32 folder from where everything can be processed by just putting the name of the engine in fron of the commandline instead of pointing the whole path. As every user gots his own path where he gots his mencoder folder ... the systemvariables or win sys32 folder solution would be the only solution if we would go for option b)

I think a) is more sexy, isn't it? :)
(In case of avs I have been doing that already for a long time, collecting ALL my avs scripts in a special "avs done encoding scripts collection" folder from the encodings I have done)

hum... not for "average" people. The idea isn't to have a collect of all bat files we used to generate, but to have any files needed for a given job in a same directory.

For instance, in my working directory I have : AUDIO_TS and VIDEO_TS directories, the d2v project, the avs script, the ac3 files demuxed by DVD2AVI, the sub/idx files. I generate the m2v and mp2 in this directory. I have ANY file involved in the process except the .bat :-(

Let say I open a text editor. I open the avs script, and want to see also the bat. Menu -> File -> Open... Oh sh!t I have to navigate till the engine directory...

Very annoying on the end. No ?

Note: I'm sure Purebasic allows to find the current working directory (cwd in PERL) that you can add in front of mencoder command into the bat file.