Project (segments, cut points) import as a text with custom syntax (currently only from file?)

[slrslr]

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

That is a lot of operations. Maybe one day, there will be a function to import cut times in a custom format (like "15.12-15.46 19.27-19.49") or a "speech to AI" which would set the segments automatically after i say: one minute fifty one seconds to one minute fifty five seconds and/then [segment2times].
#2941

Hello, currently it takes around 17 operations (mouse clicks, keyboard keys pushed) to create one segment (based on above linked discussion). Losslesscut allows to reduce this to 3 operations by importing .csv file with a segments/cut points definition https://github.com/mifi/lossless-cut/blob/master/docs/index.md#csv-files but to create the CSV file it also needs some operations on your computer (3-4) + remembering and typing all the syntactical characters.

It would reduce number of operations if user can paste or drag & drop cut points definitions as a text from their text editor/clipboard. Sample definition/syntax one may like to paste:

12:45-15:13 1:15:18-01:22:16
12.45-15.13(segment 1) 1.15.18-01.22.16(segment 2)
12m45.900s-15m13s[scene1] 1h15m18s-01h22m16s

Someone is used for separating minutes and seconds using : other using .
Someone uses space around "-"

Maybe LC "Segments" menu and/or File>"Import project" menu entry can launch a new window, where user would be able to

1. select predefined syntax they would like to use (last used syntax remembered)

2. create new syntax:
   Hours (n digits)
   Separator: input field here
   Minutes (1-2 digits)
   Separator: input field here
   Milliseconds (1-3 digits)
   Separator: input field here (optional)
   Segment label (optional)

It may be handy if above defined syntax may generate preview so user knows he entered it according to their plan:
12:45-15:13 1:15:18-01:22:16
12.45-15.13 1.15.18-01.22.16 segment label

3. paste (using button and or Ctrl+V, or even drag & drop the text?) into the input box (which would be focused with typing cursor so user does not click into the field in order to make it accept Ctrl+V content) their definition of a segments to create (e.g. 12:45-15:13 1:15:18-01:22:16). Validation of input either instant with highlighting where is the error or after the window closes (which would require user to again open the import window and again paste the input and then attempt to fix it).

Notes to internal syntax validator:

• can tolerate additional spaces around separators and at the end and the beginning of the user input.
• if user enters 99 as milliseconds, LC would round consider it as 990 so the matching is less strict.
• user is not forced to enter milliseconds (000 or 999 is used)
• 01 and 1 would both translate to 01
• if user omits hours, 00 hours would be used for less strict matching

General notes:
It would be handy if the import window is assigned a shortcut. Workflow would be like:
Ctrl+i, Ctrl+v, Enter, LC jumps to a first segment start.

[qupig]

A. Where does your timestamp data come from?

B. You can use external AI tools to convert your custom format to any format that can be imported.

C. Use external AI Agent.

LLC already supports the import of quite a few common open formats, and I don't think the method you suggest is any easier than other existing methods.

[slrslr]

A. Watching the videos on a different device using different player.

B. Good idea, though not everyone is technical/skilled enough to use AI tools allowing to save recurring AI project to turn multiple files segment cut-points definitions into a downloadable set of project files (i usually process tens of files for which i have segments written down), so these files can be copied into appropriate director(y/iess) and used in LC. Bothering with AI prompt to generate project file for 3 segments file may be time-ineffective comparing to just ability to copy paste my custom format as mentioned:
Ctrl+i, Ctrl+v, Enter, LC jumps to a first segment start.

And i disagree with you, IMO mine shown process (one line up) is more effective than bothering to open right folder, create empty project file, open it for editing, write right syntax - i always forget it, save, import project file). For some people is easier to just write down cut points in their own way.

Yes, alternative approach is not to write down cut points, but instead watch videos in LC(LLC) and make segments there during watching. Not everyone does it this way.

[reregaga]

@slrslr I also use a different time recording system for video segments when watching them in a video player, so I faced the same problem as you, but creating the functionality you mentioned would require the user to know Regex and write them, since ultimately it would come down to the user writing rules for themselves that would convert their syntax into the syntax understood by ffmpeg (00:00:00.000). Essentially, this is a kind of renaming of timestamps, and it resembles file renaming; for example, DoubleCommander has such a feature multirename, but there the user writes the Regex for themselves, and DC simply applies it to the files. How many LosslessCut users are willing to learn Regex?

Isn't it easier to write in CSV format right away, which supports all the features you mentioned?

Notes to internal syntax validator:

• ✅can tolerate additional spaces around separators and at the end and the beginning of the user input.
• ✅ if user enters 99 as milliseconds, LC would round consider it as 990 so the matching is less strict.
• ✅ user is not forced to enter milliseconds (000 or 999 is used)
• ✅ 01 and 1 would both translate to 01
• ✅ if user omits hours, 00 hours would be used for less strict matching

Right now, LosslessCut understands this CSV entry (use in File > Import projects > Time in seconds (CSV)):

 3:2.99 , 5:9,
00:45:00.123,46:4,

In summary, I think this would be a useful feature that would add customizability; for example, it would help those users who write timestamps on their smartphones (it's tedious to type a colon on the smartphone keyboard and a dot is easier), but I think few developers will consider it a priority, and therefore it won't be implemented for a long time...