Added console.logs to help debug the recorder, to get feedback from our keyboard shortcut presses, to know which state the recorder is in.
Behavior Changes:
autoPlay: true by default. During development, autoplay allows one less key to hit on every trial. For sharing, autoplay allows viewers not to have to press play if the developer forgot to set it.
localStorage: true by default. During development, I'd like to record and be able to replay on subsequent trials without further work (i.e., saving a file + coding it into to the replayer).
Also clear the recording in memory on c key.
spectatorMode: false by default. For development, this looked weird with autoPlay because the camera would suddenly jump to the spectator camera right after finishing recording. I think the first-person view is convenient for development because you don't have to control the camera to get a good angle on the test trial (i.e., avatar walks out of view of camera or ducks). Whereas the first-person view is hands-free and gives you a front row seat of the recording the whole way through. Both modes are very, very useful, but first-person by default would be my preferred.
Style Changes:
s/play/replay/g - replay emphasizes replaying from a previous recording, rather than play as in play/pause.
s/autoStart/autoRecord/g
Bug Fixes:
Fixed camera not being set by listen to camera-set-active.
Do not autoRecord by default (especially if it was off on the avatar-recorder). This caused an issue where recording start right on page load despite autoStart being off and me having not hit the space bar.
this.currentCameraEl was undefined in motion-capture-replayer. Set this.currentCameraEl in the init step.
Fix Webpack config, it wasn't updating the bundle for me.
And more unit tests.
Features:
Behavior Changes:
autoPlay: true
by default. During development, autoplay allows one less key to hit on every trial. For sharing, autoplay allows viewers not to have to press play if the developer forgot to set it.localStorage: true
by default. During development, I'd like to record and be able to replay on subsequent trials without further work (i.e., saving a file + coding it into to the replayer).c
key.spectatorMode: false
by default. For development, this looked weird withautoPlay
because the camera would suddenly jump to the spectator camera right after finishing recording. I think the first-person view is convenient for development because you don't have to control the camera to get a good angle on the test trial (i.e., avatar walks out of view of camera or ducks). Whereas the first-person view is hands-free and gives you a front row seat of the recording the whole way through. Both modes are very, very useful, but first-person by default would be my preferred.Style Changes:
s/play/replay/g
-replay
emphasizes replaying from a previous recording, rather thanplay
as in play/pause.s/autoStart/autoRecord/g
Bug Fixes:
camera-set-active
.autoRecord
by default (especially if it was off on theavatar-recorder
). This caused an issue where recording start right on page load despiteautoStart
being off and me having not hit the space bar.this.currentCameraEl
was undefined inmotion-capture-replayer
. Setthis.currentCameraEl
in theinit
step.