grafika | An image processing library for PHP | Computer Vision library

question2 needs to be the result of a call to querySelectorAll, not just querySelector. It will then be a list of all the checked elements (querySelector only returns the first matched element, no matter how many match the selector.

You would need to loop the list and see what it contains. You need to verify that only two boxes were checked, and that they were the correct ones.

Also in your code, the question4 variable isn't defined, and input[value="question2"]:checked will never match anything - there's no checkbox with that value, and looking for the value makes no sense anyway. Also your question2 checkboxes randomly had "question4" as their name. I've corrected those issues and a couple of other minor things.

Something like this will work better:

First, i have added classes where you have used id's, because id's can't be duplicated, and i have added one small change to your function call, adding current button element as argument.

So, your HTML should look like this now:

It's very likely your timestamps aren't in the same timebase. The media recording system generally wants timestamps in the uptimeMillis timebase, but many camera devices produce data in the elapsedRealtime timebase. One counts time when the device is in deep sleep, and the other doesn't; the longer it's been since you rebooted your device, the bigger the discrepancy becomes.

It wouldn't matter until you add in the audio, since MediaRecorder's internal audio timestamps will be in uptimeMillis, while the camera frame timestamps will come in as elapsedRealtime. A discrepancy of more than a few fractions of a second would probably be noticeable as a bad A/V sync; a few minutes or more will just mess everything up.

When the camera talks to the media recording stack directly, it adjusts timestamps automatically; since you've placed the GPU in the middle, that doesn't happen (since the camera doesn't know that's where your frames are going eventually).

You can check if the camera is using elapsedRealtime as the timebase via SENSOR_INFO_TIMESTAMP_SOURCE. But in any case, you have a few choices:

1. If the camera uses TIMESTAMP_SOURCE_REALTIME, measure the difference between the two timestamp at the start of recording, and adjust the timestamps you feed into setPresentationTime accordingly (delta = elapsedRealtime - uptimeMillis; timestamp = timestamp - delta;)
2. Just use uptimeMillis() * 1000000 as the time for setPresentationTime. This may cause too much A/V skew, but it's easy to try.

If you need it to be seamless, you need to investigate MediaRecorder's own time limit options, or possibly have to build things from the lower-level API objects of MediaCodec and MediaMuxer.

Specifically, look at setNextOutputFile and setMaxOutputDuration. That should allow you to automatically transition between files, with a specific length for each snippet. That will hopefully be seamless.

If not, some combination of a MediaCodec and one or more MediaMuxers should let you build this, but that's a lot of stuff to wire together correctly.

Change:

replace your HTML with this

Replace