ermau / aura Goto Github PK

Toggleable replay gain support for an element playlist

• Create new metadata elements for element playlists
• Calculate gain data
  • Re-calculate on playlist modifications
• Playback support

There's only one element in the actual database, but the list show a duplicated element

Intensity control at the encounter-state level.

If a user explicitly cancels the service enable prompt, that choice should be remembered.

• Remember choice
• Ensure game space editor can enable

Freesound allows you to download previews without a user sign-in, the provider should switch to opting into direct downloads when authed, but work without.

Look into integrating Spotify. I think the API only allows you to control the playback through another client, so that could complicate the architecture, but would probably be worth it.

• Exporting
  • Exporting individual elements (element/encounter)
  • Exporting campaign
  • Optionally including files
• Importing
  • Packaged file as zip with content.json and any source files.
  • Prompt user to download anything missing.

Creating a campaign does not update the campaign switch list, nor switch to it automatically as it should.

While the audio service doesn't especially matter, things like beginning a lighting stream should not be always-on and should start and stop with playback or similar. It might make sense to start/stop on demand when playing normally and keep it alive while in the play screen.

Adding a player list to campaigns enables the ability to attach attributes to certain players, like D&D Beyond character sheets.

Layers provide an optional building block for bundling together multiple elements to create reusable pieces of an atmosphere.

For example, to add a storm to your encounter, you might add a lightning element, a rain element and a wind element. Rather than add these three elements to each encounter you want to create a storm in, place them in a storm layer.

Right now the import flow is centered around content providers, but local file importing needs to get added.

One of the biggest questions sits around where those files are stored, especially since your library will be synchronized across machines. In the past I'd looked at trying to store these on OneDrive and the like, but I think I'm going to start simpler.

The current plan is that imported files will not be moved and instead users will be prompted to locate missing files on background check / active attempt to play.

Rather than ship with an empty library, a basic sound set should be included (or maybe prompted to download) to use as an example. The initial set of layers should include:

• Tavern
• Outside market
• Calm woods
• Storm
• Dungeon

The new timing setup should support a main trigger point, which will either be:

• Randomized min/max time
• SampleEventPoint

The general time configuration should allow you to select between these options and for SampleEventPoint, allow you to select a source of the events (Audio, Video). Then, all component timings will be relative to this main trigger point in one of these configurations:

• Synchronized
• Offset (can be negative or positive)
  • May want to consider making this random rangeable.