Is there any way of getting Xnview to automatically determine YUV image dimension from the file size or the command line?
e.g. it would be very useful when opening a .yuv file, which is 829440 bytes say, to open this in Xnview as a 720x576 image.
I use this fantastic viewer a lot to view .yuv images and have to remember to update the yuv read dimension settings between the various image formats I work with (i.e. 720x576, 720x480, 1280x720, 1920x1080 etc. as well as my own oddball dimensions such as 256x256!)
It would be very nice if I could do this automatically.
Automatically determine YUV file dimensions?
Moderators: helmut, XnTriq, xnview
Re: Automatically determine YUV file dimensions?
Yes perhaps by haviong some "standard" YUV size. So which size are standard?Anonymous wrote:Is there any way of getting Xnview to automatically determine YUV image dimension from the file size or the command line?
e.g. it would be very useful when opening a .yuv file, which is 829440 bytes say, to open this in Xnview as a 720x576 image.
I use this fantastic viewer a lot to view .yuv images and have to remember to update the yuv read dimension settings between the various image formats I work with (i.e. 720x576, 720x480, 1280x720, 1920x1080 etc. as well as my own oddball dimensions such as 256x256!)
It would be very nice if I could do this automatically.
Pierre.
Here are some of the more common "standard" sizes which are most likely to use yuv files (i.e. TV/MPEG formats etc.) :
Single Field:
--------------
*720x240 = 345600 bytes
*720x288 = 414720 bytes
Interlaced/Progressive frames:
-----------------------------------
360x240 = 172800 bytes
360x288 = 207360 bytes
352x480 = 337920 bytes
360x480 = 345600 bytes
480x480 = 460800 bytes
528x480 = 506880 bytes
544x480 = 522240 bytes
640x480 = 614400 bytes
704x480 = 675840 bytes
720x480 = 691200 bytes
720x486 = 699840 bytes
*720x512 = 737280 bytes
352x576 = 405504 bytes
360x576 = 414720 bytes
480x576 = 552960 bytes
528x576 = 608256 bytes
544x576 = 626688 bytes
640x576 = 737280 bytes
704x576 = 811008 bytes
720x576 = 829440 bytes
720x608 = 875520 bytes
1280x720 = 1843200 bytes
1280x1080 = 2764800 bytes
1440x1080 = 3110400 bytes
1920x1080 = 4147200 bytes
*=format which has a matching size elsewhere in the list and IMHO should be the first considered with the other format considered as a custom one.
This is by no means an exhaustive list however and it would be extreemely useful if the user could add some additional sizes to the .ini file? (e.g. 256x256, 1024x1024 ... etc)
Thank you for considering this and I hope you will be able to add this support.
Single Field:
--------------
*720x240 = 345600 bytes
*720x288 = 414720 bytes
Interlaced/Progressive frames:
-----------------------------------
360x240 = 172800 bytes
360x288 = 207360 bytes
352x480 = 337920 bytes
360x480 = 345600 bytes
480x480 = 460800 bytes
528x480 = 506880 bytes
544x480 = 522240 bytes
640x480 = 614400 bytes
704x480 = 675840 bytes
720x480 = 691200 bytes
720x486 = 699840 bytes
*720x512 = 737280 bytes
352x576 = 405504 bytes
360x576 = 414720 bytes
480x576 = 552960 bytes
528x576 = 608256 bytes
544x576 = 626688 bytes
640x576 = 737280 bytes
704x576 = 811008 bytes
720x576 = 829440 bytes
720x608 = 875520 bytes
1280x720 = 1843200 bytes
1280x1080 = 2764800 bytes
1440x1080 = 3110400 bytes
1920x1080 = 4147200 bytes
*=format which has a matching size elsewhere in the list and IMHO should be the first considered with the other format considered as a custom one.
This is by no means an exhaustive list however and it would be extreemely useful if the user could add some additional sizes to the .ini file? (e.g. 256x256, 1024x1024 ... etc)
Thank you for considering this and I hope you will be able to add this support.