Is it possible to mute video stimuli in Finding Five?

I am working on a comprehension experiment where participants see video recorded sentences and choose their response to the sentence with a button press. I would like to keep track of whether the response they choose is on the left of right side of the screen. 
Right now, I have button location randomized automatically. I can of course undo that and instead create pseudo randomization in my stimulus list by hand. But before I go that route, I thought I'd ask if there is a way keep the randomization and obtain information about response choice locations in the output?
Thanks!

Is there a way to do this? I find that when an instruction follows a self-paced reading trials (where participants have been clicking the spacebar rapidly), it risks being skipped unintentionally. So for certain trials, I would like to require the a mouse click to advance to the next trial.

Has anyone experienced long video stimuli crashing? I have one video that keeps crashing at 5:42. It seems to be a feature of the file somehow, because the same thing happens in an experiment where the only trial is the video. I have tried setting a fixed duration and leaving duration unspecified, and it doesn't seem to make a difference. The video plays without issues outside of the experiment (i.e. when i play it from Resource files). I have another video of the same duration that plays just fine in the same experiment - both videos are .mp4. Any advice is appreciated!

Is there a way to disable the play/pause key on the keyboard for video stimuli. I'm trying to avoid that my participants pause the video.
I have auto-play enabled and there are no clickable buttons visible. But pressing the play/pause button on the keyboard still pauses the video.

I was running through my experiment and when I got to trial 76 (my trials are hard coded, not randomized) I got an error that "The file 205_frog_shove_monkey.mp3 is either missing or in an incorrect format. Please fix the problem and preview again."
I checked and saw that that file did indeed exist; but just for kicks, I decided to upload a new file (205_frog_shove_monkey_copy.mp3) and updated the audio stimuli for trials 76 to reflect the new filename in "content".
I ran the experiment again, but this time I got the error "The file 205_frog_shove_monkey_copy.mp3 is either missing or in an incorrect format. Please fix the problem and preview again."

So the "missing file" did not seem to be the problem.
Next, I went into Procedure and deleted trials 1-74 from the experimental block to see if I could get trial 76 to play at all.
I ran the experiment again, and trial 76 played perfectly, no error message.
So why would there be an error message when I started with trial 1 and went to 76, but not when I started from trial 75?
Next, I put back trials 1-74 so the block was complete again. Now I wondered, could this have something to do, not with the fact that there's something wrong with trial 76, but there is something buggy going on when this block reaches the 76th trial position in the block.
To test this, I deleted just trial 76 from the block, so now the trials would proceed from 1-75 and then 77. My hypothesis was that if there is something wrong with the 76th position, I would get an error message about trial 77's audio file. . . .and that's exactly what happened.
Any idea what's going on?

Is there any way of adding metadata columns to results?
For instance, I am using audio stimuli of sentences that are either "active" or "passive" syntactic voice. I tried to do this by coding "voice":"active" my active audio stimuli; and coding "voice":"passive" in my passive audio stimuli. Although this coding was accepted as grammatical in the stimuli section, none of this information shows up in the results.
I would also like to include other information about the stimuli as well -- is there any way of doing this? (I know that as long as trials are uniquely identified I could just join my results file with a separate metadata file in R, but this seems like an extra step and an extra opportunity to introduce errors!)

Dear Researchers,

Thanks to a timely report from the LEAP lab at University of Arizona, we have discovered a new bug in the latest version of Google Chrome (v.92) that has impacted some of FindingFive's functionalities. Studies featuring many audio and video stimuli, including audio recordings that result from the audio responses, may become stuck at certain point, with an error message from FindingFive warning about missing stimulus file or incorrect format. Since this is a browser-level bug, your currently active sessions may be affected as well.

The cause
This is a new bug introduced by Google. Google is already working on a fix (https://bugs.chromium.org/p/chromium/iss...144736#c27).

Actions on FindingFive's end
We are also working to identify a workaround. However, since this is a browser-level bug, a fix might not be trivial. We will update everyone as soon as we have more insights into this issue.

What you can do
If your study features many audio and video stimuli, or use audio recording responses, please preview them immediately to see if you are impacted. If so, you can ask participants to use Firefox instead of Google Chrome to complete your study until either Google or FindingFive implements a fix.

Thanks for your patience and understanding!

I've been slowly building my study today, and after adding each bit of code, I've been testing and everything's been fine.
Then I added quite a bit of new code, and tried running the study. I got the error message: Your study contains coding errors that we cannot automatically detect yet. Please refer to the Study Grammar Reference for help.
So, I took out all of the new code I had added and tried to run again, thinking it should work since this is the same code I started with. Instead, I got the error: Your study contains coding errors that we cannot automatically detect yet. Please refer to the Study Grammar Reference for help.
So I looked at the FAQ #4 -- Syntax Error post. I highlighted all of my text in both trial templates and Procedure and hit tab -- looks good, but still get the error.
So I also C&P'd both trial templates and procedure into an online JSON validator -- it is valid JSON.
I am at my wits end! Two hours ago, this code worked fine -- now I can't run it and get the same syntax error: Your study contains coding errors that we cannot automatically detect yet. Please refer to the Study Grammar Reference for help 
even though this is the same code I ran earlier. 
What else can I try?

Dear Researchers,

We are happy to announce a minor feature addition to FindingFive's study grammar: it is now possible to set "barrier" on text and image stimuli! 

What's Barrier?
If you haven't heard of barrier and its function in building adapative experiments yet, please check out this tutorial: https://news.findingfive.com/2019/04/23/...-barriers/

A hypothetical setup: display two text stimuli in order
Imagine that you are displaying two text stimuli on the same trial, where the first text stimulus should stay on the screen for 3 seconds, and then the second stimulus will show up. 

This can already be done without this new barrier support for text stimuli, but it comes with some hassle and inflexibility. Essentially, you'll need to set a duration of 3 seconds to the first stimulus, which controls how long the first stimulus is visible, AND a delay of 3 seconds for the second stimulus, which tells the second stimulus not to show up when the first stimulus is visible. This is a little clumsy - we had to modify two stimuli to achieve this functionality. Moreover, if the duration of the first stimulus is variable across trials, this will get out of control: we would need to create many duplicate versions of the second stimulus, each with a different delay setting to accommodate the duration of the first stimulus!

Barrier solves this problem
Now with the newly introduced barrier support for text and image stimuli, this can be easily done. All you need to do is to add to the first stimulus a barrier setting in addition to the duration one, like this: