VOGONS


Reply 180 of 204, by Kahenraz

User metadata
Rank l33t
Rank
l33t

I'm but sure how this got derailed so quickly. My question was asking about past builds, since there used to be Windows binaries available. Building from source for Windows is not as easy as pressing a button, especially if the code has diverged for so long. This was noted even by the author.

vvbee wrote on 2023-10-16, 17:06:

If it was hard to find someone to port it to Windows a few versions ago then it'll be harder now, I'll say that much.

Also this seemed to imply that someone else may have been maintaining a Windows release. I'm but familiar with this project, and I was just trying to figure out why I couldn't find the binaries that used to be available, or if I wasn't looking in the right place.

vvbee wrote on 2023-08-18, 17:44:
mrgreen wrote on 2023-08-18, 07:57:

Hello, I would like to get the Datapath VisionRGB-pro card.
Is this software and its drivers compatible with Windows 7 (32 or 64 bits)?
Regards

Currently, no. It's available for Linux, which the VisionRGB-PRO has no drivers for. Earlier versions of VCS support the PRO and Windows XP and upwards, they're available as source code but are deprecated. Someone's maintaining a Windows version of VCS as a separate project.

Reply 181 of 204, by luckybob

User metadata
Rank l33t++
Rank
l33t++

I'm but sure how this got derailed so quickly.

I made an offhand, flippant comment about the linux community, and several people took it seriously.

It is a mistake to think you can solve any major problems just with potatoes.

Reply 182 of 204, by DLR

User metadata
Rank Newbie
Rank
Newbie

I've been trying to get a hang of Linux and how to get the VCS running on it. No previous experience so a bit lost every now and then.

I'm running:
Ubuntu 22.04.3 LTS
opencv-4.9.0
Qt Creator 12.0.2 (6.6.0)
Kit: Desktop Qt 6.7.0 MinGW 64-bit
vcs-3.4.3

I've got as far as building it in QT Creator but while doing it I run into these errors:

Multiple uint errors like this:

\\wsl.localhost\Ubuntu\home\henskelit\vcs-3.4.3\src\display\display.h:151: error: 'uint' does not name a type; did you mean 'int […]
Show full quote

\\wsl.localhost\Ubuntu\home\henskelit\vcs-3.4.3\src\display\display.h:151: error: 'uint' does not name a type; did you mean 'int'?
In file included from ../vcs-3.4.3/src/capture/capture.h:40,
from ..\vcs-3.4.3\src\capture\alias.cpp:9:
../vcs-3.4.3/src/display/display.h:151:102: error: 'uint' does not name a type; did you mean 'int'?
151 | void kd_show_headless_assert_error_message(const char *const msg, const char * const filename, const uint lineNum);
| ^~~~
| int

Something else:

👎 error: [Makefile.Release:7055: generated_files/src/capture/alias.o] Error 1

Warning:

\\wsl.localhost\Ubuntu\home\henskelit\vcs-3.4.3\src\common\disk\file_readers\file_reader_video_presets_version_b.cpp:143: warnin […]
Show full quote

\\wsl.localhost\Ubuntu\home\henskelit\vcs-3.4.3\src\common\disk\file_readers\file_reader_video_presets_version_b.cpp:143: warning: loop variable 'propName' of type 'const string&' {aka 'const std::__cxx11::basic_string<char>&'} binds to a temporary constructed from type 'const char* const' [-Wrange-loop-construct]
..\vcs-3.4.3\src\common\disk\file_readers\file_reader_video_presets_version_b.cpp: In function 'bool file_reader::video_presets::version_b::read(const string&, std::vector<video_preset_s*>*)':
..\vcs-3.4.3\src\common\disk\file_readers\file_reader_video_presets_version_b.cpp:143:37: warning: loop variable 'propName' of type 'const string&' {aka 'const std::__cxx11::basic_string<char>&'} binds to a temporary constructed from type 'const char* const' [-Wrange-loop-construct]
143 | for (const std::string &propName: kc_supported_video_preset_properties())
| ^~~~~~~~
..\vcs-3.4.3\src\common\disk\file_readers\file_reader_video_presets_version_b.cpp:143:37: note: use non-reference type 'const string' {aka 'const std::__cxx11::basic_string<char>'} to make the copy explicit or 'const char* const&' to prevent copying

Tried to include different int's in the code but none of it helped. Have I missed a step or is some of the libraries/software I'm using incompatible?

Reply 183 of 204, by vvbee

User metadata
Rank Oldbie
Rank
Oldbie

Install Ubuntu 20.04 in a VM and build it there, might be less trouble. Use Qt 5 and GCC 9. Somebody can make and distribute an appimage.

VCS 3.5.0 adds rudimentary support for digital cameras via gPhoto2. I don't know the use case, maybe put VCS on a Pi and strap it with an LCD onto your old camera to get focus peaking in your previews.

Reply 185 of 204, by Kahenraz

User metadata
Rank l33t
Rank
l33t

It seems so. I did not think to make a fork.

Does anyone have an old copy of the repo?

Reply 186 of 204, by vvbee

User metadata
Rank Oldbie
Rank
Oldbie

My interest in doing FOSS from the poverty line got to 0 as far as this project goes. It's valuable work so giving it away for nothing for years on end is just demented in this situation, but charging for it isn't an option either. As far as I'm concerned I'll hatch it as a private project and see where it goes in the future.

Reply 187 of 204, by Tree Wyrm

User metadata
Rank Newbie
Rank
Newbie

That's quite unfortunate. Thanks for all the effort put into the project. Not sure how to react on a sudden closing of the repository, so I won't. Let's hope it gets resurrected at some point, perhaps back for windows too.

Reply 188 of 204, by elszgensa

User metadata
Rank Member
Rank
Member

In the meantime, if someone needs a copy, I found some forks containing changes up to 19.2.2023 and 9.4.2024.

Reply 189 of 204, by biggestsonicfan

User metadata
Rank Newbie
Rank
Newbie

Greetings all.

I went to find my issue I filed on vcs as I had listed commands to quickly build it using cmake, however I was sadly surprised to find it deleted by the owner, as described above.

I saw the mrehkopf fork and decided to challenge myself. After about a week of banging my head on QTCreator and MSYS2 (and returning from dependency hell) I had a build that ran in Windows. (See attached)

However, as you can see, it can't actually talk to the capture card. This is most likely due to the fact I had to use the

CAPTURE_BACKEND_GENERIC_V4L

instead of

CAPTURE_BACKEND_VISION_V4L

capture source definition, as the official datapath headers use

#include <sys/ioctl.h>

, which is a control device and not available via Mingw. A workaround will have to be figured out.

Also, I mention dependency hell because this thing relies on a lot of external libraries. I began a static build of vcs, but ran into issues trying to statically include OpenGL into the executable.

Reply 190 of 204, by SquallStrife

User metadata
Rank l33t
Rank
l33t

Hello Datapath owner friends!

I'm attempting to switch to Linux for my content creation stuff, and thought VCS might be the final piece of the puzzle, but there is something fishy going on.

Some modes, such as DOS 80 col text, just result in the text "UNKNOWN" with a timer that updates in 500ms increments. The VCS interface recognises it as 720x400@70Hz, but just no picture. Higher resolutions are OK, except 800x600 specifically for some reason, which has the same behaviour. This applies whether using either an analogue or digital source. If I put my OSSC in the middle, using Line2X for all modes, then most modes are restored except 800x600.

Using the V4L2 source directly in OBS allows ALL modes to be viewed, but the fine adjustments (h-pos, phase, etc) are nowhere to be found, and some modes (e.g. 1280x1024) are significantly offset to the right.

Using the VisionRGB utility in WIndows has zero of these issues.

Interestingly, the "Vision" sample tool provided by Datapath is highly unstable, and brings down the entire system when it crashes!

I'm using Kubuntu 24.04LTS, KDE Plasma X11, kernel is 6.11.(something).

I spent 4 hours on this last night, and the only solution I came up with was to flee back to Windows 🙁

Am I missing something? Or is Datapath just a second-class citizen on Linux?

VogonsDrivers.com | Link | News Thread

Reply 191 of 204, by Kordanor

User metadata
Rank Member
Rank
Member

Datapath is a second class citizen on Windows as the VCS software is no longer developed there and only on Linux afaik.
The Datapath itsef...I continue using it (in Windows, don't have Linux), but just for "recording" basically and all the scaling is being done by my retrotink which also converts it to hdmi.
The one exception where I continue using VCS is for 320x200 games, but not for scaling, but for the pixelgate. This is doing an excellent job in the software and I have not seen any other means via OBS or Retrotink4k to do the same job. Especially with modern AV1 codec any noise is getting amplyfied in recordings. The VCS Pixelgate helps a lot there.

Reply 192 of 204, by NightSprinter

User metadata
Rank Member
Rank
Member

Even with VCS in Linux, Datapath cards just are not worth considering anymore. Even with VCS, I have encountered numerous hard-freezes with the system whenever a resolution change happens. That, plus Datapath is excessively-slow AT BEST when it comes to updating their Linux drivers. When they do, it's ONLY to support Ubuntu LTS releases.

Reply 193 of 204, by vvbee

User metadata
Rank Oldbie
Rank
Oldbie

Maybe the new drivers are dropping support for features, or some motherboard incompatibility, the E series is very old now. Run QEMU with an older distro and pass the card to it.

Reply 194 of 204, by SquallStrife

User metadata
Rank l33t
Rank
l33t
vvbee wrote on 2025-07-13, 11:21:

Maybe the new drivers are dropping support for features, or some motherboard incompatibility, the E series is very old now. Run QEMU with an older distro and pass the card to it.

I spent quite a bit of time on this, and unfortunately the E2S doesn't seem like it's able to work this way. Something to do with how it's technically a PCI-to-PCI bridge chip with two discrete devices behind it.

QEMU barfs if you try to pass both "inputs" because it thinks one conflicts with the other. You can do just one, but then the VisionRGB kernel module complains because there "should be two" and the other isn't responding.

I've resorted to hosting the card in another computer and piping the video over NDI to my main computer. This solution is working really well, with negligible impact on latency or quality. Currently using the Vision app on Windows, later I'll try an older Linux with VCS, as the auto switching profiles are a god-send!

VogonsDrivers.com | Link | News Thread

Reply 195 of 204, by NightSprinter

User metadata
Rank Member
Rank
Member

Will be curious as to your results, and what steps are required both to get direct RGB 480i/576i to work on these cards, and how to keep resolution changes from hard-locking the machine in Linux.

Reply 196 of 204, by SquallStrife

User metadata
Rank l33t
Rank
l33t

I'm investigating three approaches.

First, run VCS in Windows, add a Window Capture source to OBS, and add the "NDI Output" filter to that source. This works very well, but is not performant on my capture system: Core i7 4770k with only iGPU. The video arriving by NDI is not smooth. I'm unsure why though, the CPU and GPU load are not high at all, perhaps a memory bottleneck? This is preferred for the "capture box" setup, as I can use VCS presets and filter chains.

Next is exporting the DirectShow device directly over NDI, using the "Desktop Capture" applet in NDI Tools (despite the name, it also allows to export one DShow device or "webcam" in high quality at source resolution and frame rate). This provides no access to the input settings however, so I'm writing a small C# application against the RGBEasy API (rgbeasy.dll), to expose them. It allows you to alter the parameters, even though the capture is going a different route. The C# app may have a WinForms interface, or maybe a simple web based thing, not sure yet. Windows only until I find the right library to access these functions in Linux. This is highly performant, let down only by the configurability aspect.

The last is to further pursue the virtualisation avenue. Apparently there is a way to virtualise the entire IOMMU group as a unit, instead of trying to pass the individual PCI devices. Though I haven't been able to unravel this yet, it would allow me to run a VM with Vision 7.27, kernel 5.x, Qt5, and VCS without the missing modes and system crashes I was experiencing before. To reiterate, this is only complicated because my device, the E2S, is a composite device, consisting of a PCI-PCI bridge and two capture 'cards', together in one IOMMU group, sharing a single IRQ. A single-input card shouldn't have this issue, and such a setup would be delightfully straightforward. This route would still need something like NDI to get the video out of the VM and into OBS on the host, but my desktop is a Ryzen 9 7900X with the Radeon iGPU, much more grunt than the i7 above.

The latter may not be possible without a setup more complicated than libvirt and virt-manager alone can facilitate, I may need to pursue Proxmox or something like that.

The icing on the cake, is that as of Vision 7.28, the dkms module does not compile on kernels 6.14+ out-of-the-box. The change is that the driver does no longer supports so-called realtime Linux kernels. Even though the default kernel in popular distributions probably are not compiled with RT enabled, there is a comment in the .config file, which the VisionSDK script detects and fails on. Removing the comment allows the module to compile and the script to succeed. Issues still exist though: https://gist.github.com/mrehkopf/1100b88178ae … 9d71f5610f08256

Anyhow, more work is needed, but I'm learning a lot in the process! 😀

VogonsDrivers.com | Link | News Thread

Reply 197 of 204, by havli

User metadata
Rank Oldbie
Rank
Oldbie

I am using RGBVision E2S with VCS very often (almost daily) as a virtual monitor for my retro PCs, benchmark rigs and other stuff. Everything works perfectly. I am running old Datapath drivers from 2018 or so because I don't like the driver update flashes firmware on the card... so on all my PCs and all capture cards (I have several) I use just this one driver version.

The PC is running Windows 10 but from my brief testing Windows 11 was also fine, even with this old driver.

The rest of the PC is Ryzen 7 7700 and Asus B650E-F Gaming Wifi. The capture card is connected to the chipset pci-e lanes. I also tried another AM5 board where the card was connected to the CPU pci-e lanes, ran fine too.

HW museum.cz - my collection of PC hardware

Reply 198 of 204, by SquallStrife

User metadata
Rank l33t
Rank
l33t

It's peachy on Windows yeah, for sure.

I don't use Windows on my main PC any more though. That's the problem I'm trying to solve. 😀

VogonsDrivers.com | Link | News Thread

Reply 199 of 204, by Kahenraz

User metadata
Rank l33t
Rank
l33t
havli wrote on 2025-07-22, 06:55:

I am using RGBVision E2S with VCS very often (almost daily) as a virtual monitor for my retro PCs, benchmark rigs and other stuff. Everything works perfectly. I am running old Datapath drivers from 2018 or so because I don't like the driver update flashes firmware on the card... so on all my PCs and all capture cards (I have several) I use just this one driver version.

The PC is running Windows 10 but from my brief testing Windows 11 was also fine, even with this old driver.

The rest of the PC is Ryzen 7 7700 and Asus B650E-F Gaming Wifi. The capture card is connected to the chipset pci-e lanes. I also tried another AM5 board where the card was connected to the CPU pci-e lanes, ran fine too.

Is there a problem with the new firmware? I didn't have any issue with flashing mine.