Database Develop

Video Conversion [HELP please]

Hi, I've search many place and unable to find any good guides for video conversion for the Acer liquid(Donut). And the User Manual don't even give full specs.
I've done many conversion of my own, however the video always lag...
~~ Please tell what is the max bitrate, best codec(mp4, h.263, etc), resolution, fps to make a video play hi quality NO frame skip/lag on the Acer Liquid(Donut)~~
Note: I understand the max quality is only as same as the video/clip you've inputed, and that the Acer only support up to 20 frame per section(at least that's what written in the user manual), and I have a good video converter btw, been using it for years...

Shalala
Alrite after playing with the video for a few more day.
I STILL don't get exactly what I wanted...and I notice alots of people viewing this thread, so I'll share what I have at the moment.
~~~Good Enough~~~
Right this moment, my best conversion is...
Video Quality Superb
File Format *.MP4
Video Codec mpeg4
Resolution original as input/ since no TV-out, it is suggest 640x480 up to 720x480.
Framrate Always try to maintain the same or near framerate as the original video clips. To see how many fram per second the original clip is...right click on the video clip and choose properties > Details > Frame Rate.
Aspect Ratio either Auto or 16:9.
Audio Quality 128 kbps
Audio Codec mpeg4aac
Channels 2 Channels Stereo
Sample Rate Varies/44100 Hz
NOTE: I can't be sure if its just my phone in particular, I've only gotten it for a week. I don't wanna think that it is my phone that don't play video perfectly. However, the setting above allow me to play full screen with no frame skips, hi quality, almost everything is perfect with 1 exception.
The frame don't skip but it seem to lagg a "LITTLE BIT"... an example, you won't see black strips or shifting from 1 scene to another, but rather.....crap i can't explain it lolz

[Q] Wideband AMR or AAC in Video recording

Taken from:
http://developer.android.com/sdk/android-2.3-highlights.html
Support for new media formats
The platform now offers built-in support for the VP8 open video compression format and the WebM open container format. The platform also adds support for AAC encoding and AMR wideband encoding (in software), so that applications can capture higher quality audio than narrowband.
Click to expand...
Click to collapse
Implementing wideband codecs in video capture would be very nice as the platform now allows it, because at the moment, captured audio in videos is simply very, very bad (8kHz narrowband AMR).
Any dev willing to explain how hard would it be to implement this? Thanks.

Galaid said:
Taken from:
http://developer.android.com/sdk/android-2.3-highlights.html
Implementing wideband codecs in video capture would be very nice as the platform now allows it, because at the moment, captured audio in videos is simply very, very bad (8kHz narrowband AMR).
Any dev willing to explain how hard would it be to implement this? Thanks.
Click to expand...
Click to collapse
Can be done, but first we'll need to fix the video encoder framework problem currently found in gingerbread.

With the OTA ull have both AAC and amrwb encoding, no need to worry about that, just wait for the ota. i have seen the AOSP source for passion, there is implementation of all the new encoders

charnsingh_online said:
..just wait for the ota..
Click to expand...
Click to collapse
Isn't the libs part of AOSP?

No passion has some proprietary libs including camera n omx libs. We also need a new radio to go along with the encoders

charnsingh_online said:
No passion has some proprietary libs including camera n omx libs. We also need a new radio to go along with the encoders
Click to expand...
Click to collapse
One and half month after SDK and waiting...

Well, the OTA is here and the camera still encodes audio in AMR.
Damn.
edit: well, I was wrong! I hadn't looked at the actual file with a computer: it now has AAC audio, 16k sampling rate, 96kbps mono. It also uses the back mic (i don't know if that was the case before)
A higher sample rate would be very nice, but ah well, at least it's something

spamlucal said:
Well, the OTA is here and the camera still encodes audio in AMR.
Damn.
edit: well, I was wrong! I hadn't looked at the actual file with a computer: it now has AAC audio, 16k sampling rate, 96kbps mono. It also uses the back mic (i don't know if that was the case before)
A higher sample rate would be very nice, but ah well, at least it's something
Click to expand...
Click to collapse
Thanks for revivng the thread, I had problems finding it. So as aac is in the game now, is the sound better or just cosmetically better?

spamlucal said:
Well, the OTA is here and the camera still encodes audio in AMR.
Damn.
edit: well, I was wrong! I hadn't looked at the actual file with a computer: it now has AAC audio, 16k sampling rate, 96kbps mono. It also uses the back mic (i don't know if that was the case before)
A higher sample rate would be very nice, but ah well, at least it's something
Click to expand...
Click to collapse
How do you know its using the back Mic?

[Possible MOD] Editing build.prop to enable 1080p video recording

There a way to change this part of the build.prop to enable 1080p video recording? I tried just changing the resolution to 1920X1080 and lowered the fps to 25 but it didnt do anything.
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.media.enc.hprof.vid.bps=4000000
ro.media.enc.hprof.vid.width=1280
ro.media.enc.hprof.vid.height=720
ro.media.enc.hprof.codec.vid=h264
ro.media.enc.hprof.vid.fps=30

this would be great!!
Thatsball the phone is missing.

tassadar898 said:
There a way to change this part of the build.prop to enable 1080p video recording? I tried just changing the resolution to 1920X1080 and lowered the fps to 25 but it didnt do anything.
ro.media.dec.vid.wmv.enabled=1
ro.media.dec.aud.wma.enabled=1
ro.media.enc.hprof.file.format=3gp
ro.media.enc.hprof.aud.hz=44100
ro.media.enc.hprof.aud.ch=2
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.hprof.aud.bps=128000
ro.media.enc.hprof.vid.bps=4000000
ro.media.enc.hprof.vid.width=1920
ro.media.enc.hprof.vid.height=1080
ro.media.enc.hprof.codec.vid=h264
ro.media.enc.hprof.vid.fps=30
Click to expand...
Click to collapse
Try that.
10 char

yea tried that didnt do anything. still 1280 X720

I just saw this myself. You may need to up the bit rate if you up the resolution though. Definitely worth playing around with though.

I've also tried this, I think the issue is that the video app doesn't have an option to attempt 1080 video recording. Perhaps a 3rd party app will allow it.
-James

LGcamera maybe?

Have to agree.

jmacdonald801 said:
I've also tried this, I think the issue is that the video app doesn't have an option to attempt 1080 video recording. Perhaps a 3rd party app will allow it.
-James
Click to expand...
Click to collapse
This is correct. It must be enabled in the system, but also in the application.
Sent from my MB860 using XDA App

could it be recording in 1080 but only showint 720 in the app?

aonavy said:
could it be recording in 1080 but only showint 720 in the app?
Click to expand...
Click to collapse
You could try moving the file to a PC and opening to see what the res is there, that'll let you know if it's recording in 1080 or not. But, more than likely, the app would have to allow it as well.

HD 1080 p capable
Capture – 720p MPEG4 and H.264 at 30 fps
Playback – 1080p MPEG4, H.264, WMV, Xvid at 30 fps
(Playback through HDMI is 720p at launch and will be upgraded to 1080p via SW upgrade post-launch)
Streaming – VGA in MPEG4, H.264, H.263 at 30 fps
from http://mediacenter.motorola.com/Fact-Sheets/Motorola-ATRIX-4G-Fact-Sheet-353b.aspx

why not beat motorola to this update

This phone should be able to do 1080p recording no problem. Several reviews before its release stated that if 1080p isn't supported then it would be possible to "enable it easily" via software. The bitrate will definitely need to increase. I'm curious to see if the 720p recordings would also benefit from an increase in kb/s. I am waiting for my Atrix upgrade.. I really want to try out the camera possibilities. I also agree that the kink here is the camera app/software needs to match the settings of the phone. The Atrix will be my first droid and I can't tell you how exited I am at the possibility of 1080p on my phone!
I will gladly test any scripts/apps that anyone posts. Just found this site and I LOVE IT! Thank you to all the devs (amateur and pro) who donate their time here. I plan on donating to a few key people once I get my phone!
*Also, is it possibly to enable more than one recording setting/profile in the "build.prop" file? If that question sounds dumb I'm sorry.

Well, before build.prop mod LGCamera fails to record at 1080p, after mod it records fine with some settings adjustment for the encoder. I, however, am at work for another hour so I cannot check the actual resolution of the recorded files.

Awesome! I'm hoping it works!

do we know for sure this phone has the hardware to handle 1080 recording?

lasersocks said:
do we know for sure this phone has the hardware to handle 1080 recording?
Click to expand...
Click to collapse
They already said it was coming in an update so yeah it is
sent from my Tegra Beast MB860

Upon viewing the recorded "1080p" videos from LGCamera at home... yes, they are in fact recorded at 1080p. It doesn't have the best framerate ever, most likely due to LGCamera, but it is 1080p.
I will check settings and see which looks the nicest...
edit: http://www.youtube.com/watch?v=sfmIPrXNV2w 1080p video from my atrix.

Diviance said:
Upon viewing the recorded "1080p" videos from LGCamera at home... yes, they are in fact recorded at 1080p. It doesn't have the best framerate ever, most likely due to LGCamera, but it is 1080p.
I will check settings and see which looks the nicest...
edit: http://www.youtube.com/watch?v=sfmIPrXNV2w 1080p video from my atrix.
Click to expand...
Click to collapse
I tried LGcamera also and 1080P seems to be working. Sweet.
Sent from my Bell Motorola Olympus.

Question about 1080p Casting...

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.

OP3T not supporting 24fps video recording framerate?

Since our stock camera app does not have framerate settings, I tried to download Open Camera. When I set 24fps framerate, and hit record, it says, device does not support this framerate.
Anyone knows what other video recording apps that can support 24fps or is it a problem for our OP3T? I was actually planning to make a short film using this device.

Anyone?

Filmic Pro works fine so don't worry that the phone doesn't support 24fps.