Feature requests

Instead of starting off with a wrapping media intro clip in a YT video, allow for an !echofirst call to be made in the twitch chat, Stream Deck or in the web interface to set the previously collected clip to appear before the YT intro clip. Current YT best practices are to amp up emotion in the first 3-8 seconds and going with an exciting clip or one that is specifically a context setting clip could help with that. Put the branded media clip in the 2nd slot when triggered.

Being able to in real time denote when a compilation video should end and a new one would begin. Allow for multiple recap videos to be generated from a single stream.

In the YouTube description, include timestamps that take advantage of YouTube's native chapters that include the clips title or corresponding timestamp. On the following line, include a link to the exact second in the VOD when that clip begins.

Since Stream Deck users are experiencing the clippable moment 2-6 seconds before it is being shown on stream to viewers, provide a separate stream offset value for clips requested through the physical devices API.

Similar to the use of Stream Decks as an input interface, create an ability to request clips from a dedicated page and do simple management on them (update title, deletion).

Create an integration with Instagram so Echo Flares can be posted there as native media assets.

Using a clip from a prior stream, use a different set of wrapping media for an Echo Flare that has a lead in clip specifically intended to state "Previously on...", then the clip, then a separate Call-to-Action clip stating something to the effect of "What's going to happen on today's stream? Come find out."

For DJ sessions, similar to posting full VOD to YouTube prior to stream post-processing happening where copyrighted tracks are muted, render out an mp3 and post on behalf of the user to their Soundcloud/Mixcloud accounts.

With the deprecation of API v5, this is a requirement to keep things functional in the medium term. For more information see https://blog.twitch.tv/en/2021/07/15/legacy-twitch-api-v5-shutdown-details-and-timeline/?utm_referrer=https://discuss.dev.twitch.tv/

Currently the Echo Flare system allows for content to be submitted as 280 consecutive characters without line break. Updating this field to something that allows them would be preferential.

The ability to create tags so clips can be organized and quickly searched for and found.

In the event that you have a clip and don't want it in your recap video be able to issue a command to exclude it from that stream's rendered compilation.

While stream is not live or attempting to send an Echo Flare to Twitter from a prior stream, system fails. The issue is caused by an inability to collect clip from S3 using previous grab functions.

If clip + wrapping media is less than 100 seconds in duration, check to see if a specific ad unit can be included for a sponsor or affiliate for the streamer's partnering businesses. Total duration of clip should not be longer than 139 seconds. Make ad selection possible in the Echo Flare creation.