Héraès
Member
It's going on for years, and I'm tired of it.
FIRST PROBLEM - HOW TO REPRODUCE IT
1. Create a source for your webcam. Name it as you want.
2. Use it in a scene. Make it activated/visible.
3. Now create an other source, with the same webcam. Name it with a different name.
4. Use it in a second scene. Make it activated/visible.
5. Switch back to the previous scene : tadaaa ! The first webcam is not visible anymore.
6. Go back to the second scene, and hide the webcam.
7. Now, go back to the first scene : taaaaaaadaaaaaaaa !!! The Webcam is STILL NOT VISIBLE.
8.You're screwed.
HYPOTHESIS
OBS mess with the devices ID attributions, names, and relationship between the two. The fact that it can't accept to just fucking use the device, is mesmerizing. But the fact that even when deleting the second instance, it stay stuck, is beyond facepalming. -_-
Not mentioning that even by declaring two instances of the same device, they should share the same UUID, and there should never be another UUID attributed for the device, than the one of that device.
HOW TO SOLVE THE PROBLEM ?
I don't know. I think that previously, I just have deleted all the source, to restart from scratch. But at this present time, I have 150 scenes. I won't do that just because a lazy bunch of developers never took a minute to considere that this problem do indeed exists.
There's a workaround : it consists in unpluging the device, and re-pluging it. But I'm not a slave, I'm not supposed to bend and go behind my desk everyday when I launch OBS.
WHAT I TRIED, AND HOW STUPID IS THIS SOFTWARE (OR THE PEOPLE THAT MADE IT ?)
I understood that in the file of the scenes collection, there might be traces of the ID of my webcam, with an incorrect ID (guess how it happened ? Hmm ?).
And I also understood that the aforementioned ID (the real one) is delivered my Windows.
1. So I went in Windows' Device Manager, opened the properties of my webcam, "details" tab, chosed "class GUID", and copied the stuff. Note : The fact that this properties panel doesn't appear in the taskbar and end up being hidden behind all my windows opened, forcing me to minimize all my software to retrieve it, is also mesmerizing. Incompetency at its highest. -_-
2. I went in %AppData% -> Roaming -> obs-studio -> basic -> scenes, and opened the JSON of my scenes collection.
3. It's fucking minimized -_-. Okaaay... So, I used "find and replace", and replaced all the webcam UUID with the windows' GUID one (without the curly braces, I'm not a fool).
4. I reopened OBS. It didn't work -_-.
5. Went back to the JSON file, to realize that it has been overwritten to its previous state. O_o
6. I wondered if the .BAK was used to set the JSON back to its previous state each time OBS is launched (wich would be completely stupid), so I started again editing both the JSON and the BAK.
7. I reopened OBS. Didn't work again !!! -___- Jesus.
8. Went back to the JSON and BAK files, to realize that... they have been reseted to their previous state.
What the heck ??? Are you playing with people's mind ?
QUESTION
>>>> Where is the god damn file that overwrite the previous two ones ? Please. <<<<
And what's the point of storing in a JSON if that's to store informations in an obscure location acting like a virus stored in a ROM of a motherboard ?
FIRST PROBLEM - HOW TO REPRODUCE IT
1. Create a source for your webcam. Name it as you want.
2. Use it in a scene. Make it activated/visible.
3. Now create an other source, with the same webcam. Name it with a different name.
4. Use it in a second scene. Make it activated/visible.
5. Switch back to the previous scene : tadaaa ! The first webcam is not visible anymore.
6. Go back to the second scene, and hide the webcam.
7. Now, go back to the first scene : taaaaaaadaaaaaaaa !!! The Webcam is STILL NOT VISIBLE.
8.You're screwed.
HYPOTHESIS
OBS mess with the devices ID attributions, names, and relationship between the two. The fact that it can't accept to just fucking use the device, is mesmerizing. But the fact that even when deleting the second instance, it stay stuck, is beyond facepalming. -_-
Not mentioning that even by declaring two instances of the same device, they should share the same UUID, and there should never be another UUID attributed for the device, than the one of that device.
HOW TO SOLVE THE PROBLEM ?
I don't know. I think that previously, I just have deleted all the source, to restart from scratch. But at this present time, I have 150 scenes. I won't do that just because a lazy bunch of developers never took a minute to considere that this problem do indeed exists.
There's a workaround : it consists in unpluging the device, and re-pluging it. But I'm not a slave, I'm not supposed to bend and go behind my desk everyday when I launch OBS.
WHAT I TRIED, AND HOW STUPID IS THIS SOFTWARE (OR THE PEOPLE THAT MADE IT ?)
I understood that in the file of the scenes collection, there might be traces of the ID of my webcam, with an incorrect ID (guess how it happened ? Hmm ?).
And I also understood that the aforementioned ID (the real one) is delivered my Windows.
1. So I went in Windows' Device Manager, opened the properties of my webcam, "details" tab, chosed "class GUID", and copied the stuff. Note : The fact that this properties panel doesn't appear in the taskbar and end up being hidden behind all my windows opened, forcing me to minimize all my software to retrieve it, is also mesmerizing. Incompetency at its highest. -_-
2. I went in %AppData% -> Roaming -> obs-studio -> basic -> scenes, and opened the JSON of my scenes collection.
3. It's fucking minimized -_-. Okaaay... So, I used "find and replace", and replaced all the webcam UUID with the windows' GUID one (without the curly braces, I'm not a fool).
4. I reopened OBS. It didn't work -_-.
5. Went back to the JSON file, to realize that it has been overwritten to its previous state. O_o
6. I wondered if the .BAK was used to set the JSON back to its previous state each time OBS is launched (wich would be completely stupid), so I started again editing both the JSON and the BAK.
7. I reopened OBS. Didn't work again !!! -___- Jesus.
8. Went back to the JSON and BAK files, to realize that... they have been reseted to their previous state.
What the heck ??? Are you playing with people's mind ?
QUESTION
>>>> Where is the god damn file that overwrite the previous two ones ? Please. <<<<
And what's the point of storing in a JSON if that's to store informations in an obscure location acting like a virus stored in a ROM of a motherboard ?
Last edited: