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

Allow custom filename #96

Closed
johnnyinthedark opened this issue Sep 27, 2018 · 20 comments
Closed

Allow custom filename #96

johnnyinthedark opened this issue Sep 27, 2018 · 20 comments

Comments

@johnnyinthedark
Copy link

Hello! I want to express my gratitude for Lossless Cut. It's great for Replays during live events. @mifi could you please add the ability to rename output files? I need the output to be called exactly like the original file, without any numbers or markings.

Thanks!

@mifi
Copy link
Owner

mifi commented Sep 30, 2018

So you want it to overwrite the input file?

@reefhound
Copy link

I second this request, perhaps for other reasons. I don't foresee outputting the same filename myself (perhaps to another folder?) but would like more control over the clip naming schema. In general, I would like to see more options and settings, including ability to retain settings or provide in startup (i.e. Keyframe Clip mode)

Btw, the filenaming by clip times is one of the main reasons I went with Lossless Cut. It saves a ton of time versus typing a name to "save as" every clip. It does result in rather long filenames making it clumsy to view in file explorers. I can't imagine a clip being over an hour so the hours slot is about six wasted characters. The seconds to three decimal places is overkill.

But to be honest, a good start might be a simple checkbox to append clip times to filename (default checked), and an option to output clips to same folder as original (default) or a specified folder. That would preserve existing behaviour.

@ccoenen
Copy link

ccoenen commented Jan 8, 2019

It would be awesome to have something like Shift+E which would pop up some kind of input field pre-filled to the "regular" export name (input-intime-outtime.ext), BUT with the cursor right before the .ext. This way, one could add a short note to the filename. Then my clips would not be weirdly numbered, but could contain the reason I cut this clip with very little overhead.

Summarizing: instead of input-intime-outtime.ext
I could have: input-intime-outtime-some-custom-note.ext

(i'm not for overwriting without HUGE HONKING WARNINGS, though, see #95)

@mifi
Copy link
Owner

mifi commented Jan 10, 2019

Good idea @ccoenen ! It’s something i want to look into

@katodevin
Copy link

I would also love the ability to set a custom file name. Like the OP, I would simply like for it to be the same file name - but output to a different folder of course.

mifi added a commit that referenced this issue Nov 26, 2020
I don't know why I did that.
Sorting of segments can now be done from the menu
@mifi mifi mentioned this issue Jan 18, 2021
@ChicagoScanningMG
Copy link

I also would like custom file name output. I don't like all of the info that's automatically appended to the end of split files. I have a full renaming workflow I use AFTERWARD and the appended information interferes with my renaming software's ability to search for the source name to pull the correct information to rename the file to.

For example, I have a spreadsheet set up with "File_001, File 002, File 003, etc" and the corresponding FULL names in another column, "File_001_Full Name, "File_002_Full Name", etc. When information is appended to the file, such as, "File_001-00.00.01.067-00.35.16.080-seg1" it makes my renaming workflow more difficult. I also don't need to see the trimmed clip information in the file output name.

To plus 1 another comment, I wouldn't MIND being able to overwrite the source file, but that's not really best practice. i think it would be better to have the option to "Create Output Folder in Source Directory." That way you can retain the original file, and you don't need to worry about file name collision.

@ChicagoScanningMG
Copy link

Lastly, I see there was a concern of multiple clips being made from a master clip. I think the ideal solution would be to have to the first clip use the master clips name, then additional clips get appended with simple numbers, so, "File_001", File_001_001", "File_001_002", etc.

There's probably a more elegant solution, but that would satisfy my issues.

@ChicagoScanningMG
Copy link

Sorry, one final comment. If it's too much to ask to change the appended text on the file name, at the VERY least, I'd like to change the delimiting character. That is, the cutting information is appended with the leading character "-". if I could specify which character is used to separate the suffix, I can account for that in my renaming software.

@mifi
Copy link
Owner

mifi commented Jan 21, 2021

It could be a text field prefilled with the input name plus the appended suffix
if the input file is my-file.mp4, the default input field could be:
my-file{{DEFAULT_SUFFIX}} (which becomes my-file-00.00.04.448-00.00.14.833-seg1.mp4)
...then allow the user to change this text and have some variables to choose from:

  • {{LABEL}} - the segment's label (safely formatted for file names).
  • {{CUT_FROM}} e.g. 00.00.04.448
  • {{CUT_TO}} e.g. 00.00.14.833
  • {{SEG_NUM}} e.g. 1
  • {{EXT}} e.g. .mp4

We could also allow adding a subpath, e.g. output/to/my-file{{DEFAULT_SUFFIX}}, then the app will auto-create the folder structure leading to the path (relative to output dir) before outputting the file(s).

Should have some validation:

  • filename cannot contain any of these special variables
  • if more than one segment is exported, validate that each file name will be unique
  • check that output name is not the same as input name
  • ...

@mifi
Copy link
Owner

mifi commented Jan 23, 2021

this is now implemented and can be tested in the next version!

Screenshot 2021-01-23 at 22 49 44

@mifi mifi closed this as completed Jan 23, 2021
@ChicagoScanningMG
Copy link

Brilliant! Thanks!!!!

@masvil
Copy link

masvil commented Feb 17, 2021

Amazing implementation, hat off.

@msdobrescu
Copy link

When using cue, for example, the file names and file tags could be based on the contained meta-information, like track number, performer, track title, album title, year. Why not use that too?

@shinnlu
Copy link

shinnlu commented Jul 30, 2021

how to show export options again?
i want to use SEG_NUM instead of timecode, after tested i click on the icon "show export options screen before exporting", the filename change back to timecode, and export options icon disappear.
截圖 2021-07-30 上午11 01 04

sorry, i just found that, open the Advanced View and the export options appeared.

@mattack1
Copy link

Can I have it output in the same folder as the original file? (Possibly rename the original file to NAMEORIG.suffix
or whatever, as an option)

I want to effectively edit "in place" since I had the files in the original place I wanted them.. (and all of the cut point info is irrelevant to me in the filename). I'm usually just saving the musical portion(s) of a talk show/SNL.

@mifi
Copy link
Owner

mifi commented Aug 23, 2021

to output to same folder as original file, just press the button, then select "cancel" in the dialog. I have now improved that so there is a separate button for clearing output directory, see #805

@mattack1
Copy link

But you mean I have to do that for EVERY single file? I want it to just default to the same location....

@mifi
Copy link
Owner

mifi commented Aug 24, 2021

I'm not sure if I undertsand. If the button says "working dir unset", then losslesscut will always save the output file to the same directory as the source file, and you don't need to do anything for every new file.

@plk0507
Copy link

plk0507 commented Sep 4, 2022

Can someone give directions on how to rename the file output or delete the add-ons entirely? Thank you.

@mifi
Copy link
Owner

mifi commented Sep 4, 2022

Not possible yet. See #938

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests