You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
By default, MakeMKV makes some basic track selections for audio and subtitle tracks. These selections are not necessarily the best options for all users.
Reading the MakeMKV forums provided the answer in the form of a profile file, which contains a new track selection.
By Default ARM should be using a track selection for MakeMKV that is all-inclusive. It should include all audio and all subtitle tracks, regardless of language or audio quality/channels. Why, because Handbrake, the second step in the ARM process offers a far more convenient way of creating profiles using their GUI.
Describe the solution you'd like?
So the feature is two-fold.
Create a custom, ARM specific MakeMKV profile and use that as the default one.
Allow the user to create their own MakeMKV profile file and then upload it to ARM using the ripper settings screen in arm.
The new Option in Ripper Settings could be MAKEMKV_PROFILE_FILE which is a browse field allowing the user to upload a new file and for ARM to use that as the profile for future rips.
This can be done via makemkvcon --profile={ValueOfNewFild} when calling MakeMKV from ARM.
Describe alternatives you've considered?
I have been doing this manually by creating a new profile, uploading it to my /home/arm directory and then using the MKV_ARGS field inside arm.yaml
Anything else?
Links to the MakeMKV forums that are present in the new Wiki page that was pulled a few days ago.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is this feature missing in the latest version?
Is your feature request related to a problem? Please describe.
By default, MakeMKV makes some basic track selections for audio and subtitle tracks. These selections are not necessarily the best options for all users.
Reading the MakeMKV forums provided the answer in the form of a profile file, which contains a new track selection.
By Default ARM should be using a track selection for MakeMKV that is all-inclusive. It should include all audio and all subtitle tracks, regardless of language or audio quality/channels. Why, because Handbrake, the second step in the ARM process offers a far more convenient way of creating profiles using their GUI.
Describe the solution you'd like?
So the feature is two-fold.
The new Option in Ripper Settings could be MAKEMKV_PROFILE_FILE which is a browse field allowing the user to upload a new file and for ARM to use that as the profile for future rips.
This can be done via
makemkvcon --profile={ValueOfNewFild}
when calling MakeMKV from ARM.Describe alternatives you've considered?
I have been doing this manually by creating a new profile, uploading it to my /home/arm directory and then using the MKV_ARGS field inside arm.yaml
Anything else?
Links to the MakeMKV forums that are present in the new Wiki page that was pulled a few days ago.
Code of Conduct
The text was updated successfully, but these errors were encountered: