Configuration Files

osabe has a couple of configuration files that can be modified to change its visual style or affect how it reads and plays audio files.

These files are created the first time osabe runs and are populated with reasonable defaults, however you'll probably want to change at least the threshold-in-dB-down setting in the settings.yaml file for reading audio files before using the application.

This page describes how to edit the configuration files of osabe, and the individual settings in the configuration files are documented on the Configuration Reference page.

Editing the files

All the user-customizable configuration files of osabe reside in the same directory:

• On Windows:   %appdata%/osabe/
• On OS X:   ~/.config/osabe/
• On Linux:   ~/.config/osabe/

and can be edited with a text editor. In addition, the settings of settings.yaml can be modified by calling osabe with the correct command-line arguments.

Editing with a text editor

On Windows

Open a Windows Explorer window and in the address bar type:  %appdata%/osabe  -- note that you may need to enable the address bar.

This will take you to the configuration folder for osabe. Open the files with Notepad for editing if you're not sure what application to use.

On OS X

Open a Finder window and go to your user's home folder.

Press the  ⌘  + Shift +  .  key-combo to show hidden files, and go to .config, then to osabe.

Edit the files with TextEdit.app, but be careful that you're not in Rich Text mode and mind the quote characters -- OS X likes to insert fancy quotes in place of reuglar quotes but regular quotes are what are required in these configuration files.

Editing via command-line

You can read or edit settings via command-line by issuing commands in the following forms:

osabe config list                # list the configuration settings
osabe config get SETTING         # get the value of SETTING
osabe config set SETTING VALUE   # set SETTING to VALUE
osabe config set SETTING         # clear SETTING (if applicable)
        

On Windows

Editing settings via command-line on Windows isn't as user-friendly as one might have hoped.

Windows' Command Prompt will let you run the application via command-line with arguments, but it won't display any output because osabe is primarily a graphical application. However, if you use Windows PowerShell and pipe the output through echo, it will be displayed:

PS C:\Users\Paul> osabe config list | echo
audio-driver
default-view-span-in-seconds
max-intraclip-silence-in-ms
playback-buffer-sample-count
threshold-in-dB-down
PS C:\Users\Paul> osabe config set threshold-in-dB-down -65 | echo
Set 'threshold-in-dB-down' to '-65'.
        

On OS X

On OS X you can call the app via command-line, but since it's not part of the system's PATH by default you'll have to do it one of a few ways:

• Add the application to the system path
• Call the application using the full path: /Applications/osabe.app/Contents/MacOS/osabe
• Change directories into /Applications/osabe.app/Contents/MacOS/ and call it like so: ./osabe

A few examples of the latter two options:

Using the full path

paul@Pauls-MacBook-Pro ~ % /Applications/osabe.app/Contents/MacOS/osabe config list
audio-driver
default-view-span-in-seconds
max-intraclip-silence-in-ms
playback-buffer-sample-count
threshold-in-dB-down
        

Changing directories

paul@Pauls-MacBook-Pro ~ % cd /Applications/osabe.app/Contents/MacOS/
paul@Pauls-MacBook-Pro MacOS % ./osabe config list
audio-driver
default-view-span-in-seconds
max-intraclip-silence-in-ms
playback-buffer-sample-count
threshold-in-dB-down