Native Source Recording
- Thread starter Tormy
- Start date
Why native? Is the plugin not enough or not working?
obsproject.com
Source Record
Download Plugin for OBS Studio to add a filter that allows you to record a source. Add "Source Record" filter to your source. Installation Copy and merge the folders that are in the download zip to the OBS folder for example: C:\Program...
Tormy
Member
No it isn't. I would preferer these kind of functions are native and followed lifetime and not just based on the availability of the single developer that can leave everything when he's not more comfortable to carry on in development and fixing issue.Why native? Is the plugin not enough or not working?
Source Record
Download Plugin for OBS Studio to add a filter that allows you to record a source. Add "Source Record" filter to your source. Installation Copy and merge the folders that are in the download zip to the OBS folder for example: C:\Program...
The interfacing with OBS is even better, because carried on with versioning, without having time where the feature is frozen or really and working to changed things into the interfacing (already occurred).
Avoiding/strongly minimizing glitching issues that currently are occurring.
On top of this: feature is IMMEDIATELY available to anyone is starting with OBS without having the problem to go to looking for something that perhaps it doesn't work on their machine or works badly and to be constrained to ask to the developer that perhaps it's not more available.
= increased reliability and more future-proof
I completely agree with all of that!
But I'm a bit skeptical about the practicality of it from the development side. If you take that logic as far as it goes, then we end up with all the plugins that there ever were, baked into OBS natively instead as a giant monolithic block. Maybe some are worth more than others to do that with - I would not mind the Advanced Scene Switcher going that way, and replacing the Automatic Scene Switcher that it grew out of and *is* native, likewise for the Downstream Keyer, and...well...pretty much the things that *I personally* use - and therein lies the problem. The list of priorities is different for each person, and to satisfy all of them requires *everything* to become native, and that's just not feasible.
Sure would be nice though, from the user side...as long as we can still find things...
But I'm a bit skeptical about the practicality of it from the development side. If you take that logic as far as it goes, then we end up with all the plugins that there ever were, baked into OBS natively instead as a giant monolithic block. Maybe some are worth more than others to do that with - I would not mind the Advanced Scene Switcher going that way, and replacing the Automatic Scene Switcher that it grew out of and *is* native, likewise for the Downstream Keyer, and...well...pretty much the things that *I personally* use - and therein lies the problem. The list of priorities is different for each person, and to satisfy all of them requires *everything* to become native, and that's just not feasible.
Sure would be nice though, from the user side...as long as we can still find things...
Tormy
Member
Not necessary to have it a monolithic. keep it modular by including the plugins as for Native VSTs in a DAW
yes right, Advanced Scene Switcher also. Good mentions
Also the lower-thirds in HTML etc that it's great but it was abandoned.
Several things can be used in Pro environment. these things should be into the "core" (so to speak).
Last edited:
Tormy
Member
So the 11 of november a customer of me needs OBS for his purpose, to be able to record separated sources as for that plugin/script.
It's a training for a big Company, he should make, where he is the trainer. The use of OBS is a must-go/must-have.
But this plugin/script has a big issue regarding stability and consistency.
The issue on top tof the issue: not any reaction/answers/feedback from the plugin's programmer till today, about a blocking bug his script has. We've highlighted it in this forum and on GitHub.
This is not acceptable, and it's a situation that should be avoided. Hence the NAtive feature will eb the best way, at least it's tested womehow and always compatible with each version of OBS.
I'm wondering why this feature was not thought by the OBS Devs themselves. It's paramount.
It's a training for a big Company, he should make, where he is the trainer. The use of OBS is a must-go/must-have.
But this plugin/script has a big issue regarding stability and consistency.
The issue on top tof the issue: not any reaction/answers/feedback from the plugin's programmer till today, about a blocking bug his script has. We've highlighted it in this forum and on GitHub.
This is not acceptable, and it's a situation that should be avoided. Hence the NAtive feature will eb the best way, at least it's tested womehow and always compatible with each version of OBS.
I'm wondering why this feature was not thought by the OBS Devs themselves. It's paramount.
OBS is free, with no obligation for anyone in any direction. It's amazingly capable, probably enough that it *could* be used for professional production and the viewers would not know the difference...but the reason it's not is the not-guaranteed support, as you've found.
Serious productions use something else, not because of the capability, but because of the support. It may even be *less* capable, but they know that they can call someone and get an answer right away. THAT is worth paying a boatload for, even if the product itself is technically inferior.
With free, open-source, community-supported stuff, you're often on your own. It is what it is - take it or leave it - until a week or two goes by and the volunteer expert finally gets around to logging into the forum and just happens to see your 20th bump...
Acceptability to you has no importance to us. It simply is how it is. If you can't accept it as it is, use something else.
Serious productions use something else, not because of the capability, but because of the support. It may even be *less* capable, but they know that they can call someone and get an answer right away. THAT is worth paying a boatload for, even if the product itself is technically inferior.
With free, open-source, community-supported stuff, you're often on your own. It is what it is - take it or leave it - until a week or two goes by and the volunteer expert finally gets around to logging into the forum and just happens to see your 20th bump...
Acceptability to you has no importance to us. It simply is how it is. If you can't accept it as it is, use something else.
Tormy
Member
how to kill OpenSource in pro-environment; If we were thinking in this way 30 years ago with Linux, this one never could enter in pro-environment. A solution may be:
OBS integrates vital parts like this (and others) a s fo spline (just for example) and then fro B2B: assistance fro who buys it ... it's just one of the possible things to make it take really off ...
Another possible approach, which can be integrated with what I mentioned earlier, is that programmers can develop plugins while also contributing to the open-source project by forking and implementing their changes into the official release. This will ensure that the rules set by the developers to manage the project are respected, making their work more seamless and increasing satisfaction for everyone.
In shorts: solutions are there and can be all analyzed and eventually implemented somehow. The important is do not refuse them a priori.
To collaborate: https://github.com/obsproject/obs-studio/blob/master/CONTRIBUTING.rst
Last edited:
bcoyle
Member
This is an interesting conversation. First of all, I think this plugin is amazing.
2. It's not ready for commercial use.
3. It's purpose is risk abatement and or for later remixing.
A wedding photographer can not tell the bride, "Sorry, my batteries went dead or main main camera failed. You only get one chance.
This plugin is similar to recording a concert with 5 cameras, sending the camera video to the directors booth where they do
"Live to Tape" recording. Having each camera use it's own internal memory chip to backup the recording, is smart and necessary for one off events. Also important for remix where the directory did not see the keyboard solo until too late.
Exeldro the author of this plugin is rare. But is thin , in that he needs to support his many plugins plus the fun of creating new ones. I have found in real life as a programmer that sometimes you grind to a halt when you have created two many wonderful programs (plugins) and then you have to support them, with bug fixes or new features.
So the problem becomes "volunteers with life balance issues" vs "commercial payed software" with customer support and how responsive they are.
There is a concept called "team programing" where 2 programmers work together on the SAME code, They bounce ideas off one another, creating less bugs and just better software. The junior programmer becomes the heir apparent, the uinderstudy. So if one person is busy, the other can handle it. This isn't necessary for all plugins, but would be nice for important ones. Also as the plugin matures, stable with no known bugs, it would finally, if deemed important enough, could be added natively.
Basically there needs to be a support path for important software. Of course , it all depends on the availability of talented volunteers.
bcoyle
Member
I think that a requirement for a developer for important software, is to check the forum and gethub everyday and handle bugs as a priority. But I also know, that that can become a unpayed "JOB". What do you do when you go on vacation?, Get sick. Just don't feel like it. There is life balance. Life is complicated.
Tormy
Member
That's why such kind of feature should be integrated as NAtive. Yes it can be improved but it will be not on the hands of only one person.
it will cover the life cycle of the product and there is the occasion for the original programmer to be supported.
This feature is one of the important one smissign yet in OBS.
Today I invited @Exeldro to make that jump, to develop inside OBS itself. I hope he will think about and join asking the collaboration of the other ones to improve what seems a flaw, in this moment in time.
I hope he will do so. Credits for his collaboration will eb certainly granted.
NOTE ASIED/ you can always edit your original message to add the missing lines, just in case :-D
bcoyle
Member
yeah, i know, just lazy