![]() |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
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. :D |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
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?
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
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 |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
Quote:
Quote:
Quote:
Code:
-:14: Unable to locate image file in pixmap_path: "../../../icons/hicolor/scalable/hildon/camera_zoom_background.png" Code:
~# dpkg -l | grep -i dsp Code:
ii gstreamer0.10-plugins-camera 0.79-1+0m5 GStreamer plugins for camera application 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 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! |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
Quote:
"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. |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
Quote:
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. :confused: 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. :p 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. :rolleyes: |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
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 |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
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 |
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
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 :)
|
Re: camera-ui2 (now a part of CSSU) (updated 09. May)
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? |
All times are GMT. The time now is 15:33. |
vBulletin® Version 3.8.8