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
describe the feature you'd like to see
It would be great if there was a way to specify fallback quality selections or codecs for downloads, or at least some sort of order of preference. Something I'm currently trying to do is pull down the highest resolution video I can get up to a limit.
Something along the lines of "vQuality": "<=480" or "vQuality":["480","360","144","worst"] would be nice. Alternatively, something like "best[<=480]" would be great for this particular situation as well.
A similar fallback array system for vCodec and aFormat would be ideal too. I'm doing some weird stuff with ffmpeg and it'd be ideal to have a little more control over things in the request directly rather than just getting an ambiguous 400 error
Maybe providing the valid qualities, formats, etc in the error could be useful for the UI?
describe alternatives you've considered #571 is the only real alternative to this, but IMO it's a bit less elegant and requires more requests than this
The text was updated successfully, but these errors were encountered:
describe the feature you'd like to see
It would be great if there was a way to specify fallback quality selections or codecs for downloads, or at least some sort of order of preference. Something I'm currently trying to do is pull down the highest resolution video I can get up to a limit.
Something along the lines of
"vQuality": "<=480"
or"vQuality":["480","360","144","worst"]
would be nice. Alternatively, something like"best[<=480]"
would be great for this particular situation as well.A similar fallback array system for
vCodec
andaFormat
would be ideal too. I'm doing some weird stuff with ffmpeg and it'd be ideal to have a little more control over things in the request directly rather than just getting an ambiguous 400 errorMaybe providing the valid qualities, formats, etc in the error could be useful for the UI?
describe alternatives you've considered
#571 is the only real alternative to this, but IMO it's a bit less elegant and requires more requests than this
The text was updated successfully, but these errors were encountered: