We all know that op7t doesn't shoot HDR videos but its does take decent quality [email protected] fps although only unto 5 minutes even after android 11. Theoretically new android os supports writing files more than 4gb but I don't know why still the restriction.
Anyways more than HDR I am always fascinated with wide color gamut which comes with Rec.2020 as the videos look more vibrant and exciting. May be I like to remember places I have visited with this vivid look. So while fiddling with ffmpeg to reduce video size when hevc recording was not supported, I came across a strange behavior of my videos shot with OnePlus 7t. This has been same on official oxygen os android 10 and now 11.
This somehow doesn't apply to [email protected] fps as they still have 1-1-1 Rec. 709 (HD) color profile. But if you notice when you shoot [email protected] the resulting videos have 5-1-6 PAL SD color profile. With a simple command in ffmpeg I was able to change these videos to a richer color profile 9-1-9: Rec. 2020 SDR and I simply love the results.
Before we go any further, for those of you who d like to experiment here is the command to run with ffmpeg. Its independent of phone so If your video is shot from other devices it may work as long as the video has enough data to provide such colors. As I found Rec.709 HD didn't have.
Code:
ffmpeg -i input.mp4 -c copy -color_primaries bt2020 -color_trc bt709 -colorspace bt2020_ncl -color_range pc -bsf:v h264_metadata=video_full_range_flag=1:colour_primaries=9:transfer_characteristics=1:matrix_coefficients=9 output.mp4
As you can notice that these parameters are for videos shot without HEVC selected in the new settings. Advanced users can figure out similar command for hevc videos to experiment.
I have attached a screenshot for reference in which I paused the two video files at same point. The above part is 5-1-6 PAL SD and bottom is 9-1-9 Rec.2020 SDR.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let me know how your experiment goes and what's your take on this. Do you like the videos as they were or with this is new color definition.
This is really cool, thanks for sharing! I've updated your post to enclose the command in a code block
since I have been using the new hevc option in oos11 on my OnePlus 7t, I searched online for a simple solution as above to change color profile of videos.
here it is for use in ffmpeg with hevc videos
Code:
ffmpeg -i INPUT.mp4 -codec copy -bsf:v hevc_metadata=colour_primaries=9:transfer_characteristics=1:matrix_coefficients=9 OUTPUT.mp4
Related
Hello
Is it possible that we can enable 720p in CyanogenMod also is their any alternate camera app for Android?
Thanks
Macfan
It's possible at the moment, just not intuitive. Set the video quality to custom. Then set the video encoder to H.264 then farther up that same menu set it to 720P.
Sent from my T-Mobile G2 running Cyanogenmod.
ibemad1 said:
It's possible at the moment, just not intuitive. Set the video encoder to H.264 then set farther up that same menu set it to 720P.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
This worked. thank you
I don't have a choice for what codec to use. H264 is selected, and H263 and MPEG4 are grayed out. Also, every resolution option is grayed out. I don't even see an option for "720p". I see the resolution names like "XVGA" and "HVGA", and they're all grayed out. My camera can apparently only shoot in 720p with H.264. Anyone have a clue why this is?
Here's a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ohhhhhh, I figured it out. You have to choose Custom quality first, then all the options open up. If you choose High Quality it forces H264 and 720p. Funny thing: Now that I set it to Custom then back to High, I now see "720p" in my list of resolutions and it's selected. Previously, it wasn't there at all.
Edited my previous post to include that (critical) piece of data
Sent from my T-Mobile G2 running Cyanogenmod.
ibemad1 said:
It's possible at the moment, just not intuitive. Set the video quality to custom. Then set the video encoder to H.264 then farther up that same menu set it to 720P.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
Searched for this question in the forum and found your answer, seemingly written with me in mind. Thanks! Props to the OP, as well. Baller ****.
elusivebyte said:
I don't have a choice for what codec to use. H264 is selected, and H263 and MPEG4 are grayed out. Also, every resolution option is grayed out. I don't even see an option for "720p". I see the resolution names like "XVGA" and "HVGA", and they're all grayed out. My camera can apparently only shoot in 720p with H.264. Anyone have a clue why this is?
Here's a screenshot:
Ohhhhhh, I figured it out. You have to choose Custom quality first, then all the options open up. If you choose High Quality it forces H264 and 720p. Funny thing: Now that I set it to Custom then back to High, I now see "720p" in my list of resolutions and it's selected. Previously, it wasn't there at all.
Click to expand...
Click to collapse
i have no "custom quality" option..( i am on cyanogenmod 7)
Hi All,
I am unable to find all the features promised by JRC in the 4.4.4 update. - I personally am using the ARHD 20.1.
Features as described on this page: http://www.htc.com/us/innovations/eye-experience/
Automatic selfies/voice selfies. Found in settings.
Videochat. I have not been able to try this yet.
Split capture. Select it in modes. (Lame)
Crop-me-in. - I am unable to find this option? - We can cut and paste in pictures taken with the main camera, but we could do this before.
Face-fusion. - I am unable to find this option?
Live-makeup - This is found in settings. - I however do not see any change?
Photo booth - selet it in modes. (Really lame)
They write that not all features are available on all devices... We however have the topmodel? - What are your thoughts on this camera update?
What I personally like the most the video capture butten in the main camera interface.
/Benjamin
sblop said:
Hi All,
Videochat. I have not been able to try this yet.
Face-fusion. - I am unable to find this option?
Click to expand...
Click to collapse
i think face tracking and multi chat is in hangouts.. this morning i called my mom via hangouts and there was options for face tracking on the top left (maximus HD 8.0)
Experience a better way to video chat with Face Tracking. Sitting perfectly still is no longer necessary, because all you have to do is stay in frame and Face Tracking will automatically focus in on you.
From real-time screen sharing to video chats with up to 4 people, Face Tracking lets you naturally do your thing without compromising quality.
Compatible with most live video services such as Skype, Line, Hangouts, WeChat, and more.
Click to expand...
Click to collapse
I figured Eye Experience would be a separate update to the Gallery App in the Play Store. It says coming soon on the website, maybe they didn't roll out the graphical/ui changes yet, regardless of the settings being there or not. Crop Me In is exactly cut and paste with the Duo Camera effects stuff.
EDIT: "The HTC EYE Experience features will roll out to the following models in the coming months" IE not out yet.
Note the UI image of the icons.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm aware that many people have recently been having a problem on their S6 edge+ and Note 5 units where YouTube will display all supported resolutions (up to 1440p), but only in 30Hz.
This problem is similar to one that we experienced last year on the Nexus 5, and they're both /server side/ issues.
Whereas last year we had to edit the Android version in build.prop to 4.4.2 or L to receive 1080p YouTube, the problem with the S6e+/Note 5 lies in the model number displayed in build.prop.
Google simply hasn't added these larger devices to their list of "60Hz compatible phones", so when they see that you're using a G928 or N920, they don't give you the 60Hz option.
The fix, however, is /easy/ but requires ROOT ACCES:
0: Create a backup of your build.prop (remember to set permissions to 644 or RW R R if you restore it!)
1: Open it and change the model number from SM-G928$ to SM-G925F (European S6 edge) or from SM-N920$ to SM-G920F (European S6).
2: Save, reboot, and clear YouTube's cache
Now you should be up and running with 1080p at no cost to any other functionality whatsoever!
Everything else on your phone should work exactly the same, because you're just making apps think that you have a smaller but nearly equally-specced device (they're the same except for 1GB more ram on the + and Note, but the build.prop edit won't affect that at all).
Good luck!!
Sent from my SM-G928T
I think the term you are looking for is fps, not Hz.
How do we even know anyway what is the fps of a Youtube video? I only see mention of : 720 1080 1440. Never 30 or 60. So how do we know in which framerate the vid is shown. I'm confused!
Send from my Samsung Galaxy Note 5
Finally google added s6 edge+ to his youtube lib ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IDK if note 5 already get that
Sent from my SM-G928K using Tapatalk
Video recorded and played with MPC or VLC in Windows 10 is showed face down. Some articles talks about the issue of the camera position, but I don't know that the file stored contains the video rotated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you record your videos,using the stock camera app?
Inviato dal mio Nexus 5X utilizzando Tapatalk
(THE REAL) Neo said:
Do you record your videos,using the stock camera app?
Inviato dal mio Nexus 5X utilizzando Tapatalk
Click to expand...
Click to collapse
Yes, with the Google Camera App that comes with the Phone. The record was in UHD quality, I don't test it with 1080p but I think that the result will be the same.
known issue for a while now..
Pure stupidity on google/LGs part. they placed the camera image sensor against the android specs recommendation.
Now the software must be updated to fix it.
This impacts many apps (eg: bank apps which scan check images, bar-code scanners, qr code readers.. etc)........
The IRONY is .. most of the third party apps have now been updated and they fix this issue. However, GOOGLE.... hasn't yet fixed the native camera app. they are busy preaching developers of other apps to fix the problem.. Crazy, but true. Sucks.
I'm having the same problem videos looks fine played ba"k on phone & when copied to Pc & playednon Windows media player & latest vlc, older vlc & video editing software show the true orientation, upside down & copy to a flash drive & plug into tv & also upside-down. I have checked the video meta data & the rotation is 180 so that software can rotate to display correct way up.
I guess most users won't be aware of this fault as they just playback on there phones..
Does anyone know if Google is working on a fix.
This is a massive fault as you cannot change the orientation afterwards so all my 4k Christmas videos can never be transferred to a USB stick & played on 4k tv.
To stop nexus 5x recording upside-down videos you Have to hold the phone left handed then videos are correct way up.
Hope Google fix this as most people are right handed, anyway you should be able to hold the phone anyway you want.
My A5 (2017) is running on magisk rooted stock android 8.
I've been messing around trying to get better audio from this phone, and have found a method to... at very least make it look like I'm using LDAC.. at best actually use it.
I'm unsure if I truly am using LDAC, or if there is any difference to the audio quality at all.
(im the master of the placebo effect )
I use SetEdit w/ Feature Pack to keep a few Global settings set to 1 (true) . After a certain event involving the headphone, or a random amount of time (idk) the "_supports_ldac" settings I've changed go back to 0 (false). SetEdit keeps my changes persistent.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sidenote, this little tweak FEELS like it has an effect on the audio.
& I can do something similar with my A51 (non-rooted, One UI 4.1) & the UHQ upscaling/bit ajustment built into the settings that is usually grey-ed out.. and dedicated for wired devices?
also works with different audio devices.. like my Skull Candy Uproar, and cheap BlueHive earbuds (035-7309-4)
Now thats all fine and dandy.. but......
but I cannot set the "Bluetooth Audio Codec" in dev settings to LDAC, when clicked it returns back to SBC. my only supported codec
same goes for sample rate, bit rate and sort of the LDAC Playback Quality. My A51 behaves the same.
I can change the playback quality from Best Effort, and it sticks.
But if I click the option, the selector is back to Best Effort... AND MY SELECTION of Optimized for Audio Quality still sticks. weird.
--------------------------------------------------------
Here is screenshots of the A51.
If I launch the android shortcut "com.sec.android.app.soundalive.activity.UHQUpscalerActivity" the page below opens, and I can freely change the settings and they stick as long as SetEdit is doing its thing.
I can't figure out how to access this page without launching the activity...
-----------------------------------------
To sum it all up, I have some nooby questions.
Am I actually getting LDAC & UHQ upscaling with unsupported devices?
Is there a way to test the truth of what I'm seeing and "hearing"?
Is this weirdly specific "hack" and my curiosity confusing enough? or am I insane?