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.
It is a constant battle with youtube / yt-dlp to get the audio and video codec and container you want. Being able to see all of that information in the resulting media file in the "Raw Attributes" section would be very handy.
Describe the solution you'd like
In the "Raw Attributes" area print the:
Video Codec we got
Audio Codec we got
Container format we got
Video Resolution we got
other things like Bit rate, frame rate, audio bit rate, etc would be cool too.
Stretch goal would be amazing to see this as columns of data on the lists on the Home Page Media History page and the Source > Downloads page so you could see this info for all videos at once, but I realize this is a bigger ask.
Describe alternatives you've considered
The only current alternative is go find the file on the drive via file explorer and look at it's attributes, this is pretty tedious when you are checking more than a couple.
An alternative might be linking the file path to the local file (or the parent folder). Honestly this might be a nice feature on it's won.
Additional context
Came to this request because after I requested #411 and I figured out some custom arguments that mostly work to ensure I have the container + codecs I need I realized it's tedious to manually check them.
Thanks!
The text was updated successfully, but these errors were encountered:
I like the idea, but I'm not sold one way or the other about putting this in-app at the moment. Things like resolution are an easier sell, but I'll have to think about whether adding details about specific codecs benefits enough users for it to be worth the effort. I also don't know if yt-dlp gives me that information reliably post-download or if I'll have to use ffmpeg to determine this information
Anyway, I'll leave this issue open while I look into it! There are several other features and bugfixes I need to look at first, but I'll let you know once I have had time to dig deeper 🤙
Hi - No problem, Understood. thanks for considering it!
I actually didn't think you would have to do either of those, since PinchFlat already has RW access to the local file system where it's downloading and already printing some of that info like the file paths I figured it would already have access to that info
I actually didn't think you would have to do either of those, since PinchFlat already has RW access to the local file system
It all depends on whether the file's metadata OR the output from yt-dlp can be trusted in all cases. I haven't checked, but one hypothetical is that yt-dlp wouldn't take certain post-processing operations into account, leading to misleading output. If that's the case then I'd have to actually check the available tracks/container using FFmpeg for the most accurate details
Again, this is all hypothetical until I dig deeper. Maybe the metadata of the file will be very accurate, but I just don't know that at the moment 🤷♂️
Is your feature request related to a problem? Please describe.
It is a constant battle with youtube / yt-dlp to get the audio and video codec and container you want. Being able to see all of that information in the resulting media file in the "Raw Attributes" section would be very handy.
Describe the solution you'd like
In the "Raw Attributes" area print the:
other things like Bit rate, frame rate, audio bit rate, etc would be cool too.
Stretch goal would be amazing to see this as columns of data on the lists on the Home Page Media History page and the Source > Downloads page so you could see this info for all videos at once, but I realize this is a bigger ask.
Describe alternatives you've considered
The only current alternative is go find the file on the drive via file explorer and look at it's attributes, this is pretty tedious when you are checking more than a couple.
An alternative might be linking the file path to the local file (or the parent folder). Honestly this might be a nice feature on it's won.
Additional context
Came to this request because after I requested #411 and I figured out some custom arguments that mostly work to ensure I have the container + codecs I need I realized it's tedious to manually check them.
Thanks!
The text was updated successfully, but these errors were encountered: