OBS 28 + M1 Mac + Sony Imaging Edge issues

jalexhall

New Member
I'm having trouble getting OBS 28 (Arm) to identify my Sony A6100 after upgrading from OBS 27 (Intel) and was wondering if anyone had figured this out yet. I searched both the forum posts as well as open Github issues, and I don't see anything relevant.

My setup is that I have a Sony A6100 hooked up over USB (not a capture card) and i'm using Sony's Imaging Edge Desktop software to provide the device to OBS, which in turn provides a virtual camera to Zoom. I've used this setup for a year+ with no issues, the only thing I've changed is upgrading to OBS 28. On the new version of OBS, the device is nowhere to be found on the sources, and no combination of re-installing OBS or Sony's software seems to fix it.

The OBS logs don't provide anything particularly useful either other than the device can't be found:

19:07:46.681: Sony A6100: Could not initialize device with unique ID '054c'
19:07:46.681: Switched to scene 'Scene'
19:07:46.681: ------------------------------------------------
19:07:46.681: Loaded scenes:
19:07:46.681: - scene 'Scene':
19:07:46.681: - source: 'Sony A6100' (av_capture_input)
19:07:46.681: ------------------------------------------------
19:07:46.695: adding 21 milliseconds of audio buffering, total audio buffering is now 21 milliseconds (source: Mic/Aux)
19:07:46.695:
19:08:15.908: Sony A6100: Device with unique id '054c' not found
19:12:24.202: Sony A6100: Device with unique id '054c' not found

I think at this point my best guess is that there is some mismatch between Rosetta emulation and ARM, but I don't know enough about how those drivers work to do any real debugging to prove that. My only recourse seems to be to bypass the Sony software and get a capture card for the camera, but I was hoping there was a workaround someone had figured out before I go out and spend some $$$.
 

jalexhall

New Member
FWIW, I just checked and the x86 version of OBS 28 works just fine, so this issue seems specific to the ARM distro.
 

ewalk231

New Member
There appears to be a conflict with version 28.x. I resolved this myself by downgrading to version 27.2.4, available on the github download page.

 
Top