• Thanks: 1

Topic: "[W]: NameError(\name 'null' is not defined\)" then SVP disabled?

SVP event log from recent playback.  Everything looked fine for a while.  I even played through an episode of a TV show without issue using ffdshow raw filter playback in MPC-HC with MadVR.

16:29:08.448 [i]: VideoPlayer: new ffdshow video [1104f4] in mpc-hc64.exe (64-bit) [MPC-HC 1.9.18.0] on screen 0
16:29:08.554 [i]: Media: video 1280x640 [PAR 1.000] at 25.000 fps
16:29:08.554 [i]: Media: codec type is AVC, YUV/4:2:0/8 bits/BT.709 BT.709
16:29:08.557 [i]: Playback: starting up...
16:29:08.561 [i]: Playback [1104f4]: Frame server (64-bit) 3.7.2.0, AviSynth+ 3.7.2 (r3661, 3.7, x86_64), C:\WINDOWS\SYSTEM32\avisynth.dll
16:29:08.562 [i]: Playback [1104f4]: resulting video frame 1280x640
16:29:08.563 [i]: Playback [1104f4]: 1 acceptible profiles, best is 'Automatic' [0]
16:29:08.565 [i]: Playback [1104f4]: enabled while video is playing
16:29:08.566 [i]: Profile: using automatic profile #1 /film
16:29:08.568 [i]: Playback [1104f4]: playing at 75 [25 *3/1] 
16:49:06.932 [W]: NameError(\name 'null' is not defined\)
17:15:23.871 [i]: ffdshow: remove instance [1104f4]
17:15:23.876 [i]: Playback [1104f4]: disabled while video is paused
17:15:24.178 [i]: Playback [1104f4]: deleted

Any idea what this line is about?

16:49:06.932 [W]: NameError(\name 'null' is not defined\)

I've seen it before.  Have had SVP disable itself periodically too, but this is the first time I noticed this message was at the top of the log just after noticing the disabled OSD message.  I sometimes play videos in the background while I do other stuff, so I don't always see the changes immediately.

Re: "[W]: NameError(\name 'null' is not defined\)" then SVP disabled?

this looks like a Python error message coming from SVPtube
then it is not related to the video playback at all

3 Reply by EternalStudent (edited by EternalStudent 05-04-2022 05:50:28)

  • Thanks: 1

Re: "[W]: NameError(\name 'null' is not defined\)" then SVP disabled?

OK.  Wish the sources for each line were a little more obvious, but thanks for reading through.

Is there somewhere else I can see why it disabled itself?

I'd been running that latest version of Avisynth+ v3.7.2 for a bit, but ended up returning to 3.5.1 (though the logs say 3.5.0).  Things seem more stable so far with this older version.  Which in my mind points to an issue somewhere to fix...

Is there an Avisynth+ log I can enable?  Or more verbose information from SVP?

I have a bug up for my issues playing back with AvsF (freezes or gives green screen) instead of ffdshow raw (works).  They mentioned having me test without SVP, but I didn't know how.  I'll go back and look at that bug soon.

Wish I could see and mess around with the SVP4 code.  Even just for the manager/control panel smile.  I'm pretty sure I hit the same issue adding that openCL/openGL compatibility layer a year or two ago, and had forgotten.  I'd like to code up some protection in the GPU detection/selection feature.

For now I just removed my second 1080ti as I never seem to use it anymore.  And disabled the onboard 4600 Iris as it's not getting used instead automatically.  Everything always goes to my "primary" 1080ti with the screen attached.


(update)

Yeah, playback with AvsF worked fine minus SVP.  I've asked if they can suggest anything further to debug this stuff, but I think they're going to wash their hands of the issue.