![]() ![]() Querying objects (using buttons or menu commands starting with Get)Įxperience with scripting or programming languages is not required! As you proceed through the tutorial all the basic principles of scripting (conditionals, loops, variables etc.) will be covered and explained.Managing objects (create, copy, rename, save, remove).You should be more or less familiar with the basic tasks that could be achieved in the Praat graphical user interface (windows, menus, buttons): The only prerequisite to attend this tutorial is that you have some experience with Praat. Praat plug-in mechanism)! In fact, the Praat scripting language lets us even create our own application, backed by the power of Praat but with an autonomous GUI completely controlled by Praat scripts (cf. Furthermore (and not covered in this tutorial), because we can't only add new GUI elements but also hide existing ones, we're able to create our own individual Praat version (cf. It's even possible to create new menu items and buttons in the Praat GUI to launch your scripts. If you wish to develop generic scripts that are of 'global' interest (a functionality useful for other Praat users working with completely different materials), that's also possible with the Praat scripting language. Macros - dumb or intelligent - adapt specifically to your current materials and tasks, they are only of 'local' interest (to you and maybe your workgroup). While you can still record simple (dumb) macros, now you can add some code and have much more useful (intelligent) macros. give the user some feedback during execution.ask the user for some input before execution of actions (e.g.: do you want to look at broad band or narrow band spectrograms).looped execution of actions (e.g.: measure duration of interval for every interval in a TextGrid).conditional execution of actions (e.g.: if the speaker is female set pitch range to 150.400 Hz else set pitch range to 50.250 Hz).With a scripting language you can add some logic to your macros, like for example: The last point of the list above-writing your own code-is the second reason why Praat scripts have the potential to be much more than macros (and the reason why you may want to attend this tutorial…): Praat lets you not only record GUI-actions but provides you with the power of a full-featured scripting language. You can add new or delete obsolete actions.with the window length set appropriate for broad band analysis you can simply adjust window length later if you need narrow band analysis - no need to record the macro again). if you recorded the GUI-action Spectrogram settings. Free choice of the editor is nice (especially since the Praat script editor is pretty simple) but much more important is the freedom to edit everything in a Praat script: But it is possible for example to adjust some parameters in a script that was mailed to your smartphone and send it back. You don't even need Praat to edit Praat scripts! Usually, that's a bad idea because you want to test your scripts frequently during development and of course you need Praat to run scripts. ![]() The Praat script editor obviously is the first choice to handle Praat scripts but principally you can use any text editor you like for editing. First, because Praat scripts are plain text files. Flexible macrosīut Praat scripts are much more versatile than simple macros. Praat also provides you with a macro recording mechanism (the command history which is introduced in Session 1), accessible within the Praat script editor (also introduced in Session 1). You can save the script for later use or to distribute it among your students or colleagues (to make their lives easier or to make sure that they perform an analysis exactly the same way as you intended). You can collect any amount of Praat GUI actions in a Praat script and replay them as often as you like. The benefit of macros is threefold: recurring tasks become less tedious, much faster and more reliable. you don't need to worry about typos or missed clicks during later iterations. So, with a macro you can automate a complex task and rerun it reliably, i.e. If you replay the macro, each recorded action is executed one after the other in the order you recorded them. GUI actions are actions you perform in the graphical user interface of an application, like pointing and clicking with the mouse or pressing keys on the keyboard. text processors, Photoshop etc.) allows you to record a series of GUI actions and to replay them as often as needed. An application that supports macros (e.g. What is a Praat script? One starting point is to think of Praat scripts as macros. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |