I'm trying to make a Scratch animation of a YouTube video, like this one here.

In those videos, there is no wait () secs block - it simply uses a repeat loop.

How many frames per second does it run at? 30?

Yes, it runs at 30 FPS without turbo mode.
Either that, or it just uses unicorns.

BookOwl wrote:

Yes, it runs at 30 FPS without turbo mode.
Either that, or it just uses unicorns.

Exactly. Luckily avconv supports the –unicorn flag

Thanks though.

Scratch 3.0 might use 60… I'm not sure how that'll affect existing projects.

CodeLegend wrote:

Scratch 3.0 might use 60… I'm not sure how that'll affect existing projects.

Old projects use 30 FPS, like 1.4 projects say “bytes” instead of “assets”.

Tymewalk wrote:

CodeLegend wrote:

Scratch 3.0 might use 60… I'm not sure how that'll affect existing projects.

Old projects use 30 FPS, like 1.4 projects say “bytes” instead of “assets”.

That sentence is very confusing to me. Mind clarifying?
BTW, Scratch 1.4 runs at 40 fps, not that that is particularly relevant nowadays.

MathWizz wrote:

Tymewalk wrote:

Old projects use 30 FPS, like 1.4 projects say “bytes” instead of “assets”.

That sentence is very confusing to me. Mind clarifying?

On the loading screen of newer projects, it will say “X of X assets loaded”, whereas older projects will say “X of X bytes loaded” (or something to that effect).

Scratch 2.0 uses 30fps, even with turbo mode/run without screen refresh (which just makes the project yield less).

MathWizz wrote:

BTW, Scratch 1.4 runs at 40 fps, not that that is particularly relevant nowadays.

Today I learned. That's pretty interesting!

Does anyone know the exact details of how the framerate is throttled?

For instance:

forever
change [var v] by (1) //runs at an unlimited fps
end

//but

forever
turn cw (15) degrees //runs at 30 fps
end

Does each block just have a binary tag telling if it requires a screen update, and then at the end of each C-block it updates if one was requested (or it's been >1/30 seconds)?

EDIT: So I'm basically asking, does it work like this?

when interpreter reaches the end of a C-block or script::events hat
if <<(time since last refresh::control) > ((1) / (30))> or <<a refresh was requested::control> and <not <turbo mode::control>>>> then
refresh the screen::control
end

I like scratchblocks

PullJosh wrote:

MathWizz wrote:

Tymewalk wrote:

Old projects use 30 FPS, like 1.4 projects say “bytes” instead of “assets”.

That sentence is very confusing to me. Mind clarifying?

On the loading screen of newer projects, it will say “X of X assets loaded”, whereas older projects will say “X of X bytes loaded” (or something to that effect).

But what does that have to do with the framerate of the project? All projects loaded in the flash player run at the same FPS.

CodeLegend wrote:

Does each block just have a binary tag telling if it requires a screen update, and then at the end of each C-block it updates if one was requested (or it's been >1/30 seconds)?

That's basically it. If nothing in a loop causes a screen change, then it runs until the next frame.

MathWizz wrote:

PullJosh wrote:

MathWizz wrote:

Tymewalk wrote:

Old projects use 30 FPS, like 1.4 projects say “bytes” instead of “assets”.

That sentence is very confusing to me. Mind clarifying?

On the loading screen of newer projects, it will say “X of X assets loaded”, whereas older projects will say “X of X bytes loaded” (or something to that effect).

But what does that have to do with the framerate of the project? All projects loaded in the flash player run at the same FPS.

Same.

1.x projects load in bytes (it's loading the .sb file).
2.0 projects load in assets (it loads the project.json, then all the other assets).
That's an indicator for which version is in use, but it has nothing to do with this? Unless you meant to say 40, like MathWizz did afterwards.

CodeLegend wrote:

MathWizz wrote:

PullJosh wrote:

MathWizz wrote:

Tymewalk wrote:

Old projects use 30 FPS, like 1.4 projects say “bytes” instead of “assets”.

That sentence is very confusing to me. Mind clarifying?

On the loading screen of newer projects, it will say “X of X assets loaded”, whereas older projects will say “X of X bytes loaded” (or something to that effect).

But what does that have to do with the framerate of the project? All projects loaded in the flash player run at the same FPS.

Same.

1.x projects load in bytes (it's loading the .sb file).
2.0 projects load in assets (it loads the project.json, then all the other assets).
That's an indicator for which version is in use, but it has nothing to do with this? Unless you meant to say 40, like MathWizz did afterwards.

they're saying that 1.4 and 2.0 projects are already loaded differently, so there's no reason that 3.0 and 2.0 projects can't run at different framerates.

Personally, I don't think just automatically running older projects at the slower framerate will be good for compatibility (what happens when you remix a 2.0 project that's built for 30 fps?) so I hope they'll take a good look at how to handle this issue

NickyNouse wrote:

CodeLegend wrote:

MathWizz wrote:

PullJosh wrote:

MathWizz wrote:

Tymewalk wrote:

Old projects use 30 FPS, like 1.4 projects say “bytes” instead of “assets”.

That sentence is very confusing to me. Mind clarifying?

On the loading screen of newer projects, it will say “X of X assets loaded”, whereas older projects will say “X of X bytes loaded” (or something to that effect).

But what does that have to do with the framerate of the project? All projects loaded in the flash player run at the same FPS.

Same.

1.x projects load in bytes (it's loading the .sb file).
2.0 projects load in assets (it loads the project.json, then all the other assets).
That's an indicator for which version is in use, but it has nothing to do with this? Unless you meant to say 40, like MathWizz did afterwards.

they're saying that 1.4 and 2.0 projects are already loaded differently, so there's no reason that 3.0 and 2.0 projects can't run at different framerates.

Personally, I don't think just automatically running older projects at the slower framerate will be good for compatibility (what happens when you remix a 2.0 project that's built for 30 fps?) so I hope they'll take a good look at how to handle this issue

Maybe it warns you and defaults to 30 FPS mode?

“The project you're remixing is built to run at 30 FPS. This usually doesn't cause problems, but just in case, we've set it to 30 FPS for you. You can change this in Settings -> FPS Rate -> 60 (high).”

CodeLegend wrote:

Does anyone know the exact details of how the framerate is throttled?

Yes…

I go through it in this post.

Essentially, your idea is correct *except* that it only allows the refresh once *all* currently running scripts reach a yield point (i.e. end of pass through a loop, or script ended, or reached a “wait” of some form) *and* if at least *one* of them executed a block which (potentially) made a change on-screen (e.g. motion, looks, pen, etc. – though it does sensibly take into account if the sprite is hidden, in which case looks blocks (and maybe motion blocks if pen up?) will have no effect…)

MathWizz wrote:

Tymewalk wrote:

CodeLegend wrote:

Scratch 3.0 might use 60… I'm not sure how that'll affect existing projects.

Old projects use 30 FPS, like 1.4 projects say “bytes” instead of “assets”.

That sentence is very confusing to me. Mind clarifying?
BTW, Scratch 1.4 runs at 40 fps, not that that is particularly relevant nowadays.

Sorry to bump this, but how do you test that? Also, is there any difference in framerate between modern squeak versions (like 5.0) and the version used by “classic” 1.4?

NoMod-Programming wrote:

[H]ow do you test that?

Pretty simple to set up a frame rate coutner in Scratch to test it: https://scratch.mit.edu/discuss/topic/18037/?page=1

Also, is there any difference in framerate between modern squeak versions (like 5.0) and the version used by “classic” 1.4?

The environment Scratch is programmed in has nothing to do with the framerate projects run at. The designers of Scratch 1.x just decided to use the arbitrary framerate of 40.

30 fps but if you're on turbo mode then 88800 fps (lol i don't know)

wiseguy2011 wrote:

30 fps but if you're on turbo mode then 88800 fps (lol i don't know)

dont necropost