ShowFrameNumber Positioning long, only, ability, numbers, problem

andy

Hi,

Can anyone explain a slight oddity. Using v2.08, if you use ShowFrameNumber with a .d2v input, the numbers appear on the left hand side of the image, whereas using a BlankClip, they appear on the right.

For a long time I have wanted to have the ability to overlay a frame number on videos but with the right-aligned frame numbers, only 5 1/2 characters are visible, so is only useful for clips up to 66 mins long using PAL. I would really appreciate it if someone could finally fix this problem.

As an aside, after a long period of non-development, I am trying to bring AVSGenie up to date before I even begin to consider addapting it for AVISynth 2.5+. A couple of people pointed out that using Windows numerical formats where the decimal separator was not '.' would throw the program, which was easily fixed. There were also a few updates to AVISynth since I last did much work, which I am incorporating. Suuporting external filters has always been a bit problematic for me, as their popularity ebbs and flows, and often they have large numbers of parameters which makes doing the programming and creating a neat interface a bit of a headache. So if anyone has any views on current must have filters I would be interested to hear. My own feeling is that for all the work on temporal/spatial softening filters that has been done, there is not a huge difference over the inbuilt ones. I am not suggesting that the alternatives are not worthwhile, just that the original filters were in fact pretty effective already.

For some reason the position is dependant on fieldbased/framebased video and parity. Don't know why.

Anyway I put up a feature request (to myself) about making these functions a bit more configurable and nicer to look at.

@sh0dan : For some reason the position is dependant on fieldbased/framebased video and parity. Don't know why.

Cos it's really helpful to have the frame (field) numbers non-coincident when debugging scripts of the form
Code:
...
separatefields()
showframenumber()
...
doubleweave()
...
It's a breeze to see which fields ended up in which frames.

Now what would be useful is that if the numbers where also non-coincicident between frame numbers and even field numbers so that scripts like this :-
Code:
...
showframenumber()
...
separatefields()
showframenumber()
...
doubleweave()
...
had numbers in 3 distinct positions.

IanB

Oh - smart!

Hi,

Thanks shOdan for taking note, and also for providing a clue. I have finally found a work around, though it is a bit long-winded.

AVISource(quot:\PV Small 18.aviquot;)
vid00=last
BlankClip(vid00,width=76,height=58,color=$FF0000)
SeparateFields()
AssumeTFF()
SelectEven()
vid01=ShowFrameNumber()
Layer(vid00,vid01,quot;addquot;,x=10,y=10,use_chroma=true)

This gives a frame number on the left of BlankClip, and by changing the x and y parameters in Layer the frame number can be positioned anywhere on screen.