How to tell LC to auto-clean ALL *.log files at exit? and cache content?

[tobwz]

The fewer issues I have to read, the more new features I will have time to implement, so 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 the documentation and FAQ, Known issues, Troubleshooting to see if the feature already exists
• See if someone already suggested this under Issues or Discussions

Description

As I found out LC writes a lot of stuff to *.log files (especially in "shared_proto_db" subfolder).
I hate leaving tracks on the hard disk.

How can I tell LC to automatically clean all such *.log files (and cache content) at LC exit?

if this is currently NOT possible:
Can this feature be added in the next release?

Thank you

[mifi]

I have no idea what is shared_proto_db. I don't even know which OS you are on. losslesscut should only write files into its appData folder.

see https://github.com/mifi/lossless-cut/blob/master/issues.md#faq (Where is application data, settings and temp files stored?)

so you should be able to delete that folder and the log will be gone too. If you have evidence that losslesscut writes files outside of that directory, then please elaborate.

note that losslesscut is not a portable app so it has to write temporary files and config to the appData folder in order to function properly, see also #645
I'm probably not going to change that, because most users would want their settings and app state to be remembered and not deleted every time the app closes.

If you want this behaviour you could write a wrapper script. something like this (assuming MacOS):

losslesscut-wrapper.sh

#!/bin/bash
/path/to/LosslessCut
rm -rf ~/'Library/Application Support/LosslessCut'

then chmod +x losslesscut-wrapper.sh and run this wrapper instead of LosslessCut directly

[tobwz]

I have no idea what is shared_proto_db. I don't even know which OS you are on. losslesscut should only write files into its appData folder.

shared_proto_db is a sub folder of LosslessCut Portable Apps.
I am using LC on Windows 10

so you should be able to delete that folder and the log will be gone too.

Yes, I can delete such files manually. The problem is that I have to do it manually.
LC should remove them automatically at exit to avoid leaving tracks.

note that losslesscut is not a portable app

What would you call:
https://portableapps.com/apps/music_video/lossless-cut-portable

so it has to write temporary files and config to the appData folder in order to function properly, see also #645 I'm probably not going to change that, because most users would want their settings and app state to be remembered and not deleted every time the app closes.

Yes, no problem. During running and processing LC can create as much files as it needs.
I am asking for AUTOMATIC removal of unnecessary files at exit. And cache files are unnecessary beyond exit.
Keeping settings is welcomed. But not cache and log files.
An option to enable or disable auto-cleanup should be added.

If you want this behaviour you could write a wrapper script. something like this (assuming MacOS):

losslesscut-wrapper.sh

#!/bin/bash
/path/to/LosslessCut
rm -rf ~/'Library/Application Support/LosslessCut'

then chmod +x losslesscut-wrapper.sh and run this wrapper instead of LosslessCut directly

Yes, I can do that manually. But this feature should be a built-in part of LC.
It shouldn't be difficult to implement.

[mifi]

What would you call: https://portableapps.com/apps/music_video/lossless-cut-portable

This is an unofficial version, not maintained by me. You will have to ask portableapps.com or their maintainer of the losslesscut portable version about it. the original LosslessCut is not a portable app.

Cache files are needed for performance. Log files may be needed for debugging or other purposes. So I would have to implement an option in order to disable/enable auto deletion of these files. However considering that losslescut is not a portable app, I'm not sure I want the added code and maintenance that comes with that.