Can't find this codec listed in the device spec on Samsung website.
As far as I know, snapdragon 8 gen 2 can decode AV1. But is this decoder enabled?
Maybe it's not, because Qualcomm did not join the AV1 consortium and some patent related topics. But I am not sure about the current situation.
Can anybody test AV1 playback please?
LayerEight said:
Can't find this codec listed in the device spec on Samsung website.
As far as I know, snapdragon 8 gen 2 can decode AV1. But is this decoder enabled?
Maybe it's not, because Qualcomm did not join the AV1 consortium and some patent related topics. But I am not sure about the current situation.
Can anybody test AV1 playback please?
Click to expand...
Click to collapse
DevCheck show's it under Hardware/Audio with a bunch of other codecs.
Related
just wondering since the xoom seems to support a bit more h264 codec wise. I would like to be abe to remux mkv files for play on my atrix, but it doesnt seem to work like it does on the xoom. I noticed there are files in axf format that appear to be for decoding of h264 and mp4, if I used the ones in the xoom or transformer would I gain functionality seeing as how they have the same cpu? I would try it myself but I dont have a xoom or transformer and cant seem to find the files im after.
I think that codecs can be ported as long hey have the same proc chip.
Another thing to consider is the differences between honeycomb, froyo and/or gingerbread
Sent from my GT-I9100 using XDA Premium App
SkzBR said:
I think that codecs can be ported as long hey have the same proc chip.
Click to expand...
Click to collapse
I would love to try, could help me win an argument and be useful at the same time! Someone was trying to tell me the atrix cant play mkv because it isnt powerful enough after he misunderstood the "hardware" limitation of the tegra 2, tried to explain to him that it doesnt have the hardware codec for high profile h264...
kevnb said:
I would love to try, could help me win an argument and be useful at the same time! Someone was trying to tell me the atrix cant play mkv because it isnt powerful enough after he misunderstood the "hardware" limitation of the tegra 2, tried to explain to him that it doesnt have the hardware codec for high profile h264...
Click to expand...
Click to collapse
There is no way to argument with a people that didnt understand the diference beetween HARDWARE limitation and DRIVERS limitation.
Our hardware is compatible with h264 and other things that aren't enabled or coded right now, but with unlocked bootloader we'll make our cellphone 2x more powerful.
kevnb said:
just wondering since the xoom seems to support a bit more h264 codec wise. I would like to be abe to remux mkv files for play on my atrix, but it doesnt seem to work like it does on the xoom. I noticed there are files in axf format that appear to be for decoding of h264 and mp4, if I used the ones in the xoom or transformer would I gain functionality seeing as how they have the same cpu? I would try it myself but I dont have a xoom or transformer and cant seem to find the files im after.
Click to expand...
Click to collapse
You can ask for the files in Xoom forum. I'm sure somebody will help you.
Enviado desde mi MB860 usando Tapatalk
I have not sold my old Galaxy Tab 7 yet and I already have my shiny, new and rooted Tablet S.
I keep my movies on my networked media tank on my LAN and I stream movies to my tablets over the network within the house.
I managed to load the cifs.ko module and mount the network media player on both units. I use BS Player Lite on both units (although I have also tried mobo player and mx player on the Tablet S).
So here is my question: The Galaxy Tab is able to play even 1080p mkv's without breaking sweat, basically anything I can throw at it, whereas the Tablet S struggles with some of the 720p mkv's and cannot even start the 1080p ones without freezing. Is this normal behaviour? Is it because the screen has a greater resolution and the Tablet S has to work so much harder than the 1024x600 Galaxy Tab?
The Tegra 2 CPU used in the Tablet S struggles with HD content encoded using H.264 and the High profile. It's a known limitation.
For videos you encode yourself using H.264/x264, you should use the Main profile.
For downloaded HD content that is already encoded using the high profile we're all out of luck
I usually use MX Player Pro on my tablet, but I've tried Dice Player and it is somewhat better at playing high profile stuff, so you may want to give that a try.
Thank you! I did not know this. So actually the hardware in this dualcore tablet is weaker than the 2-year-old Galaxy Tab? Or is this only a driver issue?
sedohunta said:
Thank you! I did not know this. So actually the hardware in this dualcore tablet is weaker than the 2-year-old Galaxy Tab? Or is this only a driver issue?
Click to expand...
Click to collapse
When it comes to HD video playback the Exynos 3110 CPU used in the Galaxy Tab has the upper hand, yes. I was a bit surprised to find out that the Tegra 2 wasn't better at video decoding myself. And no, AFAIK it's not just a driver issue, so it can't be fixed through software/firmware.
Heh. Thanks again! This is a real eye-opener. To tell you the truth it never occured to me to check whether a newer chipset / tablet would actually have lower performance than the previous generation. One would think they upped the resolution of these tablets to 1280x800 to meet 720p HD requirements....
I'm using Dice Player, it has HW acceleration.
I was mildly disappointed with the Sony's high-res Video playback capabilities after I also upgraded from my venerable GT-P1000 Galaxy Tab. Now I use MX Video Player and it seems to do alright, but the Sony's hardware accelerated mode as mentioned above is very finicky about its x264 video.
Also, even if an app claims to be hardware accelerated, chances are extremely good it's probably not. Built-in Hardware Acceleration won't go live until ICS and when video players use the "Hardware Decoding" option (note that its not the same), they just use the Sony's built-in chip and all the video players will deal with it pretty much the same.
real
I use Real Player and Mobo Player and have rarely any problems.
A help if you are having issues is to shut down all of the unneeded apps, clear out your ram and shut off the data connection.
When I start to play an AVI movie, Rockplayer asks if I want hardware or software to manage the file. Which is best on the Transformer Prime? What's the difference? Thanks for your help.
Depends on the codec, really. Use hardware if available; otherwise use software.
Also, 10-bit H.264 AVC does not decode well either hardware or software as of yet on Transformer.
foolydooly said:
Depends on the codec, really. Use hardware if available; otherwise use software.
Also, 10-bit H.264 AVC does not decode well either hardware or software as of yet on Transformer.
Click to expand...
Click to collapse
Thanks for your response. Both hardware and software seem to work, so I guess I'll use hardware. Thanks!
Hey guys, i´m looking for a farily cheap box to use exclusively as a steam link device for 4k60, currently i own the OG Steam Link, and while it is a hell of a little gadget, it simply does not deal with 4k60, and my actual TV, even tho it has Android TV has some weak decoding capabilities it seems, i lose frames even at 1080p.
Anyways, anyone has any experience with Steam Link (wired) and any AMLogic S905X4 SoC decoding exclusevly 4k60 games to share?
Are both, the computer and the Android TV, wired?
The chip is for sure more than capable enough.
Let me also suggest you to try AMD link or Moonlight for nvidia.
Qualcomm has been very cloak & dagger about different versions of aptX adaptive, and aptX voice, and aptX lossless.
My main interest is aptX voice support. Since the google Tensor chip isn't a QUALCOMM thing, there's no official support for "snapdragon sound".
Does anyone know if someone can rip snapdragon sound from another device and put it on a pixel 6 with a custom rom?
see here
Does the Pixel 6 Pro include aptX, aptX HD, LDAC? Specs page is silent - Google Pixel Community
aptx is supported on the pixel so what you're asking should work, as long as you're using a compatible audio device
As already pointed out, Pixel 6 supports QCOM's aptX, aptX HD audio codecs. You couldn't "rip" support for additional codecs anyway, they are hardware dependent and rely on proprietary vendor binaries. No support for aptX Adaptive or Low Latency afaik.
aptx is low latency?
boe323 said:
aptx is low latency?
Click to expand...
Click to collapse
THis is a complicated question to answer "it depends".
HOwever, the product known as aptx-LL is not usually available with OS native bluetooth stacks, it's implemented usually with USB dongles that the computer or phone sees as a generic usb audio device. Thus, aptx-LL is vaporware without the use of a dongle.
Presumably the long term goal is for that to eventually be replaced by aptx Adaptive, which combines some of the LL & HD features to some extent. Unfortunately, it's become impossible to know which "Versions" of aptx adaptive are supported by various phones and headphones, because qualcomm's "snapdragon sound" certification is confusing to end users. Presumably, most devices support aptX adaptive, but it's really hard to figure out if a device supports aptX Voice (most don't), AptX TWS+ (most do?) and Aptx Lossless (still too new) which are all part of the "snapdragon sound" umbrella
I've just been through all this trying to find a device that supports Snapdragon Sound, as I review earbuds and need to ensure I am able to give them their best opportunity with supporting services.
Aptx-adaptive is quite commonplace now with most earbuds using the Qualcomm QCC3040 and QCC3046 chipsets, which covers many new releases from Soundpeats and Earfun to KZ, offering this codec as an option. Snapdragon Sound is a marketing term encompassing 96k Aptx-Adaptive and 32k Aptx-Voice, and very few products support it (QCY T18, Edifier NeoBuds S and Lollipods, etc.)
Whilst most 2021 Snapdragon phones support aptx-adaptive, I believe the only devices that support the three Snapdragon Sound codecs are those with Snapdragon 888 and higher processors.
I tried my Snapdragon Sound-capable earbuds on a few other devices and was able to get aptx-adaptive working but had some issues getting consistent 48k.
I ended up settling on the (otherwise awful) Xiaomi 11T Pro as the only others that supported the codecs at the time were Moto devices mostly only available in the U.S. I agree it is confusing and not particularly user friendly - there is no indication you're getting the desired codec, you have to dig around a fair bit to see what you're actually using. It's not even as easy as selecting LDAC or LHDC - seems like hi resolution sound is very much an afterthought.
can i say its killing me there aint no dolby atmos (the soundfx version, not the decoder version)
trying wavelet, but there are drop outs, im troubleshooting it
im hedging my bets, bt 5.2 etc will over take at some point with features