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

Active Topics

The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 17 hrs, 18 mins ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 5 hrs ago
more...

Page 49 of 114

Thread Tools

	woody14619	2011-09-27 , 18:06
	Posts: 1,455 \| Thanked: 3,309 times \| Joined on Dec 2009 @ Rochester, NY	#481

Originally Posted by nicolai

Hi ahmedamaj,
I can not reproduce this. I made 50 shots yesterday on my
way home. And all worked.

Nicolai

Nicolai, I'm having the same issue now, getting 0 byte "image" files from snapped photos 90% of the time. (I did get it to work once, but I'm not sure how/why.) I tried doing a re-install of the fcam-drivers and the camera-ui package, and it didn't help. The odd part is, Bless and FCam work just fine. And camera-ui snaps the photo, shows the preview, and correctly names the file, it just has no contents.

I've tried using the stock voltage profile and my slightly tweaked one. I'm using k49 & CSSU... so yes, it's quite customized. I've tried saving both to internal memory and the uSD card with identical results. One other interesting side note is I'm finding it's not saving settings either. I turn on GPS tagging, but each time I reboot it's off again. Maybe it's a gconf-based issue?

Since I don't use the camera that often, and can still use FCam/Bless if I need to, I'd be happy to offer debug time if you like. I can run a custom version, turn on debug output, maybe even give you an IP to ssh into to check it out if you think it would help. Worst case I can always revert to the old UI, but I really do like the one you've made, minus the part about it not saving pictures.

Quote & Reply |

The Following User Says Thank You to woody14619 For This Useful Post:
Estel

	int_ua	2011-09-27 , 18:50
	Posts: 676 \| Thanked: 1,067 times \| Joined on Jul 2010 @ Kyiv, Ukraine	#482

Hi, I'm getting 'Playback error' sometimes. Looks like the video files sometimes are broken. Can't reproduce it, but it happened 2 times. Anyone else experiencing this?

Quote & Reply |

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

Where are your images saved, device or memory card?
Overclocked?
Do you have sysklogd installed, if so are there any camera-ui
related logs?
Or run the camera-ui from the command line:
In X-Term as root:
dsmetook -k /usr/bin/camera-ui
(this stops the camera-ui from running in the background)
then as user(!)
/usr/bin/camera-ui
And post any error messages here.

Nicolai

Quote & Reply |

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

	woody14619	2011-09-27 , 21:13
	Posts: 1,455 \| Thanked: 3,309 times \| Joined on Dec 2009 @ Rochester, NY	#484

Originally Posted by nicolai

Where are your images saved, device or memory card?

I've tried both, and both fail.

Originally Posted by nicolai

Overclocked?

I've tried both overclocked and with standard settings, both failed.

Originally Posted by nicolai

Do you have sysklogd installed, if so are there any camera-ui related logs?

I haven't installed it, but if it would be helpful I'd be willing to give it a go.

Originally Posted by nicolai

Or run the camera-ui from the command line: ... And post any error messages here.

Done, and I got two failure lines (highlighted in red) just as the file was trying to save. Looks like it's a dsp error?

Code:

-:14: Unable to locate image file in pixmap_path: "../../../icons/hicolor/scalable/hildon/camera_zoom_background.png"
-:16: border (or stretch) without valid file
-:20: Unable to locate image file in pixmap_path: "../../../icons/hicolor/scalable/hildon/camera_zoom_slider.png"
-:21: border (or stretch) without valid file
preview window topmost TRUE
create_node: dsp node allocate failed
sink_setcaps: dsp node creation failed
preview window topmost FALSE

Is there a package maybe that I don't have installed? Or one I should attempt a re-install on? I did a package list for dsp related stuff, output below:

Code:

~# dpkg -l | grep -i dsp
ii  dsp-manager   1.1.0-1+0m5   DSP handler and watchdog.
ii  gstreamer0.10-dsp   0.7.0-0maemo2.4+0m5   GStreamer plug-in for TI's OMAP DSP.
ii  libbridge2   0.200934.1+0m5   library to access TI DSP bridge
ii  libspeexdsp1   1.2~rc1-1maemo7+0m5   The Speex extended runtime library
ii  omap3430-dsp-baseimage-ti   0.201007-1+0m5   DSP base image
ii  omap3430-dsp-libraries-ti   0.201007-1+0m5   DSP codecs

Looking at the gstreamer plugins, I'm seeing one that looks out of place, not being at version 0.10-something:

Code:

ii  gstreamer0.10-plugins-camera   0.79-1+0m5   GStreamer plugins for camera application

Could that be the culprit?

Also, I assume I use dsmetool -t /usr/bin/camera-ui to re-enable the run-in-background feature again, yes?

Thanks for any tips. I'll look at turning on sysloging tonight and see what more I can get debug wise from that.

EDIT: Installed sysklog, and enabled user debugging, got the following in the user log:

Code:

camera-ui[23559]: GLIB WARNING ** GStreamer - pad v4l2camsrc0:src returned caps which are not a real subset of its template caps
camera-ui[23559]: GLIB WARNING ** Gtk - Invalid icon size 216
camera-ui[23559]: GLIB WARNING ** GStreamer - pad v4l2camsrc0:src returned caps which are not a real subset of its template caps
camera-ui[23559]: GLIB WARNING ** Gtk - Invalid icon size 216
camera-ui[23559]: GLIB WARNING ** GStreamer - pad v4l2camsrc0:src returned caps which are not a real subset of its template caps
camera-ui[23559]: dspjpegenc0: dsp node allocate failed
camera-ui[23559]: dspjpegenc0: dsp node creation failed

EDIT: SOLUTION FOUND
So, after lots of hair pulling and using the much slower loading Bless for a while (great when you have time, sucks when you want it fast), I accidentally stumbled on a solution. Turns out, no matter how I tweaked my settings nothing worked until I installed the latest upstream drivers for dsp, via scripts freemangordon put together to pull them from the N950 repository (and some of which he rebuilt himself). Since then I've not seen this issue crop up again.

So if you're seeing this behavior, and nothing else has fixed it, it may be worth a shot to try installing the upstream drivers!

Last edited by woody14619; 2011-12-09 at 20:58.

Quote & Reply |

The Following 3 Users Say Thank You to woody14619 For This Useful Post:
don_falcone, Estel, fotis9

	nicolai	2011-09-27 , 22:16
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#485

Originally Posted by woody14619

Looking at the gstreamer plugins, I'm seeing one that looks out of place, not being at version 0.10-something:
Code:
ii  gstreamer0.10-plugins-camera   0.79-1+0m5   GStreamer plugins for camera application
Could that be the culprit?

No, I have all the same versions.

Originally Posted by woody14619

EDIT: Installed sysklog, and enabled user debugging, got the following in the user log:

Code:

camera-ui[23559]: GLIB WARNING ** GStreamer - pad v4l2camsrc0:src returned caps which are not a real subset of its template caps
camera-ui[23559]: GLIB WARNING ** Gtk - Invalid icon size 216
camera-ui[23559]: GLIB WARNING ** GStreamer - pad v4l2camsrc0:src returned caps which are not a real subset of its template caps
camera-ui[23559]: GLIB WARNING ** Gtk - Invalid icon size 216
camera-ui[23559]: GLIB WARNING ** GStreamer - pad v4l2camsrc0:src returned caps which are not a real subset of its template caps
camera-ui[23559]: dspjpegenc0: dsp node allocate failed
camera-ui[23559]: dspjpegenc0: dsp node creation failed

Ah, I remember that once I had the same error
"v4l2camsrc0:src returned caps which are not a real subset of its template caps"
It vanished after I removed (or reinstalled?) bless900.
I think I had an older version of bless or the fcam-drivers.

Quote & Reply |

The Following 2 Users Say Thank You to nicolai For This Useful Post:
Estel, fotis9

	woody14619	2011-09-27 , 23:47
	Posts: 1,455 \| Thanked: 3,309 times \| Joined on Dec 2009 @ Rochester, NY	#486

Originally Posted by nicolai

Ah, I remember that once I had the same error
"v4l2camsrc0:src returned caps which are not a real subset of its template caps"
It vanished after I removed (or reinstalled?) bless900.
I think I had an older version of bless or the fcam-drivers.

Hmm.. see, I've tried that already though. I've also tried reverting to the standard camera-ui, which yields an identical series of failures. Right now I'm trying removing the fcam-drivers completely (they were at 1.0.7-2) and seeing if maybe it's one of the apps associated with them that's causing it. The only ones claiming a dependency are mir-translator, blessn900, fcamera and hdrcapture.

Does camera-ui actually use the fcam drivers at all? I'm guessing it doesn't? Since after uninstalling it still tries to take pictures? :P What package controls the dsp stuff? In particular the dsp-jpeg-encoder stuff? If there a lib package for that I can try re-installing? I'd really hate to have this boil down to a re-flash.

Edit:
So, I'm not sure what caused it to work again, but it's mainly working. I'm still getting an occasional "dsp_thread: failed waiting for events", but those are pretty rare. I wound up purging and re-installing most of the camera apps, and the fcam-drivers package. I also re-installed anything with dsp in it's title from package manager, as well as the camera-firmware package. (That was one of the last few I did before it started working.)

Whatever the cause, I'm no longer seeing the error messages I was seeing before about "template caps" when things start up. I'm also not seeing anything special outside the normal debug output about the bad icons now.

So, if someone has a similar problem, a solution may be to simply re-install the dsp packages and camera-firmware and see if that helps? I love my quirky little device, but there are times I really have to wonder how close it's coming to being the next "Johnny 5".

Thanks for the help! May not seem like much, but even knowing someone else had this issue and solved it was encouraging.

Last edited by woody14619; 2011-09-28 at 01:32. Reason: It's working again... mainly...

Quote & Reply |

SHARP66	2011-10-03 , 23:40
Posts: 291 \| Thanked: 435 times \| Joined on Apr 2011 @ RO	#487

still waiting for my image with alpha channel on top of camera screen.
for: -golden rule
-photo reference

i wander why no one needs something like that

Quote & Reply |

	nicolai	2011-10-04 , 08:20
	Posts: 1,637 \| Thanked: 4,424 times \| Joined on Apr 2009 @ Germany	#488

Don't have much use of this, but I can try to implement this.
Can you provide me with some example grids you would like
to have.
One problem that may arise is, I don't know if the aspect ratio
and field of view of the viewfinder image is always the same as for
the resulting image.

Would you like to test this for me, capture an image and
make a screenshot of the viewfinder image and compare both.

Nicolai

Quote & Reply |

The Following 3 Users Say Thank You to nicolai For This Useful Post:
Estel, fw190, SHARP66

petur	2011-10-04 , 11:38
Posts: 650 \| Thanked: 497 times \| Joined on Oct 2008 @ Ghent, Belgium	#489

nicolai, the grid that most cameras implement is just a 3x3 grid, ie divide the screen in 9 equal chunks. Never used it though, gets in the way of proper compositions

__________________
Affordable mobile internet in Belgium: Try Mobile Vikings
2 GB, 1000 SMS and 15 euro of talk time for.... 15 euro

Quote & Reply |

The Following User Says Thank You to petur For This Useful Post:
Estel

demolition	2011-10-04 , 12:34
Posts: 560 \| Thanked: 422 times \| Joined on Mar 2011	#490

Apologies if I've missed any reference to this but I'm not sure how to resolve the following:

1. Problem: Exposure duration control.
I would like to explicitly set the amount of time the shutter is open and/or have the ability to hold the shutter open while the camera button is being held down. For example in low-light situations

2. Problem: Image "temperature"
I hope that's the correct term. I would like to be able to increase the saturation of red-colouring and reduce that of blue-green. It may be that the physical mechanism for capturing the images is insufficiently sensitve to longer wavelengths (i.e. oranges and reds). If so, this problem cannot be satisfactorally addressed.

Grateful for any help...

Should I raise these as feature-request bugs?