-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Feature request] Ask about how to convert unsupported file upon opening #595
Comments
I am looking for the similar, only i want the default be the one that will play audio and that is not the fastest one per my experience. Currently, often it convert to the fastest format without audio which is useless for me so this way there have to do one more conversion manually from the file menu (can be confusing to the newbie user). Maybe the best would be if the app shows the dialog upon detecting unsupported file. |
@Rubens10010 LosslessCut is supposed to do this automatically when it detects an unsupported file. What file is this? @slrslr I agree that it makes sense to ask about this. Maybe it could even be a configurable setting. |
@mifi Thanks for your time. I took a random shot available on https://drive.google.com/file/d/1kRHiPx9K-LsTZ4Vyr1Bg-8mWXwugyia5/view?usp=sharing. When I drag it to LosslessCut it loads and app screen gets black, sound plays normally. This was taken with a Lg Bello II. |
It seems like your file has mpeg4 video, I don't think it's supported by Chrome/Chromium (used by llc). I will try to add a check for this file type and auto convert to supported format |
Ok. I reported this bug in Chromium as well. Thanks for your support I will be waiting for next update. |
please try the suggestions first (e.g. change format to matroska) |
Hi I've been using this amazing app for a long time now but I was wondering if you could provide some sort of option to set a default convert format for unsupported codecs. Currently I have to go to file > convert to supported format > fastest - every time.
The text was updated successfully, but these errors were encountered: