Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setWithoutTimestamps(true) doesn't work. #224

Open
ocavue opened this issue Jun 25, 2024 · 1 comment
Open

setWithoutTimestamps(true) doesn't work. #224

ocavue opened this issue Jun 25, 2024 · 1 comment

Comments

@ocavue
Copy link
Contributor

ocavue commented Jun 25, 2024

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.

@ocavue ocavue changed the title setWithoutTimestamps(false) doesn't work. setWithoutTimestamps(true) doesn't work. Jun 25, 2024
@FL33TW00D
Copy link
Collaborator

FL33TW00D commented Jun 26, 2024

No this isn't a bug, lack of functionality unfortunately. My apologies, we will add support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants