Page 1 of 1
Changes in source settings make streaming window 4x size
Posted: Sun Jun 04, 2006 9:51 pm
by ekiboy69
Hello,
Just bumped into a new problem with 2 boxes running 1.22.1 on Mandrake 10.1/10.2.
If you adjust the source-settings, for example change fps settings, the "live view" opened by clicking the monitor name in the console view shows the picture in 4x size. Quite uncomfortable
I thought I messed up with the first box but I was able to replicate the problem with another box up and running.
Possible explanation
Posted: Mon Jun 05, 2006 7:00 am
by ekiboy69
Until this is solved I think this might be a permissions problem:
http://www.zoneminder.com/forums/viewtopic.php?t=6304
I don't think it is a permissions thing
Posted: Tue Jun 06, 2006 8:28 pm
by ekiboy69
For some reason this thing is on 2 different boxes. I wonder what could cause it?
The default setting for viewing size has changed to 4x
Posted: Tue Jun 06, 2006 9:18 pm
by ekiboy69
Hello,
I noticed that in all windows that show streaming content the size is 4x.
I'm using RPMs built for mandrake and running 1.22.2 at the moment.
Am I really the only one having this problem?
Posted: Tue Jun 06, 2006 9:59 pm
by jameswilson
I have had this but i dont mes with the source much so after i fix it i dont get it again, so i havnt spent any time looking into it sorry
Posted: Wed Jun 07, 2006 5:12 am
by rdmelin
In the source settings there is a misc tab. There you can select Default scale. Check what you have this set to.
Posted: Wed Jun 07, 2006 6:18 am
by jameswilson
oh i thought it kept reverting to 4x every time you cahnged the source. Oh well i should ask these things i suppose! lol
Ross found out the right answer
Posted: Fri Jun 09, 2006 7:18 pm
by ekiboy69
rdmelin wrote:In the source settings there is a misc tab. There you can select Default scale. Check what you have this set to.
This was set to 4x. It is of course possible that I have messed up this on both of the 2 boxes I had this problem with. Anoher possible expalation is that there's something with the rpm update method that caused this.
Well, in any case you guys helped me out again.
Thank you!