Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 13 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 8 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 17 hrs ago - more...
The Rotter |
2010-07-24
, 03:13
|
|
Posts: 19 |
Thanked: 4 times |
Joined on Jul 2010
|
#461
|
Originally Posted by Nathraiben
And then there's the passive-aggressive fanboys who believe it's their duty to spend every waking hour logged into TMO ready with a knee-jerk reaction and their @ss in a knot of perfection for every little thing that might be critical. They're just as bad if not worse!
Originally Posted by Nathraiben
In this analogy it's rarely the kids' fault. In almost every case it's the parents that are responsible for this type of behaviour.
 |
|
2010-07-24
, 03:46
|
|
Posts: 267 |
Thanked: 408 times |
Joined on May 2010
@ Austria
|
#462
|
Originally Posted by The Rotter
The interesting thing is, I haven't seen a single fanboy in this thread so far. Most of the people who're thanking the FCam team for their work and accept this as exiting news are people who are openly criticising Nokia in other threads.
And then there's the passive-aggressive fanboys who believe it's their duty to spend every waking hour logged into TMO ready with a knee-jerk reaction and their @ss in a knot of perfection for every little thing that might be critical. They're just as bad if not worse!
Maybe because we don't care whether something was made/sponsored/initiated by Nokia or not - if it's beneficial for us and/or the community, we'll treasure it instead of throwing a mindless tantrum.
In this analogy it's rarely the kids' fault. In almost every case it's the parents that are responsible for this type of behaviour.
| The Following 4 Users Say Thank You to Nathraiben For This Useful Post: | ||
|
|
2010-07-24
, 04:36
|
|
Posts: 540 |
Thanked: 288 times |
Joined on Sep 2009
|
#463
|
Originally Posted by titan
A bit late here, but would'nt it work in the following way:
In the future we probably need a separate fcam-drivers-package (but AFAIK HAM is not sophisticated enough to handle such dependencies and conflicts) or we would need to add modules for both kernel versions to the fcam-drivers package.
fcam (and other frontend programs) "Require: fcam-drivers", then have fcam-drivers package for stock-kernel that requires exact stock-kernel version (just to be sure), and have fcam-drivers-power that "Provides: fcam-drivers" (and naturally requires kernel-power itself). alternatively the fcam drivers can be incorporated in the kernel-power-modules package (it makes the build script slightly more complex) and add another Provides entry there.
I'm fairly sure HAM can resolve any dependency issue that apt-get can.
__________________
- Live near Helsinki, Finland & interested in electronics ? Check this out.
- Want anti-virus/firewall ? Read this (and follow the links, also: use the search, there are way too many threads asking the same questions over and over and over again).
- I'm experimenting with BitCoins, if you want to tip me send some to: 1CAEy7PYptSasN67TiMYM74ELDVGZS6cCB
|
|
2010-07-24
, 23:51
|
|
Posts: 486 |
Thanked: 251 times |
Joined on Oct 2009
|
#464
|
Originally Posted by ysss
It will only matter to those with less than 200 posts who are eagerly awaiting the ability to edit tags, but I think the minimum is 300 posts.
You need a minimum of 200 posts to edit tags, if I'm not mistaken.
__________________
The Mini-USB plug is an improvement over both the Type B plug and the Micro-B plug.
The Mini-USB plug is an improvement over both the Type B plug and the Micro-B plug.
|
|
2010-07-25
, 04:41
|
|
Posts: 992 |
Thanked: 738 times |
Joined on Jun 2010
@ Low Earth Orbit
|
#465
|
Originally Posted by j.s
Now would someone with the right privileges be kind enough to remove the childish tags?
It will only matter to those with less than 200 posts who are eagerly awaiting the ability to edit tags, but I think the minimum is 300 posts.
 |
|
2010-07-26
, 05:35
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#466
|
Originally Posted by bergie
Huh. I guess you haven't bothered to use anything else, then. Seriously. It's GREAT that the N900 got fcam, but it's hardly "the first!" at anything except finally having open-source drivers for the N900... certainly not the first good camera app on a cell phone, certainly not the first to do anything other camera apps can do (and often do more and better) elsewhere.. it's just a good start. "It was the N900 that got it first" is a silly, boggling statement. It SHOULD be said, 'At least the N900 FINALLY got some potential opened up.'
It is actually quite big news, as the ambitions of fCam go way beyond cameraphones. But it was the N900 that got it first.
http://bergie.iki.fi/blog/frankencam..._programmable/
What they did was ENABLE. They didn't pioneer anything with this app yet.
|
|
2010-07-26
, 07:45
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#468
|
Originally Posted by geohsia
That's a good question. I've never really been interested in cameras that write a "raw" file, myself, so I never really looked into it. Considering there's no agreed-upon standard for a RAW file (http://en.wikipedia.org/wiki/Raw_image_format), the question first must be asked what KIND of RAW file you're talking about, and then the next question is whether this RAW file is actually a valuable and recognized format coming from the N900 to use in any image manipulation software.
Is the N900 the first phone to have RAW?
As for my Android handset using Camera360, it can (and I have set it up to) write a 100% quality JPEG file for a near lossless JPEG file. That's probably just as good for a 5MP cell phone as writing what you think of as a RAW format, plus the benefit of compatibility with all software that can read JPEG images.
Last edited by danramos; 2010-07-26 at 07:48.
|
|
2010-07-26
, 07:57
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#469
|
The point of RAW is that postprocessing parameters can be applied (and changed) later - JPEG bakes those in and you cannot un-apply them. Compression artifacts are not even on the top of that list - think white balance, sharpening, demosaicing, noise reduction, darken/lighten with less loss of details, etc, etc.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
|
|
2010-07-26
, 16:00
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#470
|
Originally Posted by attila77
JPEG doesn't "bake those in" any more than TIFF, DNG or RAW. Once you have the image and you begin to process the image, ALL the data is just as malleable and useful as anything RAW gives you. Hell, JPEG even borrows a page out of TIFF and records a lot of that in the EXIF metadata. RAW isn't a format. It's just a proprietary aperture dump. Putting it into a 100% quality JPEG with EXIF metadata would record most of the same information (ALL of the info, if you use the MakerNote tag in the EXIF metadata) with pretty decent quality and it would at least work everywhere. To that end, unless I'm still missing something, I don't see the utility of the RAW dump. Mind you, we're also still only talking about a 5MP cell phone camera, too.
The point of RAW is that postprocessing parameters can be applied (and changed) later - JPEG bakes those in and you cannot un-apply them. Compression artifacts are not even on the top of that list - think white balance, sharpening, demosaicing, noise reduction, darken/lighten with less loss of details, etc, etc.
 |
| Tags |
| announced, color you loser, fail!, guessed wrong, misstep, riddle me this, you dun goofed |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 13:47.