Below, I have listed all of the Praat scripts that I have in my possession. Bits and pieces can be reused from other scripts, and in this way new scripts can be generated very quickly. However, I rarely code a script from scratch. This way, when the time comes to write up the Method section, all of the information is easily accessible and traceable.ĭue to this new project-based scripting technique, I create a new script for each project that I am working on. Now, for each project, I create one large Praat script that contains all manipulations: taking original measurements, manipulating intensity, pitch, ramping, etc., renaming files, and taking new measurements after all manipulations have been completed. As a result, a few years ago, I changed the way that I used Praat scripts. What I found was that the problem with such an approach is that it is very easy to lose track of what manipulations you have already done to a set of sound files - especially if you are working on multiple projects at the same time, with different normalisation scripts, etc. For instance, after a recording session, I would use one script to cut the large file of the entire recording session into smaller files, a separate script to extract measurements, another script to normalise the intensity of the sounds, and yet another script to ramp in and out, and so on. When I first started using Praat, I used many small scripts, each of which performed one small job. I cannot stress this enough: you have to know exactly what the script is doing. But be warned, a script cannot do anything that requires human judgment, such as labeling segments. As I have mentioned before, Praat scripts can take care of many repetitive actions for you, saving you many mouse clicks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |