camera-ui2 (now a part of CSSU) (updated 09. May) - Page 3 - maemo.org

Active Topics

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (9)
to SailfishOS by biketool - 5 hrs, 39 mins ago
[Announce] coderus unrestricted system-ui (297)
to MeeGo / Harmattan by nieldk - 6 days, 10 hrs ago
more...

Page 3 of 114

< Prev

Next >

Last »

Thread Tools

retsaw	2011-03-09 , 20:01
Posts: 701 \| Thanked: 585 times \| Joined on Sep 2010 @ London, England	#21

It doesn't seem to work properly with cl-launcher. I replaced the original camera-ui with your new version and when I opened the lens cover and cl-launcher popped up and I selected "camera" it didn't load, further it didn't hide when I closed the lens cover, I had to press the camera button to get it to show, further it wouldn't remember when I changed any of the settings in the "general settings" menu (they would all be selected when I restarted it). After removing cl-launcher it seems to work as expected, but after killing the camera-ui process it still forgets changes to the settings in the "general settings" menu.

Quote & Reply |

The Following User Says Thank You to retsaw For This Useful Post:
nicolai

	laasonen	2011-03-09 , 20:08
	Posts: 565 \| Thanked: 618 times \| Joined on Jun 2010 @ Finland	#22

Any plans for portrait mode?

Quote & Reply |

	joerg_rw	2011-03-09 , 20:46
	Posts: 2,222 \| Thanked: 12,651 times \| Joined on Mar 2010 @ SOL 3	#23

Originally Posted by nicolai

Using the front camera is difficult (impossible).
The camera api I use (gdigicam) doesnt
work with the front camera AFAIK.

nicolai

I can't see how gdigicam would refuse to use /dev/videoX. Well maybe it does certain assumptions about video device properties, then that's clearly sth gdigicam should learn how to do right.

/j

__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member

EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/

IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N

Quote & Reply |

handaxe	2011-03-09 , 20:54
Posts: 1,378 \| Thanked: 1,604 times \| Joined on Jun 2010 @ Göteborg, Sweden	#24

Originally Posted by retsaw

It doesn't seem to work properly with cl-launcher..... I had to press the camera button to get it to show...

I can confirm the need to press the camera button for the app to display with cl-launcher installed. Performs properly thereafter, appearing promptly upon lens cover open or button press.

Goodstuff... really!

Last edited by handaxe; 2011-03-09 at 20:57.

Quote & Reply |

The Following User Says Thank You to handaxe For This Useful Post:
Zentenario

	nicolai	2011-03-09 , 20:54
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#25

GDigicam needs a special gstreamerplugin (gstcamerabin)
and this gstreamerplugin refuses to work with the frontcamera.
(/dev/video1). Maybe there is some way to get it to work.

Quote & Reply |

The Following 3 Users Say Thank You to nicolai For This Useful Post:
drangina, Mentalist Traceur, Natan_xy

	nicolai	2011-03-09 , 21:00
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#26

Originally Posted by retsaw

It doesn't seem to work properly with cl-launcher.

Yes, this is not suprising. My camera-ui has a different name(binary
and dbus-service name).

Originally Posted by retsaw

further it wouldn't remember when I changed any of the settings in the "general settings" menu (they would all be selected when I restarted it). After removing cl-launcher it seems to work as expected, but after killing the camera-ui process it still forgets changes to the settings in the "general settings" menu.

That is what I wrote, the additional settings aren't saved. I am
not sure which extra functions are actually useful, and so I
don't want to make them persistent.

Quote & Reply |

The Following 3 Users Say Thank You to nicolai For This Useful Post:
drangina, Mentalist Traceur, retsaw

	nicolai	2011-03-09 , 21:06
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#27

Originally Posted by jo21

u using the default drivers or fcam drivers?

The default driver.
In theory the default driver is capable to deliver
the raw-image buffer. I wrote a version which catches the
raw-image buffer and I wrote a simple DNG-File export.
Sadly there is a bug in a gstreamer-component. Even if
the buffer has the full 2592x1968 pixel data (this is the
raw resolution of the camera chip), the gstreamer plugin
only copies at image capture resolution (2576x1960).
That means there are some missing lines at the bottom of the
raw-image.
But the gstreamer plugin (gstv4l2camsrc) is open as well, so it could be fixed.

Nicolai

Quote & Reply |

The Following 2 Users Say Thank You to nicolai For This Useful Post:
joerg_rw, Mentalist Traceur

	nicolai	2011-03-09 , 21:16
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#28

Originally Posted by MohammadAG

Is Night Video working? I'd expect the ISO to be very low there and so the frame rate of the viewfinder would be low, but it seems to be the same as normal video.

This is a bug, I used the wrong exposure mode for night video :-)

Nicolai

Quote & Reply |

The Following 4 Users Say Thank You to nicolai For This Useful Post:
joerg_rw, Mentalist Traceur, MohammadAG, OVK

handaxe	2011-03-09 , 21:20
Posts: 1,378 \| Thanked: 1,604 times \| Joined on Jun 2010 @ Göteborg, Sweden	#29

Tests: set iso to 100, 200 or 400 (ie not auto). Set exposure compensation to +1.5, 2.0 or...

Result: incorrect (very dark) viewfinder and image.

Exposure compensation with Auto iso works well.

Nicolai: anything in particular you want tested? Want anything noted?

Quote & Reply |

The Following User Says Thank You to handaxe For This Useful Post:
drangina

	nicolai	2011-03-09 , 21:27
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#30

Originally Posted by handaxe

Tests: set iso to 100, 200 or 400 (ie not auto). Set exposure compensation to +1.5, 2.0 or...

Result: incorrect (very dark) viewfinder and image.

Exposure compensation with Auto iso works well.

Yes, this is a bug in the builtin app as well

https://bugs.maemo.org/show_bug.cgi?id=10384
Sadly, I don't think I can fix this. From my observations this
bug is in ibomap3cam or in omap3camd - both are
closed components.

Originally Posted by handaxe