The timing of my videos differentiates between the small screen and "presentation mode." Also, when I open the program and play the video for the first time, the timing is drastically different. It is not a matter of what waiting blocks I put where, for even if my timing is incorrect, it still changes every time I play the video. I don't know how to make a good video if in every instance I check my timing it is a little different. This occurs on the Scratch program itself when I am making videos, not only on the internet. Why does this happen? Is there anything that I can do to fix this?
Offline
I used to run into this problem a lot
But don't worry, there is something you can do to fix it
You could try making some broadcasts - they make timing a lot smoother, no matter which player you run it in (small screen, presentation mode, online...) It's basically like making one sprite tell all or some of the others to do something - here is a nice tutorial by pippintoon that explains more clearly.
Hope this helps
Offline
When you first open the program, if your project is large, it will run slow, it happens to me. I always run my large projects through, and then the second time they are much faster. I believe the speed in presentation mode, is similar to the speed online in the Java player, if the project isn't over a couple megabytes
Offline
The broadcast idea really helped. I had to reorganize my entire video, but it made the timing a lot better. Scratch continues to be an imperfect time keeper, miscalculating sometimes by a couple tenths of a second, but that will be a problem forever. I thank you, Wolfie1996, for helping me to mitigate the imperfection of my videos.
Offline
What a lot of people do is make sure the project runs properly in presentation mode and try not to play it in normal mode, because it has so much lag. Plus, the timing in presentation mode is the same as the online player, which is why a lot of people try to avoid is a good solution.
It's really complicated, unfortunately. But using the broadcasting method Wolfie1996 described is also a good way around it.
Offline