Roadmap

[nzoschke]

Some rough plans...

Port to Kotlin

Kotlin is a more modern and productive language that iterops with Java and the JVM. Most of the Android experiments I'm doing around this library and beat-link are in Kotlin.

2.0 message format

Lots of learnings in the 1.0 message format. Some things to consider:

• Adopt standard field names for music files and metadata such as https://github.com/nzoschke/jukelab/blob/main/src/lib/types/music.ts
• Simplify source to a flat src and use everywhere to correlate events with tracks
• Add waveform and any other missing beat-link primitives

Integrate with OBS

When using with OBS, listen to its key events like recording start / stop and add them to the message stream.

High resolution artwork

Needs more research but CDJ and beat-links concept of high resolution is not good enough for a 4k projector.

One idea is an offline utility that extract artwork from embedded in the MP3 / FLAC files and writes them to the USB key in a way that beat-link can fetch it.

Publish messages to the cloud

In addition to saving to the local disk, publishing events to an external service would unlock new possibilities like auto published playlists.