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.
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.
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.
@ZackMamba__ Yeah that gets into DaVinci stuff I couldn’t help ya with. Best way to test would be to create a new project, set the frame rate at 30 and see if it still happens when importing that clip.
@ZackMamba__ Audio and Video are treated as two separate tracks. Audio is likely matched at either 44.1 Hz or 48 Hz and that’s why it’s fine in the editor. Likely that the clip is at 30FPS, project at 60. Since you’ve got half as many video frames it would run appear at 2x.
@EduardoP_Dante Things should be resolved at this point. Tested with several newly created accounts and each proceeded through the initial account setup without issue. If you run into problems, let me know.
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.
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.
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.
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.
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.
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.
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.
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.
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.