Search options

Downgrading to PotPlayer 64bit 1.7.22129 as per the ThreeDeeJay PotPlayer site didn't fix the issue.
I am able to get it working properly with PotPlayer VapourSynth script if I do the following.
Set the MVC 3D Transfer Mode to "Synthesized View: TAB/SBS at half resolution" followed by stopping restarting the video, then once the video is playing selecting Input Source "Full Resolution" twice (the first time it doesn't seem to work).
I don't like this solution because it means it's going to be generating a synthetic half resolution video before stretching it back (thus defeating the point).
But it just goes to show it works.
I looked into the vapuursynth script and I made some minor changes.
Irregardless of whether one selects half/full for "Synthesized View: SBS at half/full resolution" the "clip.width" seen by base.py is always 1920.
It should I believe be getting a clip.width of 3840 when Synthesized View: SBS at full resolution" is selected, but it is not....

I did the same test with avisynth and I get the same issue it shows 1920 as the width regardless of if Synthesized view is full or half width.
```
input2 = input.Subtitle("Width: " + String(input.Width()), size=60)  # Display the width
interpolate(input2)
```

Now for the interesting part.
For AVISynth If I disable the entries in "filter control" "custom filter manager".
And just add a simple subtitle to show the clip width in the inline avisynth logic it prints out the correct width 3840 for synthesized full width and 1920 for synthesized half width.
```
input = potplayer_source()
input2 = input.Subtitle("Width: " + String(input.Width()), size=60)  # Display the width
input2
```

And also for VapourSynth, same thing a custom added script properly shows the correct clip width and height for full and half transfer sizes.
```
import vapoursynth as vs

core = vs.core
clip = video_in
text = f"Width: {clip.width}"  # Get the width
clip = core.text.Text(clip, text, scale=6)  # Display the width with a larger font

clip.set_output()
```

Looking at the generated vapoursynth script the issue seems to be that.
```clip = VpsFilterSource.std.Trim(length=5000000)``` is getting a clip which always has 1920 irregardless of the transfer type half/full.
Meanwhile internal vapour_synth scripts to potplayer itself get a clip width that correctly matches the transfer type half/full.

I tried to load the script into potplayers varpoursynth plugin script location that change "clip = video_in". Then I proceeded to try and empty base.py in hopes that maybe it would work. But for whatever reason PotPlayer crashed, perhaps because SVP was still trying to load the second VapourSynth script and causing problems, or perhaps because the DLL cannot be loaded from within a VapourSynth script typed directly into PotPlayer..

At this point I'm at a bit of a loss. If the author of SVP wants to chime in and let me know why he thinks.
VpsFilterSource.std.Trim(length=5000000) is returning a different width from what the internal scripts get from "video_in"
I'm happy to try testing afew more things until my 30 day trial runs out.

Hey Greg,

One other update, regarding PotPlayer there is actually an installer script written by ThreeDeeJay
https://github.com/ThreeDeeJay/PotPlayer3D/releases
In his 1.2 release notes he said the following.
"""Updated PotPlayer to 240315(1.7.22128) (32-bit, as required by SVP) - ⚠️ Version 240509+ broke 3D SBS layout detection so SBS view looks quadrupled and manually changing it doesn't work, so avoid updating unless it was fixed, though you can always just run the script again to downgrade."""
This issue sounds similar to what you described as your problem with PotPlayer, you may want ot try downgrading to 240315(1.7.22128) (32-bit) and see if that fixes your issue (I havent tried it just yet).

Hey Greg,

I saw a post a month ago that detailed how to get "half 4k 3d" resolution on many 3d capable 4k projectors using a custom resolution with ToastyX CRU tool.
I can't find the original post I read, but I found a similar post that is pretty good.
You may want to check it out, getting the pixel clock and timings just right is difficult otherwise you can get tearing.
If I were buying a new 4k 3d capable projector I would definitely try that with SVP and see if you can get amazing results
half resolution 4k at 60 hz for 3D would be something special I have no doubt
https://www.avsforum.com/threads/setup- … r.3291217/
I didn't get a chance to try SVP just yet as I'm waiting for a period where I will have a few days to take full advantage of the 1 week trial to try and get it working right!
EDIT:
I think I found the original link I had read I'll post it here for completeness (it's by the same guy who would have guessed this guy is pretty rigorous in his documentation just like you).
https://www.avsforum.com/threads/playin … e.3289889/