I agree! In the general search for series, it also searches by year, just like it is configured for movies with TITLE AND YEAR. Doing this for series searches the same way, and therefore it finds nothing. However, the part where you can choose the episodes of the series is super editable and I love it.
Generally speaking I'm thinking to remove the search box from tv show. The whole idea is to search for an episode.. what's the point if you search the tv show name and then need to navigate to the right episode or change the search... Anyway, I'll fix it.
Also, I'll see how to improve the season and episode selection. Maybe save the last episode you clicked on or something
It would be incredible to be able to follow up on what was seen, although with a huge difference it is the best app of all! Congratulations on the work! Now I am thinking about paying for the lifetime subscription on Android, although it would be 21€, I think it's good!! When on APPLE?
Personally, I have no trouble finding a series in the "Discover" menu using the search function. The year isn't added if you configure the option correctly. Personally, I use this format:
Pretty much ready but I need to focus on finalizing it. Apple's process is a bit long. I wanted to release a good update on Android/fire os before I release iOS/tvOS since they mostly now use the same codebase so good and stable android version means good and stable iOS/tvOS version
That setting only affects the search by episode! In the series menu, the button that has TITLE AND YEAR configured for movies also searches in television series.
I understand and I tried to do it that way, but the problem is that there are many movies with the same name, so if you don't include the year, it's hard to find the one you want!
I understand your issue. That could help people like you. Personally, I create my own movie and series files and don't add the year to the title, but it's a good idea to ask for a setting option for people in the same situation as you.
VLC uses software decoding. Useful for devices that have no native hardware support
But your hardware supports it. So best case is exo
Because exo uses hardware decoding
For the same 4K H.265/MKV file of 4 GB, on a Smart TV with 3 GB of RAM, the following is typical if playback runs smoothly:
With hardware:
ExoPlayer: approx. 250 to 600 MB
Kodi: approx. 350 to 700 MB
VLC: approx. 500 to 1,200 MB
With software:
ExoPlayer: approx. 600 MB to 1.5 GB
Kodi: approx. 700 MB to 1.6 GB
VLC: approx. 900 MB to 2 GB or more
Realistic order:
Lightest:
ExoPlayer with hardware
Intermediate:
Kodi with hardware
Heaviest:
VLC with hardware Even heavier
Any of the three software-based options, especially VLC.
Most importantly
The 4GB file isn't loaded entirely into RAM.
The RAM is consumed by the buffer, the player, and the decoding.
On your 3GB TV, hardware decoding is the best option.
Direct answer
For that specific case, I would estimate the following:
ExoPlayer + hardware: ~400MB
Kodi + hardware: ~500MB
VLC + hardware: ~800MB
ExoPlayer + software: ~1GB
Kodi + software: ~1.1GB
VLC + software: ~1.5GB
🇪🇦Para un mismo archivo 4K H.265/MKV de 4 GB, en una Smart TV de 3 GB de RAM, lo normal es esto si la reproducción va bien �.
Con hardware
ExoPlayer: aprox. 250 a 600 MB.
Kodi: aprox. 350 a 700 MB.
VLC: aprox. 500 a 1.200 MB �.
Con software
ExoPlayer: aprox. 600 MB a 1,5 GB.
Kodi: aprox. 700 MB a 1,6 GB.
VLC: aprox. 900 MB a 2 GB o más �.
Orden realista
Más ligero
ExoPlayer con hardware �.
Intermedio
Kodi con hardware �.
Más pesado
VLC con hardware �.
Más pesado todavía
Cualquiera de los tres por software, especialmente VLC �.
Lo más importante
El archivo de 4 GB no se carga entero en RAM �.
La RAM la consumen el buffer, el reproductor y la decodificación �.
En tu TV de 3 GB, lo que más conviene es hardware decoding �.
Respuesta directa
Para ese caso concreto, yo estimaría así:
ExoPlayer + hardware: ~400 MB.
Kodi + hardware: ~500 MB.
VLC + hardware: ~800 MB.
ExoPlayer + software: ~1 GB.
Kodi + software: ~1,1 GB.
VLC + software: ~1,5 GB
In pure, unadulterated playback with the outdated and neglected VLC from its French support team, the image quality is simply awful. Exoplayer, after its recent abandonment by its support team, is now supported by a group of engineers from the Alphabet (Google) platform. Simply incredible; my sincerest thanks to this support team.
█
🇪🇦. En reproducción pura y dura el anticuado y dejado VLC de su grupo de soporte Francés, la imagen es simplemente para cine Horrible. Exoplayer tras su último abandono de su grupo de soporte, actualmente el soporte lo realiza un grupo de ingenieros de la plataforma Alphabet ( Google ) Simplemente Increíble,mis más sinceras gracias a este grupo de soporte.
Hola. . Ayer se me actualizo la app en la tv, uno de los cambios más notorios es que al finalizar un episodio y darme la opción entre ver créditos o siguiente episodio ya no puedo seleccionar (no marca la opción con los botones del control solo me sigue saltando 10 segundos). .
Yes, that's absolutely true.
The old standalone ExoPlayer repository (com.google.android.exoplayer2) was officially deprecated by Google after version 2.19.1. However, the ExoPlayer engine hasn't been abandoned; instead, it has been migrated to the official AndroidX Jetpack Media3 ecosystem.
## What exactly has changed?
* New official location: The library is now imported as androidx.media3:media3-exoplayer.
* Same team at the helm: It continues to be developed and maintained as open source by the same team of Google engineers.
* Active development and improvements: The integration into Media3 has simplified the architecture by unifying the player with MediaSession calls. It also includes new features such as native components for Jetpack Compose UI, performance improvements, memory optimizations, and integration with new codecs and formats.
## By using the androidx.media3 APIs, you are using the recommended, modern, and continuously supported version of ExoPlayer.
## Documentation and Useful Links
* Official Migration Guide to AndroidX Media3 (Android Developers)
* General Media3 ExoPlayer Documentation
* AndroidX Media3 Release Notes on GitHub
Thank you 👍🏻
█
Sí, es totalmente cierto.
El repositorio independiente antiguo de ExoPlayer (com.google.android.exoplayer2) fue descatalogado (*deprecated*) oficialmente por Google tras la versión 2.19.1. Sin embargo, el motor de ExoPlayer no se ha abandonado, sino que se ha migrado al ecosistema oficial AndroidX Jetpack Media3.
## ¿Qué ha cambiado exactamente?
* Nueva ubicación oficial: La librería pasa a importarse como androidx.media3:media3-exoplayer.
* El mismo equipo al frente: Sigue siendo desarrollado y mantenido en código abierto por el mismo equipo de ingenieros de Google.
* Desarrollo activo y mejoras: La integración en Media3 ha simplificado la arquitectura al unificar el reproductor con las llamadas a MediaSession. Además, incluye novedades como componentes nativos para Jetpack Compose UI, mejoras de rendimiento, optimizaciones de memoria e integración con nuevos códecs y formatos.
> Al utilizar las API de androidx.media3, estás usando la versión recomendada, moderna y con soporte continuo de ExoPlayer.
>
## Documentación y enlaces de interés
* Guía oficial de migración a AndroidX Media3 (Android Developers)
* Documentación general de Media3 ExoPlayer
* Notas de lanzamientos de AndroidX Media3 en GitHub
Thank you 👍🏻
