[BUG] Image sequence not working in new version

[BUG] Image sequence not working in new version - 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: [BUG] Image sequence not working in new version (/thread-1714.html)

Pages: 1 2

Image sequence not working in new version - Brutoloco - 02.02.2021

Windows x64 version

I can't encode videos from image sequence imput since last version: 2021.21.31.1

I'm using jpg images and trying to encode to x264.

I tried changing many options, executing with or without admin rights and misc.ini.

Always "Crashed with status 0"

Tried to encode to x265 and gives another error:

"-> 2021-02-02@10_24_20_6910_02_video crashed: ERROR: D:\Temp\2021-02-02@10_24_20_6910_02.265 was not created!
Aborting '2021-02-02@10_24_20_6910_02_video' due to: ERROR: D:\Temp\2021-02-02@10_24_20_6910_02.265 was not created!"

I have done this without problem with previous version 2020.12.13.1.

Thanks you

RE: Image sequence not working in new version - Selur - 02.02.2021

Looking at the Vapoursynth script used:

# Imports

import vapoursynth as vs

core = vs.get_core()

# source: 'D:/Edicion/098/000000.jpg'

# current color space: YUV420P8, bit depth: 8, resolution: 1440x1080, fps: 29.97, color matrix: 709, yuv luminance scale: full, scanorder: progressive

# Loading D:\Edicion\%01d98\000000.jpg using vsImageReader

clip = core.imwri.Read("D:/Edicion/%01d98/000000.jpg", firstnum=0)

clip = core.std.Trim(clip=clip, length=38841)

# Input color space is assumed to be RGB24

# making sure frame rate is set to 29.97

clip = core.std.AssumeFPS(clip=clip, fpsnum=30000, fpsden=1001)

# Setting color range to PC (full) range.

clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=0)

# adjusting output color from: RGB24 to YUV420P8 for x264Model (i420@8)

clip = core.resize.Bicubic(clip=clip, format=vs.YUV420P8, matrix_s="709", range_s="full")

# set output frame rate to 29.970fps

clip = core.std.AssumeFPS(clip=clip, fpsnum=30000, fpsden=1001)

# Output

clip.set_output()

I see no direct problem with the script. Aside from that folder name, which might cause problems with "ImageMagick Writer-Reader" source filter.
-> So my first advice would be to try whether chaning the folder name helps.

Looking at the encoding call:

"C:\Program Files\Hybrid\64bit\Vapoursynth\vspipe.exe" "D:\Temp\encodingTempSynthSkript_2021-02-02@10_40_08_0910.vpy" - --y4m | "C:\Program Files\Hybrid\64bit\x264.exe" --preset slower --crf 16.00 --profile high --level 4.0 --ref 5 --bframes 5 --sync-lookahead 12 --qpmax 51 --psy-rd 0.40:0.00 --aq-mode 3 --vbv-maxrate 25000 --vbv-bufsize 31250 --sar 1:1 --deblock 1:1 --demuxer y4m --input-csp yuvj420p --input-range pc --fps 30000/1001 --output-depth 8 --output "D:\Temp\2021-02-02@10_40_08_0910_02.264" -

everything looks fine too.

The error:

x264 output: y4m [error]: bad sequence header magic

usually means that something went wrong with the processing of the Vapoursynth script.
-> Does the Vapoursynth Preview work properly or does it show an error message?

Cu Selur

RE: Image sequence not working in new version - Brutoloco - 02.02.2021

(02.02.2021, 16:40)Selur Wrote: Looking at the Vapoursynth script used:

# Imports import vapoursynth as vs core = vs.get_core() # source: 'D:/Edicion/098/000000.jpg' # current color space: YUV420P8, bit depth: 8, resolution: 1440x1080, fps: 29.97, color matrix: 709, yuv luminance scale: full, scanorder: progressive # Loading D:\Edicion\%01d98\000000.jpg using vsImageReader clip = core.imwri.Read("D:/Edicion/%01d98/000000.jpg", firstnum=0) clip = core.std.Trim(clip=clip, length=38841) # Input color space is assumed to be RGB24 # making sure frame rate is set to 29.97 clip = core.std.AssumeFPS(clip=clip, fpsnum=30000, fpsden=1001) # Setting color range to PC (full) range. clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=0) # adjusting output color from: RGB24 to YUV420P8 for x264Model (i420@8) clip = core.resize.Bicubic(clip=clip, format=vs.YUV420P8, matrix_s="709", range_s="full") # set output frame rate to 29.970fps clip = core.std.AssumeFPS(clip=clip, fpsnum=30000, fpsden=1001) # Output clip.set_output()
I see no direct problem with the script. Aside from that folder name, which might cause problems with "ImageMagick Writer-Reader" source filter.
-> So my first advice would be to try whether chaning the folder name helps.

Looking at the encoding call:

"C:\Program Files\Hybrid\64bit\Vapoursynth\vspipe.exe" "D:\Temp\encodingTempSynthSkript_2021-02-02@10_40_08_0910.vpy" - --y4m | "C:\Program Files\Hybrid\64bit\x264.exe" --preset slower --crf 16.00 --profile high --level 4.0 --ref 5 --bframes 5 --sync-lookahead 12 --qpmax 51 --psy-rd 0.40:0.00 --aq-mode 3 --vbv-maxrate 25000 --vbv-bufsize 31250 --sar 1:1 --deblock 1:1 --demuxer y4m --input-csp yuvj420p --input-range pc --fps 30000/1001 --output-depth 8 --output "D:\Temp\2021-02-02@10_40_08_0910_02.264" -
everything looks fine too.

The error:

x264 output: y4m [error]: bad sequence header magic
usually means that something went wrong with the processing of the Vapoursynth script.
-> Does the Vapoursynth Preview work properly or does it show an error message?

Cu Selur

Vapoursynth Preview didn't load at that configuration. I click it, and do nothing. That's the first thing I found about this bug. Then, I realize that I could not encode anything coming from an imput of "image sequence".

I uninstalled hybrid and installed previous version, encoded the same file with no problem. I'm sure is something with the new version. Maybe some default config? I don't know.

I'm also asking here if someone is being able to encode image sequence using last version.

Ty

RE: Image sequence not working in new version - Selur - 02.02.2021

Okay, I think I know what I going wrong.
When I load an image sequence with frame 00001.jpg to 00430.jpg
Hybrid creates:

# Loading E:\sequence\jpg\0000%1d.jpg using vsImageReader

clip = core.imwri.Read("E:/sequence/jpg/0000%1d.jpg", firstnum=1)

clip = core.std.Trim(clip=clip, length=430)

which causes an error in Vapoursynth Preview for me:

Failed to evaluate the script:

Python exception: Trim: last frame beyond clip end

No clue why.
I even get this when calling:

clip = core.imwri.Read("E:/sequence/jpg/0000%1d.jpg", firstnum=1)

clip = core.std.Trim(clip=clip, last=10)

only when I remove the 'Trim' the whole thing works.

Since I didn't really change anything in the code (at least intentional) so no clue atm. what could have changed.
-> looking into it some more

Cu Selur

RE: Image sequence not working in new version - Selur - 02.02.2021

I see the problem the "0000%1d.jpg" part is wrong.
For me image sequence starting with 00001.jpg and ending with 00430.jpg it should be "%05d".
This probably happens due to some changes related to Qt6.
-> will look into it.

Cu Selur

RE: Image sequence not working in new version - Brutoloco - 02.02.2021

(02.02.2021, 18:18)Selur Wrote: I see the problem the "0000%1d.jpg" part is wrong.
For me image sequence starting with 00001.jpg and ending with 00430.jpg it should be "%05d".
This probably happens due to some changes related to Qt6.
-> will look into it.

Cu Selur

Hi,

I do not understand much about programming, but I just focus on this issue didin't happen in the previous version.
That limits the issue about something different between 2020 13 dec and next (actual) 2021 jan 31. Maybe it helps finding the issue.

Ty

RE: Image sequence not working in new version - Selur - 02.02.2021

I switched to Qt6 with the latest version and they changed how RegularExpressions work.
-> I know what the issue is. I know where the issue is, just need a bit to write some code to fix it. Smile

Cu Selur

RE: Image sequence not working in new version - Selur - 02.02.2021

Think I fixed it know.
Will send you a pm with a link to a dev version for testing in ~15min.

Cu Selur

RE: Image sequence not working in new version - Brutoloco - 02.02.2021

(02.02.2021, 19:33)Selur Wrote: Think I fixed it know.
Will send you a pm with a link to a dev version for testing in ~15min.

Cu Selur

Dev version works. Many thanks.

RE: Image sequence not working in new version - kirkland - 04.02.2021

(02.02.2021, 20:06)Brutoloco Wrote:
(02.02.2021, 19:33)Selur Wrote: Think I fixed it know.
Will send you a pm with a link to a dev version for testing in ~15min.

Cu Selur

Dev version works. Many thanks.

I am having the exact same error message when trying to encode an image sequence. Can I get a link to the dev build as well?
thanks so much Big Grin