May 9, 2022 at 3:53 pm #8162
Lately, several participants of our experiment told us that there’s trouble loading the images and/or some experimental sound files. However, everything worked fine a week ago and no recent changes have been made, neither on the experiment scripts, nor on the materials themselves. Is there anything else that we can do to troubleshoot?
Thank you in advance!May 9, 2022 at 7:46 pm #8165JeremyKeymaster
Do you have a link to your project that I could inspect? Also, take a look at this thread: Chrome seems to have trouble preloading audio file, see if your situation improves after implementing the trick I describe on that thread
JeremyMay 10, 2022 at 1:01 am #8166
I tried doing the modifications in the link you sent, and it seems to work.
The link of our experiment is https://farm.pcibex.net/p/ZruNar/. I will be back in touch if the issue arises again.
Thanks so much!
LilyMay 10, 2022 at 1:06 am #8167
Actually, i think the issue is not completely fixed. We tried it on several different computers / browsers. The preloading message shows up the first time we click the link and goes away after we refresh. Would it be possible for you to still take a look at our experiment?
LilyMay 10, 2022 at 6:28 pm #8171JeremyKeymaster
I was able to reproduce the issue the second time I took your experiment. I inspected my webconsole and noticed multiple 403 errors: those are called “Forbidden errors,” which means that the server will not accept the request. This means that the servers hosting your audio and image files sometimes refuse to serve some of them
Unfortunately there is not much you can do on the PCIbex Farm’s end, since it’s up to the host server to decide whether to accept the farm’s requests. It could be that admins there have added a check that blocks requests when too many are received in too short a time window. One option you could consider is to compress your audio files in a zip archive (and also your image files if you’d like, in the same or in a separate zip file) and fetch that instead of each audio file individually, using
PreloadZipin addition/instead of
AddHost. You’ll find more info on the procedure in the documentation. You might need to contact IT for assistance, depending on whether their webserver accepts
NB: I recommend you share your project’s demonstration link rather than the production link, or you might end up with noise in your results file. Also, I need demonstration links, which come with a very useful debugger, for troubleshooting (which, in this case, I retrieved by looking up associations in the farm’s database)
Let me know if you have any questions
- You must be logged in to reply to this topic.