2 New Plugin/Object Ideas

New releases and general discussions.

Post » Thu May 26, 2011 7:05 pm

1. New video player - Everything that the old one does, but without the timeline bar.

2. Video Recorder Object - Allows you to record everything that happens within a specified layout or several specified layouts, creating an .avi file that is then sent to a specified folder based on 'App Path'.

Here are several action ideas:

*Record For & Temp Save - allows you to record for a specified amount of time. The video file then temporarily saves to a temp folder and then deletes itself after it's been replayed in the game, or can be deleted based on an event.

*Record For & Save - allows you to record for a specified amount of time. The video file then saves itself to an App Path specified folder.



*Start Recording & Temp Save - allows you to begin recording any time after an event such as a collision, a button press, or a specified amount of time, etc. The file then temporarily saves to a temp folder and then deletes itself after it's been replayed in the game, or can be deleted based on an event.

*Start Recording & Save - allows you to begin recording any time after an event such as a collision, a button press, or a specified amount of time, etc. The file then saves itself to an App Path specified folder.

AND...

*Stop - allows you to stop recording any time after an event such as a collision, a button press, or a specified amount of time, etc.



... the default would always temporarily save the file to a temp folder.

... we should also be able to set the object to 'Global', and also make certain sprites and graphic objects invisible to the recorder by clicking on them in an editor (similar to how the Bones animator allows you to choose limbs/points by clicking on them), so that those sprites and graphic objects won't show up in the final recording file.

Why does Start and Stop have 'after' commands, and what do they mean?

The 'after' command for 'Start' means that the object will begin recording video whatever milliseconds you choose after an event occurs.

The 'after' command for 'Stop' means that the object will stop recording video whatever milliseconds you choose after an event occurs


Why is having the 'after' command important?

2 reasons: First, the user may not want to have a sudden stop of recording right when the event occurs because in some instances it can look jolting and therefore unprofessional, so having a bit of a buffer between the event and the stop will eliminate that problem.

Secondly, for programmers who may make a sports or military combat games, a buffer of time between an event and when the recording stops is imperative for replays, because you'll want to be able to show graphic wipes, transitions, stat overlays, etc. and much of that will come right after a collision event or scoring event or some other type of event occurs. So by allowing the programmer to set the amount of time to keep recording after an event has happened and then stop after a specified time, it allows the programmer to put graphics on top of the video and allows for a smooth transition to the next layout.

This can also be said for the 'Start' action. There are times when you'll want to begin recording the video after an event, but only after a certain amount of time has passed after that event occurs. The reason is because you're probably trying to zero in something very specific, so having the 'after' command will allow it.

So then, how would I start or stop recording immediately when an event happens?

By setting the Millisecond command to '0' like this:

B
12
S
4
G
3
Posts: 426
Reputation: 2,458

Return to Construct Classic Discussion

Who is online

Users browsing this forum: No registered users and 1 guest