You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to run the ratchet-whisper example. I notice that DecodingOptionsBuilder has a setWithoutTimestamps() method. I assume that builder.setWithoutTimestamps(true) will remove the [00:00.000 --> 00:07.400] prefix from the output. However, after calling setWithoutTimestamps(true), I still can see these prefixes from the log.
{
"processing_time": {
"secs": 18,
"nanos": 379500000
},
"segments": [ ... ],
"formatted": "[00:00.000 --> 00:07.400] It's a beautiful day in Abakadeth and the silly crocodile just woke up from a good night of sleep.\n[00:07.400 --> 00:10.600] What are you going to do today, silly crocodile?\n[00:10.600 --> 00:12.600] I'm gonna get some breakfast.\n[00:12.600 --> 00:15.400] Eat breakfast.\n[00:15.400 --> 00:16.140] Morning.\n"
}
I'm not sure whether this is a bug, or if I misunderstand this method.
The text was updated successfully, but these errors were encountered:
ocavue
changed the title
setWithoutTimestamps(false) doesn't work.setWithoutTimestamps(true) doesn't work.
Jun 25, 2024
I'm trying to run the
ratchet-whisper
example. I notice thatDecodingOptionsBuilder
has asetWithoutTimestamps()
method. I assume thatbuilder.setWithoutTimestamps(true)
will remove the[00:00.000 --> 00:07.400]
prefix from the output. However, after callingsetWithoutTimestamps(true)
, I still can see these prefixes from the log.I'm not sure whether this is a bug, or if I misunderstand this method.
The text was updated successfully, but these errors were encountered: