Rockbox Development > New Ports
Rockbox as an Application (Android, WebOS etc.)
ploco:
--- Quote from: steak on September 15, 2015, 04:05:40 PM ---I clearly don't want to drop rockbox but I'm interested. Could you write the name of the app on Google Play in regular letters that I or anyone can read & use ? Here whatever you wrote looks similar to "EQ §§§§§".
--- End quote ---
Sorry, my bad, can be found as "EQ Media Player"
[Saint]:
--- Quote from: ploco on September 15, 2015, 07:58:26 AM ---...The freedom of parametric eq one may said.
--- End quote ---
FFmpeg Filters Documentation :: 6.35 equalizer
The more I look into it, the more I'm convincing myself that android-ffmpeg is the obvious choice.
--- Quote from: wodz on September 15, 2015, 08:11:52 AM ---Well, fiddling with RaaAoA is just some fun excersize for me. Just like hacking rockbox in general. Some people like solving puzzles some like reverse engineering, disassembling and hacking. I guess you are aware of http://gerrit.rockbox.org/r/#/c/683/
--- End quote ---
Oh, certainly. I understand that completely, and there's certainly no reason for this project to stop existing, especially not just because some guy (me) said some words on the Internet. :)
I suppose this was largely more of a philosophical discussion about starting anew, the future, and what exactly Rockbox consists of. If we can gain enough momentum to move in a particular direction, what do we bring with us, and what do we leave behind? What if anything defines Rockbox? etc.
--- Quote from: wodz on September 15, 2015, 08:11:52 AM ---I guess you are aware of http://gerrit.rockbox.org/r/#/c/683/
--- End quote ---
Yes. I was aware of this, thanks. But as with the answer I gave to ploco above, the more I look into it the harder it is for me to convince myself that android-ffmpeg isn't the obvious choice. Unless there is something I am missing from either a technical standpoint or something we need (see "what defines us?" from above) that it is totally lacking.
[Saint]
wodz:
Considering current HW, ffmpeg is probably the best choice. Decoding is easy part. Decent UI and proper balance between features and usability is the hardest thing. Rockbox was designed with very constrained embedded hardware in a mind. Current mobile hardware is much more like PC and hence rockbox with its all architectural peculiarities is not the best fit. Symbian passed away for the very same reason. This is called progress :-)
wodz:
For brave souls who can't live without rockbox on Lollipop here is *HUGE* hack which makes it running on ART. http://gerrit.rockbox.org/1211
kugel proposed other, cleaner solution but I don't know if I'll go around to work on this some more.
p.h.:
--- Quote from: wodz on September 18, 2015, 08:45:12 AM ---For brave souls who can't live without rockbox on Lollipop here is *HUGE* hack which makes it running on ART. http://gerrit.rockbox.org/1211
--- End quote ---
What does patch set 2 change? I've applied set 1 and in general it works, but themes don't work and sometimes it spontaneously starts to act as if an user was pressing up/down/enter.
Does the kugel's solution preserve theme engine work?
As to the question what Rockbox is. Rockbox has many unique features still not implemented in any of existing Android music players. They make Rockbox so unique. Together with the way user experience Rockbox they compose what Rockbox is. At least from an user's point of view.
Only relatively recently rockbox DSP features were outperformed (but still not in every aspect!) by Viper's Audio DSP for Android (root required). See http://vipersaudio.com/blog/
Still, show me a mobile player with cue sheet support, extensive codec support (including AC3, WavePack and Monkey's Audio), gapless playback, resume and bookmark features (just to mention only a few first coming to my mind)...
And speaking of bookmarks and resume - I know a person, who reverted from Lollipop to KitKat just to have Rockbox working. That means something.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version