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

Project .csv output file include proper time marks and video filename #545

Closed
markusd1984 opened this issue Dec 11, 2020 · 15 comments
Closed

Comments

@markusd1984
Copy link

If one needs to share time marks a proper time format to be included in a separate columns would be useful.

image

As well as potentially having the source file name included in the first row so that ideally Load Project can auto load the source file as well (just like opening video first auto loads the project when present in same folder). Similar to #199 #181 #251.

image

@mifi
Copy link
Owner

mifi commented Dec 13, 2020

Yea, but I think if the project file is going to be more complicated than cutpoints (like file path, cut mode, track data etc), then we should use something like JSON instead. csv will be a hack for that. However I'm not sure if this is something most people need for a quick cutting tool.

@markusd1984
Copy link
Author

markusd1984 commented Dec 13, 2020

Human readable time marks within a .CSV can be easily read and shared with somebody (who might do further advanced video editing) rather then a JSON, that's why I proposed it.

(Currently one would have to take a screenshot/s of the segments list or write them manually down to do so).

Auto loading video via project file probably shouldn't need the full file path (just like it currently works the other way around looking for an existing .CSV file with same name as video), thus name in first row could be sufficient.

I doubt that more info besides filename, time codes, hour/minute marks and labels would be needed/beneficial, thus perhaps no need (yet) for JSON and better to maintain .CSV for readability?

@mifi
Copy link
Owner

mifi commented Dec 14, 2020

I think we can provide an "export project" option with a human readable CSV as one of the output formats.

@mifi
Copy link
Owner

mifi commented Dec 14, 2020

I agree that we could auto load video based on name pattern taken from the csv file when someone opens a CSV, but this is already what happens when someone opens a video and there is a corresponding CSV file

@mifi
Copy link
Owner

mifi commented Dec 14, 2020

Screenshot 2020-12-14 at 17 27 18

Screenshot 2020-12-14 at 17 25 24

mifi added a commit that referenced this issue Dec 14, 2020
@markusd1984
Copy link
Author

@mifi autoload video when open a project prevents the error message I shared above, that's why I would add that and because it's the most common way in other editors to open a project rather then video (to load a project) 😃

@markusd1984
Copy link
Author

markusd1984 commented Dec 14, 2020

@mifi Looks great, but TSV not CSV? 😀

I wouldn't call it human readable, this was more the term I used to differentiate hour/minute timestamps Vs timecode. Perhaps "timestamps" would be better.

@mifi
Copy link
Owner

mifi commented Dec 14, 2020

I think TSV is more readable than CSV because got natural spacing between the timestamps. CSV is more cramped. and most programs that can import CSV can also import TSV

@markusd1984
Copy link
Author

markusd1984 commented Dec 14, 2020

I see, yeah in my entire IT life never heard of TSV, people are mainly familiar with CSV just as they are with TXT thus just wondering if people might wonder why to export as "TSV" or "human readable." Anyway i'd recommend at least to change the wording to laymen terms.
I just saw in your screenshot that it seems to be a TXT file you exported?!? (Or do you mean a .txt in TSV format) lol

@mifi
Copy link
Owner

mifi commented Dec 14, 2020

Yea I changed the wording to "Timestamps (TSV)" instead of human readable. I can create one CSV option also, it's super easy. I was thinking that txt is easier for people to open in notepad or whatever. They might wonder about how to open a .tsv file if they don't have any app for it. If it's .txt they can just easily glace over the data there, or they can copy paste the data into excel or other programs and it will show up as columns automatically

@markusd1984
Copy link
Author

why not call it TXT then? 😀

"Timestamps (TXT)" makes more sense.

@mifi
Copy link
Owner

mifi commented Dec 14, 2020

Because TSV is also a well recognized format. I think "Timestamps (TSV/TXT)" is nice. and i allow saving both to .tsv and to .txt

@markusd1984
Copy link
Author

Brilliant

@quorten
Copy link
Contributor

quorten commented Jan 27, 2021

Relating to storing more info in a JSON project file format... For supporting the use case of generating the output video segment(s) via "command-line export" like Inkscape, the export/merge parameters would be additional useful information to store in a project file.

mifi added a commit that referenced this issue Aug 24, 2021
- Allow editing segment tags #427
- Store main project file as .lcc (JSON5 format), for future flexibility. existing CSV will still be loaded and converted to .llc #545
- Rename menu items to Export/import project (as we are not changing the save location) #593
@mifi
Copy link
Owner

mifi commented Aug 24, 2021

The newest version now saves the main project file as .llc which is a JSON5 format and it includes information like per-segment tags, and the name of the media file that it relates to. Can also open the .llc files directly if they are in the same folder as the media file, and losslesscut will open up the file with the segments at the same time. Closing this

@mifi mifi closed this as completed Aug 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants