avatarbr wrote: Thu Jan 30, 2025 11:43 pm
- Spoiler: show
PlayfulGuy wrote: Thu Jan 30, 2025 10:37 pm
I downloaded this tease and had a look, and unfortunately, this is a result of differences between EOS and GuideMe, and how the downloader converts the tease. Fixing it requires both significant reworking of the downloader,
and changes in GuideMe.
Since no one is currently maintaining GuideMe, and I have my hands full with the downloader and other projects, this is not likely to get fixed anytime soon. So, you're basically left with playing it online.
Over time I will do what I can on the downloader side, but it's getting to the point where we desperately need someone to pick up the maintenance of GuideMe. As much as I'd like to do that, I just don't have the knowledge and time.
If/when I get the downloader fixed up to where I'd like it to be, then maybe I'll have the time and energy to learn how to update GuideMe, but don't hold your breath.
Wish I had better news for you....
PG
No problem.
Thank you for the downloader anyway. I usually download a tease to change the pictures (in this case, I didn't liked the AI generated).
EDIT: just noticed than GuideME is not cutting at 4 or 5 seconds. Is cutting the last second (or 2), because even audios with 2 seconds are cut. I will see if I find a tool to add silence into the end of the files.
Adding silence to the end of the sound files won't help.
What happens is the timed dialog in the page often advances before the sound finishes playing, and Guidme stops the sound and moves on. You would need to go through the downloaded tease and increase the length of the delays on the timed "say" actions wherever the sound gets cut off prematurely. It would be a lot of work, but doable. Maybe do something like a global search and replace of any 2 second delays with 4 seconds or something?
Here's a couple examples from page1:
Code: Select all
{ action: 'audio', file: 'elevenlabs*.mp3', loops: '0', background: false, bpm: '' },
{ action: 'say', text: "<p><span style=\"color: #ce93d8\">Edging Spaces will have a countdown. You must keep stroking until "zero." </span></p>", mode: 'pause' },
This starts an audio clip, and the uses a say action that pauses. If you click to continue before the audio finishes it will get cut off.
A bit later in the same page there's
Code: Select all
{ action: 'audio', file: 'elevenlabs*.mp3', loops: '0', background: false, bpm: '' },
{ action: 'say', text: "<p><span style=\"color: #009688\">Spinning....</span></p><p>lets see how tough the beginning of our challenge will be. </p>", mode: 'timed', style: 'hidden', duration: '4' },
This starts an audio playing, and follows it with a timed say of 4 seconds. If the audio is more than 4 seconds long it will get cut off when the timed say action advances. If the audio is exactly 4 seconds long variances in Guideme's timing might still cause it to cut off early sometimes.
In other places (like the edging segments on page2) a metronome sound is started and then a series of timed say actions follows. Because of the way the downloader converts the tease, Guideme is reloading the page to advance to the next action. In doing so it stops the metronome sound, then starts it again every time the text updates. EOS doesn't do that and the metronome sound plays continuously. The current version of GuideMe doesn't allow a sound to play continuously. It was planned for a future release, but the person working on that has disappeared.
Those sequences will take you a lot more work to fix up. I would modify any of the say actions that have a one second delay to be mode 'instant' instead of timed, and then increase the time on the following say a bit. This would eliminate some of the stops and starts.
Hope that helps.
PG