¿Existe un método para que un script personalizado que tarda mucho tiempo en ejecutarse (en realidad realiza el remux) informe de vuelta a MCEBuddy para que pueda reportar el progreso?
That’s a great question, Dan!
Unfortunately, MCEBuddy doesn’t have a built-in method for custom scripts to report real-time progress back to the main application for display. The custom script functionality is primarily designed for pre or post-processing tasks that run to completion and then return control to MCEBuddy.
While you won’t get a progress bar directly in MCEBuddy, some users have implemented workarounds to get a sense of long-running script activity. This often involves:
- Logging to a file: Your script could periodically write its current status or the percentage of completion to a separate log file. You could then monitor this log file manually.
- Command Line Output: For some simple scripts, printing progress updates to standard output might be visible in the MCEBuddy command prompt window if it remains open during the custom command execution. However, this isn’t a robust solution for detailed progress.
If you’re interested in exploring these workarounds further, or if you could provide more details about the “remux” process your script performs, the community might be able to offer more specific suggestions.
You might also find some related discussions in the forum about custom commands and their execution, though they may not directly address progress reporting:
For future feature considerations, you could also suggest this as a new feature in the #Bugs / Feature Requests category!
Tengo un script personalizado para hacer el remux sin perder los datos HDR10+. Puedo simplemente monitorear los registros como estoy haciendo ahora.