Virtual Cam Plugin 2.0.5 not working with OBS 28
- Thread starter ramraver
- Start date
-
- Tags
- #obs28 #vcam #virtualcamera
we have same problems here. May I know how to install the old version and what version is that, please?
deFrisselle
Member
You should check with plugin dev for those you use before updating Not all plugins are updated to work with 28 yet
Should have read the notice that popped up when OBS updated
Should have read the notice that popped up when OBS updated
As you can see, my initial question was what users who need more than 1 vcam can do now. You have an answer to that? Fenir said in June he is not going to release updates on vcam 2.0.5. So as far as i know there is no vcam that gives you more than 1 instance.
deFrisselle
Member
Then it's a dead plug-in You're stuck using the previous update till it is no longer supported Though you may have issues if other plugins you use only update to support V28 as you will have to use the older versions
You could look for external programs that will create a virtual webcam that OBS can pick up as a webcam or try to get others to develop the plugin
You could look for external programs that will create a virtual webcam that OBS can pick up as a webcam or try to get others to develop the plugin
People depend on these "dead" plugins. Often non technical people. Most software maintains backward compatibility. From looking at the forum, this new update seems to have broken far too many things for far too many people to have been released without very explicit warnings on what will work and what will not. It almost seems like a new version entirely, like moving to Windows 7 from Windows XP.
Puuhbear
New Member
you can easily revert back to version 27.2.4 by downloading and installing here: https://github.com/obsproject/obs-studio/releases
and the next time an update "warning" appears don't just click it away ;)
and the next time an update "warning" appears don't just click it away ;)
I didn't update, still on the older version, but good advice. I only wish Microsoft would do the same, but they enforce updates with little regard for what they break.
However, the problem with using the older version it is is not going to be a viable solution in the long term because it will date rapidly. Apart from security fixes, any new plugins or existing ones that get updated may not work. The new user who comes along in a year from now needs the virtual camera with sound or more than one virtual camera won't know how to proceed, where to get the older version of plugins etc. I suppose this is a generic problem with plugins compared to a monolithic non-extensible package. Could we perhaps put all the plugins (the major ones at least) in the same place as the version of OBS they are compatible with and archive it somewhere?
However, the problem with using the older version it is is not going to be a viable solution in the long term because it will date rapidly. Apart from security fixes, any new plugins or existing ones that get updated may not work. The new user who comes along in a year from now needs the virtual camera with sound or more than one virtual camera won't know how to proceed, where to get the older version of plugins etc. I suppose this is a generic problem with plugins compared to a monolithic non-extensible package. Could we perhaps put all the plugins (the major ones at least) in the same place as the version of OBS they are compatible with and archive it somewhere?
Brookers55
New Member
The big question is WHY did the developers update OBS when they knew a lot of plugins would not work with it? Surely they should have checked that there is backwards compatibility. As a result they just end up annoying a lot of users.
Puuhbear
New Member
well... first of all it IS a new version... hence the new version number 28!
second, why would a software developer take care of plugins that seem abandoned for so long? that way you can never evolve!
third: they reported the changes really early and had long testing phases and open beta tests. every plugin developer had plenty of time updating. and a lot of them did!
second, why would a software developer take care of plugins that seem abandoned for so long? that way you can never evolve!
third: they reported the changes really early and had long testing phases and open beta tests. every plugin developer had plenty of time updating. and a lot of them did!
It hasn't been abandoned for so long. The developer was planning not to update it in June. That's only 2 months ago and as I said earlier, the reason was the plugin was so good the developers tried to mainstream it around stepping 26. Regrettably, they didn't really understand what it was being used for and didn't include sound in the main branch version nor multiple outputs, so in fact the official replacement was not a functional replacement, only a partial one. However, its creation undermined the rationale for updating the plugin the developer had developed. I tried making the point at the time but because the plugin still worked, it wasn't deemed sufficiently important to restore the missing functionality in the core software.
The effect of updating to the new QT had been to break the functionality still supported by the old plugin and that means the user community who depended on that it can't update beyond 27, at least not until the situation changes.
The effect of updating to the new QT had been to break the functionality still supported by the old plugin and that means the user community who depended on that it can't update beyond 27, at least not until the situation changes.
deFrisselle
Member
It's not the OBS devs job to manage the plugins It's the job of the plugin devs to keep up on OBS development Testing against alpha and beta releases while they follow OBS development It's all documented Other plugins managed it
I really despair at your attitude ddFrisselle. You are basically saying yah boo to users like me and many others. The problem this time has been such a big change has broken many plugins real users use and all I see at the moment are schadenfreudesque comments like that, that add absolutely nothing and are clearly intended to upset those people impacted.
Supporting plugin updates is in the interest of developers because without the plugins and the user community, OBS would be nothing compared to what it is now. It would be a little used app, if it survived as a project at all. Plugins provide features that attract users and that use in turn attracts investment in the project, makes developers feel their work is worthwhile and introduces new developers. That is why the developers have tried to help ensure plugins work.
So, in practice there is an obligation on both sides, from the main developers not to change too much too often that it puts a burden on the plugin developers and on the plugin developers to continue support if the can. Sometimes they can't for many reasons.
Supporting plugin updates is in the interest of developers because without the plugins and the user community, OBS would be nothing compared to what it is now. It would be a little used app, if it survived as a project at all. Plugins provide features that attract users and that use in turn attracts investment in the project, makes developers feel their work is worthwhile and introduces new developers. That is why the developers have tried to help ensure plugins work.
So, in practice there is an obligation on both sides, from the main developers not to change too much too often that it puts a burden on the plugin developers and on the plugin developers to continue support if the can. Sometimes they can't for many reasons.