Auto Close When Export Complete

[ChicagoScanningMG]

I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first

• Check out all the menus and keyboard shortcuts. Maybe the feature already exists?
• Try with the newest version from GitHub
• Read all the documentation at https://github.com/mifi/lossless-cut to see if the feature already exists
• See if someone already suggested this under Issues or Discussions

Description

I would love to have the option to enable closing the program when a file finishes exporting.

[mifi]

what's the use case for this?

[ChicagoScanningMG]

Generally speaking, if a user is externally opening (say with a script or right click-> open with) multiple files in Lossless cut periodically throughout the day, it will open a new instance of Lossless cut each time a new file is opened. Having the option to auto close when an export is complete will prevent multiple instances of Lossless cut from running if that is not desired. I have a python script set up so that when an OBS recording is stopped, it's automatically opened in Lossless cut for trimming. When I hit export, I leave Lossless cut to run in the background while I start another recording or do something else. The issue is that when my next recording stops, it opens up a new instance of Lossless cut. I had thought about editing my script so it closes all other instances of Lossless cut, but the problem is that it will close Lossless cut if an export is currently in progress, which is not great. A lot of other encoding software has this or similar features as an option. I believe Handbrake and Adobe Media encoder have the option to shut down when complete or close when complete.

…

On Sun, Sep 4, 2022 at 7:19 AM Mikael Finstad ***@***.***> wrote: what's the use case for this? — Reply to this email directly, view it on GitHub <#1265 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASQKE2AOOHOGOMCWEO76MCLV4SHUBANCNFSM56MUG3FQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ChicagoScanningMG]

This is in Windows 10 by the way.

[mifi]

Could an alternative be that LosslessCut would check for an existing running instance when starting up, and only start up if not already running (probably behind a setting)? I believe this is how it works on MacOS out of the box

[ChicagoScanningMG]

That would be fine so long as the new file opens in place of the old one in the currently running instance.