-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal data stream error when trying to render interlaced video as interlaced stream (v0.7.2) #118
Comments
I've tested this with interlaced videos in the past and IIRC it's worked. There might've been some code changes so I'll test it again, but it would be helpful if you shared the video that you're having trouble with. There is a difference between telecined and interlaced videos, and I haven't tested the former. |
The videos are encoded as an MPEG-2 interlaced stream and they are true interlaced, by telecined I meant NTSC-RS assumes they are telecined. The Use field setting is greyed out when a video that NTSC-RS guessed is telecined is selected and cannot be changed until you open another video, so maybe it was disabled for a reason, but idk.
It's not just a specific video, it seems to be all videos encoded as an interlaced stream, at least with the MPEG-2 codec anyway. Neither NTSC or PAL spec video was rendered without giving an error though. I have to go now, but I'll do some additional testing to see if maybe only MPEG-2 interlaced streams fail to render. |
I've confirmed that ntsc-rs doesn't work with telecined video; this will be fixed in the next release. Here's an MPEG-2 interlaced video that ntsc-rs correctly recognizes as interlaced and not telecined. Can you share any example of these "MPEG-2 interlaced streams" that are showing up as telecined in ntsc-rs but interlaced when their metadata is inspected with e.g. ffmpeg? |
Here's a short clip I recorded with my camera (Sony DCR-SX34E) a while ago, as an example for something that fails to render in NTSC-RS. M2U00259.zip |
Hey, I downloaded the new version of NTSC-RS because I saw that my bug was fixed in it, and... Additionally here's the preset I'm trying to use, incase it throws an error over some effect being enabled, or I don't know |
I'm not sure either; I'll have to investigate more. I can reproduce the issue with the video you sent, but if I re-encode the video using ffmpeg, it gets properly recognized as interlaced and renders with no issue. It may be a GStreamer bug. |
Can confirm, happens for me too (tried re-encoding as Quicktime and x264
and
the re-encoded versions were made from a
UPDATE: Okay, i tried clicking the "Render" button out of frustration; it worked... |
If I try to render an interlaced (encoded as interlaced) video in NTSC-RS with the Use field setting on Interleaved, and set Interlaced output to true in the render settings, NTSC-RS gives the following error: Error creating pipeline: Internal data stream error.
I have tried both NTSC and PAL resolution interlaced videos, but neither of them renders at all.
Probably what causes this is that interlaced videos all get detected as "telecined" by NTSC-RS as far as I have seen and that might mess some stuff up and cause this error. Trying to render a progressive video (both encoded as progressive and detected by NTSC-RS as progressive with the Interlaced output setting will not give any errors.
Pretty funny because I would guess the interleaved mode is there for actual interlaced content.
![annoying issue with ntsc-rs](https://private-user-images.githubusercontent.com/71499525/337926332-26aaeb8d-39e3-4184-9cfa-bc50ac04b0ca.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ4MDYwODUsIm5iZiI6MTcyNDgwNTc4NSwicGF0aCI6Ii83MTQ5OTUyNS8zMzc5MjYzMzItMjZhYWViOGQtMzllMy00MTg0LTljZmEtYmM1MGFjMDRiMGNhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI4VDAwNDMwNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPThhNjk1MjcyMGM2YTA0MzhmMDVkNjgzNGEzY2Y2MDk5YzI5ZWQwNDY1YzQ1ZmMxYjNhMWExNWEyNmZiYzNlMTYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.2F4nmdte8-vjNypksBlQcOdGXOgkCCMIfeKWdhfFHn0)
The text was updated successfully, but these errors were encountered: