foobar2000 mobile v1.4 previewAndroid (Google Play) (https://www.foobar2000.org/test-android)
Android (APK downloads) (https://www.foobar2000.org/apk)
iOS (https://www.foobar2000.org/test-ios)
Preview change log:https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Mobile_Version_1.4_Preview_Change_Log
Most notable changes:- Revised Android TV support. Defaults to dim screen with current system time and subtle now-playing-track info instead of glaring skinned playback controls that don't work with TV remote anyway.
- REMOVED support for Android's sandboxed filesystem
- Latest revision of HTTP & FTP code, improved use of persistent connections, implemented encrypted FTP support.
- Added WebDAV share support in Media Library / Media Servers, add as webdav-http:// or webdav-https:// URL.
- Codec tech updates.
- Browsing by folder now lists archives & lets you browse their contents.
- Lots of bugs fixed.
- Added media buttons lock mode, press play/pause repeatedly to activate/deactivate.
- New DSP: Push the Tempo
Details about Android filesystem changesSupport for Android sandboxed filesystem, also known as "Storage Access Framework", or "DocumentFile API", has been removed.
I'm sorry. Some will hate it. I also hate axing something I spent months working on. It's simply broken. It was responsible for fun issues such as "loading list of playlists takes over 10 seconds". I can't go around yelling at users to stop using it, because that's not how software is supposed to work.
Please either use "foobar2000 music folder", or give foobar2000 full disk access permissions if you wish to access normal SD card folders.
You might have to remove & re-add your music folders for new foobar2000 to pick them up.
Thanks for understanding.
thx for the new beta Peter,
will this effect my Samsung Galaxy S21+?
I found using folder viewing method easiest instead if trying to create playlists...
you mentioned above filesystem changes.. O_o
If you only use "foobar2000 music folder", you're not affected.
If you use SD card folders on some new-enough phone, you might have to remove folders from foobar2000 media library and add them again, at which point you will be asked to grant foobar2000 full disk access permissions.
I do not use the Foobar2000 music folder.. I don't even know where it is located on the phone's file system.. lol
I use [ JoeMusic ] folder in the root of my android phone's internal storage...
as the Samsung Galaxy S21+ does not have an SD card slot...
I hope this addresses FTP server hammering issues some have been suffering from.
The new release was like Christmas for me, but I'm afraid to report: the problem with "421 Unauthorized client limit reached" still exists.
What did you change? Is there a hardcoded "x connections per minute" or "sleep x seconds" value, that could be made configureable via the options?
I don't mind waiting for 30-60mins to get the indexing done, as long as it succeeds.
The new beta is still only able to index about 1/3 of my whole song library.
Edit: There seem to be additional new entries in the indexing error log saying "225 ABOR command successful", which I don't remember to be there before.
They also sometimes popup when trying to play a file.
Towards the end of the indexing error log, the messages change to "network error".
Browsing by folder now lists archives & lets you browse their contents.
On a related sidenote:
shouldn't fb2k display embedded cover art when playing a file?
At the moment I only see a cover displayed when there's a cover.jpg in the same folder.
For files with embedded cover art it's neither indexed nor extracted & shown when played.
Additional observation:
I seem to be only able to play FLAC files via FTP with the new version.
OGG and MP3 files don't play at all: "Playback error: 225 ABOR command successful" comes up and the next file is tried with the same result.
This procedure doesn't stop before a FLAC file is in the list, which then plays.
OGG and MP3 playback via FTP works when I go back to the previous version.
Edit: Managed to play a MP3 file (320Kbps CBR, 12.5MB) via FTP.
A Podcast file in the same folder with 64 Kbps CBR (12.2MB) doesn't play ("225 ABOR").
When I download the podcast file to the fb2k music folder, the file plays there.
Confusing...
Is there any chance I can try this FTP server software myself? What device/software is it exactly?
Is there any chance I can try this FTP server software myself? What device/software is it exactly?
Basically any AVM Fritzbox router (70% market share in DE/AT/CH) with its integrated NAS function.
They run this FTP daemon (https://boxmatrix.info/wiki/Property:ftpd_(lincmd)).
Build 752 posted, see link above.
Again fixed lots of FTP bugs (thanks to pyr452 for great help).
I was finally able to get encrypted FTP working.
Use ftps:// for implicit encryption (rare), ftpes:// for explicit (more common).
If you connect to a server that requires explicit AUTH TLS using ftp:// address, foobar2000 will automatically enable encryption.
the link/url for the new beta is coming back as not found 404.
https://www.foobar2000.org/downloads/Android-752.zip
the link/url for the new beta is coming back as not found 404.
https://www.foobar2000.org/downloads/Android-752.zip
https://www.foobar2000.org/downloads/752.zip (Peter will probably fix the link soon)
Peter also squashed many bugs affecting embedded cover art indexation
(Peter will probably fix the link soon)
Peter also squashed many bugs affecting embedded cover art indexation
yeah,
he probably will fix it sooner or later lol. ;)
It was just important enough to report it though.
I'm happy to learn mobile fb2k is still being developed, although with some trepidation since the filesystem change applies to me, as I have a 128GB microSD with a load of music crammed into it in OPUS format. I have very little internal storage, so it's essential. If it means I'll have to copy everything off and back on again, I may take the opportunity to start over from scratch, and may use onewaysync going forwards...
A few features I'm hoping will be added:
- Exposing the Date field for the currently playing song. Maybe any user-defined metadata fields could be displayed, but Date feels to me like it should be a default.
- Failing that, since the above can be managed via skinning AFAIK, fixing the currently broken skin support. Ideally I'd just keep/modify the default skin though, if that's possible.
- Exposing the Date field for the currently playing song. Maybe any user-defined metadata fields could be displayed, but Date feels to me like it should be a default.
Where would you position the date?
Another optional useful feature would be the data from the status bar of the desktop app (filetype, bitrate, hertz, mode). In the mock-up below it's positioned in the middle, but if and where could be configurable: "no data/top/middle/bottom"
(https://abload.de/img/suggestion26sdtl.png)
- Exposing the Date field for the currently playing song. Maybe any user-defined metadata fields could be displayed, but Date feels to me like it should be a default.
Just another mockup idea:
(https://abload.de/img/suggestion3y6dzw.png)
Where would you position the date?
Personally it would make no difference to me, wherever is fine, so long as it's there somewhere.
New build up.
Fixed widget errors, updated target API levels to latest (33) as Google Play Store isn't accepting API 30 I used until now.
I'm working on getting this released as open beta in Google Play Store.
New build up.
Fixed widget errors, updated target API levels to latest (33) as Google Play Store isn't accepting API 30 I used until now.
I'm working on getting this released as open beta in Google Play Store.
nice!
thx Peter :D
will there be any issues with the video game music components built in from Kode54 src that you are still working with?
SNES & Sega Genesis, PlayStation 1&2, Sega Saturn, etc are what I use.. :D
New build up.
https://www.foobar2000.org/downloads/755.zip not found
The same goes for https://www.foobar2000.org/downloads/Android-755.zip
New build up.
https://www.foobar2000.org/downloads/755.zip not found
The same goes for https://www.foobar2000.org/downloads/Android-755.zip
same problem with the last build...
Sorry, it seems I keep failing at linking for some reason.
Added download info to https://www.foobar2000.org/apk
In meanwhile, the update got rejected by Google Play, they disagree with full storage access.
This is BULLSHIT.
Mainstream competing media players (VLC, Kodi) have full storage access.
Google insists that it's not "core functionality" and it's possible to use foobar2000 without it.
It seems I have to choose between releasing dumbed down version without access to SD card folders, or dumbed down version without "foobar2000 music folder" so you have to grant full storage access to play music at all.
Reverting to use Storage Access Framework is not an option, it was the main source of bug reports with past versions.
I'm forced to postpone updating Google Play until this is sorted out one way or another.
Google insists that it's not "core functionality" and it's possible to use foobar2000 without it.
Is that the result of an automated inspection or did some human actually look at the app?
I could imagine that the app in its current form almost exclusively uses read commands, while Google expects to see at least some (or more) usage of write commands . So then the verdict is "why full storage access?".
Some sort of workaround (although pretty work intensive) might be to add the possibility to edit ID3 tags.
Just an idea - it could also be that I'm completely wrong about Googles terms regarding the full storage access.
Seemingly automated rejection >> appeal >> apparent human reply rejecting appeal.
There's no option to have only read access.
There's no sanely working option to have only music folder access. Secure Access Framework does it, but with severe bugs and horrible performance, should be avoided this at all costs, caused bugs like "list of playlists takes 10s+ to load" with past foobar2000 versions. I can't yell at every user reporting these bugs to use private foobar2000 music folder instead.
There's no sanely working option to have access only to music files - "media files only" mode hides files that Android doesn't recognize as music, such as Musepack.
I expected trouble, but VLC and Kodi do the same and somehow haven't been rejected.
Finally, users don't actually have to grant foobar2000 full disk access if they don't want to, foobar2000 prompts for full disk access only when trying to add local folders to Media Library.
Meanwhile, iOS version has been released to beta testers.
Seemingly automated rejection >> appeal >> apparent human reply rejecting appeal.
There's no option to have only read access.
There's no sanely working option to have only music folder access. Secure Access Framework does it, but with severe bugs and horrible performance, should be avoided this at all costs, caused bugs like "list of playlists takes 10s+ to load" with past foobar2000 versions. I can't yell at every user reporting these bugs to use private foobar2000 music folder instead.
There's no sanely working option to have access only to music files - "media files only" mode hides files that Android doesn't recognize as music, such as Musepack.
I expected trouble, but VLC and Kodi do the same and somehow haven't been rejected.
Finally, users don't actually have to grant foobar2000 full disk access if they don't want to, foobar2000 prompts for full disk access only when trying to add local folders to Media Library.
" private foobar2000 music folder instead"
where exactly is this located?
I could not find its location on my phone, so I just used the root of my phones internal storage,
since my phone a Samsung Galaxy S21+ does not have a microSD card slot at all.. only the sim card slot...
I use the same folder layout as I do on my Windows PCs (desktop and laptop).
C:/JoeMusic/ sub-folders named based on consoles and other factors..
> apparent human reply rejecting appeal.
There's no way to escalate this?
The horrible performance of the Secure Access Framework in combination with many files is well known (http://magicbox.imejl.sk/forums/topic/storage-access-framework-performance/).
Edit: this exception (https://support.google.com/googleplay/android-developer/answer/10467955?hl=en) should apply to fb2k:
There is currently no alternative method to provide the core functionality, or the use of privacy-friendly alternatives (for example, MediaStore API or Storage Access Framework) has a substantially detrimental impact on the critical features of the app that are tied to the core functionality.
I mean, when they test it with 5 files, they won't see a performance problem...
" private foobar2000 music folder instead"
where exactly is this located?
I could not find its location on my phone, so I just used the root of my phones internal storage,
since my phone a Samsung Galaxy S21+ does not have a microSD card slot at all.. only the sim card slot...
I use the same folder layout as I do on my Windows PCs (desktop and laptop).
C:/JoeMusic/ sub-folders named based on consoles and other factors..
It is located inside app's private data. It's not normally accessible from Windows Explorer or Android file manager apps
In foobar2000 console you will see on each startup lines like this:
Monitoring: foobar2000 Music Folder : /data/user/0/com.foobar2000.foobar2000/data/Music
This points to where it's located within the device filesystem.
You can manipulate files there using developer tools such as ADB.
But it's much easier to just use foobar2000 FTP server to transfer music there.
I'm open to ideas how to make accessing it even easier. I personally like VLC's web interface for uploading files but doing anything like it is waaaay beyond my HTML skills.
> apparent human reply rejecting appeal.
There's no way to escalate this?
The horrible performance of the Secure Access Framework in combination with many files is well known (http://magicbox.imejl.sk/forums/topic/storage-access-framework-performance/).
Edit: this exception (https://support.google.com/googleplay/android-developer/answer/10467955?hl=en) should apply to fb2k:
There is currently no alternative method to provide the core functionality, or the use of privacy-friendly alternatives (for example, MediaStore API or Storage Access Framework) has a substantially detrimental impact on the critical features of the app that are tied to the core functionality.
I mean, when they test it with 5 files, they won't see a performance problem...
Thanks for the tip, I'll try submitting again in a few days with a new build.
" private foobar2000 music folder instead"
where exactly is this located?
I could not find its location on my phone, so I just used the root of my phones internal storage,
since my phone a Samsung Galaxy S21+ does not have a microSD card slot at all.. only the sim card slot...
I use the same folder layout as I do on my Windows PCs (desktop and laptop).
C:/JoeMusic/ sub-folders named based on consoles and other factors..
It is located inside app's private data. It's not normally accessible from Windows Explorer or Android file manager apps
In foobar2000 console you will see on each startup lines like this:
Monitoring: foobar2000 Music Folder : /data/user/0/com.foobar2000.foobar2000/data/Music
This points to where it's located within the device filesystem.
You can manipulate files there using developer tools such as ADB.
But it's much easier to just use foobar2000 FTP server to transfer music there.
I'm open to ideas how to make accessing it even easier. I personally like VLC's web interface for uploading files but doing anything like it is waaaay beyond my HTML skills.
aah ok..
I usual use a USB cable to plugin my phone into my Windows PC,
so I can upload music to the root of the phone in my JoeMusic folder...
so accessing my phones root folder as Foobar2000 does now is essential for me..
I keep it simple...
good luck Peter.
Follow up rant:
Even on locked-down iOS, private app data folder can be accessed from your computer over USB cable.
On Android, there's no standard interface to manage files in app-specific folders and Google clearly doesn't want apps to touch the filesystem outside app-specific folders at all.
Tested Manifest.permission.READ_MEDIA_AUDIO instead of Manifest.permission.MANAGE_EXTERNAL_STORAGE
Works, but makes all files not recognized by Google as audio to disappear. You get your MP3s and FLACs, but anything more exotic = empty folder presented.
No external covers picked either, whoever designed this had no clue WTF they were doing.
I'm going to respond with:
https://www.foobar2000.org/temp/MANAGE_EXTERNAL_STORAGE.txt
Anything to add?
> Anything to add?
In regards to SAF performance: maybe mention that the problems appear with larger collections (basically every additional file makes SAF slower) and that fb2k is targeted towards power users, which often have large collections.
You could also mention a link between fb2k and VLC/Kodi, which were granted MANAGE_EXTERNAL_STORAGE and basically do the same stuff as fb2k (minus video files). If they wouldn't have access to MANAGE_EXTERNAL_STORAGE, they'd suffer from the same UUX-degrading problems.
I'm going to respond with:
https://www.foobar2000.org/temp/MANAGE_EXTERNAL_STORAGE.txt
Anything to add?
wow lol, good luck Peter.
thoughts.
I use Foobar2000 mainly for MP3(more video game music and anime music), SNES spc, Sega Genesis gym/vgm, PlayStation 1&2,
and Sega Saturn ssf
all done via a game music component(s)
thx Peter for doing what you can to revive them for use with 64bit version... till then I will stick with the 32bit version of Foobar2000 on Windows PC and for ANDROID devices like my Samsung Galaxy S21+ thx for including the video game music components
Anything to add?
IMO, it should be toned down a bit, since it sounds very confrontational (even if it was not intentional).
I do understand your frustration with Google policies and/or with the way they handle things like this, but, from my experience, voicing it in such a way is counter-productive and might reduce the possibility of your appeal acceptance.
E.g. phrases like "Whoever designed this obviously had no clue about typical music collection structure" should be avoided, since they don't add any useful information to the appeal, but will more than likely trigger defensive reaction from the responder, if he identifies himself as part of the Google, which might make him ignore the appeal altogether.
IMO, it should be toned down a bit, since it sounds very confrontational (even if it was not intentional).
I do understand your frustration with Google policies and/or with the way they handle things like this, but, from my experience, voicing it in such a way is counter-productive and might reduce the possibility of your appeal acceptance.
E.g. phrases like "Whoever designed this obviously had no clue about typical music collection structure" should be avoided, since they don't add any useful information to the appeal, but will more than likely trigger defensive reaction from the responder
I second that (including removing the "Useless to me"), though I can understand the frustration after that massive rewrite and the fact that similar apps (VLC/Kodi) got MANAGE_EXTERNAL_STORAGE granted.
Try to be as explanatory and friendly as possible when you want to convince them that you need that right.
What you're reading is already the censored and toned down version. But OK I'll work on it some more.
Edit: Updated and toned down some more.
Potential mitigation I just thought of is requesting both READ_MEDIA_AUDIO and READ_MEDIA_IMAGES so we can read external covers. It still sucks (limits audio format support, no archive support) but will cause way fewer false bug reports.
I might have to do this for Google Play and at the same time provide standalone APK with MANAGE_EXTERNAL_STORAGE.
Build 757 up, now with detailed change log.
OK, success.
After some constructive exchange of appeal messages, build 757 is up on Google Play.
OK, success.
After some constructive exchange of appeal messages, build 757 is up on Google Play.
ok kool, Thx Peter.
are all the video game music components and Kode54 worked on still included that were in earlier ANDROID builds?
that is in essence why I use Foobar2000 Windows and android mobile.
plus .FLAC, .MP3, and .ogg
please and thx of course.
OK, success.
After some constructive exchange of appeal messages, build 757 is up on Google Play.
Superb! Friendly tenacity pays off.
ok Peter,
I got the alpha update installed via Google Play Store.
I had to remove the old folder listings and re-add them..
after granting full access permissions.. lol O_o
SNES .spc files, working.
while accessing Sega Genesis .gym after playing an SNES .spc file
there was no playback stalled..
I had to use the controls to manually change track to get playback going.. as a possible bug note..
I tried to run a .spc SNES music file this time while a Genesis .gym was playing... stalled too... pause/p[lay button did nothing..
but like before the skip track button worked to get playback going again.. lol
.mp3 files do not appear to be effected...
only the Sega Genesis (.gym/.vgm) and SNES (.spc) music files..
strange.. I wonder what is causing it.. lol ;)
last bug the music/files playing at least for an .mp3 did not stop/pause when I closed the Android app.
v1.4.0-alpha_build.757.
also it is not remembering the last viewed folder so its not staying ion the folder it was in before when I close the app and reopen it unless the music is still playing..
lol wow loads of bugs..
have fun Peter fixing them. :D ^_^ ;)
edit1:
I do not bother with making playlists on the ANDROID mobile version too much hassle to add on the music to them as it is on Windows..
no problem though... I browse by folder and that works well enough for me.
last bug the music/files playing at least for an .mp3 did not stop/pause when I closed the Android app.
v1.4.0-alpha_build.757.
Did this work for you in previous versions?
I can't remember it to work ever, same as in VLC, because the background service used for playback doesn't notice when an app was closed. However I provided Peter with a link, that might be able to fix this. At least there must be some way, because I read (not tested ) that some players are able to recognise when they're closed and afterwards stop playback.
last bug the music/files playing at least for an .mp3 did not stop/pause when I closed the Android app.
v1.4.0-alpha_build.757.
Did this work for you in previous versions?
I can't remember it to work ever, same as in VLC, because the background service used for playback doesn't notice when an app was closed. However I provided Peter with a link, that might be able to fix this. At least there must be some way, because I read (not tested ) that some players are able to recognise when they're closed and afterwards stop playback.
It worked fine before on Foobar2000 (v1.3.2) for android.
It just paused and not fully stopped the playing track on closing the app.
and it use to remember the folder I was viewing before...
Build 758, addressed playback not getting suspended on app close among other things.
Build 758, addressed playback not getting suspended on app close among other things.
ty Peter.
I noticed the functionality for playing .psf/.psf2 Sony PlayStation 1&2 music component and the Sega Saturn one are missing and I can not play those files... :(
and has build 758 been published to Google Play Store yet?
Build 758, addressed playback not getting suspended on app close among other things.
Hi Peter, trying this build on my Fiio M11 Pro and still the same bug as the previews before:
Playback getting suspended although app *not* closed. Playback stops after every title 1 second before its shown duration. So I have always to skip manually to the next title and then pushing Play/Pause button (ore swiping the blue button in the progress bar when I want to repeat the last title) :-[ (either in Android and Pure Music mode)
Last version without detected flaws was 1.2.30, Version 1.3.0 became unresponsive with huge playlists (shuffle all tracks --> Playlist), but that issue seems to be resolved with 1.4 ;-)
Fiio M11Pro, ca. 102000 files, only mp3 (CBR and VBR)) on 1TB SD card
Just noticed that streaming for certain public radio stations in Germany doesn't work anymore:
https://liveradio.swr.de/sw282p3/swr1bw/ (128KBit MP3)
https://liveradio.swr.de/sw331ch/swr1bw/ (96Kbit AAC)
This used to work in 1.3.x, now the entries are listed with "empty track list".
Build 758, addressed playback not getting suspended on app close among other things.
Hi Peter, trying this build on my Fiio M11 Pro and still the same bug as the previews before: Playback getting suspended although app *not* closed.
To encircle the problem: Some titles play flawlessly, and the player skips to the next title in the playlist; some files stop 1 second before shown duration and I have to skip manually, (skip silence not activated), and when starting playback more in the middle of a track, it sometimes happen that a 1-second-excerpt of that track loops infinetely. As mentioned, only MP3 files in my music library, it occures both with CBR and VBR encoded files.
May there be an issue with an updated MP3 decoder in FFmpeg 6.0?
May there be an issue with an updated MP3 decoder in FFmpeg 6.0?
Sounds more like a dying SD card to me.
Other players play the files without any problems on the device?
May there be an issue with an updated MP3 decoder in FFmpeg 6.0?
Sounds more like a dying SD card to me.
Other players play the files without any problems on the device?
Checked with MP3's on Fiio's internal memory - same problems
Checked with FLAC's on Fiio's internal memory and SD card - no problems
Complete MP3 library with Foobar 2000 v2.0 on my Windows notebook - no problems
1.31播放Flac非常好听，1.4非常难听，感觉声音挤在一块了，不知道是不是设备问题。
系统版本：Android 13
设备：Samsung Galaxy S23ultra
Please provide English translation in future posts.
TOS 10 (https://hydrogenaud.io/index.php/topic,3974.0.html). All members must post in English. Content in other languages allowed as long as full English translations are provided, or otherwise at the discretion of the staff.
Google translation:
Playing Flac on 1.31 is very pleasant, but 1.4 is very unpleasant. I feel that the sound is squeezed together. I don’t know if it is a device problem.
System version: Android 13
Device: Samsung Galaxy S23ultra
MOD: Edited for TOS 10 only.
1.31播放Flac非常好听，1.4非常难听，感觉声音挤在一块了，不知道是不是设备问题。
系统版本：Android 13
设备：Samsung Galaxy S23ultra
Please provide English translation in future posts.
TOS 10 (https://hydrogenaud.io/index.php/topic,3974.0.html). All members must post in English. Content in other languages allowed as long as full English translations are provided, or otherwise at the discretion of the staff.
Google translation:
Playing Flac on 1.31 is very pleasant, but 1.4 is very unpleasant. I feel that the sound is squeezed together. I don’t know if it is a device problem.
System version: Android 13
Device: Samsung Galaxy S23ultra
MOD: Edited for TOS 10 only.
Sorry
Hi :)
Standalone Android APK downloads
https://www.foobar2000.org/apk
Download version 1.4 preview 2023-07-02:
All architectures (install correct APK from the archive)
↑can't download
Thanks.
↑can't download
Try https://www.foobar2000.org/getfile/foobar2000-mobile-v1.4-2023-07-02.zip
@pyr452
Oh great.
Many Thanks.
@pyr452
Oh great.
Many Thanks.
The same version just rolled out via the Playstore Beta channel.
I've confirmed.
[foobar2000 mobile] foobar2000 Mobile for Android v1.4.0 Preview 2023-07-02 Google Play
https://foobar2000.xrea.jp/?FrontPage
Build #761
The forum link on the about page, https://www.foobar2000.org/forums/mobile (https://www.foobar2000.org/forums/mobile), 404s.
Build #761
The forum link on the about page, https://www.foobar2000.org/forums/mobile (https://www.foobar2000.org/forums/mobile), 404s.
Where did you get that build?
AFAIK there's no such thing as Build #761.
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Mobile_Version_1.4_Preview_Change_Log
https://www.foobar2000.org/apk
Build #761
The forum link on the about page, https://www.foobar2000.org/forums/mobile (https://www.foobar2000.org/forums/mobile), 404s.
Where did you get that build?
AFAIK there's no such thing as Build #761.
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Mobile_Version_1.4_Preview_Change_Log
https://www.foobar2000.org/apk
The Play Store.
The Play Store.
Ah, OK, didn't notice that.
Peter has, at least in the changelog, switched to calling the builds by date rather than build number.
- Revised Android TV support. Defaults to dim screen with current system time and subtle now-playing-track info instead of glaring skinned playback controls that don't work with TV remote anyway.
Can you please consider making this screen also available on phones and tablets somehow?
Modern skinned playing screen is not usefull to screen reader users. The controls and playing info is completelly inaccessible on that screen.
With this new android TV specific plaing screen I assume we will get at least something more than just an empty window.
I can think of making it available as an option in the settings somehow or force it when some accessibility service is detected running (Relevant SO question (https://stackoverflow.com/a/12362545)) when showing now playing screen.
I'm running the latest public preview version dated 2.7.2023 downloaded from google play. I've added a FTP location and its library scanning is in progress. Perhaps this does not contributed to the issue I just wanted to describe my configuration a little.
When going to Internet radio and trying to play streams from this icecast server http://live.slovakradio.sk:8000/ The Foobar on Android is not allowing those MP3 streams to play, error 400 bad request is displayed instead. No matter if I add a new URL or try to play an existing one I have added before updating to v 1.4 preview.
I'm running the latest public preview version dated 2.7.2023 downloaded from google play. I've added a FTP location and its library scanning is in progress. Perhaps this does not contributed to the issue I just wanted to describe my configuration a little.
Is your FTP server probably running on some SOHO router?
In that case scanning takes some time, since the hardware isn't very potent.
When going to Internet radio and trying to play streams from this icecast server http://live.slovakradio.sk:8000/ The Foobar on Android is not allowing those MP3 streams to play, error 400 bad request is displayed instead.
http://live.slovakradio.sk:8000/Devin_256.mp3.m3u works for me.
Which URI doesn't work for you?
http://live.slovakradio.sk:8000/Devin_256.mp3.m3u works for me.
Which URI doesn't work for you?
Thanks for the hint.
The url without .m3u at the end is not working.
http://live.slovakradio.sk:8000/Devin_256.mp3 does not work with 1.4 but it used to work in 1.3
http://live.slovakradio.sk:8000/Devin_256.mp3.m3u is working in both 1.3 and 1.4.
In fact it's not limited to this single icecast instance. I believe both variants should be working.
Hello,
Is the FTP support using UTF8 charset to parse directory listings?
I am getting object not found errors while scanning whenever the filename has some non ascii characters in the filename such as...
ftpes://<user>:<password>@<hostName>:<port>/<some>/<path>/Darinka Rolincova - Keby som bola princezna Arabela-1983/10 - Darinka Rolincová - Slávik a ruža.mp3
And the correct file name should be
10 - Darinka Rolincová - Slávik a ruža.mp3
Other FTP clients such as rclone or LFTP can handle this fine.
Would there be a way to improve this?
With total commander I used to be able to workaround this by manually posting an FTP command
OPTS UTF8 ON
However I haven't used this for ages thus I don't know if this is still needed or if it might be usefull here too. My understanding is that most modern FTP servers do support UTF8.
Edit:
The server side is Pure-FTPd on linux.
I'm sorry for the triple posting...
Just curious: do you sometimes have the same problem as described below?
Play a song via FTP
Switch to a different song (FTP source as well)
New song doesn't start to play - only seeking to a random position starts playback.
This doesn't happen every time for me, but I'd say in about 40% when doing so.
Just want to check if this is related to my slow FTP server or a general problem with Peters latest FTP improvements.
I have only played MP3 and FLAC files so far. For me the playback advances automagically to the next track in the list when one track finishes playing. Also when I manually tap to play a different track from the same FTP source while in the middle of a playing track it'll start playing the new track with no issues.
I am using no DSP effects and library indexing is enabled for that foobar 2000 library location.
The FTP server I am connecting to is a remote pure ftpd instance, I'm connecting through the internet to it. No VPN and other helper tools are involved.
It is a nice effort, thank you very much! I've got 2 Qs.
Is it possible to install and test it side by side with the stable build? - To avoid losing media library from the stable build, which takes a lot of time to scan.
And I've checked a few days ago, the reworked beta had issues with recognizing ReplayGain tags in music files, while the stable build sees them fine. Do you need help with reproducing/debugging it?
Also a little curious, if it's possible to put "foobar2000 music folder" on an external SD card? If so, would it still require full permissions?
Is it possible to install and test it side by side with the stable build? - To avoid losing media library from the stable build, which takes a lot of time to scan.
No, the beta/preview will overwrite the stable version but if you've used SAF for file access till now, the indexation speed should improve noticeably (SAF is/was a bottleneck with many files).
Is it possible to install and test it side by side with the stable build? - To avoid losing media library from the stable build, which takes a lot of time to scan.
No, the beta/preview will overwrite the stable version but if you've used SAF for file access till now, the indexation speed should improve noticeably (SAF is/was a bottleneck with many files).
Yes, the problem is that I'll likely need to rollback and build it up again with the old, slower version. Or maybe old version can also index fast if not using SAF? (if it can do so somehow?)
Or maybe old version can also index fast if not using SAF? (if it can do so somehow?)
Yes, I've understood for Foobar 2000 music folder even the older version is using storage apis directly with no SAF involved.
Yes, I've understood for Foobar 2000 music folder even the older version is using storage apis directly with no SAF involved.
Hasn't been my experience, or maybe I'm not noticing something. It uses a file picker that tells me I can't select a top-level path on my sdcard, because security-something. And there are no other ways to add folders to the Media Library.
2023-07-19 and 2023-07-20 preview builds have listed http and internet radio fixes. I know it takes time but my issue where direct links to media streams return error 400 are still present. It can also be observed when trying to play search results from the radio browser. Links to m3u, pls and possibly other supported playlist formats are working fine. Links to the same MP3 streams that are playable when referenced by the playlist are not playable when accessed directly.
Hi Peter,
I noticed you removed the some of the VideoGameMusic functionality from the android mobile version of Foobar2000.. ?? :( can you please restore it. I am talking about Sony PlayStation psf and psf2 files and Sega Saturn ssf and Dreamcast dsf files..
https://www.foobar2000.org/components/view/foo_psf
https://www.foobar2000.org/components/view/foo_input_ht
I cannot access or play half my collection of music now.. :(
I came here to ask the same. A huge part of the appeal of mobile foobar2000 for me is being able to cram in a large amount of music, since storage space is at a premium. xSF formats score hugely for this. I hope this is just an oversight and their support will be restored.
I hope this is just an oversight and their support will be restored.
I'm pretty confident Peter will restore this, probably just some accidental regression.
I suppose he's currently on vacation, since he wasn't online for a while.
On IOS v1.4 beta 22, the text in the Advanced Settings and DSP Manager menus is hidden in dark mode.
Another cosmetic issue: the page when you download from a media server looks odd with the dark skin. I am also having issues getting the album artist and album thumbnails to load for some reason; I have never had these an issue like this until this update.
Build 758, addressed playback not getting suspended on app close among other things.
Hi Peter, trying this build on my Fiio M11 Pro and still the same bug as the previews before: Playback getting suspended although app *not* closed.
To encircle the problem: Some titles play flawlessly, and the player skips to the next title in the playlist; some files stop 1 second before shown duration and I have to skip manually, (skip silence not activated), and when starting playback more in the middle of a track, it sometimes happen that a 1-second-excerpt of that track loops infinetely. As mentioned, only MP3 files in my music library, it occures both with CBR and VBR encoded files.
May there be an issue with an updated MP3 decoder in FFmpeg 6.0?
Same issues in the newest beta version :( - but they disappear when enabling <smooth seeking/pausing/volume> in Tools ->Advanced-> AUDIO ;)
Some radio stations playable in IOS Foobar2000 1.3.1 do not play in Android Preview 2023-07-31. Play stops with "Internet radio Error. Bad request (400)". Station urls have the format as this:
PartyFM - http://stream.partyfm.dk/Party320/
Another example with Bad Request (400): http://198.204.228.202:8160/flac
Plays fine in Firefox and VLC.
I've just reproduced the problem - inability to read ReplayGain info from Musepack files in v1.4-2023-07-31 (arm64).
When Media Library scanning is finished, "ReplayGain Scanner" shows that there is no info ("567 albums and 23 single tracks need scanning.")
If I choose "Reload from tags", it gets busy for around a minute, and finishes with no change.
I have looked into "Console", there are no clues.
The same files but before v1.4 are recognized without issues.
This also seems to be specific to Musepack - I tested v1.4 with a few mp3 and opus files, their ReplayGain info is recognized correctly.
Is Musepack still supported?
Is there anything I can help with fixing this?
There's a bug in the newest build (that has been in all 1.4 releases) when rapidly tapping next track after 5-10 seconds, any further songs will not play and the only way to remedy the problem is to completely restart the app.
I have tried this with DSPs on/off and the problem persists. My music is exclusively FLACs from SD card. The problem exists on both my Tab S7+ and Note 20 Ultra running Android 13.
Here is what it looks like:
(https://i.ibb.co/CzzqRGf/foobarbug.gif)
There's a bug in the newest build (that has been in all 1.4 releases) when rapidly tapping next track after 5-10 seconds, any further songs will not play and the only way to remedy the problem is to completely restart the app.
I have tried this with DSPs on/off and the problem persists. My music is exclusively FLACs from SD card. The problem exists on both my Tab S7+ and Note 20 Ultra running Android 13.
Here is what it looks like:
(https://i.ibb.co/CzzqRGf/foobarbug.gif)
I have discovered that this problem only occurs when "smooth seeking/pausing/volume" is enabled under Advanced settings.
Preview 2023-08-10 hotfix : Trying to add Music folder on External Storage to Media Library -> App crashes >:(
Only whole External Storage selectable for Media Library.
In former previews selecting the Music folder worked flawlessly
Hello everyone, it is obviously possible to connect this new version of foobar to a Webdav share. But I can't do it at all! Anyone got the secret?
Thank you so much !
Hello everyone, it is obviously possible to connect this new version of foobar to a Webdav share. But I can't do it at all! Anyone got the secret?
See the changelog:
WebDAV sources can now be accessed via webdav-http:// or webdav-https:// URLs
same thing with the decoding speed test page
theres also a weird gap on the utilities page
Playback will randomly pause when in the background.
Here is what the console says.
Is there a plan to sort albums by album artist? Same thing with displaying albums as a list.
I hope this is just an oversight and their support will be restored.
I'm pretty confident Peter will restore this, probably just some accidental regression.
I suppose he's currently on vacation, since he wasn't online for a while.
I'm becoming less hopeful.
I'd like to regress to an older version if this isn't going to be fixed.
not updated. foobar2000 Mobile for Android 1.4.2 preview 2023-12-07 build #791