The following warnings occurred: | ||||||||||||||||||||||||||||||||||||||||||
Warning [2] Trying to access array offset on null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.3.12-nmm1 (Linux)
|
[HELP] Unexpected behavior with importing and exporting as image sequence - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [HELP] Unexpected behavior with importing and exporting as image sequence (/thread-3666.html) |
Unexpected behavior with importing and exporting as image sequence - RRINN - 08.04.2024 This happened with the latest Windows version of Hybrid as of writing from the official site, Hybrid 2024.04.06.1, with the Torch and vsgan models installed, if that matters.
Basically, I have this video with some parts, especially frames with dark areas, with massive banding all over it. Since it's hundreds of frames we're talking about here, I thought Hybrid would be a very nice tool to do batch debanding on these images so I tried the Flash3kDB under Vapoursynth, left the parameters at default, tested on just one frame in Hybrid, and thought hmm...looks good enough. But since I'm inputting and outputting image sequences, and possibly because I did something wrong, Hybrid is not outputting image sequence as expected; it is not outputting to the output I have set but instead left the VPY script in the folder and all the results in my %temp% with filenames that I am not preferring as results so a simple copy & paste is not an option. I thought I could maybe create some sort of script to batch rename them but I prefer to see if this is something that can be fixed by posting in the forum, just to see if it's a bug or I'm the idiot one here. By the way, the same behavior was presented when I input and output as single image too when I was testing the deband filter.
Below is how I did everything.
All the images that were debanded looked nice. Loved it, the filter is working well. But damnit, they are all in %temp% and I think their filenames are in an order but as in 00000001_1_001.png, 00000001_1_002.png, and so on. And in the folder I set for the output, is a single VPY file. I don't know why but my guess is that this is either an unexpected behavior, or it's because of the way I did everything, especially the output part. Right now, I'm doing a workaround where I will just output everything as an FFV1 MKV and then extract their frames as PNG. RE: Unexpected behavior with importing and exporting as image sequence - Selur - 08.04.2024 Trying to reproduce the problem. I did the following:
=> I can reproduce the problem, will look into where the cause of the problem is. Cu Selur RE: Unexpected behavior with importing and exporting as image sequence - Selur - 08.04.2024 Send you a link to a dev version, via pm, which should fix the problem. Cu Selur RE: Unexpected behavior with importing and exporting as image sequence - RRINN - 08.04.2024 First of all, thank you for entertaining my post but oh my goodness you are terrifyingly and impressively responsive. I received the dev version via PM and yeah it did fix the output issue but the naming scheme is still something like 00000001_1_%03d.png. Is there a way to enforce it so that it does not change the filenames from the input? I tried something like %08d.raw but Hybrid will always suffix that last part to the names. Once again, thank you. RE: Unexpected behavior with importing and exporting as image sequence - Selur - 09.04.2024 There is no way to tell Hybrid to use the same numbers as the source, you can enable 'PNG->Number as name' to tell to only use numbers as the name. Cu Selur RE: Unexpected behavior with importing and exporting as image sequence - RRINN - 09.04.2024 I didn't mind the small inconvenience but yeah, I don't know how did I not see the Number as name checkbox there. Will try that out later since I'm already done with the crap I've been working on here. |