Millisecond Forums

My script breaks in Web Version 6 because it can't load or "transfer" mp3 files , but script runs fine on local Inquisit 4

https://forums.millisecond.com/Topic28621.aspx

By James Rounds - 3/28/2020

Hello all!

I'm trying to start an experiment running on Inquisit Web (Inquisit 6 I believe?) - the script runs fine on my local computer in Inquisit 4. When we upload the files and script, everything seems fine. But when I test it on the Web version, I get this error for my two mp3 files:

sdlm_2teachers_counterbalanced_long_moredata_032720_online.iqx - Unable to open file 'https://scripts.millisecond.com/xxxxx/xxxxxxxxxxx.mp3'. Error transferring: 403 -

I see in older forum posts that it could be due to bad metadata or corrupted encoding. I created the mp3's myself in Audacity, and manually created the metadata. Is that a possible source of the error?

Thank you for any advice you have!
By Dave - 3/30/2020

James Rounds - 3/29/2020
Hello all!

I'm trying to start an experiment running on Inquisit Web (Inquisit 6 I believe?) - the script runs fine on my local computer in Inquisit 4. When we upload the files and script, everything seems fine. But when I test it on the Web version, I get this error for my two mp3 files:

sdlm_2teachers_counterbalanced_long_moredata_032720_online.iqx - Unable to open file 'https://scripts.millisecond.com/xxxxx/xxxxxxxxxxx.mp3'. Error transferring: 403 -

I see in older forum posts that it could be due to bad metadata or corrupted encoding. I created the mp3's myself in Audacity, and manually created the metadata. Is that a possible source of the error?

Thank you for any advice you have!

You get a HTTP 403 error code, which typically means that the URL for the MP3 in question is not accessible. The file may not have been uploaded, there may be a caching issue, or a problem with the file's name. Whichever it is, I cannot tell without the link to the web experiment.
By James Rounds - 3/30/2020

Dave - 3/30/2020
James Rounds - 3/29/2020
Hello all!

I'm trying to start an experiment running on Inquisit Web (Inquisit 6 I believe?) - the script runs fine on my local computer in Inquisit 4. When we upload the files and script, everything seems fine. But when I test it on the Web version, I get this error for my two mp3 files:

sdlm_2teachers_counterbalanced_long_moredata_032720_online.iqx - Unable to open file 'https://scripts.millisecond.com/xxxxx/xxxxxxxxxxx.mp3'. Error transferring: 403 -

I see in older forum posts that it could be due to bad metadata or corrupted encoding. I created the mp3's myself in Audacity, and manually created the metadata. Is that a possible source of the error?

Thank you for any advice you have!

You get a HTTP 403 error code, which typically means that the URL for the MP3 in question is not accessible. The file may not have been uploaded, there may be a caching issue, or a problem with the file's name. Whichever it is, I cannot tell without the link to the web experiment.

Thank you so much for your quick response! Here's the link to the experiment - maybe my mp3 file name is too long? (that happens to me sometimes) - https://mili2nd.co/b6qb
By Dave - 3/30/2020

James Rounds - 3/30/2020
Dave - 3/30/2020
James Rounds - 3/29/2020
Hello all!

I'm trying to start an experiment running on Inquisit Web (Inquisit 6 I believe?) - the script runs fine on my local computer in Inquisit 4. When we upload the files and script, everything seems fine. But when I test it on the Web version, I get this error for my two mp3 files:

sdlm_2teachers_counterbalanced_long_moredata_032720_online.iqx - Unable to open file 'https://scripts.millisecond.com/xxxxx/xxxxxxxxxxx.mp3'. Error transferring: 403 -

I see in older forum posts that it could be due to bad metadata or corrupted encoding. I created the mp3's myself in Audacity, and manually created the metadata. Is that a possible source of the error?

Thank you for any advice you have!

You get a HTTP 403 error code, which typically means that the URL for the MP3 in question is not accessible. The file may not have been uploaded, there may be a caching issue, or a problem with the file's name. Whichever it is, I cannot tell without the link to the web experiment.

Thank you so much for your quick response! Here's the link to the experiment - maybe my mp3 file name is too long? (that happens to me sometimes) - https://mili2nd.co/b6qb

Thanks for the link. In your  online script, you've specified a file called "MR_TeacherB_Lewis_021720_denoised_030520mp3.mp3"

<video sound_loconnhicomp_teacherB_MR>

/ items = ("MR_TeacherB_Lewis_021720_denoised_030520mp3.mp3" )

/ playthrough = true

</video>

That is not what the file you've actually uploaded is called, however. In the uploaded file's name, there is a space between Teacher and B:

https://scripts.millisecond.com/vz29/sdlm_sp2020/mr_teacher%20b_lewis_021720_denoised_030520mp3.mp3

Similarly, in

<video sound_hiconnhicomp_teacherA_AS>

/ items = ("AS_TeacherA_Bauer_022120_compressed_Slowed5perc_030520mp3.mp3")

/ playthrough = true
</video>

you've specified a file called "AS_TeacherA_Bauer_022120_compressed_Slowed5perc_030520mp3.mp3", but in the uploaded file's name, there is a space between

TeacherA and the underscore:

https://scripts.millisecond.com/vz29/sdlm_sp2020/as_teachera%20_bauer_022120_compressed_slowed5perc_030520mp3.mp3

You need to fix these inconsistencies.
By James Rounds - 3/30/2020

James Rounds - 3/30/2020
Dave - 3/30/2020
James Rounds - 3/29/2020
Hello all!

I'm trying to start an experiment running on Inquisit Web (Inquisit 6 I believe?) - the script runs fine on my local computer in Inquisit 4. When we upload the files and script, everything seems fine. But when I test it on the Web version, I get this error for my two mp3 files:

sdlm_2teachers_counterbalanced_long_moredata_032720_online.iqx - Unable to open file 'https://scripts.millisecond.com/xxxxx/xxxxxxxxxxx.mp3'. Error transferring: 403 -

I see in older forum posts that it could be due to bad metadata or corrupted encoding. I created the mp3's myself in Audacity, and manually created the metadata. Is that a possible source of the error?

Thank you for any advice you have!

You get a HTTP 403 error code, which typically means that the URL for the MP3 in question is not accessible. The file may not have been uploaded, there may be a caching issue, or a problem with the file's name. Whichever it is, I cannot tell without the link to the web experiment.

Thank you so much for your quick response! Here's the link to the experiment - maybe my mp3 file name is too long? (that happens to me sometimes) - https://mili2nd.co/b6qb

Actually it's resolved now! I modified the metadata so that it was complete for each category (Title, Year, etc.), and re-created the mp3 files (and decreased the audio quality slightly), and now it's working great. Thanks again!
By James Rounds - 3/30/2020

James Rounds - 3/30/2020
James Rounds - 3/30/2020
Dave - 3/30/2020
James Rounds - 3/29/2020
Hello all!

I'm trying to start an experiment running on Inquisit Web (Inquisit 6 I believe?) - the script runs fine on my local computer in Inquisit 4. When we upload the files and script, everything seems fine. But when I test it on the Web version, I get this error for my two mp3 files:

sdlm_2teachers_counterbalanced_long_moredata_032720_online.iqx - Unable to open file 'https://scripts.millisecond.com/xxxxx/xxxxxxxxxxx.mp3'. Error transferring: 403 -

I see in older forum posts that it could be due to bad metadata or corrupted encoding. I created the mp3's myself in Audacity, and manually created the metadata. Is that a possible source of the error?

Thank you for any advice you have!

You get a HTTP 403 error code, which typically means that the URL for the MP3 in question is not accessible. The file may not have been uploaded, there may be a caching issue, or a problem with the file's name. Whichever it is, I cannot tell without the link to the web experiment.

Thank you so much for your quick response! Here's the link to the experiment - maybe my mp3 file name is too long? (that happens to me sometimes) - https://mili2nd.co/b6qb

Actually it's resolved now! I modified the metadata so that it was complete for each category (Title, Year, etc.), and re-created the mp3 files (and decreased the audio quality slightly), and now it's working great. Thanks again!

Ah, I just saw your earlier post, too, about the file-name errors. I think that was an upload issue (since I changed the mp3 filenames a couple times, and my collaborator might not have uploaded the newest versions), so that must have been part of the problem, too. Thanks again!!