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

Writing to .txt seems to get cutoff #161

Open
Ph-ADD opened this issue Sep 5, 2024 · 2 comments
Open

Writing to .txt seems to get cutoff #161

Ph-ADD opened this issue Sep 5, 2024 · 2 comments

Comments

@Ph-ADD
Copy link

Ph-ADD commented Sep 5, 2024

First of all, thanks for the really awesome plugin. I've only just found it a few weeks ago and have been toying around with it as a way to generate notes for meetings. Currently I have it set so that both my mic and audio output write the captions to a .txt file (I admit it is probably ill-conceived to have two LocalVocal processes writing to the same file simultaneously). However, it does seem to work for a while. Then the output just seems to stop at some point during the call.

I'm hoping for some help investigating what might be causing this.

  • is it just that I'm having two processes write to the same file?
  • should I be using a different output format?
  • is there some hard limit on number of lines or characters written?
  • are there some settings I should be tweaking?

Happy to provide whatever information might be useful.

@royshil
Copy link
Collaborator

royshil commented Sep 9, 2024

@Ph-ADD can you get the OBS logs from a session where this problem has occurred?

@Ph-ADD
Copy link
Author

Ph-ADD commented Sep 10, 2024

@royshil I've attached an OBS log from this morning.

2024-09-10 07-33-51.txt

The last line of the file suggests the issue has to do with buffering:

08:51:09.429: Source Audio Output Capture audio is lagging (over by 474669.54 ms) at max audio buffering. Restarting source audio.

This timestamp does match the last modified time for the audio transcript file.

Update: If I leave OBS running, it does seem to start clearing the buffer and writing out to the file. Maybe this indicates I've got this setup poorly and some better settings would avoid this?

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