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

Feature Request: Batch Transcribe #70

Open
Kuiriel opened this issue Jul 3, 2024 · 8 comments
Open

Feature Request: Batch Transcribe #70

Kuiriel opened this issue Jul 3, 2024 · 8 comments

Comments

@Kuiriel
Copy link

Kuiriel commented Jul 3, 2024

This program is fantastic. It's real fast on CUDA too - transcribing videos faster than the videos actually are. Less than a minute for nearly a 4 minute video.

I've got a bunch of videos to transcribe, and I would have been happy for each file to be taken in and transcribed to an identically named subtitle file, automatically without further interference from me.

This isn't NECESSARY, it's already an awesome free program. It would just be useful.

Anyway. Thank you for this beautiful time saver.

@kaixxx
Copy link
Owner

kaixxx commented Jul 3, 2024

Great that you like it and yeah, batch processing is high on the list for the future. It will, however, take a few months before this gets implemented because it depends on some other internal changes that are currently beeing worked on.
I'll keep this feature request open to remind me...

@Tenome
Copy link

Tenome commented Aug 11, 2024

Damn, I also installed it before noticing it didn't have a batch option. Here's hoping!

@mfostersyda
Copy link

I could really use batch myself. Any chance we can just pass start arguments to noscribe on the command line instead of only via a GUI form?

@kaixxx
Copy link
Owner

kaixxx commented Jan 13, 2025

Let me think about this for a moment. I had a more complex solution in mind, but may be able to add a simpler command line interface in the meantime.

@mfostersyda
Copy link

With start arguments, we could at least create a batch script to run noscribe once for each file, instead of having to run an entire batch within noscribe itself.

@kaixxx
Copy link
Owner

kaixxx commented Jan 14, 2025

Would it be ok to still show the GUI and just start the transcription automatically if all necessary parameters are given? This would be easier to implement compared with a full-fledged nogui option. I might be able to add an option to start noScribe in a minimized state.
Followup question: Should noScribe automatically exit the app if a job from the command line is finished? Probably yes, otherwise batch processing would be impossible, I guess.

@kaixxx
Copy link
Owner

kaixxx commented Jan 14, 2025

I've found a problem for the solution I was imagining: noScribe is compiled with pyinstaller into a GUI-only app. This means that if we start the app from the command line, it will spawn a new GUI process and then terminate immediately. There is no easy way for the calling batch script to know if noScribe is still busy transcribing or not.
At the moment, the only option I see would be to use the non compiled version of noScribe and run it with python directly. Would this be feasible? Or do you have another idea?

@mfostersyda
Copy link

I don't think using the non-compiled version is an issue, since it really doesn't affect run-time performance only start-up, but I'm unclear as to how using the non-compiled version makes it easier to pass-in start arguments.

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

4 participants