I noticed that when saving the textgrid file, praatio would try to fill up the tiers with new blank intervals, which seems not to be quite friendly to automatic aligning. I am not sure but what would happen if the tier is left there and not filled up? Or can I use praatio to fill the blanks by extending the existing intervals (which would not change the total number of intervals, making it much easier for machines to recognize)?

Hi,

I've studied a little bit of forced alignment so currently I have a wav file which spoke "hello" and a .txt file which contain the word "hello". Can I use some sort of forced alignment to find out where is the start or end of the sentences along with its pronunciation? If so is it possible to do it in a Window 10 OS?

Thank you.

Hi I am very new to Praat overall, not just the python version.

is Praat a good tool to use to segment a .wav file if I know the exact times marks where I want to chop up the file? I like to just use Praat, because afterwards I will be extracting pitch and tempo from the segments.

I've had a couple of users reporting issues with loading TextGrids exported from ELAN. The issue seems to be that the "item [1]" lines are formatted without a space ("item[1]"), so the parsing in https://github.com/timmahrt/praatIO/blob/master/praatio/tgio.py#L1896 fails. I think a reasonable fix would be something like re.split(r'item ?\[', data, flags=re.MULTILINE)[1:].

Looks like you're working on a 5.0, so don't know if that would be the place to fix it or if it would be better for me to submit a PR for the main branch.

A user might make certain assumptions about their data and praatio will silently break those expectations. It can make calculation errors go unnoticed.

Scenario A

• Textgrid A has a maxTimestamp of 10.12345
• Textgrid B has a maxTimestamp of 10.123456
• both textgrids have an intervalTier with a final entry that runs to the end of the file
• if those Textgrids are combined (using append) the interval in Textgrid A will no longer run to the new end of the file, although that may have been the original intention

Scenario B?

Solution?

• validate on save will probably be too late for Scenario A but can be caught when adding the tier to the Textgrid
• validation could potentially be desired anywhere (will this pollute function signatures more? Is there a cleaner way to do this?)
• only offer validation in "risky" functions? Some functions already have the option to throw exceptions if unexpected data is encountered
• to what extent is it the users responsibility to validate and to what extent is it praatios?

Hi, I'm new to praat and after following your tutorial I've created a Textgrid that looks like this:

bobby.TextGrid File type = "ooTextFile short" Object class = "TextGrid"

0.0 1.194625 1 "IntervalTier" "phoneme" 0.0 1.194625 1 0.0 1.194625 ""

However when I tried to print out data from my textgrid it doesn't work. When I use bobby_phone.TextGrid for example it works. My question is do you need the praat.exe to do it manually?

Bobby_phone.Textgrid: File type = "ooTextFile" Object class = "TextGrid"

xmin = 0.0 xmax = 1.194625 tiers? size = 1 item []: item [1]: class = "IntervalTier" name = "phone" xmin = 0.0 xmax = 1.18979591837 intervals: size = 15 intervals [1]: xmin = 0.0124716553288 xmax = 0.06469123242311078 text = "" intervals [2]: xmin = 0.06469123242311078 xmax = 0.08438971390281873 text = "B" intervals [3]: xmin = 0.08438971390281873 xmax = 0.23285789838876556 text = "AA1" intervals [4]: xmin = 0.23285789838876556 xmax = 0.2788210218414174 text = "B" intervals [5]: xmin = 0.2788210218414174 xmax = 0.41156462585 text = "IY0" intervals [6]: xmin = 0.41156462585 xmax = 0.47094510353588265 text = "R" intervals [7]: xmin = 0.47094510353588265 xmax = 0.521315192744 text = "IH1" intervals [8]: xmin = 0.521315192744 xmax = 0.658052967538796 text = "PT" intervals [9]: xmin = 0.658052967538796 xmax = 0.680952380952 text = "DH" intervals [10]: xmin = 0.680952380952 xmax = 0.740816326531 text = "AH0" intervals [11]: xmin = 0.740816326531 xmax = 0.807647261005538 text = "L" intervals [12]: xmin = 0.807647261005538 xmax = 0.910430839002 text = "EH1" intervals [13]: xmin = 0.910430839002 xmax = 0.980272108844 text = "JH" intervals [14]: xmin = 0.980272108844 xmax = 1.1171482864527198 text = "ER0" intervals [15]: xmin = 1.1171482864527198 xmax = 1.18979591837 text = ""

Hi Tim,

You've explained how to create a blank textgrid from audio file in your tutorial. I was wondering how do you extract out the (phoneme / phone) and words from audio and insert into textgrid.

Thank you!

I have many textgrid files with some or all the labels in specific tiers being deliberately set to be blank. Praatio just skips over them, ignoring the time information (which is what I need to retrieve). I have tried both a prebuilt version from "pip install" and the latest version from github, installed using setup.py

The attached file has three entries in its only tier, and two of them are empty. Only one is retrieved by praatio.

EmptyLabelBug.Txt

praatio/utilities/xsampa.py is listed as "does not carry any license". IANAL, but my understanding is that without any license, no one has permission to use it. It may be included in the source of the project with permission, but without an explicit license for the file no one else can know exactly how they are allowed to use it, if at all. Is there any way to contact the author and get a specific license for the file, such as MIT like the main project?

Files like the following:

item []:
	item [1]:
		class = "IntervalTier"
		name = "Tokens"
		xmin = 0.0
		xmax = 16.6671875
		intervals: size = 22
		intervals [1]:
			xmin = 0.0
			xmax = 0.32
			text = "#"
		intervals [2]:
			xmin = 0.32
			xmax = 1.165
			text = "zao
chen
liu
wan
er
ne"

Only the "zao part is recognized. According to the manual of Praat, string variables are identified by double quotes instead of newlines. (double quotes in text are turned into two double quotes in the file: " → """"

It is not hard to fix it, but I'm unfamiliar with git/github. So I paste the changed code in below (in place of original _fetchRow in tgio):

def _fetchRow_for_text(dataStr, searchStr, index):
    startIndex = dataStr.index(searchStr, index) + len(searchStr)
    first_quote_index = dataStr.index("\"", startIndex)
    
    looking = True
    next_quote_index = dataStr.index("\"", first_quote_index+1)
    while looking:
        try:
            neighbor_letter = dataStr[next_quote_index+1]
            if neighbor_letter == "\"":
                next_quote_index = dataStr.index("\"", next_quote_index+1)
            else:
                looking = False
        except IndexError:
            looking = False
    final_quote_index = next_quote_index
    
    word = dataStr[first_quote_index+1:final_quote_index]
    word = word.replace("\"\"", "\"")
    
    return word, final_quote_index + 1

I suppose it might be possible that in other places, like textgrid short version reading and writing, there are also problems due to this issue.

        if tierType == INTERVAL_TIER:
            while True:
                try:
                    timeStart, timeStartI = _fetchRow(tierData,
                                                      "xmin = ", labelI)
                    timeEnd, timeEndI = _fetchRow(tierData,
                                                  "xmax = ", timeStartI)
                    label, labelI = _fetchRow(tierData, "text =", timeEndI)
                except (ValueError, IndexError):
                    break
                
                label = label.strip()
                if label == "":
                    continue
                tierEntryList.append((timeStart, timeEnd, label))
            tier = IntervalTier(tierName, tierEntryList, tierStart, tierEnd)

Why wouldn't I want the intervals exactly as they appear in the file?

audio.py suffers from a number of inconsistencies and bugs.

This PR aims to remove redundant methods and add documentation, and test coverage to audio.py

The json format exported by praatio largely mirrors the textgrids, in terms of the data that is output.

As requested on a different github project, (https://github.com/MontrealCorpusTools/Montreal-Forced-Aligner/issues/453) there isn't really any need to be bound by the textgrids. We should structure the json files to be their own thing.

Details can be found in the above link.

As far as I can tell from your examples, the canonical way to access a TextGridTier from a TextGrid is to access the internal tierDict (Example).

However, because tierDict is mutable, one can end up adding a new TextGridTier to this tierDict, e.g.,

new_textgrid_tier = new_textgrid.tierDict.setdefault(
    "new_tier",
    IntervalTier(
        "new_tier", [], textgrid_obj.minTimestamp, textgrid_obj.maxTimestamp
    )
)

If this happens, the TextGrid will essentially be in an Illegal State, because TextGrid.tierNameList will be missing the new tier. This obviously breaks functions like TextGridTier#replaceTier, among other things.

I think there are at least two possible solutions:

1. Add a getTier method and rename tierDict to _tierDict to indicate that it is a protected member that shouldn't be altered
2. Change tierDict to an OrderedDict and remove tierNameList entirely. You can then just use tierDict.keys() in place of tierNameList

I think it'd probably be best to implement both solutions, particularly because it's dangerous to have two parallel data structures that you need to keep in sync. However, simply implementing number 1 alone should solve the problem quickly and easily.

I'm also happy to submit a PR for this if you'd like.

Thanks again for all your work!

audio.extractSubwav calls audio.openAudioFile with a keepList containing startT and endT and no deleteList:

def extractSubwav(fn: str, outputFN: str, startT: float, endT: float) -> None:
    audioObj = openAudioFile(
        fn,
        [
            (startT, endT, ""),
        ],
        doShrink=True,
    )
    audioObj.save(outputFN)

In audio.openAudioFile L491, it calls utils.invertIntervalList with duration given as the min:

elif deleteList is None and keepList is not None:
        computedKeepList = []
        computedDeleteList = utils.invertIntervalList(
            [(start, end) for start, end, _ in keepList], duration
        )

In this case, the computedDeleteList will always be empty, because the min time provided is the end of the original wav file.

This means when you call audio.extractSubwav, you will always get an empty result.

To further complicate things, even if you changed L491 to specify min=0, max=duration, you'll still get an empty result for audio.extractSubwav.

This is because on L489, it sets computedKeepList = [], and then on L499, the original keepList is overridden with the now empty computedKeepList:

keepList = [(row[0], row[1], _KEEP) for row in computedKeepList]

Finally, when we actually do the operations, because audio.extractSubwav calls audio.openAudioFile with doShrink=True, it won't actually delete anything on LL519-521:

        elif label == _DELETE and doShrink is False:
            zeroPadding = [0] * int(framerate * diff)
            audioSampleList.extend(zeroPadding)

And it won't keep anything because keepList is empty.

I had a project that needed support for Klattgrids, so I added it to Praatio. However that was a long time ago and I'm not sure the code still is functioning.

It was refactored a bit in the move from Praatio 4 -> Praatio 5.

We should add some more robust tests for it maybe?