After opening project, click on play timeline icon, play animation twice

[sanjuchopracool]

first time it plays animation very fast
second time it plays normally

Expected Behavior:
It should play only once (if loop not selected) with normal speed

Branch : wip (master not tested)

[rodlie]

The first run generates the playback cache.

[sanjuchopracool]

ohh, I did not look into the code. To a new user it feels like a bug.
May be we can generate cache without updating canvas in first run ( displaying some message or some user feedback )

[rodlie]

To me this is normal behavior and what most (related) programs does. But I'm open for suggestions/discussion.

A better way to visualize cache generation might be enough? Not sure about disabling the canvas during generation, if so it should be an option.

[sanjuchopracool]

I am also not good with UX ideas. Yes, a better way to visualize cache generation should be enough.

May be just keep this as a low priority issue. Later if others also request, change the priority.

[rodlie]

Sure, my current goal it to get the wip branch ready to merge this week(end). Need to fix various ui stuff and try to get the Windows port up-and-running.

[samytichadou]

Hi this behavior always bothered me with enve.
Coming from after effects, the cache generation is at best real time (composition framerate), but often slower

A better way to visualize cache generation could be enough, but maybe limits cache generation speed to real time if processing is faster (meaning framerate of the current scene) would be a more intuitive way of dealing with it ? (at least to me)
If it was realtime, perfect, user has seen its timeline, otherwise, cache is ready to play it again.

Cheers !

[rodlie]

We could do something about this, but it will require a bit of planning first.

• The simplest solution would be to just wait until enough frames has been buffered, then start the playback (once).
• Another solution would be to buffer frames in the background, giving the user instant playback (in theory)

[samytichadou]

I guess after effect does your first suggestion (not sure, a long time since i didn't use it) but i guess both solutions seems a better behavior to me.
Buffer frame in the background sounds perfect, especially for motion graphics, the slow caching would be visible only if scene is too heavy and buffering took to much time. That seems to be more understandable as a user to me.

Cache visualisation, as said, could also benefits from a new look to make it more understandable for new user !

[rodlie]

I will probably have time to do something about this after v0.9.2.

Cache visualisation, as said, could also benefits from a new look to make it more understandable for new user !

There will be several UI changes.

I'm currently prioritizing features/issues related to work with these first releases. The company I work for use Friction in-house and the priority is to get work done as fast as possible :) (svg animations)

[samytichadou]

I'm currently prioritizing features/issues related to work with these first releases. The company I work for use Friction in-house and the priority is to get work done as fast as possible :) (svg animations)

of course ! not knowing really what is under the hood, the only input i can give is about ux/ui, but having it works rock solid for its primary purpose (svg anim) sound way more important than cache UI :)