pass arguments to yt-dlp in SimpleYoutubeDLGui.py #3
Comments
|
This is the main repo where I work on this app. I'm heavy at work on another app, but I'll see if I can't get this updated for what you need early next week. |
|
I'd like for you to test this in the latest build This is not ported over to FFMPEG Audio Encoder yet, I made the standalone update here to test and improve it. Going to close this comment, but will be looking forward to hearing back from you on this matter EDIT: When using the new entry box, it needs to be in the format as you requested value:key (value colon key, no spaces) |
|
Great, it works. The protected video can be downloaded. However, may I suggest to be able to put multiple values in there. So: The User-Agent is a bit more complicated since the key contains semicolon and therefore must be in quotes. Actually, initially I thought of a possibility to pass any ytdl argument. Examples: Thanks so far. |
Keep in mind, I'm not using the CLI version of yt-dlp. This is built around the python module, it's calling to it directly. |
|
Have you seen my bigger version of the tool? That actually runs with the CLI? https://github.com/jlw4049/Youtube-DL-GUI Maybe we should be focusing on improvements for this one. This SimpleYoutubeDLGui, was meant to be just that, simple. I could improve either one of them to do anything, but as far as run the CLI commands easily, it would probably be best to focus the other tool. |
|
Well the Use-Case I originally had in mind is to re-encode the audio track of a downloaded video with FDK AAC or QAAC encoder. The video is mainly interview style, so having a portable audio track allows for taking it with me on my smartphone. I wasn't aware of the way the Simple GUI works, but I totally get it now why passing the arguments wont work. In the end only the most basic switches shall be there. Having support for multiple HTTP Header is sufficient. I tried the Youtube-DL-GUI and for the protected video it shows "WARNING: [generic] Could not send HEAD request to [url]: HTTP Error 403: Forbidden" already when clicking on "Add Link". With the Simple GUI the [url] is straight accepted, even keeping the new HTTP Header input field empty. Sure, the bigger version does also benefit from being able to customize HTTP Header. I see a "View Command" Button in that tool. Being able to manually edit the command would be sufficient I guess. |
|
Do you think it would be best, we turn our attention on working on the larger version of the app? |
|
fine for me, as the link can#t even be parsed there |
I can work on it and make that a non issue. Is there anyway you can share this link or a "protected" link with me for testing purposes? |
|
|
|
Thanks, I am able to produce the error on both simple and the larger CLI version of the app. The Simple version of the app just handles the error differently and loads the link for you. I'll try to get around to this today! |
|
I'm sorry as work on the other app took much longer then I originally planned. Is this still something you are interested in? |
|
As my download needs are covered by now it's not of much relevance to me personally. Would be rather a question of how feature rich you want that software to be, to the good of all other users. |
|
Would a custom command line section be of use to you with the GUI? |
Is your feature request related to a problem? Please describe.
In order to be able to freely control yt-dlp behaviour, especially the download and geo-unblocking options, a input field for command line arguments passed to yt-dlp shall be provided.
Describe the solution you'd like
I'd like to set the argument
--add-header "Referer:<some_url>"to download a specific video via yt-dlp that is hosted on a cdn that checks the Referer HTTP Header to be a specific url.The text was updated successfully, but these errors were encountered: