Open pedro-nonfree opened 9 months ago
Thanks for this valuable discussion. Initially, dividing into audio and video was prepared for potential file processings, such as inserting screenshots, converting to GIFs, etc., where audio and video might differ. However, at present, there is no substantial difference between these two.
This seems leading to unnecessary complications. Merging audio
and video
into one media
could be feasible. In the future, if there is a need to distinguish between different types of processing, it might be more appropriate to differentiate based on the file extension rather than the link type.
I need to think about whether there are other issues and how to make it compatible with older versions.
Congratulations on the autoinsert timestamp feature, it is very useful
I was using it in an audio file, but it was not doing the auto timestamp insertion. I forced timestamp insertion with
i
and then it did the following link:nil:~/path/to/audio.aac
which it's the case for commit https://github.com/yuchen-lea/org-media-note/commit/bde775c08da29987c7c4959d024e5c383ea72bd9 , the problem is that aac audio extension was not recognized as audio link, and it is fixed for PR https://github.com/yuchen-lea/org-media-note/pull/44Looking at the problem, I had some questions that I wanted to share with you guys:
then I think, is it relevant to separate audio from video? what about just a media link? something such as org-media-note or omn: ? Maybe separating what can only be video to video, audio to audio, and the containers to media?
Anyway, that was just thinking out loud, for me, the most important thing is to have the autoinsert timestamp feature working most of the time, and I think that will be the case from now on today :)