Playing with the new word level timestamps in large-v3, however for some reason the json returns with single quotes instead of double quotes. Running the json through chatGPT easily converts it but its pretty risky if it decides to hallucinate any of the output.
It seems you are describing Python’s adaptive reporting on the contents of string objects. It depends on how you got there and the contents whether you see single or double quotes, or escaped quotes of either type.
The bytes returned from a direct “requests” library call to the API is JSON:
Set a data object with a mix of strings with double quotes and escaped single quotes: chunks = [{'text': 'He said "Hello"', 'timestamp': (0.0, 0.54)}, {'text': ' because', 'timestamp': (0.54, 1.48)}, {'text': ' it\'s', 'timestamp': (1.48, 2.04)}, {'text': '"polite"', 'timestamp': (2.04, 2.2)}]
Print: print(chunks)
See the alternation of string enclosure for ideal presentation of the contents of any one string: [{'text': 'He said "Hello"', 'timestamp': (0.0, 0.54)}, {'text': ' because', 'timestamp': (0.54, 1.48)}, {'text': " it's", 'timestamp': (1.48, 2.04)}, {'text': ' "polite"', 'timestamp': (2.04, 2.2)}]
Or we make a JSON string, that is no longer the list and dictionary structure references you’d use for parsing.