Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 20 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 5 hrs ago - more...
 |
|
2011-03-09
, 21:44
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#32
|
Originally Posted by joerg_rw
Oh, for some odd reason it works, but only with video mode.
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
I can not capture images but videos with the front camera.
Nicolai
__________________
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker
-Donate-
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker
-Donate-
| The Following 3 Users Say Thank You to nicolai For This Useful Post: | ||
|
|
2011-03-09
, 21:48
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#33
|
Originally Posted by Char
It should not do that. My tests show that camera-ui2 runs much the same cpu/mem wise as does camera-ui. It peaks at ca. 30/40% cpu after taking a picture and idles around 10%. How do you run it?
camera-ui2 seems to not only be using 10% of my memory but 40-50% CPU constantly
nohup ~/bin/camera-ui2 > /dev/null&
i know im doing it wrong but not nohupping it doesnt let it continue running after i quit the terminal
what exactly do I have to do to get this running normally?
I do
Code:
sudo dsmetool -k /usr/bin/camera-ui sudo dsmetool -t /usr/bin/camera-ui2
Last edited by handaxe; 2011-03-09 at 22:37. Reason: added sudo rather than running as root
| The Following 2 Users Say Thank You to handaxe For This Useful Post: | ||
|
|
2011-03-09
, 21:51
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#34
|
Originally Posted by handaxe
The reason is, nokia provides a good camera-api, all the work
Out of interest, why an enhancement of the camera app (with the kinds of problems noted above) and not say something built around OSS fcam? It too has some deficiencies..
they have done for an open source gstreamer based digicam
api is great and it makes it possible to create any third party
camera applications. BUT at the same time they put a closed
source camera-ui on this device which always pops up when
you open the lenscover, and no simple way to reconfigure
this behavior. I just want to remove this camera-ui and replace
it with an open source clone.
Nicolai
__________________
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker
-Donate-
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker
-Donate-
|
|
2011-03-09
, 21:55
|
|
Posts: 701 |
Thanked: 585 times |
Joined on Sep 2010
@ London, England
|
#35
|
Originally Posted by nicolai
I replaced the original camera-ui with your version so the binary would have the same name, but if cl-launcher is using dbus to launch the camera, that would explain it
Yes, this is not suprising. My camera-ui has a different name(binary and dbus-service name).
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.
| The Following User Says Thank You to retsaw For This Useful Post: | ||
|
|
2011-03-09
, 22:13
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#36
|
Originally Posted by joerg_rw
Yes this may work for images, but don't know how to do it for
remaining pics and video recording time is just guesswork also in Nokia's cam. Use a reasonable hardcoded set of constants to divide free storage. There's actually no better way I know of. (well, make that gconf-consts ;-D)
video recording. I made some test videos with different recording
time, but the file size doesn't grow linear.
Originally Posted by joerg_rw
Pausing and resuming works but I get
Given the fact there seems to be no usable video cutting/editing app on maemo, a video-rec pause function would be mad useful
\o/ for focus on video
some warnings on the console:
dsp_thread: failed waiting for events
I don't know where they come from, and the recorded video
is playable.
__________________
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker
-Donate-
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker
-Donate-
| The Following 3 Users Say Thank You to nicolai For This Useful Post: | ||
|
|
2011-03-09
, 22:36
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#37
|
Originally Posted by handaxe
After a reboot (my run time was ca. a week), matters appeared a little different. As invoked, camera-ui2 idles a few cpu%s richer than camera-ui (ca. 8/9% vs 5/6%) but when filming the difference is more marked with camera-ui2 at ca. 30/40% whilst camera-ui is around 25%. omap3camd seems also run a tad hotter in harness with camera-ui2 than it does with camera-ui.
My tests show that camera-ui2 runs much the same cpu/mem wise as does camera-ui. It peaks at ca. 30/40% cpu after taking a picture and idles around 10%.
Keep in mind that my tests are not science....
|
|
2011-03-09
, 22:42
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#38
|
Trivial difference noted: films taken under camera-ui get categorised in media player as "recorded by device camera". Those done by camera-ui2 are placed under "Films".
A matter of how the interfaces are invoked perhaps - have not investigated.
A matter of how the interfaces are invoked perhaps - have not investigated.
| The Following 3 Users Say Thank You to handaxe For This Useful Post: | ||
|
|
2011-03-09
, 22:49
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#39
|
Originally Posted by handaxe
Yes, noticed this as well. I have not looked further, what
Trivial difference noted: films taken under camera-ui get categorised in media player as "recorded by device camera". Those done by camera-ui2 are placed under "Films".
A matter of how the interfaces are invoked perhaps - have not investigated.
the reason could be.
nicolai
__________________
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker
-Donate-
my contributions:
Desktop Clock Widget|Calendar Home Widget|Lens Cover Reminder|ConnectNow|Scout|App Search Widget|ProfilesX|
Desktop-Switcher|SMS-Messageblocker
-Donate-
| The Following User Says Thank You to nicolai For This Useful Post: | ||
 |
|
2011-03-10
, 00:19
|
|
Posts: 1,030 |
Thanked: 792 times |
Joined on Jun 2009
|
#40
|
Is it possible to add functionality to allow the LED to be enabled during recording or would this require a patched driver?
Out of interest, why an enhancement of the camera app (with the kinds of problems noted above) and not say something built around OSS fcam? It too has some deficiencies..
Whatever, thanks for your productivity...