That is, the participant should not start reading the prompt before the prompt appears on the screen. Scoll forward to the last few trials to make sure that they are aligned properly.Once you’ve located the last beep, note its start time in the wav file, writing it in the participant speadsheet, then run parselog.py again, replacing the 0 with the start time of the last beep.Look at the waveform for where the talking seems to occur at regularly spaced intervals, and zoom into the first of these, playing the recording to be sure the speech corresponds to the first prompt text. Looking at the prompt tier, you can see what the first utterance is supposed to be (hint, it’s the first labeled prompt interval).Open the crXX_log.TextGrid with the crXX.wav file in Praat and locate the last beep (which should be the occlusal plane in recent recordings) in the wav file.To open a Praat window, use the terminal window, and type:.In this example, we would estimate that the beep is around 200 seconds or so before the first prompt (926-715=211). The difference in time between the last and the first should be approximately how much earlier you should expect to see the beep before the first prompt was spoken in the recording (plus however long the participant took to start speaking after pressing ). The last before the button was pressed should co-occur with the occlusal plane recording, but may occur later in some cases. ![]() The first tells you how long the arduino was plugged in before the first alignment, which may have occurred before the recording began.Running parselog.py creates a TextGrid that is not synchronized with the sound, and outputs the arduino information, including alignment (tare), beeps (beep), and when the right arrow was clicked (next).Python /phon/scripts/parselog.py -input LOG00790.TXT -output cr01 -beep 0 -threshold 2 Run the parselog.py script with “ -beep 0” and the appropriate LOG00XXX.TXT file, just to see the times when the beeps occur (after cd-ing into the participant’s main directory):.After each of these steps, update the Covart Participant Details with the appropriate numbers or your initials, to show that you have compled that step, and to help figure out who to ask in case you forgot to change the permissions for the group.Alternately, if you are still in the participant’s directory in the terminal window, you can type (replacing the file name):.Click on the Permissions tab and change the Group settings to “Can Read”. One way to do this is to locate the file in the file browser (Dolphin on the lab computers), right click, and choose Properties (or select the file and hit alt+return). (If you copy it from the ultrasound machine, you won’t own it and can’t change the permissions). Copy the wav file into data_upload on the phon server from any computer, and then copy it into the audio_capture folder using cox-515-4 or 5.Copy the log file from the sd card to the participant’s directory (e.g., /phon/cr/cr01/LOG00790.TXT), and make sure it is group readable. ![]() Inside of that directory, create a subfolder called audio_capture, and make sure it also is group rwx
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |