Shot some video over the weekend for the first time with the O2X. Was shocked to find that the recorded footage did not auto-rotate when transferred to my PC and played back, Am I missing something?
If not is there a way to rotate the footage and keep the 'quality' as I've converted to AVI and then rotated in Windows movie maker and the quality is pretty crap even on DV-AVI
You are missing that video are not the same as pictures and does not have features to "rotate"
Video are defined in specifik formats - you do not have a viewing option for landscape or portrait like you do for pictures. Video are allways in specific landscape dimensions, like 1280x720 pixels or 640x480 etc. and allways played back in landscape format.
So video should allways only be recorded holding the phone in landscape mode, never in portrait mode.
So I noticed, just like OP. But is there any way to rotate the video without quality loss?
Sent from my Optimus 2X using Tapatalk
no thats not possible
rotating a video means reencoding and cropping to a correct videoresolution
Ah, yes... It figures when you need to crop... Thanks for the info.
Sent from my Optimus 2X using Tapatalk
Whether it's Allcast, Localcast, Castaway, etc. None of these apps can do 1080p without stuttering. Is this a hardware limitation of the chromecast, or my phone?
The Chromecast is capable. As I write this, I am streaming Ender's Game in 1080p from Plex to my Chromecast. I have never had good results with AllCast however, and I'm guessing the case would be similar with other device-local content casting apps. My theory is that most Android devices aren't capable of the throughput necessary to support 1080p streaming locally. When uploading a test video from my Note 2 to my Plex server for testing, the best xfer rate I could get is just under 1MByte/sec, not really enough for 1080p streaming. Once uploaded, playing via Plex worked just fine.
siratfus said:
Whether it's Allcast, Localcast, Castaway, etc. None of these apps can do 1080p without stuttering. Is this a hardware limitation of the chromecast, or my phone?
Click to expand...
Click to collapse
The Chromecast itself is fully capable of 1080p playback. The issues lie in wireless bandwidth and video format (compression and container).
See WiFi Bandwidth and Router considerations and Supported Media for Google Cast
siratfus said:
Whether it's Allcast, Localcast, Castaway, etc. None of these apps can do 1080p without stuttering. Is this a hardware limitation of the chromecast, or my phone?
Click to expand...
Click to collapse
My way to figure out if a video will stream on my network is (this isn't a perfect science mind you, and this is as far as i know)
-Check my wireless connection by my chromecast (72 mbits/s with mine)
-Divide by 8 (that gives you mb/s)
-Check to make sure video source falls within that value
This would give me (in a perfect world) the ability to stream a 9mb/s video source. Don't forget to divide by 2 if the source of your content is wireless as well. In my case I have my netbook direct connected to the router so it's a non issue.
Someone please correct me if i'm wrong
sherdog16 said:
My way to figure out if a video will stream on my network is (this isn't a perfect science mind you, and this is as far as i know)
-Check my wireless connection by my chromecast (72 mbits/s with mine)
-Divide by 8 (that gives you mb/s)
-Check to make sure video source falls within that value
This would give me (in a perfect world) the ability to stream a 9mb/s video source. Don't forget to divide by 2 if the source of your content is wireless as well. In my case I have my netbook direct connected to the router so it's a non issue.
Click to expand...
Click to collapse
Sounds about right.
The only other limiting factors would be
your router's ability to sustain the wireless rate (lower-end routers sometimes only peak at advertised rates)
your device's ability to sustain the required rate
your device storage's ability to sustain the required read rate
Any video whose bitrate is higher than 5000 Kbits/s (that is: most 1080p videos) is likely to stutter due to not enough WiFi bandwidth available or too irregular. WiFi sucks compared to Ethernet.
For some reason I've noticed stuttering only on videos taken with my phone. I cautiously played 720p videos for a time because I thought the issue was that the vid was full hd. Turns out it wasn't as Thor 2 in 1080p played flawlessly for me. It helps to have the fastest speed your provider offers...in my case I have 30mb down which is reduced to around 20mb through my wall. I hope Google Fiber makes it's way to my town eventually.
I use serviio and avia. Don't have any stuttering on 1080p. I did have issues with AllCast and 1080.. but I tend to use AllCast with other software and do not have any issues as long as the video is below 1080.
For what it's worth "1080" isn't always the same "1080". It really comes down to the bitrate of a video. Native 1080p (ripped from a bluray) is something like 30MB/s. My s4 records at something like 15-20 MB/s. If you download a yify torrent that is "1080p" it'll tend to be around 4MB/s. As you can see there is a big difference (these are approximated numbers off the top of my head but you get the point). If you're having a problem with a video i would suggest a run through Handbrake and it'll play fine. My suggested settings are as follows:
High profile
Web optimized checked
Set Denoise under filter settings (more takes longer, I default to weak)
Choose your poison for encode speed and RF quality. (Over night I do very slow and usually a 19 if i'm looking for HD quality and a decent file size)
Under the audio tab make sure you're giving the result an AAC codec audio to work with. (I tend to bump the rate up to 256(
My guess is that this is the reason Google doesn't want to officially support local content. There are a lot of hurdles to jump and all content is not created equal. Someone streams an "HD" video on netflix and then thinks that they should be able to stream ANY "HD" content. Not the case as we're finding out
Speaking of yify (happy retirement), I get no stuttering from any of their mp4's but I do if I use bubble upnp. I don't think it's just limited to video bitrate, though that clearly does have an impact. I think the software used should also be considered as a possible chocking point. As I mentioned earlier, serviio has consistently given me the best results.
Great point. "1080" is just part of the story, "1080p" is a little more, but still not the full story. It's like calling a seamstress and asking them to make you a shirt, but only telling them "I'm male" or "I'm a tall male" - not unhelpful, but still not enough data.
A video file consists of:
Resolution
This is the stored or "captured" resolution, not necessarily the displayed size
Pixel aspect ratio (PAR)
The "shape" each data pixel should be displayed at. The combination of resolution and pixel aspect ratio determines the display aspect ratio (DAR), which is sometimes defined in place of PAR. Unfortunately pixel aspect ratio is not defined the same way in all formats. For MPEG and most containerless formats, it's defined by the CODEC itself. The AVI container does not have a place to store it, so AVIs will play assuming square pixels except Windows Media Player makes some assumptions about certain video frame sizes and tries to compensate (sometimes incorrectly).
Luckily, the HD and UHD resolutions use square pixels so there's less to worry about.
Field Order
Whether samples are full frames (progressive), or fields (interlaced) in upper/top field first (UFF/TFF) or lower/bottom field first (LFF/BFF) order. Sometimes you'll see field order referenced as "odd" or "even" field first, but this is ambiguous as some things label the upper field as field 0 (which would be even) while others label the upper field as field 1 (which would be odd)
Sampling rate
How many samples per second (ie, 50 Hz, 60 Hz)
Higher sampling rate = smoother motion. This is why 24 Hz content that isn't shot specifically for film rate (avoiding fast motion and fast pans/zooms) looks "jumpy" compared to "regular" video.
Bitrate
What the data rate is - usually stated in bits per second (bps), kilobits per second (Kbps) or megabits per second (Mbps)
This is what determines the size of the video portion, regardless of resolution, interlacing and sampling rate.
Bitrate and video quality go hand-in-hand. The more bits you have, the better each video frame will look.
Compression type (CODEC)
What format the video is compressed in, for example, MPEG-1, MPEG-2, MPEG-4, WMV, VP6, DivX, Lagarith, etc.
CODEC and bitrate go hand-in-hand as well. More-complex compression algorithms can provide better quality with a lower number of bits.
Container format
How the video is "wrapped" or packaged. Some formats like MPEG and Windows Media support multiplexing and can be self-contained, so they can exist outside of a container. Other formats usually exist in a QuickTime container (.mov file) or DirectShow/Video for Windows container (.avi file)
Elements from containers can be added and removed without impact to audio/video quality.
Audio compression type
Like video compression, what format the audio is compressed in, if any. Common formats include MPEG-1 Layer 3 (aka "MP3), AAC, Dolby Digital, etc. Audio can also be uncompressed LPCM, often referred to as just PCM.
Audio sampling rate
The number of audio samples per channel, per second - usually in kilohertz (KHz)
Audio sample depth aka bit depth
How large each audio sample is, usually stated in bits (8-bit, 16-bit, etc)
Audio bitrate
What the data rate is - usually stated in bits per second (bps), kilobits per second (Kbps) or megabits per second (Mbps)
This is what determines the size of the audio portion, regardless of channels, sampling rate and sample depth.
Bitrate and audio quality go hand-in-hand. The more bits you have, the closer the audio will sound to the source.
The overall size of the video portion is video bitrate x length of video in seconds
The overall size of the audio portion is audio bitrate x length of video in seconds
Add any additional metadata overhead and additional tracks (subtitles, etc) from the container (if applicable), and you have the total file size.
So "1080p" only says it's a 1920x1080 resolution, and progressive samples. It does not say what the bitrate is or display/sampling rate is.
This will be slightly off topic but worth noting...
sherdog16 said:
For what it's worth "1080" isn't always the same "1080". It really comes down to the bitrate of a video. Native 1080p (ripped from a bluray) is something like 30MB/s.
Click to expand...
Click to collapse
Your post is pretty spot on just wanted to note Full Native 1080P is actually a little more than 1Gb Bitrate over HD-SDI.
Almost no one but the production crew ever gets to see the full resolution, not even the Networks that will broadcast it unless you mail the tapes to them.
Everything else is compressed to hell including BluRay and 40Mb is about as high as you will ever see outside of the Master Tapes. And since most networks have decided NOT to support the HDCAM format in favor of XDCAM or digital storage (which are not much higher than BluRay quality and compressed) It's rare to ever see a full resolution 1080 signal in real life.
All these phones and such who claim to record in 1080P really only save in 1080P. Their CMOS doesn't have the resolution to properly capture 1080P Native at most it is 720 or 480 upconverted to a 1080 resolution file.
As for CCast and Wifi I would never go over 10MB on a source without transcoding. 4-8Mb is the sweet spot for WiFi transmission (IMO).
Unless your used to seeing full resolution 1080 signal your really not going to miss or gain much by going higher than that for your library. You wouldn't see a significant difference till you got up to 40MB which is a little higher than what your original source was. Going Higher than source does not bring back the resolution of the original so there is no point to it.
Most of my Library is encoded at 4-6Mbs in 1080P and I hardly ever have a problem streaming them to any device.
I think that you have a typo Asphyx.
Plenty of phones have CMOS sensors exceeding 2 MP (that's about all a single 1080p frame is), so it's not resolution holding that back, it's a chain of poor response times.
EarlyMon said:
I think that you have a typo Asphyx.
Plenty of phones have CMOS sensors exceeding 2 MP (that's about all a single 1080p frame is), so it's not resolution holding that back, it's a chain of poor response times.
Click to expand...
Click to collapse
Well yes and no...The CMOS may have 2MP (and some have higher than that) but two things are in play there....
1 - Some of those pixels are split between G, R and B so a 6 MP CMOS could be using 4MP for Green and 2MP each for Red and Blue. so a 2MP Camera is probably not really getting full HD. 6MP would be the minimum for full 1080P.The old 4:2;2 standard
But more importantly is:
2 - Most video capture is not using the entire CMOS to capture image due to the 16:9 ratio of HD capture.And thats not so much about the CMOS as it is the lensing system.
In broadcast we use Three 3/4" CCDs or CMOS chips one for each color with a prism to split and send the color to each chip. Each chip is full resolution so we get 4:4:4 and every color is captured at full resolution.
Because of the lensing and focal length, the image reflected on these chips is very large compared to what is reflected on a Phone CMOS so the image is a lot clearer. less fuzz and better pixel resolution. In broadcast we shoot higher than HD as we have an overscan sized signal and we cut out the HD bit we need when recorded.
So yes Phones have the Pixels needed but in most cases they are not in the right place for full HD resolution. And due to the short focal length they rarely ever use the entire chip.
Thanks, I'm very familiar with the RGBG Bayer filter, for those that aren't - http://en.wikipedia.org/wiki/Bayer_filter
As for the 2 MP thing - I didn't mean to imply that a 2 MP sensor would take 1080p vids and no one making a phone claiming 1080p uses such a low MP-count sensor.
Smallest I know of is the HTC One at 4 MP and that's 16:9 all of the time, most everything else is 5, 8, 12 or more MP.
So, on that basis, allowing for the Bayer filter, lower quality without oversampling, and 16:9 masking, I'll maintain that the problem on the top end phones claiming 1080p video isn't resolution - it's response time.
I'm familiar with 3-chip cameras, I used to own a Canon XL-1 (SD obviously), and I'm way too familiar with CMOS and CCDs at the silicon level.
The CMOS mobile sensors are noisy, not terribly sensitive and s.l.o.w. They're price effective but they're just not CCDs.
You can dial in a higher bit rate for many Androids, especially with root options, that's probably the darling camera app mod - but you won't get faster than the sensor response time + readoff time + binning time + processor time of attention (usually an image processor in the main SoC, but sometimes a CPU core) + the frame rate processing algorithm time + compression time + plus whatever else I forgot.
And that's why phone videos stutter. When the system can't keep up, it simply lowers the fps rate.
The new crop is promising higher frame rates. We'll see.
As for frame quality - that's affected by all of the things you mentioned (and let's toss in inaccurate color rendering and plastic lenses for those without an iPhone while we're at it).
1080p can be done, sufficient phone sensors exist in terms of MP, and you can wind up the Mbps - but you can't cure light sensitivity and noise and what most people shoot slows down an already slow subsystem.
Edit - posting this made me think - so I went and checked my video closet - I actually still have a 3CCD Canon GL1 that I completely forgot about. rotflmao - I'll have to dust it off and see what I get.
I agree with you that the speed is a problem as well...
But when push comes to shove at some point phones (and CMOS) will catch up and we won't have to wonder if a particular model is true HD or not.
A recently as a year or two ago HD Record was more of a Marketing pitch than a reality.
Phones (and their camera's) have improved a lot since then and we even have a few Cameras with phone being made where the Camera and lensing is prioritized to get better picture.
It's something I expect us to tell our kids about the good old days when HD cameras in phones weren't really HD! LOL
They won't believe us!
EarlyMon said:
I think that you have a typo Asphyx.
Plenty of phones have CMOS sensors exceeding 2 MP (that's about all a single 1080p frame is), so it's not resolution holding that back, it's a chain of poor response times.
Click to expand...
Click to collapse
EarlyMon, you do have too much knowledge for the human being.
I feel embarrassed.
Hello people! I'm trying to record video with my new OP3T, but when I watch the recording, the video frame size (or field of view I suppose) is smaller than what it looks like when I'm shooting. I mean the video resolution is still 1920x1080, but things at the edges of the screen are now out of view. I'm using 1920x1080 @30 FPS, stock camera app, Android 7.0. Same thing happens with other resolutions and FPS settings, and with OpenCamera app for example. But it does not happen when taking pictures, and even when I take a static shot WHILE shooting video, that picture comes out fine.
Is this a known issue? How could I solve this? Is there any modification that could help?
PhantomGlass said:
Hello people! I'm trying to record video with my new OP3T, but when I watch the recording, the video frame size (or field of view I suppose) is smaller than what it looks like when I'm shooting. I mean the video resolution is still 1920x1080, but things at the edges of the screen are now out of view. I'm using 1920x1080 @30 FPS, stock camera app, Android 7.0. Same thing happens with other resolutions and FPS settings, and with OpenCamera app for example. But it does not happen when taking pictures, and even when I take a static shot WHILE shooting video, that picture comes out fine.
Is this a known issue? How could I solve this? Is there any modification that could help?
Click to expand...
Click to collapse
Seems to be a known issue. Watch this video (pay attention at 3:30): https://www.youtube.com/watch?v=XFC9OB85Tpk&t
I don't know if this can be solved as i received my 3T yesterday and haven't had a chance to use the camera yet.
panart said:
Seems to be a known issue. Watch this video (pay attention at 3:30): (snip)
I don't know if this can be solved as i received my 3T yesterday and haven't had a chance to use the camera yet.
Click to expand...
Click to collapse
It seems so, yeah. Do you know if this sort of cropping happens during shooting or is it a separate process that's done afterwards? I figured this might be solvable somehow, since you do see the whole picture while you're recording. So it's not a physical limitation of the camera lens or anything.
PhantomGlass said:
It seems so, yeah. Do you know if this sort of cropping happens during shooting or is it a separate process that's done afterwards? I figured this might be solvable somehow, since you do see the whole picture while you're recording. So it's not a physical limitation of the camera lens or anything.
Click to expand...
Click to collapse
Sorry, but i don't know why this happens.
panart said:
Sorry, but i don't know why this happens.
Click to expand...
Click to collapse
Noticed that OpenCamera has a function to enable Camera2 API, which fixed the cropping! Also I found that on stock camera app, recording on 4K UHD (3840x2160) doesn't crop the video frame. But it limits to 10 minutes per shot (also workable on OpenCamera due to its restart recording function.)
It's the electronic image stabilisation. It needs to zoom in a little bit to stabilize the video. That's why the 4k isn't cropped, because in 4k, there is only OIS, and not EIS.
G4B33 said:
It's the electronic image stabilisation. It needs to zoom in a little bit to stabilize the video. That's why the 4k isn't cropped, because in 4k, there is only OIS, and not EIS.
Click to expand...
Click to collapse
Exactly what I thought was the cause of it, thanks for clearing this up ??
Is there any way to disable stabilisation? Different camera app, some mod or something? Even OpenCamera doesn't specifically have a setting for that, but I guess Camera2 API doesn't support EIS or something, which feels like a crutch "solution" at best.
PhantomGlass said:
Is there any way to disable stabilisation? Different camera app, some mod or something? Even OpenCamera doesn't specifically have a setting for that, but I guess Camera2 API doesn't support EIS or something, which feels like a crutch "solution" at best.
Click to expand...
Click to collapse
Scan build.prop see if there is some line related to ois or eis.
The LG V40 ThinQ has a Live Photo mode similar to later iPhones. That photo is about 9 frames of video with sound and 1 picture. There are a few things I can't figure out though.
A. Is the photo 9 frames at full resolution, with audio tacked on.
or is it 1 frame + a small connected movie
B. Can I edit this off-phone, can I peel out all the frames and pick the best one, or edit/use the video portion elsewhere.
There are a few things I have done so far, that are not satisfying my needs.
save to video, or screen cap in the phone, both provide terrible results.
using the "in-phone" saved video outside the phone, also terrible.
Any help would be appreciated
Did you manage to solve the live photo problem? I am looking for a solution for finding and making copies of photos that were made in live photo (visible in the gallery when browsing but not saved an mp4). I sent this question to LG technical support but so far I have no answer.
Hi,
I wanted to know if this is normal on Xiaomi mi 11 Ultra, but
when I shoot in 4k 60 fps in HDR10+ (10 bit colors), I'm getting weird artifacts in the video. Look at: StockCamera10Bit.jpg
It's such an unusable mess. I'm shooting at PRO. It doesn't matter what ISO, shutter speed and white balance is selected. It's always this. Subject has to be moving.
If I select 8bit, it's ok, just normal motion blur.
Is it normal on this phone? Can anybody confirm it?
I have the same problem in McPro24FPS in anything over 30 FPS even in 8 bits, so that's troubling me a bit.
I have the phone for a few weeks now and it's just amazing how the video footage degrades, when you do not want to film in AUTO
And even, if you satisfy with AUTO and only lock exposure and focus, it's also crap, when you move the camera or something is moving in front of it
I can see, that the only thing that manufacturers are interested in is AUTO mode which gives you nice HDR, but is always changing exposure, so it's interesting only for YouTube reviewers and DXOMark I guess. But for semi-serious video shooter I'm still amazed how they market 8k video and I cannot get even decent 4k 60 fps for slow mo (not even usable Full HD in 60 FPS).
I would satisfy with 8 bit, but it's unusable in stock app, because it's changing exposure even if it's locked and other app give me these artifacts anyway...
wait... did they convert 8-bit to 10-bit using bad dithering?
GuyWithRootedPhone said:
wait... did they convert 8-bit to 10-bit using bad dithering?
Click to expand...
Click to collapse
Alexander from McPro24FPS said, that it is a bug in HDR merging. It should have phones with HDR on by default.
It is some setting, that can be be turned off programmatically, but it's the matter of finding it.