"New title" - Milovana's first Eos Trailer

[Roblsforbobls]

I was kind of blown away by this Eos tease (what do you call an eos non-tease?) by Longplay1. Although the rating (as of the time of writing) is 3.3/5, I was impressed by the level of hype that Longplay1 was able to achieve through the use of gifs and nocopywrite music. A considerable number of images and timers were used in the making of New title, but I think the work payed off. I'm always happy to see more creators experimenting with using gifs in their teases, and it looks like we can add trailer-style videos to the list of ways they can be incorporated!

The music was a great addition, but I felt like it could have been timed better to give the whole thing more impact. Specifically,

- it would have been cool to see the messages displayed when the music did those bass swells. Also,
- the track ended before the title of the upcoming tease was shown, and that killed the momentum you were building throughout. To fix that, I would start a stopwatch from when the music ends until when the title is displayed in order to find out how many seconds need to be shaved off of the "video". Then I would shorten the delay timers for the text images (which lasted on the screen for a bit longer than they needed to) so that the whole "video" lasts that many seconds fewer in total.

It would be pretty difficult to make it have both of those things, but if it is possible I think it would be that much better!
Another thing I would suggest when releasing non-tease teases would be to make clear what your creation is in the description. I think a lot of the negative ratings your tease is getting are from people who click on your creation, expecting to masturbate or something, but only see a trailer for a tease. If people know what they are going to see when they click on the link, they will be kinder with the ratings (which in-turn will lead to more views because the rating of the tease is higher).

Anyways, those were my thoughts on the "New title" tease by Longplay1. Thanks for making this tease and pushing our ideas of what can be made in Eos! I'm sure your unique tease will serve as inspiration for current and future creators!

[Bandit224]

I agree. It was entertaining to watch what felt like an action movie trailer for the milovana's site content in general.

[Ghingis]

That tease did not use any gifs... it played images with 0.04s timings (~25 FPS) that were downloaded (by the preloader) while you were watching the whole thing.
Also the music was on point for me (it stopped right before the comming soon page), because I have a fast internet (1 Gigabit/s).
Did you ever noticed that the tease stopped on a "sexy" image for a sec or two?
If it did, that were because of your browser still downloaded the images for the next page.

Let the tease finish once and refresh the page and watch it that way.
(Your browser won't have to download the images for the second time it will be cached already).

[Roblsforbobls]

That tease did not use any gifs... it played images with 0.04s timings (~25 FPS) that were downloaded (by the preloader) while you were watching the whole thing.
Also the music was on point for me (it stopped right before the comming soon page), because I have a fast internet (1 Gigabit/s).
Did you ever noticed that the tease stopped on a "sexy" image for a sec or two?
If it did, that were because of your browser still downloaded the images for the next page.

Let the tease finish once and refresh the page and watch it that way.
(Your browser won't have to download the images for the second time it will be cached already).

I am aware of how the illusion of movement was created, using individual images and manually adding delay timers between them to control the speed of the movement. I only call it a "gif" for lack of a better term - they were probably gifs before getting split up into individual frames, and the frames are shown with a built in delay between each one is almost like manually building a gif file using eos. I will continue to call them gifs until someone comes up with a better name for them.

I watched the trailer to the end, then refreshed and watched it a second time, as you suggested, and the timing didn't change for me, which leads me to believe that we saw it with the same timing, and my original critique wasn't explained well enough. For me, the music ended at "...which is new...", which was followed by another gif, before the tease name was shown. Was that not the case for you?

Lastly, is there a way to make a tease that can load all the images at the beginning so that the kind of internet bottleneck you are describing is not an issue?

I agree. It was entertaining to watch what felt like an action movie trailer for the milovana's site content in general.

I'm glad it wasn't just me! I was a little saddened by the rating score this creation got, because it was actually pretty cool and required a decent amount of effort to put together

[computergeek]

/// Automatically hearing Carly Simon singing the Anticipation song in my head ///

- it would have been cool to see the messages displayed when the music did those bass swells. Also,
- the track ended before the title of the upcoming tease was shown, and that killed the momentum you were building throughout. To fix that, I would start a stopwatch from when the music ends until when the title is displayed in order to find out how many seconds need to be shaved off of the "video". Then I would shorten the delay timers for the text images (which lasted on the screen for a bit longer than they needed to) so that the whole "video" lasts that many seconds fewer in total.

Everything was pretty well timed on me end. Since it is a web based app, thinking this is one of those issues that will only comply if the end user is on similar clocked hardware as the author.

[Roblsforbobls]

Everything was pretty well timed on me end. Since it is a web based app, thinking this is one of those issues that will only comply if the end user is on similar clocked hardware as the author.

I'm not well-versed in this kind of thing. Are you saying the bottleneck might be how fast the GPU is? I am using a core i7 system (if that means anything). Or would it be a difference in internet speed? My internet download speed is about 100 Mbps.

[Bandit224]

Everything was pretty well timed on me end. Since it is a web based app, thinking this is one of those issues that will only comply if the end user is on similar clocked hardware as the author.

I'm not well-versed in this kind of thing. Are you saying the bottleneck might be how fast the GPU is? I am using a core i7 system (if that means anything). Or would it be a difference in internet speed? My internet download speed is about 100 Mbps.

You also have physical distance between you and the server you are connecting too. Although your setup is pretty good, it operates at a different speed than the author which will cause the web based app to not sync up exactly.

[FATALES]

It looks like progress. I know how much work it will take to create just that sample, so I gave it in 5 *
I thought gifs were already enabled but I know there are instructions on how to work around it - https://milovana.com/webteases/showtease.php?id=41623

[Roblsforbobls]

You also have physical distance between you and the server you are connecting too. Although your setup is pretty good, it operates at a different speed than the author which will cause the web based app to not sync up exactly.

That definitely makes sense. I imagine something like this can be really difficult (if not impossible) to make consistent across different devices. Coming up with a way to ensure that the experience doesn't change based on hardware specs (like perhaps pre-loading images in the beginning of the tease?) could easily be a necessary next step in innovation of this technique.

It looks like progress. I know how much work it will take to create just that sample, so I gave it in 5 *
I thought gifs were already enabled but I know there are instructions on how to work around it - https://milovana.com/webteases/showtease.php?id=41623

That is exactly how "New title" was made! Currently, Eos still only supports the .jpeg and .jpg image formats, so .gifs and .mp4 files can't be uploaded. It is genuinely gratifying to see other creators experiment with this technique, and making such inspiring work with it! My favorite thing about Eos and this platform is the drive we share to create something new for everyone to enjoy, and being innovative with the resources we have to make them. To me, that spirit is embodied by recreating casino games, re-imagining and re-mastering classics, and shoe-horning in unintended features like moving pictures. This is the type of thing I find most inspiring about this community

[fapnip]

I experimented with simulated GIFs in EOS but abandoned it mainly because it's basically impossible to get any reliable timing on a broad variety of browsers/devices without resorting to a painfully slow frame rate. To get something resembling consistency I used a dynamic timer function between frames to track and estimate what the actual delay should be. Static timers didn't work well for me. (But then neither did dynamic timers in the end.)

Internet speed is less an issue (images can be cached, you'll just need to wait before the animation can start) than is variability in local I/O, how much load the CPU is under at any given moment, etc.

Then there's the potential issue of increased load put on milovana.com if this kind of thing becomes popular...

That said, I applaud Longplay1 for the huge effort in making that trailer, and Roblsforbobls for his tech-demo. It's a real pain to assemble these animations in EOS. Looking forward to seeing how it's used in a completed tease.

P.S.:
To get this trailer a little more in-sync with the audio track, It should be possible to record the start time of the audio track in a global init variable (var start = Date.now()) then dynamically adjust the time the teaser text frames display by checking the current offset since the start of audio (var offset = Date.now() - start), and dynamically calculating the text frame's display time in ms to adjust for any drift. Problem is, on slow devices, that text tease may only show momentarily.

[Roblsforbobls]

I experimented with simulated GIFs in EOS but abandoned it mainly because it's basically impossible to get any reliable timing on a broad variety of browsers/devices without resorting to a painfully slow frame rate. To get something resembling consistency I used a dynamic timer function between frames to track and estimate what the actual delay should be. Static timers didn't work well for me. (But then neither did dynamic timers in the end.)

I've been experimenting with timing as well, and it's definitely SUPER hard to get any kind of consistency. I've found that the system takes 1 ms to store variables or run a simple function, etc. In order to have it store a variable and call a variable, there has to be at least a 1 ms timer in between those two actions for it to work properly. For example, I had the system store var start = Date.now() when an audio track was paused. Then in one eval I paused the audio and set a notification title with the variable "start." It took a long time to figure out that "start" was being stored properly, just not before the notification title was set. To fix this, I had to put those two actions in separate eval actions, separated by a 1 ms timer.

Then there's the potential issue of increased load put on milovana.com if this kind of thing becomes popular...

That sounds ominous...

P.S.:
To get this trailer a little more in-sync with the audio track, It should be possible to record the start time of the audio track in a global init variable (var start = Date.now()) then dynamically adjust the time the teaser text frames display by checking the current offset since the start of audio (var offset = Date.now() - start), and dynamically calculating the text frame's display time in ms to adjust for any drift. Problem is, on slow devices, that text tease may only show momentarily.

I'll definitely have to try this out! Another possibility is advancing the music backwards (maybe 1 second?) to account for half of the delay, so that the burden is not entirely placed on the delay timer for the text images. It might be a little jarring depending on the music chosen, but that is only for a moment