Quote:
Originally Posted by astronob
Hi,
Can someone advise me why QTinput doesn't seem to work with Avisynth+, when it was working fine with Avisynth?
This is how it outputs now in Avisynth+
|
I haven't had a chance to play with the sample you sent me yet, but I suspect 10 bit is an issue for QTSource.
Code:
Video
ID : 1
Format : YUV
Codec ID : v210
Codec ID/Hint : AJA Video Systems Xena
Duration : 13 s 280 ms
Bit rate mode : Constant
Bit rate : 221 Mb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 5:4
Frame rate mode : Constant
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 10 bits
Scan type : Interlaced
Scan type, store method : Interleaved fields
Scan order : Top Field First
Compression mode : Lossless
Bits/(Pixel*Frame) : 21.333
Stream size : 350 MiB (99%)
Language : English
Encoded date : UTC 2019-10-24 09:55:33
Tagged date : UTC 2019-11-13 06:32:06
Color primaries : BT.601 PAL
Matrix coefficients : BT.601
I hadn't considered that possibility until I saw the sample because you said it decodes the video fine when you're using Avisynth 2.6. Someone with more smarts than me will have to explain why that happens, because I don't understand it myself. I assume AvsPmod can display bit depths greater than 8 bit? I haven't had a chance to test that yet as I don't use AvsPmod much myself and I almost always work with 8 bit sources. Depending on your target playback device, you might have to convert it to 8 bit for encoding anyway. You're using mpeg2 encoding again for that one?