Quality Problems

[jordi]

I'm building a little project of a friend art exhibition...

I'm using the last pano.swf, and also updated the autorotator, and hotspot plugin, but as you can see here (http://caloliaire.com/vv/academia/), the problems with the visualitzation are very clear...
I hope it's just about parameters, and even I have been trying many number combination for frame rate, quality motion, segments , ... I can't get with the optimal one, and I just get a very bad quality :?:

I'm using mov's, and I was trying to use cube but the same happened

here are the parameters I'm using for this project :

panoType = mov
panoName = panos/1bn
loaderBandwidth = 600
loaderStreamed = 1
disableLoading = 0
segments = 30
frameRate = 40
qualityStatic = high
qualityMotion2 = medium
zoomMin = 0.7
zoomMax = 1.3
tiltHome = -4
panHome = -124
behaviour = 2
sensitivity = 100
keySensitivity = 30
friction = 0.6
threshold = 0.000001
loaderBackColor = #000000
loaderTextColor = #000000


and here the XML (http://caloliaire.com/vv/academia/dopo.xml) file... I make autorotation speed very low so when autoplaying you can see good quality, but when you drag the mouse, then the jerking and framerate interruption starts...

can someone help me to make it turn smoothly on a standard computer?

thanks in advance

[DMCDigital]

What is a standard computer ? I have a laptop i still use from 1999, one from 2002 and a desktop from 2005...to me these are all standard...please let us know what you are running for hardware and OS.

[jordi]

For me standard computer must be something like what you say 4-5 years old, pentium 4, 2GHZ processor, and 1G of RAM, and a quite simple graphics cart...

I'm working on a dell station from last year, which I'm extremlly happy, so it must have enough power to run any panorama...


Could you see the jerky effect on the example link I have insert above (http://caloliaire.com/vv/academia/) ?

[tzes]

Your quality settings will strain any computer, new or old.

Try: segments=25
qualityMotion=low
qualityStatic=medium

and for the autorotator quality = low

[HansNyberg]

The xml is different than you posted.
It says
segments = 30
frameRate = 40
qualityStatic = high
qualityMotion2 = best
zoomMin = 0.7
zoomMax = 1.3
tiltHome = -4
panHome = -124
behaviour = 2
sensitivity = 100
keySensitivity = 30
friction = 0.6


The worst is that you have friction=0.6

That will give you some jerky movements together with qualitymotion2= best which is what you xml actually has.

friction = 0,8 is a nice value and motion quality medium as you say in your post.
There are people who go up to friction 0.9 but I do not like that as the pano will move by it self after you release the mouse.

Segments has no effect at all for people with Flash 10 but for the flash 9 users you should not use more than 30 in combination with qualitymotion=low (default)

Hans

[jordi]

hi tzes,

I have set up the parameters as you say, but I can't see any diference;
also I just have updated to the last flash player, and nothing happened...

[jordi]

Sorry Hans I just missuploaded a wrong file, now everything is setup correctly :


segments = 25
frameRate = 40
qualityMotion2 = low
qualityStatic2 = medium
friction = 0.8


But unfortunately still jerking

[HansNyberg]

Works fine now even on my 4 year old PPC Mac 2.0 which has a very low framerate with flash.

Remember also that adding large scaled images on the panorama as you have may affect panning.

Hans

[siesfor]

hey jordi,

Your autorotator parameter is set to "quality=high" which is bound to cause some performance problems. You should remove that and try adding

quality=low
quality2=medium

to your <autorotator> parameters.

I imagine that should fix it, but if you're still having problems after the change, you may want to think about disabling the autorotator while the user is pressing on the pano.

[jordi]

Hi Siesfor & Hans, and thanks for your help, but it seems not to work as I though it would...I was changing the quality parameters in the autorotation, and even disabling it completly, but the jerky effect is always here :???:

I'm gonna try using 6 cube faces with this new parameters, and I will tell you if it runs better.

Thanks for the support

[Jochum]

Have you empted the browsers cache and then tried?

Yes, you are right, it is quite jerky on my computer too.
I doesn't have framerate (why?) and nor friction. What if you remove them?

[HansNyberg]

Hi Siesfor & Hans, and thanks for your help, but it seems not to work as I though it would...I was changing the quality parameters in the autorotation, and even disabling it completly, but the jerky effect is always here :???:

I'm gonna try using 6 cube faces with this new parameters, and I will tell you if it runs better.

Thanks for the support

When you say it is jerky what do you compare to.
Can you point us to another site which you mean is not jerky.

Also what screen resolution do you use. Do you display it on for example a full 1920x1200 or perhaps even larger.
What framerate do you have when panning.

I am used to quite Jerky panning on my old PPC dualcore 2.0 mac but that is the same for all viewers QTVR also.

On my 2 year old MacBook Pro it is fine and I get a framerate of 17-19 which I know is much less than newer PCs

Hans

[jordi]

I'm cleaning the cache regulary in order to refresh all files...

I've seen quite projects where the jerky effect is not so visible, like this one from Jochum (http://illustrata.com/pages/sodermanland/pages/kyrkor/lid/lid_a/lid_a.html), but when I get in fullscreen then I can see it more clearly, so defenetly I'll start thinking it's all about screen size, and the rendering issue it causes.

I'm working on a 1440 x 900 pixels screen, and while panning I have a framerate of about 30 fps.

Thanks again for your support

[HansNyberg]

Framerate of 30

Well I wish I had a computer which could produce that.
My working Mac PPC dualcore 2.0 G5 from 2004 gives me a framerate of 9 at 1440x900
but only 5 at my screen size 1920x1200
In fullscreen I get 8. The better performance in fullscreen seems to be a special Mac thing which might only be associated with some video cards.
However also the browsers are different. Opera reverses the above values giving me 8-9 in browser full size but just 5 in flash fullscreen.
And Opera uses much less memory than Safari/ Firefox for the same panorama.

Most people report around 30 on PC but I also seen some claim they have 45. However as you can see the size of your browser window can easy make 100% difference.
Even at 5 I do not consider it very jerky.

Hans

[Jochum]

Sorry if I mixed things up, I was surprised to see framerate in the xml but thats only because I was not familiar with it, forget what I wrote, now I have learned.
I also see now my example there is jerky on my computer too, I thought it was because I havent restarted in a long time but now when I think about it I think it always have been a little jerky but I only thought it was my computer but I also recall seen even bigger panoramas around here that was much more fluid, I begin to suspect that the older version of FPP was better than the last, no one else seen that?
Otherwise I think your xml file is quite big, hard to find a error there if it is any error, can't you simplify an example with same picture and size and see if that moves better and then add like five or ten lines code and go on so to see where it begin to go jerky?

[jordi]

Yes Jochum, yours is also a bit jerky but not so much, Hans was pointing to the fact of the screen size, which I think it have many sense, because as bigger it is more pixels it have to render...

I have created a minimal version of the XML (http://caloliaire.com/vv/academia/index1.html) in order to determinate if some spot or function was causing some error but I couldn't see any difference...

The code it's not so long, but this is a good point to talk about :

how many lines could manage a single XML, about 2000 ?

I suppose that it depents on how you optimize and organize the code it self.

On the other side I have used the 2.2 version and also see the same problems...

[Jochum]

Right now everything is jerky on my computer, so don't listen to me. :) The window size seems to have something to do with it yes.