Registax resampling and invalid floating point

[iceman]

Why is it that some avi's will error out with "Invalid Floating Point" when trying to resample, but others don't?

Is there any common cause? I'm trying to upsize my ganymede image and it's crashing EVERY time :(

[Robert_T]

It's annoying isn't it, I find Registax 3 a very "buggy" program that regularly crashes and gives that floating point error. The only solution I've found when it takes a dislike to one of my avis is to open the avi in Virtual dub and resave it as an avi from there. Works for most things then back in Registax.

cheers,

[iceman]

hmm i'll try that, thanks.
I was just able to resample the ganymede avi by using a bigger alignment box (256 instead of 32).. very buggy.

[davidpretorius]

i used to get that during resampling when the images were not centred (ppm centre). as my tracking is not spot on, any sort of drift seemed to give the resampling the you know whats!

[iceman]

Yep, that's my problem too.. the next problem is though, the moons are too small to use on ppmcentre!

[davidpretorius]

i tried this last week with a -width=500 -height=400 and different combos, but it started to get fiddly/frustrating so i gave up.

the only other way is to maybe "save the avi" at the stack stage from memory and then load it up again. i am thinking it saves the optimised centred alignment box frames as a movie?????

[asimov]

I only get that problem if the AVI is bigger than 2300 frames. 2200 & less is ok....that's with no resampling in V2.

[Muddy Diver]

I'm also geting it while trying to adjust the wavelet setting of a reference image of only 20 -40 frames!

My avi's are only 400 frames long most of the time. I get through it while my cursor changes to (and stays at) an hourglass, but I'm not sure that i'm adjusting anything.:shrug: