This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[HELP] No preview window
#61
Uploaded a new dev (Hybrid_dev_2025.07.20-161323) which hopefully helps.
Deinstall old Hybrid before installing it.
=> let me know if this version works for you.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#62
Yes, no preview window with no filters. I've been using progressive source material for the past few weeks, it's the same case - no preview.

Will report back shortly on the new dev, thanks again for trying to fix this. Smile



Sadly it's still the same - the preview window pops up displaying grey, then the window quickly closes.
Reply
#63
Hmm,.. running out of ideas.

It can't be:
  • caused by libmvtools like I first assumed, since the latest dev only comes with the older libmvtools.
  • that vsViewer doesn't find the portable Vapoursynth (that comes with Hybrid), since the latest dev comes with a vsviewer.config and properly displays the version info.
  • any other filtering, since you checked that Vapoursynth Script View does not show that anything aside from the source filter:
    # loading plugins
    core.std.LoadPlugin(path="<Hybrid>/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll")
    # Import scripts
    import validate
    gets loaded.
  • a general Windows 10 issue since it does work fine on my updated Windows 10 laptop.
So it's either:
  • the source filter,
  • some general Vapoursynth issue, or
  • something interfering (could be a background service)

What happens if you:
  1. create a test.vpy file with the following content:
    # Imports
    import vapoursynth as vs
    # getting Vapoursynth core
    import sys
    import os
    core = vs.core
    # loading plugins
    core.std.LoadPlugin(path="C:/Program Files/Hybrid/64bit/vsfilters/SourceFilter/LSmashSource/LSMASHSource.dll")
    # Source: 'S:\Nasties-2398-IN\Trailer 28 MinutesHB.mp4'
    # Current color space: YUV420P8, bit depth: 8, resolution: 720x576, frame rate: 23.976fps, scanorder: progressive, yuv luminance scale: limited, matrix: 470bg, transfer: bt.709, primaries: bt.601 ntsc, format: AVC
    # Loading S:\Nasties-2398-IN\Trailer 28 MinutesHB.mp4 using LibavSMASHSource
    clip = core.lsmas.LibavSMASHSource(source="S:/Nasties-2398-IN/Trailer 28 MinutesHB.mp4")
    clip.set_output()
  2. open that file in vsViewer and press F5
  3. open a Terminal Window inside "C:/Program Files/Hybrid/64bit/Vapoursynth" and then call:
    VSPipe.exe "PATH TO the test.vpy" NUL -c y4m --progress
  4. open a Terminal Window inside "C:/Program Files/Hybrid/64bit/Vapoursynth" and then call:
    VSPipe.exe "PATH TO the test.vpy" --info
  5. Does it make a difference if you open the TaskManager and check that under processes no other 'Apps' are running when using Hybrid?

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#64
Opening VsViewer at first says:

[Image: Screenshot-2025-07-21-151451.png]

It then briefly opens (grey) and the quickly closes.

[Image: Screenshot-2025-07-21-151917.png]

[Image: Screenshot-2025-07-21-152024.png]
Reply
#65
Quote:open a Terminal Window inside "C:/Program Files/Hybrid/64bit/Vapoursynth"
your Terminal was opened in "c:\Users\Admin" Angel
then first enter
cd "C:/Program Files/Hybrid/64bit/Vapoursynth"
before you do the vspipe calls.
Also you need to replace
"PATH TO the test.vpy"
with the actual path to the test.vpy, in example:
"c:\Users\Admin\Desktop\test.vpy"
Angel
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)