Am I right in thinking that this only affects low light performance in videos and not photos? Also the caveat is that it's no good for concerts?
Does this apply even for the 5s as well?
Does this apply even for the 5s as well?
Am I right in thinking that this only affects low light performance in videos and not photos? Also the caveat is that it's no good for concerts?
Does this apply even for the 5s as well?
Strange it would do that. Here, a Cydia repo not responding to HTTP requests would only result in the Cydia client's elongated, but definitely cancelable Package.gz fetching during refreshing. Strange the Cydia packages would be refreshed during booting up - I've never seen anything like that (and it'd be pretty pointless - why would Cydia fetch the packages, anyway, other than updating the badge of updated apps?).
All in all, it's highly unlikely the Cydia timeout caused the boot issue - unless the Evasion 7 JB has a bug.
(BTW, my repo is working again.)
Videos only.
1, better low-light performance (on the expense of lower-than-30p framerate on the 5s)
2, wider and significantly taller image (that is, significantly wider FoV)
Rock concerts was an example where my tweaked mode shouldn't be used - there, steady 30p is needed, which not even on the 5s is feasible under bad lighting, let alone less capable iDevices. As opposed to scenes / subjects with little movement, where the gains in the wider FoV or low-light performance easily outweigh the framerate drop problem - a conference or lecture, for example.
For lack of better terminology, does it rely on the user to be more stable when taking videos?
Best way I can describe what I'm asking is when taking photos during the day and at night, the higher ISO means if there is any shake, 9 times out of 10 you'll end up a blurry photo.
Does this also apply to when taking videos with this new lower light mode, does it require absolute stablility to not end up with blurry videos (more so than what is usual)
Will a tweak ever be possible to get better low light performance out of older devices (or even make the newer devices better in low light)?Yup, no image stabilization is utilized either. After all, Apple's current iDevices all lack teh superior Optical IS; the only IS they have is the inferior electronic, which uses the outermost area of their sensor. That's one (but not all) of the reasons they have (even horizontally) far narrower FoV during video shooting than during shooting stills.
Will a tweak ever be possible to get better low light performance out of older devices (or even make the newer devices better in low light)?
Different question, did a test video and can instantly see the difference on playback on the 4s I'm using to test. I tried to copy the 2 files to my (Windows) machine, the standard video plays fine in WMP but the tweaked video doesn't play on WMP but does in QT player (which I can't stand), why is this?
Am I getting this right ?
- This tweak is only for videos..
- I should use this tweak when the subjects I'm recording don't move fast
and they are in a low light scenario.
I should not use this tweak when I'm at a concert
or I'm recording fast moving objects (car races, bike tricks, kids running etc)
and the scenario has normal light conditions.
Yes.
Yes
Not necessarily. In low light, my tweaked mode "brightens up" the image because of the upsampling. However, it reduces the framerate even further, even on the 5s.
Therefore, under low light, you may want to prefer my mode to the factory one if you'd prefer as bright image as possible, even with the framerate suffering.
Depends on what kind of concert. Rock concert with plenty of movement? Avoid it. Classical (e.g., piano)? Might be OK.
Yup, in these cases it is to be avoided.
It works just fine in normal light on the 5s.
The other main advantage of the tweak is the significantly wider FoV.
#!/bin/bash
dirnames=( N90 N94 N41 N42 N51 N53 J2a P101 P103 )
for currIteratedSubdirname in ${dirnames[@]}
do
dirname=/System/Library/Frameworks/MediaToolbox.framework/$currIteratedSubdirname
if [ -d $dirname ]; then
chown mobile $dirname/AVCaptureSession.plist
chmod o+w $dirname/
exit 0
fi
done
echo !!!!!
echo !!!!!
echo !!!!!
echo !!!!!
echo Incompatible hardware - check if you have supported hardware!
echo !!!!!
echo !!!!!
echo !!!!!
echo !!!!!
exit 255
NSArray* dirNameArr = @[@"N90", @"N94", @"N41", @"N42", @"N51", @"N53", @"J2a", @"P101", @"P103"];
NSString* dirPrefix = @"/System/Library/Frameworks/MediaToolbox.framework";
BOOL subdirFound = NO;
for (NSString* currSubdirName in dirNameArr)
{
NSString* fullDirPath = [NSString stringWithFormat:@"%@/%@", dirPrefix, currSubdirName];
BOOL fileExists = [[NSFileManager defaultManager] fileExistsAtPath:fullDirPath];
if (fileExists)
{
self.plistSubdirNameOfCurrDevice = currSubdirName;
subdirFound = YES;
break;
}
}
if (!subdirFound) exit(255);
to do anything else?:
Does a higher bit rate mean less stress on the H264 encoder/decoder hardware? Since the compression would be lower
Would this increase frame rate? (In cases where it would normally drop below 30 fps)
I can't find " AVCaptureMode_AudioVideoRecording> LiveSourceOptions>"