The reason I want to do this is that I have an application that needsto show a video of a non supported codec (HLS or TS), but I wouldn'twant to build a full blown video player - just integrate with theexisting, built-in, player.
The reason I want to do this is that I have an application that needs to show a video of a non supported codec (HLS or TS), but I wouldn't want to build a full blown video player - just integrate with the existing, built-in, player.
You can try out adding your codec through openMAX IL layer then call up the android media player to play it(I believe vlc has done in this way but uses its own player). The awesome player, the android default player, just fetch a list of codecs available through openMAX API and if there is a codec, it plays. So it is worth to try adding your codec during initialization of your app, and call up media player.
Hope someone can advise.
I have Eufy homebase 2 and 2 Eufy Cam 2 Pro.
System runs ok but videos download onto Android phone although claiming to be MP4 wont play video, only sound. When transferred to a laptop will also not play. Get a message about an issue with the codec.
If you look at the Video quality setting for the camera it says that 1080p will work with legacy hardware and software, but 2K recording may require a newer codec. What version of android are you using?
Thanks for your reply. Cameras are set at 2k and was just accessing using android phones standard video player. Have installed the suggested video player and they now play but at a reduced 1080 which I presume the player reverts to if it cannot show at 2k due to a codec issue. I didnt set the cameras to 1080 so either the player does it or the cams are not recording at 2k.
Phone is Android 10. Cameras set to 2k, have now installed suggested video player and now plays but at 1080 not 2k. I presume the player runs it in lower definition because it cannot handle 2k but unsure. System shouldnt be recording at 1080 as cameras set to 2k.
While I know Android phones play mp4 the best, I wanted to know what other specification in this container is the best for playback, (the bitrate, resolution, fps etc). Or perhaps some other codec/format that Android can (or is designed to) play smoothly and with an acceptable file size/quality ratio?
I searched the Android developer page and tried the H.264 setting on my converter etc, but the file fails to play natively on my handset and when I tried to open it using RockPlayer. It plays slowly and the video-audio gets out of sync progressively. I tried many external players. However, 3GP videos from my Nokia phones play smoothly (even natively). So I want to know what is ideal for my low end phone (video should be normal quality and size)?
Also if anyone has tips, what types of encoding is recommended, if I'd be using the software decoder mode in apps like RockPlayer, so I can achieve more file size compression yet achieve smooth playback?
I have a phone with the same specs... I found that If I encode using wmv2 and wmav2 it actually plays smoother, go figure. libx264 is a lot more complex of a codec and takes about 30 sec. to start playing a movie, but quality will be better. For a player I use MXplayer with the arm6 codec pack. Within MXplayer settings I set it to use software video decoding and hardware audio encoding as default. Here is a sample of my encoding process:
In order to take advantage of that feature and avoid software decoding, you will want to store your video in MP4 format. You can reduce the resolution of the video to match the display of your phone (320x240).
A great tool for transcoding your video media is Handbrake. You can use Handbrake to transcode to MP4 format at 320x240 resolution. Once you find a combination of settings that work well for you, consider publishing it as a preset for other u8510 users to try.
Most FLV video files play on Software Rendering mode (ARMv6 MXVideoPlayer) at appreciable speed (sometimes lagging at certain points, but overclock to more than 600 Mhz, and it runs fairly good at all points)
Standard MP4s or MPEG-4 Part-2 compressed video files seem to be the best file format to play on low end android phones which is easy on the CPU (plays perfect in HW mode) and has good balance between clarity and file size.
I had this problem intermittently over the past few months: I work-around I had was to upload the .mp4 (from Premiere Pro), into Photoshop, save again as .mp4 via Export >> Render Video, and although the file size was 3-4x that worked fine on my phone. This however now produces a file which (on the phone) is not a 4x5 crop and so is useless.
From all the research I have done it seems likely one of the codecs used in the .mp4 is not supported by my phone. I have tried every setting in the Export diaglog box and without success. Different file types often won't allow the 4x5 crop so are a no-go.
SOLVED - Ok, now it seems obvious right? The file dimensions were too large for the android .mp4 codec... some of my (timelapse) file dimesions were >4000 x >3000 or so (images from camera turned straight into frames in video). Codec couldn't handle it.
I have an update: I found out that regular movie films work fine in .mp4 when transferred to mobile device. But... the timelapse files (which are 25fps / 59.97fps / 60fps .mp4 files which seem identical as far as I can tell) still do not work!
Since the processor used by your device is only slightly above the minimum system requirements for running the Zoom client, it is not surprising that the performance is less than ideal. While the requirements listed on that page are for the Zoom client, they should be pretty closely aligned with what is required for the SDK.
For comparison, we have also run a custom (non-Zoom) video streaming app on this same platform.
With that app, we have found that using the HW-accelerated H.264 codec gives much better performance.
Using the HW codec, we can stream 720p video at 30 fps with no problem.
Thanks for checking that! It seems that it will be difficult to improve the performance on that device with the current implementation in the SDK. Since there was a slight improvement with a simple UI, it is possible that the Video SDK could perform even better. Do you think that you could consider using the Video SDK for your use case, or do you need access to the Zoom Meeting ecosystem?
Bluetooth audio quality is defined by the codec algorithm and bitrate transmission versus the Bluetooth version. You no longer need to sacrifice audio quality for wireless convenience with a little knowledge.
MacBook and macOS users: great news! Your Mac supports Qualcomm aptX and AAC and you can easily discover what codec it is streaming over Bluetooth audio by holding down the option key and checking your paired device settings on the menu bar as you can see below:
The Qualcomm aptX audio coding algorithm originated in the late 1980s at Queen's University Belfast. This innovative work was focused on bit rate reduction and achieved significant bit rate efficiencies while preserving audio quality.
Qualcomm aptX has been the best kept secret of the professional audio industry, used by major public broadcasters and film studios around the world. Now available on leading consumer devices, aptX enables music lovers to enjoy a rich listening experience.*
Qualcomm aptX HD was designed to answer the growing demand for high resolution audio. This enhanced codec supports 24-bit music quality over Bluetooth. This means listeners can hear even the smallest details in their music.
Qualcomm aptX HD is designed to deliver 24-bit wireless HD audio wirelessly over Bluetooth and improve signal-to-noise ratio, resulting in lower background noise. With lower Total Harmonic Distortion (THD) and no audio artefacts, you can enjoy your music with hardly any interference.*
The low-complexity sub-band codec (SBC) divides the signal into multiple frequency bands and encodes each one independently. It is mandatory among all A2DP-enabled devices, making it virtually universal.**
Both the iPhone and Google Android phones seem to have limited codec support when it comes to video. Both support MP4, so I did a bit of searching on the internet to find out how to convert to a suitable format using MPlayer's MEncoder.
I downloaded VLC player on my android earlier and it plays in that but not in Chrome. The issue is going to be that people will be browsing in Chrome and if its embedded in the forum it wont play. If its just a link like that one above it will also open in Chrome unless there is a way to force Android to open it in VLC player but that doesnt fix the issue. Whatever the issue is.
The codec AND the settings are important, as not all output settings are compatible across all devices. Chrome has a narrow set of mpeg 4 video settings it can play because of integration with Chrome OS. This has been an issue with embedded video files for a number of years.
People have found ways around this by using HTML5 coding to change how Chrome interprets the files but it doesnt always work. Direct linking to videos like on 9gag is a bad idea, because chrome interprets those direct links as an html page with CSS settings for the video that dont really exist.
Hmm. Interesting. If I email that clip to myself and click on the link and open it in VLC player it plays fine but the browser you think maybe just refusing to play it as its too high res? Will see if I can find that setting
This is a known headache with browsers and how they use codecs on Android. It also changes from one device to another depending on how the device ROM was made, and whether any additional codecs were installed.
This article updated on MiniTool official web page mainly introduces audio codecs for Android phones, Bluetooth audio codec Android, what audio format does android use, how to change the default Bluetooth audio codec, as well as what to do if the audio codec is not supported on android.
c80f0f1006