@MakeEchoes profile picture
Make Echoes @MakeEchoes

You make content, we Make Echoes. A social media content engine for Twitch streamers. @KadeDworkin behind these tweets and every line of code.

Joined July 2020
  • Tweets 1,276
  • Following 831
  • Followers 606
84 Photos and videos
Pinned Tweet
Make Echoes@MakeEchoes
5 Mar 2023
I sent out a notice to all customers that Echoes was closing Dec 31, 2022 and didn't yet announce it here. Now that we're past the 60 day holding on those final clips, everything was shut down earlier today. Thankful to every creator who trusted my crazy tool with their content.
1
1
12
1,589
I sent out a notice to all customers that Echoes was closing Dec 31, 2022 and didn't yet announce it here. Now that we're past the 60 day holding on those final clips, everything was shut down earlier today. Thankful to every creator who trusted my crazy tool with their content.
1
1
12
1,589
Some final stats before I mothball this account: 188 Twitch Streamers 12,046 Streams 53,242 Hours Observed 30,824 Primary Stream Clips 2,494 Multi-Stream Clips 3,315 YouTube Uploads I won't say I will never come back to this idea but I wouldn't hold your breath on it. Cheers.
3
7
276
If you're looking for a bit more context, head on over to makeechoes.com/ to read about it.
1
3
194
Make Echoes retweeted
David | PoppaElite@PoppaElite
8 Oct 2022
It's Drinks & Duty and we're firing on ALL cylinders, right @KhronikEnt? @SpecterEsports_ LIVE: twitch.tv/PoppaElite | Captured by @MakeEchoes
0:49
3
7
Make Echoes retweeted
Fellybishh
@FellyBishh
31 Aug 2022
Ive been spending my time in esports utilizing my anthropology skills to consult on improving team culture accessibility team/program communication/inclusion. I decided to make the leap to put myself out there to announce Ill be offering a wide range of services and materials.
4
8
Finishing up the to-dos for the day job a little earlier than expected. Very tempted to build something today that isn’t core architecture but is adjacent to it.
1
Totally didn't get out of the chair after the last tweet. Found a fractional timing error that was annoying me. We're talking less than 0.2 seconds but on clips that matters. Forcing the system to wait by 1.8 seconds solves the problem.
1
1
Bummed I have to make the system wait. Result is a deviance measured in a single /- frame. Average full processing time is still less than 4 seconds though so it remains an improvement off of the prior system.
The updates required in order to make real-time clips work with the new RTMP pass through mode have been deployed and fully tested. Want to test it one more time tomorrow when I'm not exhausted to make absolutely certain things are where they should be.
1
Trying to get the fix for the RTMP clip generation deployed in the next 90 minutes. Initial testing last night showed real potential for solving not only the problem experienced yesterday but also to make things a lot easier for re-timing clips so you get exactly what you want.
1
Interesting first set of tests with @Clintus and his 11.5 hour stream today. Definitely a couple of bugs to work out on the clip side but the stream quality was exactly as it always has been with near-0 additional latency which is good news.
1
2
Spent the last 3 hours finding the solution to the clip side of the equation. Don't have the energy/focus to code it all up now but it'll happen before too long. The system will be much more resilient after I deploy this though and that makes me happy.
2
And when I'm talking that this is an entire order of magnitude faster than the fastest pieces I could build on the Twitch VOD system, I'm not kidding. Check out these processing times... Almost all under 2 seconds to render out an mp4 and push to S3.
2
More progress on the new infrastructure. I still have to do another round of testing for Stream Deck inputs and make sure that's all good and then three more minor details to nail down. Suspect I'll ask a couple streamers to use it Thursday/Friday.
2
Finally breaking for dinner. That has taken a lot longer than expected. That’s mainly because of the crazy amount of rules I’ve built into checking for things like user permissions to request clips and clip collision events. Likely will jettison a few to get things running.
Another 3 hours in the chair and now clips are being generated from local files and pushed to S3. All that's left is connecting the dots between the way Echoes handles clip requests from chat and Stream Decks to check for the new way first, then default to the old. Close...
1
3.5 hours in to today's session and there's positive motion but the thing doesn't yet do the thing. Spent the majority of the time writing new supporting functions from scratch instead of trying to port over the older ones. That said, they're in place, I'm breaking for lunch.
Final mini session went as well as all the others today: ridiculously productive. Bunch of little creature comforts in place now. Mounted an additional Volume on the primary application server while as that'll be where I store streams in real-time.
1
Once I see that this all works, I'll create another server role specifically for these stream passthrough servers. Then I'll start cloning them in multiple regions. Thought being to give you options to use the geographically closest server. Start with 2, grow as user base does.
End of stream activity now performs exactly as expected. All VOD segments in a single folder on S3 within 3% of total stream run time. This is gonna be huge for post-stream re-timing of clips where you can extend a clip forward and backwards.
1
2
This was supposed to be the end of the day’s work, but @NyyKage’s stream set has me, @KadeDworkin, a bit amped up. Gonna grab some dinner and then likely do some of the customer facing touches. Leaves the big lift for tomorrow at really one thing: real-time clip generation.
Load more