VSEDIT crash

[george84]

The following script crashes VSEdit r19 on Windows 10 on doing preview. There shortly appears an empty preview and then VSedit exits.

import vapoursynth as vs
from vapoursynth import core
x = core.imwri.Read("C:/Users/Walter/Documents/SMIL/BSG23/testsuite/media/testchart1/testchart1.png", firstnum=0, mismatch=False, alpha=False)
x = x * 120
x=core.resize.Bicubic(clip=x, format=vs.YUV420P8, range_in_s="full", transfer_in_s="linear", matrix_s="709",  transfer_s="709", primaries_s="709", range_s="full")
x = x.text.ClipInfo()
x.set_output()

It seems to be caused by specifying primaries

primaries_s="709"

. When this parameter is left out the script works.

[poisondeathray]

I can reproduce crash when primaries_in_s="unknown" (to 709 in your case) . If you specify primaries_in_s along with primaries_s - it doesn't crash ( or unknown to unknown doesn't crash either)

[Myrsloik]

Originally Posted by poisondeathray

I can reproduce crash when primaries_in_s="unknown" (to 709 in your case) . If you specify primaries_in_s along with primaries_s - it doesn't crash ( or unknown to unknown doesn't crash either)

Is this something that can be reproduced without VSEdit? Also specify VS version.

[ChaosKing]

Originally Posted by Myrsloik

Is this something that can be reproduced without VSEdit? Also specify VS version.

There is not output in vspipe (silent crash). No problems if the resize line is commented out.

[Myrsloik]

Originally Posted by ChaosKing

There is not output in vspipe (silent crash). No problems if the resize line is commented out.

Will be fixed in the next release which should happen quite soon due to how annoying this kind of thing is.

[Myrsloik]

Grab R47 RC1 and verify that it's fixed.

[ChaosKing]

Hmm I can't start vsedit with R47-RC1. No Window, nothing. Restarted PC just in case.

EDIT

And vspipe shows now with core.std.BlankClip().resize.Bicubic(format=vs.YUV420P8, transfer_in_s='709', matrix_s='709', primaries_s='709')

Error: Failed to retrieve frame 0 with error: Resize error: Resize error 3074: no path between colorspaces (0/8/2 => 1/1/1). May need to specify additional colorspace parameters.

Is this correct?

[Myrsloik]

Re-download rc1. I sneakily fixed a bug.

[ChaosKing]

Originally Posted by Myrsloik

Re-download rc1. I sneakily fixed a bug.

vsedit is working now, but the resize error is still present. What does "no path between colorspaces (0/8/2 => 1/1/1)" mean exactly?

[Myrsloik]

Originally Posted by ChaosKing

vsedit is working now, but the resize error is still present. What does "no path between colorspaces (0/8/2 => 1/1/1)" mean exactly?

That you didn't specify primaries and so on for the input. For input that's not correctly flagged you need to specify everything.

[jackoneill]

Originally Posted by ChaosKing

And vspipe shows now with core.std.BlankClip().resize.Bicubic(format=vs.YUV420P8, transfer_in_s='709', matrix_s='709', primaries_s='709')

Error: Failed to retrieve frame 0 with error: Resize error: Resize error 3074: no path between colorspaces (0/8/2 => 1/1/1). May need to specify additional colorspace parameters.

Perhaps you meant to write "transfer_s" instead of "transfer_in_s"?

[ChaosKing]

Originally Posted by jackoneill

Perhaps you meant to write "transfer_s" instead of "transfer_in_s"?

It was just copy&paste, but it works with transfer_s now