Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. Domains: forum.doom9.org / forum.doom9.net / forum.doom9.se |
|
|
#1 | Link | |
|
Registered User
Join Date: Aug 2025
Posts: 6
|
Newbie seeking help with QTGMC 'memoryview' error on 1080i50 source
Hey guys,
I'm a beginner trying to get my head around a VapourSynth script and I've hit a wall. I've been wrestling with it for a while now, got some of the basics put together from reading forums and with AI assistance, but I'm completely stuck on a persistent error that seems to be above my paygrade. My goal is to do a proper archival encode of a clean 1080i50 HDTV rip. The plan is to deinterlace with QTGMC, decimate it back to single rate, and then reverse the PAL speed-up to restore the original 23.976 fps. Afterwards, I want to run some light post-processing for minor chroma bleed and blocking before piping it all to ffmpeg with the audio slowed to match. The weird thing is, the script actually works perfectly fine if I use a simple QTGMC(Preset="Fast"). But as soon as I try to use a higher quality preset like "Slower" or "Very Slow", the script immediately fails with vapoursynth.Error: argument val was passed an unsupported type (memoryview). The error always happens when the clip is passed from QTGMC to the next filter in the chain. I've tried every sanitizing trick I could find, from core.std.Expr(clip, "x") to forcing a YUV->RGB->YUV conversion right after QTGMC, but nothing seems to touch this error. It feels like the slower presets are outputting a frame format that's just fundamentally incompatible with other plugins. A sample from the HDTV rip (cut losslessly with ffmpeg, the original is a .ts file): https://files.catbox.moe/k3p33g.mp4 Here's the script that's failing. Quote:
So I'm really hoping someone here might have seen this memoryview issue before and knows the proper way to handle the output from QTGMC's more advanced modes. I'm also open to any feedback on the post-processing chain itself. Is AWarpSharp2 a reasonable choice for the minor chroma bleed on a clean digital source? And is DFTTest(sigma=1, tbsize=1) a good call for trying to preserve the film grain as much as possible? Also, maybe I should use some kind of fake grain plugin. Do you know any that would be well-suited? I feel like I'm so close to getting this to work but I'm just missing a key piece of the puzzle. Any help or advice would be hugely appreciated. Thanks. |
|
|
|
|
| Thread Tools | |
| Display Modes | |
|
|