I'm torn between making Aetherial a general-purpose mp3/aac/vorbis/flacc/opus streaming radio client and making it a very specialised iOS client for listen.moe incorporating their websocket metadata API.. what to do, what to do?
I'm torn between making Aetherial a general-purpose mp3/aac/vorbis/flacc/opus streaming radio client and making it a very specialised iOS client for listen.moe incorporating their websocket metadata API.. what to do, what to do?
Just a small #AetherialApp update - no I didn't ditch or abandon the project, just did enough research to warrant.. well.. researching how to store all my findings properly so I could actually make use of them.
(That's what lead to me finding Obsidian and through it PARA and through that read the BASB book)
I'm still very much into this project and want to see it through, just had to take a few steps back to sort shit out
~:Project Aetherial Update:~
After a week of punching AVAudio and AudioToolbox I am able to play any of the standard CoreAudio formats as well as OGG/Vorbis without having to resort to VLCKit.
Bonus feat: I can chop up and save an Internet Radio stream into song-scoped audio files if I want (with metadata and all) - would that be a feature people are interested in?
While I don't plan to open-source the whole app I will try to
make the player component for Aetherial available as an open-source Swift Package since I didn't find anything working or maintained on GitHub or DuckDuckGo.
No I did not just release some swift bindings for libogg, libvorbis and libopus on my github because the only existing versions I could find were unmaintained and written in a weird way.
I'd never ever do such a thing.
Really.
#healsCodes #swift #audioprocessing #ogg #vorbis #opus #AetherialApp
Project Aetherial update:
I can handle ICY and OGG in-stream song metadata now
(playback already works for anything libvlc can handle on iOS)