Video Capture Device flips image 180 degrees

pschmehl

pschmehl

New Member
Lately, I've been experiencing random occurrences of the video capture device flipping the image 180 degrees. This only happens in a scene where I also have MacOS Screen Capture setup as well. It does not happen in another sceen where I'm only using the Video Capture device. So, I end up with the screen capture right-side up and the video capture upside down. I can fix it by deleteing the video capture and resetting it up. (I'm using the MacOS Facetime Camera.) This has only been happening since th emost recent update.

I'm running MacOS Sequoia 15.0.1 (24A348) on a Mac Powerbook with OBS 31.0.0-beta2 installed.

Has anyone else seen this occur?
 
K

Kk_Nutz

New Member
Mine did the same until I noticed that since I am using the original camlink (non4k) that the new video capture device software does the flip. I found a way to use video capture device (legacy) and problem solved. Im using a MacMini and OBS 30.2.3

Create a scene
Add video capture device and right click using your mouse
Go to ADD at top of screen
Go to Deprecated at bottom and click on Video Capture Device (legacy)
proceed as normal to add your capture card info.
 
Last edited:
A

AaronD

Active Member
Right-click the source (or however you get the context menu on a Mac) -> Transform -> Rotate 180

One of my rigs has a USB PTZ camera that insists on displaying upside down, for both Windows and Linux, and for other apps too. That transform in OBS fixed it. Then I set up OBS's virtual camera to feed the other apps that don't have that function.
 
F

FrankReality

New Member
AaronD said:
Right-click the source (or however you get the context menu on a Mac) -> Transform -> Rotate 180

One of my rigs has a USB PTZ camera that insists on displaying upside down, for both Windows and Linux, and for other apps too. That transform in OBS fixed it. Then I set up OBS's virtual camera to feed the other apps that don't have that function.
Click to expand...

Have similar issue and have used this as a workaround, but do you have any ideas to permanently fix it? I have the issue where OBS doesn't shutdown cleanly and on restart gives the safe mode vs. normal options, so I'm wondering if that has something to do with it.

Every time I restart OBS, every scene that uses that same source goes back to flipped. Just plain goofy.
 
F

FrankReality

New Member
Kk_Nutz said:
Mine did the same until I noticed that since I am using the original camlink (non4k) that the new video capture device software does the flip. I found a way to use video capture device (legacy) and problem solved. Im using a MacMini and OBS 30.2.3

Create a scene
Add video capture device and right click using your mouse
Go to ADD at top of screen
Go to Deprecated at bottom and click on Video Capture Device (legacy)
proceed as normal to add your capture card info.
Click to expand...

Thanks for the suggestion... worth a try.
 
pschmehl

pschmehl

New Member
I'm happy to know that it's not just me that is seeing this problem. I wonder if the developers are aware?
 
A

AaronD

Active Member
FrankReality said:
Have similar issue and have used this as a workaround, but do you have any ideas to permanently fix it? I have the issue where OBS doesn't shutdown cleanly and on restart gives the safe mode vs. normal options, so I'm wondering if that has something to do with it.

Every time I restart OBS, every scene that uses that same source goes back to flipped. Just plain goofy.
Click to expand...
I think if you solve the shutdown problem, then this will be fixed too. In the sense of remembering the setting, that is; the source itself still needs it.

In most of my rigs, I have a script that sets things up, then starts OBS, then waits for me to say I'm done, and shuts things down in the right order so that OBS doesn't see things being different and try (incorrectly) to adapt to that different environment. Problem is, there's no signal that a script can send to OBS that shuts it down cleanly. There's supposed to be one, but there isn't. So it effectively crashes at that point. And so the script tells it to disable the clean-shutdown check, because I already know why it crashed and don't need Safe Mode.

Knowing all of that, I close OBS manually, just before the script would have, whenever I've changed something that I want to save. Then it shuts down cleanly, and remembers the change for next time. Never had a problem with that.

Stick your logfile into our automated analyzer (link in my sig), and see if something jumps out as possibly causing a crash on close.
 
F

FrankReality

New Member
AaronD said:
I think if you solve the shutdown problem, then this will be fixed too. In the sense of remembering the setting, that is; the source itself still needs it.

In most of my rigs, I have a script that sets things up, then starts OBS, then waits for me to say I'm done, and shuts things down in the right order so that OBS doesn't see things being different and try (incorrectly) to adapt to that different environment. Problem is, there's no signal that a script can send to OBS that shuts it down cleanly. There's supposed to be one, but there isn't. So it effectively crashes at that point. And so the script tells it to disable the clean-shutdown check, because I already know why it crashed and don't need Safe Mode.

Knowing all of that, I close OBS manually, just before the script would have, whenever I've changed something that I want to save. Then it shuts down cleanly, and remembers the change for next time. Never had a problem with that.

Stick your logfile into our automated analyzer (link in my sig), and see if something jumps out as possibly causing a crash on close.
Click to expand...
 
F

FrankReality

New Member
The workaround noted above configuring the Deprecated Video Capture Device (legacy) does indeed work.

Have been trying to figure out that shutdown issue for several weeks. As others have suggested in other places, I've tried removing unused/obsolete plugins and downgraded to V29 from V30. The OBS log stops right after it ends NDI. Not sure I know what a normal OBS shutdown looks like in a log - it's been a long time since I've had one. Even a start OBS, do nothing, shutdown OBS doesn't shutdown cleanly.

The odd part is the Mac log shows this (excerpt):
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [740]

VM Region Info: 0 is not in any region. Bytes before following region: 4464680960
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 10a1da000-10a610000 [ 4312K] r-x/r-x SM=COW /Applications/OBS.app/Contents/MacOS/OBS

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 Chromium Embedded Framework 0x143dec32a ChromeAppModeStart_v7 + 33417450
1 Chromium Embedded Framework 0x143dec0ae ChromeAppModeStart_v7 + 33416814

I don't get much time to work on the system, so my priority is to get NDI working again after trying to go to the previous to 6.0.0 level because of "DEPRECATION: obs_frontend_get_global_config is deprecated." errors See https://obsproject.com/forum/threads/obs-29-1-0-issue-with-obs-ndi-plugin.166424/

Am tempted to uninstall Chrome from the system and clean up any residue, then see if it still crashes.
 
A

AaronD

Active Member
FrankReality said:
The workaround noted above configuring the Deprecated Video Capture Device (legacy) does indeed work.

Have been trying to figure out that shutdown issue for several weeks. As others have suggested in other places, I've tried removing unused/obsolete plugins and downgraded to V29 from V30. The OBS log stops right after it ends NDI. Not sure I know what a normal OBS shutdown looks like in a log - it's been a long time since I've had one. Even a start OBS, do nothing, shutdown OBS doesn't shutdown cleanly.

The odd part is the Mac log shows this (excerpt):
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [740]

VM Region Info: 0 is not in any region. Bytes before following region: 4464680960
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 10a1da000-10a610000 [ 4312K] r-x/r-x SM=COW /Applications/OBS.app/Contents/MacOS/OBS

Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 Chromium Embedded Framework 0x143dec32a ChromeAppModeStart_v7 + 33417450
1 Chromium Embedded Framework 0x143dec0ae ChromeAppModeStart_v7 + 33416814

I don't get much time to work on the system, so my priority is to get NDI working again after trying to go to the previous to 6.0.0 level because of "DEPRECATION: obs_frontend_get_global_config is deprecated." errors See https://obsproject.com/forum/threads/obs-29-1-0-issue-with-obs-ndi-plugin.166424/

Am tempted to uninstall Chrome from the system and clean up any residue, then see if it still crashes.
Click to expand...
Probably needs to be a new thread at this point. New people aren't going to look for a crash problem in this one.
 
You must log in or register to reply here.
Top