Related
ALL THE CREDIT FOR THIS FIX GOES TO GALNET
Galnet posted a fix for 720p choppy recording in the MIUI post.
The problem I found was that it didn't work for everybody.
So, after doing a tkdiff on the changed file for the fix: media_profiles.xml, I saw that the 720p fix is a change of the recording bitrate from 12,000,000 to 10,000,000.
For my phone it wasn't enough and I was still getting choppy recordings, so lowered the bitrate even further to 5,000,000 and now I have flawless 720p recording!!!
How to fix the issue:
1) Make /etc/ R/W (use root explorer)
2) Edit the file: media_profiles.xml and change the bitrate line:
<CamcorderProfiles cameraId="0">
<EncoderProfile quality="hd" fileFormat="mp4" duration="60">
<Video codec="h264"
bitRate="12000000"
to:
bitRate="5000000"
3) save the file
4) make /etc/ R/O again
5) enjoy 720p recording
NOTES
1) HD playback is still choppy -- so you have to transfer the file to your computer to test!!!
2) You can try and increase the bitrate from 5000000 to 10000000 (which was GALNET's original value) -- and if it is still good for you great.
THANKS A LOT GALNET!!!
Somebody knows what the bitrate is for 720p videos in Samsung roms?
JVP:
quality = 'high'
fileformat = 'mp4'
duration = '60'
video codec = 'h264'
bitrate = '10000000'
width = '1080'
height = '720'
framerate = '30'
HaTeNL said:
Somebody knows what the bitrate is for 720p videos in Samsung roms?
Click to expand...
Click to collapse
On XXJVP rom the bitrate for recorded 720p videos is ~12mbps
When on cm7 i found out that playing with different cpu governors influences the 720p choppiness more or less as well. Conservative governor messes 720p up, while on demand improved it....but didnt get rid of it.
Havent tried galnet's fix or their latest miui but on a pc the reported bitrate of 720p material from SGS is ~12mbps + ~2mbps audio track
Im on Doc kitchen jvp rom now with SGS2 camera app and works butter smooth. Its not just the recorded material that is smooth but also when panning around just after starting the camera app is very fluid (as opposed to cm7/miui)
Thanks! I also found out about this workaround by looking at the patch to 7.7, which diff showed a change from 12,000,000 (in 7.5) to 8,000,000. I don't recommend lowering that value to 5,000,000 because more kb/s = smoother video. Though I noticed something strange:
1. After upgrading to 7.7 (8,000,000 bitrate), I tried catching a HD video with MiuiCamera, that produced a very choppy video (still...) with unsynced audio.
2. I catched another 720p video with Android Camera, and the result was better, though I don't like the m4v container for the output files.
3. I used MiuiCamera to record another HD video, but this time it was perfect!
4. The following videos shot by MiuiCamera were still as good, even after a reboot, for now.
So, I don't think we require the Camera.apk to make MiuiCamera.apk work as it should. There is probably something about the governor or kernel ticks (HZ) which is clashing with the 720p recording. For the "record" (lol), I'm using the smartass governor on Zach's NEO 08, while scheduler and OC/UV don't seem to have a high relevance.
Also, why does MiuiCamera produce a 3gp video for 720p recordings, while it's clairly specified to use the mp4 container? I also used Avidemux and ffmpeg to check the video, and it has a 1280x720 resolution with H.264 and AAC codecs. So, why the 3gp extension?
EDIT: I forgot, have you understood why the m4v max bitrate was lowered to 2,000,000 while stock JVP has 12,000,000 ?
Any other feedback aside from this comment?? I would appreciate if you guys found a way recording a nice 70p vdieo from my phone
Currently on CM7 recording is bad, doen't work properly. Users from galnetMIUI forums claim that recording works fine with Chameleon release. Fix is not public, so... CM7 hasn't got proper 720p video recording
It isn't the unique change...
Probably some more changes in the kernel also.There was a thread on their forums, where a user said thar 720p recording works only with default kernel, while with custom kernels doesn't. It's quite annoying, using a stock/custom ROM based on official looks really slow for me, using CM7 feels really good and fast... but with the loose of recording, which I really need for my little girl's unique moments in life recording. The High setting for camera in CM7 makes recording possible, there are very small glitches sometimes, but it's a pitty to not use it a fully potential.
Thats not a "fix"? It just lowering the bitrate which means less smoothness and worse quality.
That aint a "fix" for the problem to me
Actually looking at the xml file mentioned in the first post, in the case of latest nightly of CM7 the value is 10000000. But, keep in mind that the post is from june, and in the meanwhile the real fix came with galnetMIUI chameleon (or something) which is later. So, they must have figured it out in the meanwhile...
worked for me
Worked for me.
I decreased HD bitRate from 10000000 to 5000000 bps
also decreased HIGH bitRate from 3000000 to 2000000
my video is now playing quite smooth.
Thanks
SGS I9000, Cyanogen 7.1.0
is this applicable to galnet miui weekly?
screwing around with the lgcamrecorder app settings may help?
on HD i' 10000000 too, but had ploblems on recording. record in format M4V, but look mediaprofiles it wrote as MP4. why it record different format?
I have a issue with the video recorder in CM7. I had this in RC1v2 and also in latest nightly, don't know in versions before that.
I can't use the high and youtube resolution setting. I can select them, but when I press the record button nothing happens. The other settings, for example wide, do work.
Is this normal? If not is there a sollution to solve this?
I installed Nordic rom and reinstalled CM7 latest nightly, that didn't solve my issues.
However changing the frame rate for the encoder profiles (in media_profiles.xml) to 24 did. (this was a suggestion in the developers forum). Now I can use all resolution settings.
My defy has red lens.
During testing I also noticed that the standard bitrate for the high and wide recording setting are really high.
For a 640x480 (high) mp4 video it is 10000 kb/s
For a 848x480 (wide) mp4 video it is 8000kb/s
This a lot higher then most good looking xvid 720p movies I have , which are around 2000 kb/s.
I now use 1300 kb/s (high) and 1500 kb/s (wide) which seems to give usable results but with a lot smaller videos.
Which settings do other people use/suggest?
Try the newest LG Cam (free) from market an set it to these parameters:
video resolution: 848x480
video encoder: mpeg4
video file format: mpeg4
video bitrate: 8
video framrate:24
audio encoder: ACC
audio samplerate: 44100
audio bitrate: 62900
and check force autofocus before capture
This works great on mey Defy (red lense)!
After much experimentation, I have found that the epic prefers 5:3 aspect ratio. If you want the maximum in clarity and optimized file size for your videos, here are the settings I came up with. Adding more to either bitrate wont help the quality.
Customized MP4 Movie (*.mp4) template in Freemake
Video Code: MPEG4 (NOT h.264 or x264)
Frame Size: 1000x600 (5:3 ratio)
Video Bitrate: 1280
Video framerate: 24
Encode Passes: 2
Audio Codec: AAC
Audio Bitrate: 160
Sample rate: 44100
Audio Channels: 2
Disable Audio: No
A/V Sync: Default
These settings work great on my Arnova 10b (Capacitive) and my Touchpad. They would also work great in an iPad or XBOX. I used the high resolution to fill the screen of my Arnova without stretching. It works fine on my Epic.
Here the question: Why 5:3? Any other aspect ratio does not actually fill the screen. If you make a 800x600 (4:3) video, you will find that the player does not actually fill the screen. Thoughts?
The screen resolution is 800x480, which is 5:3...
Just make the video 800x480, and it won't have to do any scaling.
Interesting. Gonna check my videos and see what res I have them in, because they look awesome as it is.
LunaticWolf said:
The screen resolution is 800x480, which is 5:3...
Just make the video 800x480, and it won't have to do any scaling.
Click to expand...
Click to collapse
I did that resolution... It worked great for my epic.. I settled on the resolution I used because it worked awesome on all my devices.. even my touchpad. The cost in file size is almost nothing between the two resolutions.
Ok, I have a 720p video.. it looks amazing at its normal resolution of 1280x720.. no cropping that I can notice..
I'm an editor by trade.
What you're looking for is H.264 in .mp4. I tend to go for a video bitrate that hangs out around 1.5mbps and AAC stereo audio at 160kbps, 44.1kHz. There are quite a few artifacts in the shadows, but for watching a movie on an airplane it'll suffice.
The key to both a sharp picture and long battery life is to properly prepare the video. When your video is under or over 800px wide the Epic has to perform scaling to make it fill the screen (or sacrifice filling the screen if it is under). This scaling is an additional calculation it must perform, which hits the battery, and is a transformation on a lossy codec - a quality killer. If you have the render power (48 i7 cores and segmented processing makes for fast work) you can always hit it with mild sharpening for that extra pop.
Export your video at 800 pixels wide by whatever makes the correct aspect ratio. It's a bit of simple algebra, set up a proportion, cross-multiply, divide, and bang.
ex:
(1280/720)=(800/x)
1280x=720*800
1280x=576,000
x=450
800x450 <-- use this for any 16x9 broadcasts
(1.85/1)=(800/x)
1.85x=800
x=432
800x432 <-- use this for movies presented in 1.85:1, 2.35:1, and 2.40:1.
If it's 4x3 export at 640x480.
I just scale up to 4k. Looks pretty good =D
Questions for all the OP3 Users. Can it play HEVC x265 1080p 10bit 30FPS Videos in HW/HW+ Mode on MXPlayer?
Are there any Artifacts or it lags and sttutters?
i have been Asking This question but only 2 OP3 users have replied.
One says it cant play in HW only SW mode. Other Says It Can on Stock ROM.
If Few more users confirm it does or does not, then it will help me decide to buy this one or Le Max 2.
Please Reply.
Thanks in Advance.
I played h.265 videos encoded in 10bits and 1080p23 through the stock video player as well as mxplayer with HW and HW+ modes. I also played a 4k 60fps 10 bit video used to showcase the samsung 4k tvs with no issues what so ever. HW playback yet again. Both on the stock ROM and kernel.
Mine on stock Oxygen ROM.....10Bit x265 CAN'T play in HW/HW+ mode...only in SW.
However, 8Bit x265 CAN play in HW/HW+ without problem.
EDIT: Got mine solved now my OP3 can play x265 10bit video file in hw+ .
sample from here http://demo-uhd3d.com/fiche.php?cat=uhd&id=45
H265 10bit, up to 23.976fps
Resolution : 3840x2160
File size : 655 MB
Duration : 01min 46sec
Format : TS
Codec : HEVC
Overall bit rate : 51.4 Mb/s
Bit depth : 10 bits
Frame rate : 23.976 fps
rom:
OXYGENOS 3.2.1
Yes it can play without stutters with HW+ turned on
also
this http://demo-uhd3d.com/fiche.php?cat=uhd&id=96
H265 10bit, 59.940fps
Resolution : 3840x2160
File size : 818 MB
Duration : 02min 12sec
Format : TS
Codec : HEVC
Overall bit rate : 51.6 Mb/s
Bit depth : 10 bits
Frame rate : 59.940 fps
rom:
OXYGENOS 3.2.1
Played without stutters with HW+ turned on
and this one: http://demo-uhd3d.com/fiche.php?cat=uhd&id=144
HDR 10bit HEVC, 59.940fps
Resolution : 3840*2160
File size : 1120 MB
Duration : 02min 07sec
Format : MP4
Codec : HEVC
Overall bit rate : 75.8 Mb/s
Bit depth : 10 bits
Frame rate : 59.940 fps
Played without stutters with HW+ turned on
lokr said:
sample from here http://demo-uhd3d.com/fiche.php?cat=uhd&id=45
H265 10bit, up to 23.976fps
Resolution : 3840x2160
File size : 655 MB
Duration : 01min 46sec
Format : TS
Codec : HEVC
Overall bit rate : 51.4 Mb/s
Bit depth : 10 bits
Frame rate : 23.976 fps
rom:
OXYGENOS 3.2.1
Yes it can play without stutters with HW+ turned on
also
this http://demo-uhd3d.com/fiche.php?cat=uhd&id=96
H265 10bit, 59.940fps
Resolution : 3840x2160
File size : 818 MB
Duration : 02min 12sec
Format : TS
Codec : HEVC
Overall bit rate : 51.6 Mb/s
Bit depth : 10 bits
Frame rate : 59.940 fps
rom:
OXYGENOS 3.2.1
Played without stutters with HW+ turned on
and this one: http://demo-uhd3d.com/fiche.php?cat=uhd&id=144
HDR 10bit HEVC, 59.940fps
Resolution : 3840*2160
File size : 1120 MB
Duration : 02min 07sec
Format : MP4
Codec : HEVC
Overall bit rate : 75.8 Mb/s
Bit depth : 10 bits
Frame rate : 59.940 fps
Played without stutters with HW+ turned on
Click to expand...
Click to collapse
Can you play x265 10bit in mkv format in hw/hw+? Mine cannot..Dont know why.
Yup, it can play tested with jellyfish-120-mbps-4k-uhd-hevc-10bit.mkv 438 MB http://jell.yfish.us/media/jellyfish-120-mbps-4k-uhd-hevc-10bit.mkv
and with jellyfish-100-mbps-hd-hevc.mkv 100 Mbps 365 MB http://jell.yfish.us/media/jellyfish-100-mbps-hd-hevc.mkv
give some links with vids that OP3 cannot play so I will check on mine, my op3 have all stock, no root.
lokr said:
Yup, it can play tested with jellyfish-120-mbps-4k-uhd-hevc-10bit.mkv 438 MB http://jell.yfish.us/media/jellyfish-120-mbps-4k-uhd-hevc-10bit.mkv
and with jellyfish-100-mbps-hd-hevc.mkv 100 Mbps 365 MB http://jell.yfish.us/media/jellyfish-100-mbps-hd-hevc.mkv
give some links with vids that OP3 cannot play so I will check on mine, my op3 have all stock, no root.
Click to expand...
Click to collapse
Nevermind....I get it play fine now in hw+. All I did was to change the mkv extension of the 10bit x265 video file that refused to play in hw/hw+ to mp4. It played fine in hw+. Change it back to mkv...it also play fine in hw+. Now all my x265 10 bit mkv can play in hw+. Weird!!
Thanks Everyone.
I think i will buy this.
sorry for jacking this thread, but can anyone try hi10p h264 in this phone? I want to know before getting this phone.
I'm currently on zenfone 2 which is x86, no problems with h264 hi10p.
xjammetx said:
sorry for jacking this thread, but can anyone try hi10p h264 in this phone? I want to know before getting this phone.
I'm currently on zenfone 2 which is x86, no problems with h264 hi10p.
Click to expand...
Click to collapse
Short answer would be "yes, as long as it's not 4k".
For the long version, it depends on several encoding characteristics. These are video grain, bitrate, framerate (taking anime into consideration, there shouldn't be any 60fps releases so it's okay), chroma subsampling (4:4:4 and 4:2:2 being more CPU intensive to decode than the usual 4:2:0) and colour space (BT.601 and BT.709 are more widely supported and easier on the CPU than BT.2020, but you'd need a beast of a desktop CPU to software render anything in the BT.2020 space anyway, not a mere phone).
If the SSA subtitles are heavily animated, you can't do much about it. You'd need to find a video player on android that can properly render it, or hope that overclocking the phone might reduce the subtitle lag. Testing the file you linked on the MX Player 10-bit playback topic, it seems that the CPU usage doesn't increase by much with the subtitles flying around the screen, but the delays are noticeable while MX Player struggles to render them. It ain't as bad as you might imagine, as there aren't many dropped frames, but the frame representation is delayed severely. As a sidenote, reducing the rendering quality of the video doesn't affect the subtitle rendering lag in any way.
Dariusdd said:
Short answer would be "yes, as long as it's not 4k".
For the long version, it depends on several encoding characteristics. These are video grain, bitrate, framerate (taking anime into consideration, there shouldn't be any 60fps releases so it's okay), chroma subsampling (4:4:4 and 4:2:2 being more CPU intensive to decode than the usual 4:2:0) and colour space (BT.601 and BT.709 are more widely supported and easier on the CPU than BT.2020, but you'd need a beast of a desktop CPU to software render anything in the BT.2020 space anyway, not a mere phone).
If the SSA subtitles are heavily animated, you can't do much about it. You'd need to find a video player on android that can properly render it, or hope that overclocking the phone might reduce the subtitle lag. Testing the file you linked on the MX Player 10-bit playback topic, it seems that the CPU usage doesn't increase by much with the subtitles flying around the screen, but the delays are noticeable while MX Player struggles to render them. It ain't as bad as you might imagine, as there aren't many dropped frames, but the frame representation is delayed severely. As a sidenote, reducing the rendering quality of the video doesn't affect the subtitle rendering lag in any way.
Click to expand...
Click to collapse
thanks for the reply.
how about 40Mbps~ coalgirl's level encodes?
Will you test a file for me?
xjammetx said:
thanks for the reply.
how about 40Mbps~ coalgirl's level encodes?
Will you test a file for me?
Click to expand...
Click to collapse
https://www.nyaa.se/?page=view&tid=789147
Tried that one. It's bloated and the noise levels are over the top. Simply put, it lags during high bitrate scenes, doesn't during lower bitrate scenes. It is rather watchable with just a few dropped frames if you lower the colour format from YUV to 16 bit RGB and use speedup tricks which butchers dithering and makes the video blocky with visible dither artifacts. Even so, the processor usage sits usually at 100%
I've also tried: http://coalgirls.wakku.to/657/evangelion the first movie in 1080p.
It works fine, colour format YUV with no speedup tricks. The processor usage jumped between 55 and 90%. Do note that this has only ~17Mbps bitrate. I think that 40Mbps is a bit farfetched as well as useless on a screen this small. Fortunately, most encodes have more reasonable bitrates, so it shouldn't pose much of a problem.
Tested on arter97's CM13 + kernel using MX Player Beta 1.8.6. This also means the processor had stock clockspeeds. For 10 bit h264 decoding, Samsung's Exynos 8890 and Huawei's Kirin 950/955 should be a little better than Snapdragon 820. I don't know by how much, but you should take note that the Galaxy S7 had its codec support gimped by Samsung (specifically, it lost 10 bit h265 decoding) after a certain update for both Exynos and Qualcomm versions, and I am not sure about the current codec support of HiSilicon chips like the Kirin.
Dariusdd said:
https://www.nyaa.se/?page=view&tid=789147
Tried that one. It's bloated and the noise levels are over the top. Simply put, it lags during high bitrate scenes, doesn't during lower bitrate scenes. It is rather watchable with just a few dropped frames if you lower the colour format from YUV to 16 bit RGB and use speedup tricks which butchers dithering and makes the video blocky with visible dither artifacts. Even so, the processor usage sits usually at 100%
I've also tried: http://coalgirls.wakku.to/657/evangelion the first movie in 1080p.
It works fine, colour format YUV with no speedup tricks. The processor usage jumped between 55 and 90%. Do note that this has only ~17Mbps bitrate. I think that 40Mbps is a bit farfetched as well as useless on a screen this small. Fortunately, most encodes have more reasonable bitrates, so it shouldn't pose much of a problem.
Tested on arter97's CM13 + kernel using MX Player Beta 1.8.6. This also means the processor had stock clockspeeds. For 10 bit h264 decoding, Samsung's Exynos 8890 and Huawei's Kirin 950/955 should be a little better than Snapdragon 820. I don't know by how much, but you should take note that the Galaxy S7 had its codec support gimped by Samsung (specifically, it lost 10 bit h265 decoding) after a certain update for both Exynos and Qualcomm versions, and I am not sure about the current codec support of HiSilicon chips like the Kirin.
Click to expand...
Click to collapse
mean/average bitrate of that movie must be near to (((18823.5 * 10^6) *8) / 7200) * 10^-6
or 20.91500 Mbps
try this one
http://coalgirls.wakku.to/6368/nisemonogatari
^
try that, just get the
Code:
[Coalgirls]_Nisemonogatari_OP3_(1920x1080_Blu-ray_FLAC)_[948BD021].mkv
(((458.18 * 10^6) * 8) / 90) * 10^-6
40.7271111 Mbps on average.
^ my zenfone 2 decodes that file with no problems, given that its an x86 architecture rather than arm.
xjammetx said:
try this one
http://coalgirls.wakku.to/6368/nisemonogatari
Click to expand...
Click to collapse
Using YUV there are a few dropped frames between 1:20 and 1:27, otherwise it's a flawless playback. Using RGB32 there aren't any visible dropped frames during the entire run. I've tested it several times. During those 7 seconds, the processor stays at 100% usage, otherwise it sits around 80-85%. Understandably, the phone gets hot and the battery drains like mad.
I don't think sustained playback at these levels of processor usage is good for the device.
A few weeks ago I decided to use h.265 in every device at home, I managed to reduce videos from 1 GB to 300 MB without sacrificing quality.
So I´m curious if the HTC 10 or HTC U11 are capable of video record with h.265 codec. I know Snapdragon 810, 820, 835 are capable of using H.265 codec.
As far as I know camera takes the video and audio information from media_profiles.xml file. Is it just as simple to copy a preset video and audio config from any other devices as OnePlus 3/3T?, as I see some of forums from OnePlus changing video configuration to use 60FPS with the ported ZSL Google Camera.