Thanks for your fast reply...
>If you set AutoSize to TRUE, the video size should be always the original clip size (320x240).
nope, not true with me , the resulting size depends on the size the video was (set with DisplaySize = <value>) before I set Autosize = TRUE...
>If you set AutoSize to FALSE, the video size should follow the DisplaySize arguments.
nope, not true with me, the videosize changes only after 1) setting AutoSize = FALSE 2) setting DisplaySize = <value> 3) changing AutoSize = TRUE again...
strange huh?
btw, the resulting sizes seem to be OK: 'Double', 'Halfscreen' and 'Default' seem to give absolute (res-independent) video-sizes, 'OneHalfscreen' gives a relative (res.-dependent) size. Is that right?
also setting avclip.XY seems to be executed later than immediate after I set the var...
>If you set AutoSize to FALSE and set DisplaySize to FitToSize, the video size follow fas.avclip.rect.
true, DisplaySize = FitToSize always gives me the exact sizes I specify.
But due to performance-issues I cannot make use of this all the time. I recon that if I use a resolution independent videosize the load on CPU will be smaller when my swf is scaled other than 100%. Don't you think so?
>You mail email your fla to
[email protected] with your order receipt(If you are a registered customer) for troubleshooting.
We will register, but only after we are sure that FlashAnts qualifies for our current project. Controlling exactly what and how the video plays is one of our biggest issues we are investigating momentarily.
My impression is that controlling the videosizes is somewhat random or at least indirect. Can this be related to the version of the FMPlayer browser-plugin? You released version 1.5 but my test-machine had the version prior installed and never asked me to update...
tnx Hank