Some phones can record slowmo at vga resolution ( usually arround 200fps )
So... SGSII with the super power, i think can do 60fps at 720p? or at WVGA?
Why i'm sayng this? ok if you go to any party, race event, or something similar, isn't the same at 30 fps than at 60fps ( more fluid )
So... its posible?
thanks and forgive my bad english
Regarding wikipedia, it should be possible...
Generally: The less the resolution, the higher the fps (found it in german Wikipedia)
But i guess you'll need an application to do that.
Well, it a bit more complicated than just less resolution means u can have more frames. You have to consider things like cmos line read spead and shutter speed. Then if some1 did an app, it would suffer heavy from rolling shutter, does now, high frame rate would make it worse. I may look at media profiles cause it would be good to see if it can
Sent from my GT-I9100 using XDA Premium App
Sounds like a good idea. If someone can do this say @ 60fps, maybe we can check if there's some difference. If not much difference, then we can stick to what we have now.
rd_nest said:
Sounds like a good idea. If someone can do this say @ 60fps, maybe we can check if there's some difference. If not much difference, then we can stick to what we have now.
Click to expand...
Click to collapse
My cousin have a digital HI-Performance camera, and records at 720 -30/60FPS and 1080p at 30FPS...
And i can say, there is a noticeable diference at 30 than 60 FPS, the video is more fluid, and you can apreciate more details when the camera is in movement, like in a car race.
Soon i will get my SGSII, after reconsidering to get O2X.
I for one would like this too, especially if you could go further down the scale too, something like this;
1080p30 (Default)
720p60
480p120
240p240
Naturally, filming at something ridiculous like 320x240 (yes, yes, it's not 16:9) at 240FPS may not be useful to many, it would still provide some great slow-motion shots
I also fully expect the device to be not capable of shooting at that many frames per second anyway, 120 is pushing it
Like i said previously depends on shutter speed!
The shutter speed on old cameras used to be the amount of time the shutter exposed the film to light, on new DSLR or (Single Lens Reflex) it's the amount of time the mirror locks up and exposes the sensor, for video on a cmos sensor it's the speed at which the sensor is scan-line read. So to do 120fps, it would be not possible if it takes 1/30th of a second for the sensor to be read.
After looking at this a LITTLE, I think most of the crap capability is embedded in the camera firmware. It's possible to change media profiles but they do nothing.
Could be wrong and would like to do an app that can record 60 or 120 or even more, but after looking at this, would need a better dev than I and I would GUESS even then that it isn't likely due to hardware/camera firmware.
i'm happy with my camera performance
__________________
Device: Galaxy S II
ROM: Lite'ning Rom v1.4 - overclocked to 1.4GHz
Kernel: CF-Root v.3.8 XWKF1
Previous Phone: Galaxy S
so... for example:
if the SGSII have another 3rd CPU ( secret disabled CPU ) you will not unlock it?
It's working good so isnt necessary...
that's ridiculous...
tomeu0000 said:
so... for example:
if the SGSII have another 3rd CPU ( secret disabled CPU ) you will not unlock it?
It's working good so isnt necessary...
that's ridiculous...
Click to expand...
Click to collapse
I didn't make the comment that your referring to, but I do think your analogy is a little off. You kinda says if you had a audi and a ferrari, wouldn't you want to use the ferrari?
But it's actually more like, well we have a ferrari now lets try and tune the hell outta it (with a risk of damage) to get more out of it. Some people just wouldn't want to do that lol.
And yes, a cmos sensor creates heat, and I suspect making it read faster creates more heat. So yeah, possible damage
Personally I still want to look into this when I have some more free time though
deanwray said:
I didn't make the comment that your referring to, but I do think your analogy is a little off. You kinda says if you had a audi and a ferrari, wouldn't you want to use the ferrari?
But it's actually more like, well we have a ferrari now lets try and tune the hell outta it (with a risk of damage) to get more out of it. Some people just wouldn't want to do that lol.
And yes, a cmos sensor creates heat, and I suspect making it read faster creates more heat. So yeah, possible damage
Personally I still want to look into this when I have some more free time though
Click to expand...
Click to collapse
Some phones on the market support a loot of features, but that, are disabled by default...
Like the motorola defy, have a FM transsmiter but isn't enabled...
Like the Defy, now have 720P recording, not default WVGA, that isn't dangerous for the phone...
is more dangerous to overclock the CPU, than modify system files... ( ever if u know what are you modifyng )
About 3 years ago I used to have the Samsung INNOV8 (i8510, running on symbian), first one with the wide-angle 8mpx camera ( which i suspect remained exactly the same throughout the chain of models) and there was an integrated option in the camera sw for 120fps video, low-res ofcourse ( TI OMAP 2430 with a 330Mhz CPU )
So if they, indeed, use the same camera unit does that mean it allows that frame capture rate gibberish i can barely understand?
tomeu0000 said:
Some phones on the market support a loot of features, but that, are disabled by default...
Like the motorola defy, have a FM transsmiter but isn't enabled...
Like the Defy, now have 720P recording, not default WVGA, that isn't dangerous for the phone...
is more dangerous to overclock the CPU, than modify system files... ( ever if u know what are you modifyng )
Click to expand...
Click to collapse
again were not talking about an extra feature, we are talking about cranking a feature up to beyond what it is at the moment. And YES there are potential risk factors in altering read speeds of a cmos sensor, I know many cmos sensors that have burned due to normal use (manufacturing error, heat) and cranking them up increases the chance of damage.
I think you missunderstand what would need to happen, altering system files is easy, but what is actually going to happen in a hardware sense is that instead of the sensor being read 30 times every second, it would be read 120 times every second. Now, that, due to the increase in electical flow would create more heat, increaseing heat is not always a safe thing to do in electrical components.
Now I'm not saying it cant be done, or that I'm posative that it will damage my phone, I only mean to say that calling a poster ridiculous cause they don't want to take the chance, while citing a dissacosiated anology is perhaps a little wrong.
Also to say that overclocking the CPU is more dangerous is a little off unless you have info on the cmos that I cant find? As if it's rated at 30reads per second and 35 reads at 1 minute would blow it, then no, it's not safer. It's almost EXACTLY like overclocking your cpu
Neways, I'm looking to get some info on the cmos and camera info inside the sgs2 but tis hard to find.
bahkata said:
About 3 years ago I used to have the Samsung INNOV8 (i8510, running on symbian), first one with the wide-angle 8mpx camera ( which i suspect remained exactly the same throughout the chain of models) and there was an integrated option in the camera sw for 120fps video, low-res ofcourse ( TI OMAP 2430 with a 330Mhz CPU )
So if they, indeed, use the same camera unit does that mean it allows that frame capture rate gibberish i can barely understand?
Click to expand...
Click to collapse
Would be good if it was, but 3 years? Hmmm
I need to find info on the camera hardware I think
Those who are "content" are on the wrong forums
We're here to push boundaries, find new frontiers.
You're worried that using the camera at 120FPS is going to melt the device? I severely doubt that, you can overclock the I9100 from 1.2 to 1.5GHz and it gets WARM for example, but not hot enough to cause damage.
Accessing a camera at a faster rate won't generate heat, at the end of the day you're just reading the values across the CMOS sensor, it's not having to do complex mathematical calculations so it won't generate much heat, if any at all.
foxdie said:
Those who are "content" are on the wrong forums
We're here to push boundaries, find new frontiers.
You're worried that using the camera at 120FPS is going to melt the device? I severely doubt that, you can overclock the I9100 from 1.2 to 1.5GHz and it gets WARM for example, but not hot enough to cause damage.
Accessing a camera at a faster rate won't generate heat, at the end of the day you're just reading the values across the CMOS sensor, it's not having to do complex mathematical calculations so it won't generate much heat, if any at all.
Click to expand...
Click to collapse
Reading CMOS = Electricity = heat Same with any CMOS (less so with CCD)
not sure if this post is still alive, but.
i was looking to do the same , and today i saw SiyahKernel 2.2 beta 6.
http://www.gokhanmoral.com/gm/
which removed 30fps limit.
"increased the fps limit in the camera driver (30 to 120). I hope that the one who sent me a PM about this modification can manage to use it to have better image or video quality."
so technically the hardware will not stop you now to go to 30fps+ in videos.
i tried Lgcamera/lgcamcor from market, since it allows you to select the FPS in the video recording setting (selected 60), BUT it didn't record at that FPS.
i'm guessing that the camera settings will be phone specific.
just wanted to share this , since i'll keep trying/asking around , thought the ppl on this thread might also have some experience in this
Agreed, 60fps would be great idea, as SGS2 has a powerful camcorder for making movies. PLS, anyone have any idea about that??!?!
A bit off topic but download fast burst camera from 4shared, amazingly fast!
Sent from my GT-I9100 using xda premium
fasburst cameras are a bit pointless imho, better to record video... cause all of these fast burst things all they do is save the on screen preview buffer....
Related
GOT 720p clearing up the hack a bit and will release it most probably tomorrow
sorry for the confusin
http://www.megaupload.com/?d=RP7LCIU4
here is the image
now thats the kinda stuff im talking about !
lets get some effort on this, gonna start digging thru the source now..
it would be awesome if we can get this working !!!!!!!!!!!
Everytime there is a new post, I check this thread, sadly its just motivational comments. If this happens though, we will have one more thing that makes the Nexus and even better phone.
Btw guys, the sensor is definitely capable of it. Like mentioned by the OP, it's just the encoding that is holding this up.
coolbho3000 said:
Btw guys, the sensor is definitely capable of it. Like mentioned by the OP, it's just the encoding that is holding this up.
Click to expand...
Click to collapse
What is the problem with the encoding to start with? I would much prefer to use the h264 codec to record video to start with, why does using it crash the camera app?
I think it would be better if we could get a constant bit rate for the video recorder instead, just like on the Milestone/Droid, rather than the frame skipping in indoor light conditions.
I also hope one day we can get a better audio format rather than 8kHz AMR in our video recordings :-(
But this is a good initiative anyway..
dsixda said:
I think it would be better if we could get a constant bit rate for the video recorder instead, just like on the Milestone/Droid, rather than the frame skipping in indoor light conditions.
I also hope one day we can get a better audio format rather than 8kHz AMR in our video recordings :-(
But this is a good initiative anyway..
Click to expand...
Click to collapse
Thats exactly what I'm looking for in terms of fps. Made a thread requesting someone add the ability to records at constant 30fps and from my testing the framerate only drops when recording indoors or in low light conditions. The indoor lighting slows everything down but out side it records perfectly and smooth. If we can get that fixed by an android pro that would be great.
As for 720p I still think thats a hardware limitation somewhere in the lense or motherboard. If it was hardware possible, how come google didnt include that from the start?
dsixda said:
I also hope one day we can get a better audio format rather than 8kHz AMR in our video recordings :-(
Click to expand...
Click to collapse
Just want to second this. The audio quality is pathetic and makes it useless for recording voice. It is one thing I miss from the iPhone. I'd assume that changing the audio codec and bitrate wouldn't be too hard for a good dev (which I certainly am not).
Records VERY well in ideal outside conditions, shot this the other day:
http://www.youtube.com/watch?v=gPh9NQAiBPA
Haven't tried low light, but that is using MoDaCo A21 Desire ROM.
vr24 said:
Records VERY well in ideal outside conditions, shot this the other day:
http://www.youtube.com/watch?v=gPh9NQAiBPA
Haven't tried low light, but that is using MoDaCo A21 Desire ROM.
Click to expand...
Click to collapse
Yes I know it works well in outdoor lighting - the point was that it skips frames indoors.
From my experience of playing DSLR
the skipping in dim environment is probably because of insufficient CPU performance. When the light is dim, slower shutter speed and higher iso is required to obtain proper exposure, thus increase the noise. More cpu resource is needed to perform noise reduction. Then if the cpu is not strong enough, it skipps
If you take photos you know when you use high ISO and noise reduction at the same time, speed and the maximum frames of continuous shooting is usually affected.
So from my view, if we cannot improve the algorithm of encoder to achieve higher efficiency(which I think is quite difficult), then force disabling the noise reduction might be a way to solve this, although the video will be noisy...
just guessing...
along with this i was also working on 30fps and 44khz sound. the max fps i could get indoor was 26, couldnt test outdoor. i am testin the sound now. Hey and 30fps is a go but 44khz sound causes fc, will check the logs. Uploading a 26.176fps video recorded on my N1. IT STILL skips some frames but the limit is lifted from 24fps stock android
Great ...
I will try it out
BUT
Your screen shot says 720 x 480 ??
That is not 720p ... http://en.wikipedia.org/wiki/720p
The 720 refers to the height, not the lines
What you have is what is commonly referred to as DVD resolution (although really only for NTSC, as PAL is higher).
Incidentally ...
The Desire camera on the Nexus One can record at 800x480, but the I think it does it at 15 FPS and crap audio. 720x480 at 25-30 FPS with half decent audio would be very cool
Yes currently only 720x480. First trying to get decent video at this resolution. Then will move to increasing resolutions.
wow
480p to 720 p is a big jump
it's 2.67X data to process...
Nexus has the capability to do that, try recording a video on ur phone and see how fast it processes a 480p video. IDC if it takes a bit more time to process and if it can decode it it should be able to encode it. 528mhz magic 32a can record 640x480 so it should be possible for nexus with a far far better processor to atleast to 720p
anybody have the exact specifications of the nexus one processor, info about GPU and stuff, the problem on 720p is the excess load on processor which makes it hang and reboot
charnsingh_online said:
anybody have the exact specifications of the nexus one processor, info about GPU and stuff, the problem on 720p is the excess load on processor which makes it hang and reboot
Click to expand...
Click to collapse
This is what i could find in terms of info
http://forum.xda-developers.com/showthread.php?t=576627
http://www.edn.com/info/CA6631784.html?industryid=48661
Not sure if it helps.
I also get the FCs with H264 but not with H263.
"10mp" camera?! HDR, sports mode, night vision, and more dual-camera possibilities!
fattank said:
BlueScreen said:
1) HTC EVO 3D will isolate twin cameras to produce the firsts 180 degree panoramic photo at 5mp resolution. (Option will be in sense UI)
2) HTC EVO will produce the first ever 10mp photo on cell phone by using what is called paralax photo capture (each camera will capture an image and over lay it to produce 10mp photo) (Once again tap on 10mp photo)
3) Light sampling will be independent of each CMOS sensor to produce what will be close to night vision capture (Night Owl)
4) Camera will have a Sport mode, the 5mp camera's will function in tandem, but alternate. Each camera will burst alternately and provide crystal clear photography on high speed action events. (11 fps) I have tested this out and watch a 20ft putt go in the hole in frame, by frame increments. To be upfront burst sport mode will only work in 2d mode for obvious reasons, because the two cameras are sharing the [email protected]
Click to expand...
Click to collapse
Granted that this garbage above was initially spewed by some poser who pretended to work for HTC/Sprint... some of the ideas are genuinely clever. I've added them to my own in the list below of what could possibly result from the dual-camera setup. Tell me what you think!
Greater detail. Using both cameras at once to capture two 5mp images and "overlaying" them is interesting. Maybe adaptively "adding" the details in one to the other? Maybe using some kind of "interlaced" trick, or maybe the tilt is a bit different so both can take pictures of 2 different [but adjacent] visual fields for "instant panorama"?
Greater depth of focus. Each camera can shoot simultaneously with a different focus, and the result easily combined into a picture with incredible depth of focus.
Sport mode (shutter speed enhancement) seems like a wonderful idea. Both cameras fire, one a few ms after the other, and the result motion compensated. The perspective difference may also be used to identify and correct for motion blur. As an instantaneous "anti-shake" this would work wonderfully, too. All in all, this would allow the camera to capture faster motion with less blur!
Double speed burst-mode. Burst mode could theoretically be twice as fast, since the other lens could fire during the recovery time of the first.
Dark mode / night owl / de-graining. A fantastic idea would be to use both cameras to capture a picture simultaneously at high ISO and use a simple perspective-corrected denoiser to drastically improve quality of night scenes, which suffer most from grain issues. Each picture is bound to have a different amount of "random noise" or "camera noise" from the two cameras, and after perspective correction (and/or motion compensation if one fires after the other), the randomness is detected and removed from the combined image.
HDR (High Dynamic Range) can be achieved with no additional delay by having both cameras snap at different exposures and combining the result, solving the "low dynamic range" problem with the Sensation and other phone cameras.
Apply all of these to video. If both capture video simultaneously, there could be some benefit in 2D mode -- timestamps of the recorded frames can allow them to be combined to produce a single video of higher effective average framerate -- again, with some simple HW perspective correction filter. It could also drastically improve the quality of night video in the same way as the above "night mode" camera use with the additional potential advantage of temporal denoising, resulting in the cleanest night video you can imagine. Not to mention the first ever high dynamic range (HDR) video on a mobile device.
Click to expand...
Click to collapse
It's obvious these aren't going to be included in the official ROM, but I'm sure there can be "an app for [some of] that" provided the API of both cameras are exposed. Exciting prospect, is it not? The only one of these that seems a bit hard to chew is of course the 10mp nonsense. At most the combined detail would just produce a "very nice" 5mp shot.
Phew......someone walk a truckload of sick horses through here?
Lolz
Sent from my HERO200 using XDA Premium App
daneurysm said:
Phew......someone walk a truckload of sick horses through here?
Click to expand...
Click to collapse
I don't quite get it.
Anyway, I also think it would be neat to use the two cameras to offset an alarming trend in phone cameras -- low dynamic range. Both can fire simultaneously at different exposure settings, and combined into one HDR image.
I think what they mean by the horses, is that this is kinda crap.
It's already been known that when taking 2D pictures, it uses the top-most camera only. It uses only one. Only in 3D does it use both cameras.
random1204 said:
I think what they mean by the horses, is that this is kinda crap.
It's already been known that when taking 2D pictures, it uses the top-most camera only. It uses only one. Only in 3D does it use both cameras.
Click to expand...
Click to collapse
Ah... gotcha. More than "kinda" crap, it's genuine crock, yes.
But I'm saying the ideas are so good -- the potential is there. With a system update from HTC, these can be almost trivially enabled. Otherwise, if the API for camera 2 is accessible, an app can be created to provide the remaining functionality.
curiousGeorge said:
Ah... gotcha. More than "kinda" crap, it's genuine crock, yes.
But I'm saying the ideas are so good -- the potential is there. With a system update from HTC, these can be almost trivially enabled. Otherwise, if the API for camera 2 is accessible, an app can be created to provide the remaining functionality.
Click to expand...
Click to collapse
I think these are really cool ideas. I'm sure there will be some developer(s) out there who will develop apps to take full advantage of the 2 cameras, perhaps implementing some of the ideas you have suggested.
mlin said:
I think these are really cool ideas. I'm sure there will be some developer(s) out there who will develop apps to take full advantage of the 2 cameras, perhaps implementing some of the ideas you have suggested.
Click to expand...
Click to collapse
Cool! I just added a few more to the list, including some links and explanations of "how it could work."
curiousGeorge said:
Ah... gotcha. More than "kinda" crap, it's genuine crock, yes.
But I'm saying the ideas are so good -- the potential is there. With a system update from HTC, these can be almost trivially enabled. Otherwise, if the API for camera 2 is accessible, an app can be created to provide the remaining functionality.
Click to expand...
Click to collapse
Yea, forget all the crap that everyone spews. Anything is possible, with the devs here on xda. As Mlin said, I'm sure there will some dev or a team of devs that will develop an app to take FULL advantage of the dual cams. Granted, I'm sure there will be plents of limits on what the cams are capable of, however, I'm sure that those limits will be pushed and that we'll eventually get max potential out of the cams.
Did anyone think we'd ever get Full HDMI mirroring working on the OG Evo?
Sounds good but nobody seems to care about the camera, look at aosp cameras
daneurysm said:
Phew......someone walk a truckload of sick horses through here?
Click to expand...
Click to collapse
This about sums it up.
This might sound great and all but come to execution, I don't see it happening.
cordell12 said:
Sounds good but nobody seems to care about the camera, look at aosp cameras
Click to expand...
Click to collapse
Good point. But hopefully the actual camera hardware on the 3D will be quite nice, so more will be able to be done with it. Hopefully. I would think that there could be more potential to be unlocked in the cams, but who knows.
Anyone know which devs have said they will be coming over to the 3d to develop yet?
jayharper08 said:
Anyone know which devs have said they will be coming over to the 3d to develop yet?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1008413
Search is your friend.
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
user7618 said:
http://forum.xda-developers.com/showthread.php?t=1008413
Search is your friend.
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
Click to expand...
Click to collapse
Nice.... Thank you. It's been a long time since I've had to search for something. Totally forgot what that even meant
curiousGeorge said:
Greater detail. Using both cameras at once to capture two 5mp images and "overlaying" them is interesting. Maybe adaptively "adding" the details in one to the other? Maybe using some kind of "interlaced" trick, or maybe the tilt is a bit different so both can take pictures of 2 different [but adjacent] visual fields for "instant panorama"?
Greater depth of focus. Each camera can shoot simultaneously with a different focus, and the result easily combined into a picture with incredible depth of focus.
Sport mode (shutter speed enhancement) seems like a wonderful idea. Both cameras fire, one a few ms after the other, and the result motion compensated. The perspective difference may also be used to identify and correct for motion blur. As an instantaneous "anti-shake" this would work wonderfully, too. All in all, this would allow the camera to capture faster motion with less blur!
Double speed burst-mode. Burst mode could theoretically be twice as fast, since the other lens could fire during the recovery time of the first.
Dark mode / night owl / de-graining. A fantastic idea would be to use both cameras to capture a picture simultaneously at high ISO and use a simple perspective-corrected denoiser to drastically improve quality of night scenes, which suffer most from grain issues. Each picture is bound to have a different amount of "random noise" or "camera noise" from the two cameras, and after perspective correction (and/or motion compensation if one fires after the other), the randomness is detected and removed from the combined image.
HDR (High Dynamic Range) can be achieved with no additional delay by having both cameras snap at different exposures and combining the result, solving the "low dynamic range" problem with the Sensation and other phone cameras.
Apply all of these to video. If both capture video simultaneously, there could be some benefit in 2D mode -- timestamps of the recorded frames can allow them to be combined to produce a single video of higher effective average framerate -- again, with some simple HW perspective correction filter. It could also drastically improve the quality of night video in the same way as the above "night mode" camera use with the additional potential advantage of temporal denoising, resulting in the cleanest night video you can imagine. Not to mention the first ever high dynamic range (HDR) video on a mobile device.
Even if these aren't included in the official ROM, I'm sure there can be "an app for [some of] that." Exciting prospect, is it not? The only one of these that seems a bit hard to chew is of course the 10mp nonsense. At most the combined detail would just produce a "very nice" 5mp shot.
Click to expand...
Click to collapse
You get an "A" for thinking so far outside the conventional box, but unfortunately I don't see any real possibility of any of that ever coming to pass, for one inescapable reason: the two cameras aren't shooting from the same location. Every concept you describe requires that both cameras see the same thing, and they don't, for the simple fact that the pictures they take are from two different physical locations.
oldjackbob said:
You get an "A" for thinking so far outside the conventional box, but unfortunately I don't see any real possibility of any of that ever coming to pass, for one inescapable reason: the two cameras aren't shooting from the same location. Every concept you describe requires that both cameras see the same thing, and they don't, for the simple fact that the pictures they take are from two different physical locations.
Click to expand...
Click to collapse
Fixed-point location adjustment is trivial and can be performed in software/hardware with minimal effort (even perspective/angle adjustment via convolution-deconvolution of 3d signal matrix). Also, even if they weren't shooting from precisely the same location or perspective, the motion-compensated technique can be applied even to different frames in a video (making 'night shots' more doable), since the temporal element is the most tricky. If both cameras fire simultaneously, tracking synthetic "motion vectors" is utterly trivial.
Even if a developer was lazy and didn't want to implement perspective correction, a subset of the two pictures near the center (where they overlap) can be used for all of the rough work, and a simple guassian averaging function can perform the spreading (or simulated annealing) from that point.
No, location is certainly not a problem -- and even perspective is fairly easy to (accurately) account for via straightforward signal processing algorithms both in hardware and software.
Smells like a big fart in here
toxicfumes22 said:
Smells like a big fart in here
Click to expand...
Click to collapse
Sorry, that was me (despite your clever username).
jayharper08 said:
Nice.... Thank you. It's been a long time since I've had to search for something. Totally forgot what that even meant
Click to expand...
Click to collapse
No problem. I actually didn't use the search, either. That thread was like two below this one on the list.
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
I would really love being able to do some slow-mo videos with my SGS2, any way to do so?
The camera simply isn't built for that kind of use. You could do it, if there were software, but the framerate would be atrocious.
Here's an app for playing back videos in slow motion...
https://market.android.com/details?id=com.krovex.slowerVideo&feature=search_result
johncmolyneux said:
The camera simply isn't built for that kind of use. You could do it, if there were software, but the framerate would be atrocious.
Here's an app for playing back videos in slow motion...
https://market.android.com/details?id=com.krovex.slowerVideo&feature=search_result
Click to expand...
Click to collapse
Probably the best and only solution. The camera was only built for up to 30fps I believe. If you know how slow motion cameras work (very high frame rate), you should see how this is a problem .
I'm bringing this thread back to life to save cluttering the board up with yet another similar one. I've been looking for an app to do the same thing and have, like other searching, not found anything to suit.
The reason I'm still chasing it down is that I had the Samsung Jet before my SGSII and even given it's age and utter lack of power compared it had the feature to be able to record video at high speed so that when played back it would be very good quality slow motion (25% speed if my memory recalls correctly).
Now, if that phone could do it so long ago with little native power and a poor camera then surely the SGSII could do something like that at the very least, even if the max video size had to be dropped to 640x480 or similar to keep the framerate more locked in?
Want that too!
Can somebody pls answer this question.. Is 30fps hardware limitation?? Really??
I once had Samsung OmniaHD with 8Mpix camera, probably not much different from any other, and 320x240 resolution it was able to capture 120fps..
How can it be a limitation of hardware? Isn't it possible to write an app that would capture even 240fps at lower resolutions?
8axter said:
Can somebody pls answer this question.. Is 30fps hardware limitation?? Really??
I once had Samsung OmniaHD with 8Mpix camera, probably not much different from any other, and 320x240 resolution it was able to capture 120fps..
How can it be a limitation of hardware? Isn't it possible to write an app that would capture even 240fps at lower resolutions?
Click to expand...
Click to collapse
I'm searching for this since a year from now, I think the problem remains in the drivers and not in android SO, there is one or two android phones that support is, but I dont know how exactly, if I dont misstake samsung galaxy note 2 and one motorola has slowmotion, I belive that they build a driver to use de camera as fast as possible, on other devices I think that is not possible unless some can build such driver, and that probably will need to do in some native assembler code of each device cpu and irqs, unless the company release that driver
the functions of android to get frames from camera are very limited to useless stuff and pre-set formats and fps
I dont know whats about with android 3.1+ or 4, maybe thats SO has this functionality natively
get fast fps from a ccd camera is not a MP issue nor too much CPU requeriments nor related to amount of RAM
with a windows mobile 6.1 device such samsung omnia i900, that has a 625mhz CPU and a 5MP camera you can record 120fps in 320x240, the camera of this phone has ISO 800 (it doesn't mean 800fps, but means that it can get a very tiny little power signal from sensor in a very short amount of time) but android cameras discard this features and incorporates functions very limited and related to normal users
8axter said:
Can somebody pls answer this question.. Is 30fps hardware limitation?? Really??
I once had Samsung OmniaHD with 8Mpix camera, probably not much different from any other, and 320x240 resolution it was able to capture 120fps..
How can it be a limitation of hardware? Isn't it possible to write an app that would capture even 240fps at lower resolutions?
Click to expand...
Click to collapse
I don't think you understand the concept of cameras well. The hardware determines whether it is 30 or 60fps and not the software.
For slow motion, the highest a consumer (or affordable) camera does is 1080p at 60fps.
There are cameras like phantom hd that do well over 1k fps but they cost 100k
Sent from my GT-I9100 using Tapatalk 2
Hidden Username said:
I don't think you understand the concept of cameras well. The hardware determines whether it is 30 or 60fps and not the software.
For slow motion, the highest a consumer (or affordable) camera does is 1080p at 60fps.
There are cameras like phantom hd that do well over 1k fps but they cost 100k
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Not completely accurate.
For a consumer camera, the highest framerate at 1080p might be 60fps like you say, but some low cost consumer sensors can do high fps at lower rez. My $100 Canon Elph 100HS from 2011 will do 640x480 at 120fps or (I think) 320x240 at 240fps. I've used the 480p120 option and it came out very nice for sports use, especially for reviewing batting swings with players. The sensor tech for fairly high frame rate at decent (480p) rez is not limited to >$1000 cameras, leading me to believe it's probably more software related. I don't know enough about the sensor in the GSII though.
*Edit*
Apparently the Galaxy S II uses one of two identically spec'd (according to Anandtech) sensors from either Samsung or Sony. The Sony IMX105 specs are here. According to that page the sensor should be capable of 120fps at 1/8 sub sampling. I am not entirely sure what they mean by 1/8 sub sampling, but I would assume that it means using 1/8 of the effective pixel count or about 1M pixels. If all that is true, then the hardware should be capable of 640x480 at 120fps. Some assumptions there, though.
Why the photo resolution in Panoramic shoot mode is just 400 pixel?
It must be a mistake in some .ini file because even Samsung Wave S8500 with a less powerful HW can shoot panoramic photos at 800 pixels...
It's a shame Samsung haven't fixed this problem yet (official KI4, A2.3.5).
hexaae said:
Why the photo resolution in Panoramic shoot mode is just 400 pixel?
It must be a mistake in some .ini file because even Samsung Wave S8500 with a less powerful HW can shoot panoramic photos at 800 pixels...
It's a shame Samsung haven't fixed this problem yet (official KI4, A2.3.5).
Click to expand...
Click to collapse
I absolutely agree. That was a disappointment to me when I realized the low res of the panoramic picture. I'm hoping that ICS will bring high res panorama picture taking by standard though..
Take a couple of high-res, max-res "normal" pics and stitch them together with PanoStudio (PC App).
You'll NEVER get panos like you get that way with any built-in panoramic feature, even the panofeature of my "real" photocam suxx compared to stitching normal shots with PanoStudio - not the mention the resolution you're gonna end up with
Just saying
Camera Panorama Issue - SGSII
Eventually Pano mode sucks in all modes in SGSII, when i compare pano's with Samsung jet the quality is far much better.
Although the picture seems good on the phone, it not the case when you look at it on a pc full view!
Attached there's a re-sized sample. You could clearly notice grains.
Don't know whether you have the same issue.
Out of curiosity I just tried the pano-mode of the S2.
OMG, what a bad quallity
Original Samsung software is excellent: is fast and attached pics are near perfection, and saved in standard JPG format.
There are no good alternatives on the Android Market (= they are slow, bad quality, they save pics in custom panoramic format...), nor I want to use an alternative external app since the option is already built-in!
The only problem with GS2 is they forgot to change the 400pixel resolution (probably for low-end Android phones). It's actually UNUSABLE at 400 pixels. A real pity because for example Samsung Wave S8500 can do much better and uses the same internal software (I guess), but is set to 800 vertical pixels!
Here is a quick comparision between GS2 unusable 400 pixel resolution, and Wave S8500:
Wave:
GS2:
As you can see the poor 400pixel version of Gs2 is unusable. A picture quality worth a 6 years ago cheap phone (below the old VGA standards), without reason.
What really surprises me is that NOBODY's done something to fix this problem. They are all hardly working in customizing fancy video effects and custom roms but nobody ever took a look to the Panoramic camera shoot and released at least a mod-fix for this phone....
We have a powerful and very nice option we can't actually use, because of a Samsung mistake.
The difference is alot !!
I always use the stock camera app for best results
So many updates recently and still haven't been solved...I hope that one day we can notice that it has been fixed because using panorama at this stage is totally useless...
Still the same after more than 1 year?????
Nobody in Samsung even noticed this?
Do we look like Samsung to you ? Complain to/ask them. Nothing will be done about it if you moan about it in a thread on XDA. If you really want something done about it, go straight to the source.
Isn't there a mod fix for this at least?
By the way, FYI, reporting something in a forum may wake up also other users and move much more than a useless single mail to the Samsung support center that will reply with the usual form "Thank you for your interest... bla bla" and stop.
Forums exist also to discuss about problems and bugs. Oh, and I've reported to Samsung the problem with poor Panoramic shoot resolution at least 12 times already...
I Found This In A N4 Thread.
Just Add This Line To build.prop And Reboot.
Code:
debug.egl.swapinterval=0
Again,This CAN Cause Glitches,So Depends On The User.
NOT RECOMMENDED FOR DAILY USAGE.
Enjoy.
Here Are Some Benches.
Nenamark 2-144fps
Quadrant-8264
Regards,
acervenky,
XPT
Works! Pass Mark bench is the highest 4716
Can see as high as 102 during quadrant.
OG e970 stock+
mystery emotionz 6.1
1.8 GHz oc/uv
Does this have any other benefits beyond benchmark
I've had some interesting results enabling this.
I havent run any benchmarks, but running GTA Vice City with this enabled does make for smoother gameplay, but also gives minor graphical tearing .
As far as I know, our screens are only 60hz. Anything above 60fps is almost pointless and would cause more harm than not. Yes, you may see smoother gameplay, but you're overworking the GPU for a slight boost and visual problems.
I'm not a developer or anything of the sort from Android but I do a LOT of tinkering and programming with computers so I expect the same results since smart phones are Pretty much the same.
Sent from my CM10.2 LG-E970
I would wager this is harmful.... As the user above me pointed out they're no gains to be had in terms of usage.
Outside of that it's one thing to go past 60 fps on a desktop or even laptop designed to handle more intense graphics but, there is no exhaust in your phone which works twice as hard for no real reason.
The excess heat just increases your chances of nasty things happening.. And I mean nasty you need a new phone before 2 years type things.
Sent from my LG-E970 using xda app-developers app
Warning heeded... I don't game though I just like to tweak. I never use intense graphics for long stretches and it makes a difference in short bursts when I'm browsing video heavy sites or watching short videos (placebo, maybe). I'm also a benchmark whore (no shame). I expect to not make two years anyway. .. G2 is sweet and who knows what will be here by next summer, lol. Thanks though.
OG e970 stock+
mystery emotionz 6.1
1.8 GHz oc/uv
---------- Post added at 07:54 AM ---------- Previous post was at 07:43 AM ----------
Neroga said:
As far as I know, our screens are only 60hz. Anything above 60fps is almost pointless and would cause more harm than not. Yes, you may see smoother gameplay, but you're overworking the GPU for a slight boost and visual problems.
I'm not a developer or anything of the sort from Android but I do a LOT of tinkering and programming with computers so I expect the same results since smart phones are Pretty much the same.
Sent from my CM10.2 LG-E970
Click to expand...
Click to collapse
You may be thinking refresh rate... that's the screen measurement. I've never seen one for a phone. Fps is video source measure, chip. I'm definitely no techy, but would it cause that much more heat... it's not overclocking (although I am) just running at higher speeds longer, maybe. No extra heat yet, mhl for movies most intense thing I've done since tweak though.
OG e970 stock+
mystery emotionz 6.1
1.8 GHz oc/uv
Ok, time to clear some stuff up. Unless specifically stated in a lcd display's specifications, and it was made in the last few years, it only supports up to a 60hz refresh rate. No matter what you do, you can't make it refresh faster. You'll just get screen tearing and your GPU will consume more electricity and generate more heat. This isn't a cathode ray tube display with adjustable refresh rate.
Sent from my Optimus G using xda premium
Frame rate/Refresh rate the same?
I was just wondering if frame rate and refresh rate are both the same. For example in a PC if the screen's refresh rate is , say 60 Hz. Won't it be able to display anything with frame rates greater than 60? If so, I beleive it applies to the mobiles too. Can someone clear up this mystery for me with some citations?
Thanks
Andromann said:
I was just wondering if frame rate and refresh rate are both the same. For example in a PC if the screen's refresh rate is , say 60 Hz. Won't it be able to display anything with frame rates greater than 60? If so, I beleive it applies to the mobiles too. Can someone clear up this mystery for me with some citations?
Thanks
Click to expand...
Click to collapse
Correct and as Death said, it'll cause screen tearing on mobile devices. 60fps matches the 60hz of our screens. I'm not too familiar with how this works on Android, but if you could raise the fps to about 65 then you'd notice a boost in performance when it comes to games. 60 is ideal for gaming but with the cap at 60 it tends to dip below frequently and causes slight lag. 65 would make everything stay nice and smooth and shouldn't give you any graphical errors as well as not burning battery life.
Sent from my Paranoid 4.3 LG-E970
Neroga said:
Correct and as Death said, it'll cause screen tearing on mobile devices. 60fps matches the 60hz of our screens. I'm not too familiar with how this works on Android, but if you could raise the fps to about 65 then you'd notice a boost in performance when it comes to games. 60 is ideal for gaming but with the cap at 60 it tends to dip below frequently and causes slight lag. 65 would make everything stay nice and smooth and shouldn't give you any graphical errors as well as not burning battery life.
Click to expand...
Click to collapse
mmm.. i'm sorry but i think that you're confusing fps caps with vertical synch, fps caps give almost no fps drops because it only throw away every frame superior to the cap, but with vsync caps it to 60fps but it synchronize it with the lcd hz, fps caps can cause tearing even at same framerate than lcd hz but vsync doesn't
D4rk_W0lf said:
mmm.. i'm sorry but i think that you're confusing fps caps with vertical synch, fps caps give almost no fps drops because it only throw away every frame superior to the cap, but with vsync caps it to 60fps but it synchronize it with the lcd hz, fps caps can cause tearing even at same framerate than lcd hz but vsync doesn't
Click to expand...
Click to collapse
A fps cap does not discard frames. It will not render the extra frames. The GPU will fills it's clocks with NOP instructions until it needs to render the next frame.
Wouldn't this be useful if someone has attached his smartphone to External display , which supports displays with higher refresh rates .:good: