Well, your diveice could be doing something but 11 is where the door slammed shut.
It is a permission/restricted memory issue regardless. Somany non standard Android OSs that it's hard to keep track of what is going on where but the over aching theme of "old school everybody can access a public directory" is over.
I'm having the same issue and it's frustrating as hell! The app won't even show the skin files I've moved into the skins folder! Same with the presets. How can I fix this? Is there even a fix?
Caustic does not work properly at all for Android 11 phones. It's built for older model version phones. Please update the app for newer model phones. UPDATE: If you are having trouble loading sample packs and files in caustic with a new phone, simply take that file and move it to the samples folder in caustic. This helps load drum kits in the beatbox machine, and make a copy of the same folderor what ever folder you have samples in and move it and paste it in the pcm synth folder.
Caustic does not work properly at all for Android 11 phones. It's built for older model version phones. Please update the app for newer model phones. UPDATE: If you are having trouble loading sample packs and files in caustic with a new phone, simply take that file and move it to the samples folder in caustic. This helps load drum kits in the beatbox machine, and make a copy of the same folderor what ever folder you have samples in and move it and paste it in the pcm synth folder.
Not very likely - Rej will completely re-design the way how storage is used in Caustic
either by using the Storage Access Framework for example (which is a massive pain),
or by moving all Caustic storage into the app's private isolated storage "/sdcard/Android/data/com.singlecellsoftware.caustic/files/....".
Rather likely - You will downgrade your Android device to Android 10 or lower.
or by moving all Caustic storage into the app's private isolated storage "/sdcard/Android/data/com.singlecellsoftware.caustic/files/...."
Note that this folder seems to actually be vaguely accessible: e.g. Total Commander pops up a dialog to give it a permission to read and write subdirectories in the folder.
This may be the simplest way to go for Caustic: I know that some apps with the oldschool approach to files did this, e.g. specifically OpenTTD—and I seem to be able to read and write OpenTTD files with Totalcmd. Alas no such capability in the open-source Ghost Commander, but Totalcmd is freeware, doesn't seem to have any user-hostile misfeatures, and is generally very nice to use (the desktop version has been around since 1993). Dunno about other file manager apps.
Of course, there's no telling whether Google decide to take away this ability too, in the next versions (they probably will, judging by the trend so far).
P.S. However, presumably with such change Caustic Guide, Caustic Mastering, and apps supplying presets, will all stop working—if they currently read or add files in Caustic's song, patches and samples directories. That is, unless they take Totalcmd's approach and ask for permission to access Caustic's new data directory.
Yes, this is a problem Rej knows about.
Thanks Mike!
Haven't used Caustic in a while, and was surprised this was an issue.
Knowing Rej, I know he'll solve the problem within a reasonable time. But then again last time I heard from him he was busy with raising a family.
And couldn't do much dev work.
How are you though?
I have no thoughts really, I know Rej knows that Android 11 has finally turned off non sandboxed public memory.
I was unaware that Android 11 was out. My Samsung Galaxy S10 just upgraded to 10.
Well, your diveice could be doing something but 11 is where the door slammed shut.
It is a permission/restricted memory issue regardless. Somany non standard Android OSs that it's hard to keep track of what is going on where but the over aching theme of "old school everybody can access a public directory" is over.
I'm having the same issue and it's frustrating as hell! The app won't even show the skin files I've moved into the skins folder! Same with the presets. How can I fix this? Is there even a fix?
Just noticed my phone is on Android 11. Maybe it updated overnight without me realizing.
Caustic does not work properly at all for Android 11 phones. It's built for older model version phones. Please update the app for newer model phones. UPDATE: If you are having trouble loading sample packs and files in caustic with a new phone, simply take that file and move it to the samples folder in caustic. This helps load drum kits in the beatbox machine, and make a copy of the same folderor what ever folder you have samples in and move it and paste it in the pcm synth folder.
Whiteboi Beats
Caustic does not work properly at all for Android 11 phones. It's built for older model version phones. Please update the app for newer model phones. UPDATE: If you are having trouble loading sample packs and files in caustic with a new phone, simply take that file and move it to the samples folder in caustic. This helps load drum kits in the beatbox machine, and make a copy of the same folderor what ever folder you have samples in and move it and paste it in the pcm synth folder.
Whiteboi Beats
this is all fine until you realise there are phones that support android 11 with only 32 gbs of internal storage so even this solution is useless,
i personally have over 20 gbs of samples on my SD, all of them are useless with this update
LR
Lol, I tried to reinstall caustic, downgrade to 3.1, restart my phone and the app but the back folder is still gone.
Youtube
https://www.youtube.com/channel/UCq5ojFDwsSnEE0sMt0Gw8gA
Well there are to ways to get it fixed:
either by using the Storage Access Framework for example (which is a massive pain),
or by moving all Caustic storage into the app's private isolated storage "/sdcard/Android/data/com.singlecellsoftware.caustic/files/....".
Other than that... no, there is no fix.
> the Storage Access Framework for example (which is a massive pain),
Yes, this has wasted a nice little portion of my life.
Note that this folder seems to actually be vaguely accessible: e.g. Total Commander pops up a dialog to give it a permission to read and write subdirectories in the folder.
This may be the simplest way to go for Caustic: I know that some apps with the oldschool approach to files did this, e.g. specifically OpenTTD—and I seem to be able to read and write OpenTTD files with Totalcmd. Alas no such capability in the open-source Ghost Commander, but Totalcmd is freeware, doesn't seem to have any user-hostile misfeatures, and is generally very nice to use (the desktop version has been around since 1993). Dunno about other file manager apps.
Of course, there's no telling whether Google decide to take away this ability too, in the next versions (they probably will, judging by the trend so far).
P.S. However, presumably with such change Caustic Guide, Caustic Mastering, and apps supplying presets, will all stop working—if they currently read or add files in Caustic's song, patches and samples directories. That is, unless they take Totalcmd's approach and ask for permission to access Caustic's new data directory.