DroidCam OBS Camera 2.5.0

[dev47]

@Tonny Sarmento please check the 4K Guide here: https://droidcam.app/obs/4k.html#top
If its not working, could you send details to support@dev47apps.com (with the OBS log where you tried to enable 4K)

 

[kafkalino]

Hello, i install the 2.5.0 setup .exe, but the new options are not present in obs, and i see dat :

Strange... is it normal ?

 

[dev47]

@kafkalino , yes, this probably means you have an older version of OBS Studio. Release 2.4.1 and later are for OBS v32.

 

[MrDodi]

Latest 2.5.0 Plugin Breaks / Shows black screen when using AVC or HEVC coded with activated hw acceleration. Only MJPeg + 1080p works.
4k30fps was working with 2.4.2 on AVC but now its unusable.
Main setup is iphone15pro with a usb-c 20gbps cable.
The phone actually seems to be "fine" it shows that its connected and the usual "stats" but within obs, its all black as seen on the screenshot.
Also tried via WiFi (5ghz) , different iphone, different cable, all same results.
It shows a picture when HW Accel. is disabled, but the latency / lag from it makes it borderline unusuable.
Not sure if there is anything i can do on my side, but for now i stay with Plugin Version 2.4.2.

 

[dev47]

One of the changes in 2.5.0 was the addition of D3D12 as the main hw decoding option for Windows , and my initial hunch is this is the likely problem. I will make a note switch the order and stick with D3D11 as the default. If you could upload an OBS log with the video coming out blank, that would be really helpful (in OBS, use Help -> Upload log or find the previous logs. you can also email this to support@dev47apps.com).

 

[ashl1]

@dev47 Thank you for the great app and OBS plugin!
I found out that version 2.5.0 of the plugin still doesn't work with libavcodec-62. Ubuntu 26.04 (Resolute Raccoon) has been released almost month ago and has had libavcodec-62 and OBS 32.1.0. Ubuntu don't like flatpak, so I use repo version of OBS but still cannot use Droidcam plugin.
I see the note for version 2.4.3 stated "downloads will be available after the OBS Studio PPA/Flatpak officially switch to FFMpeg 8." OBS Studio PPA version 32.1.2 uses `Depends: ... libavcodec62 (>= 7:8.0.1), ...`.

I just want to ask when do you plan to publish the released files at least for 2.4.3 plugin version?

 

[MrDodi]

One of the changes in 2.5.0 was the addition of D3D12 as the main hw decoding option for Windows , and my initial hunch is this is the likely problem. I will make a note switch the order and stick with D3D11 as the default. If you could upload an OBS log with the video coming out blank, that would be really helpful (in OBS, use Help -> Upload log or find the previous logs. you can also email this to support@dev47apps.com).

now that you mention it, it actually shows an hw decode error in the log
19:09:43.522: error: hardware accelerator failed to decode picture
..
I attached 2 Log Files - since i tried it with 2 different obs versions (the latest official release and the closed beta twitch enhanced version)
Thank you in advance for your hard work! One of the handfull plugins i wasnt dissapointed in spending money for the full version

 

[dev47]

It looks like ffmpeg 8 was merged into obs-deps 2 weeks ago, so the next update will support it.

 

[ashl1]

the next update will support it.

Good to hear that! When do you plan for the new release approx?
I need to switch to flatpak version of OBS and Droidcam plugin until that...

 

[dev47]

An ffmpeg8 build has been uploaded to Github releases

 

[ZYNCTECHNO]

Hi team Droidcam and droidcam users!
I bought Droidcam to get the most out of my camera. Let me tell you what my current challenges are:

So my setup is:
Livestreaming DJ sets on TikTok LIVE. I use OBS Studio with the Virtual Camera send to TikTok Studio. This all works perfectly after adding Droicam in OBS as Source.

Now the challenges:
I want to have the best picture quality so I figured out that I need to use Camera 0 on 1.0x zoom. This way my Samsung S25 Ultra uses the main camera (so the biggest sensor). Also with this 1.0x zoom you can manually set the focus which is great.

The challenges I have are with AWB and EV level.

So first the EV level:
I can crank up the light output of my Elgato Key Light and this way I can lower the EV value to as much as - 20 if I want to. The other way is to put the EV value on 0/default and turn down my Elgato Key Light. Or of course everything in between this. Which is the best way to go for this?

Then there is the AWB. I found out in this topic that for the Droidcam dev team it was not possible to have a "real" color scale (in Kelvin) for the silder but that it should be between 2000K (silder 0) and 10000K (slider 100). Is that still applicable for the current version combined with my S25 Ultra?
And here is what is strange to me as for the AWB: when I put my Elgato Key Light on 5600k and the silder in Droidcam in the middle it should theoretically be around 5600k but it seems way too flat/blue. When putting it on AUTO in droidcam it seems to become to red. And what is also strange to me is that I cannot achieve the same result with the manual slider that auto gives me. So what I mean is that putting the AWB setting on AUTO and compare this with the manual silder there is not a single value (0-100) that comes even close to the AUTO outcome.

Any input?

 

[dev47]

Hey @ZYNCTECHNO -
#1) This is mostly up to you, but I would say keep EV close to zero and adjust your lighting instead. EV=0 means less image processing.
#2) Android has finally introduced the option to set WB with kelvins. The code changes for this are ready and are pending release (soon™). For the time being, you will just need to eyeball the 0-100 slider to your visual taste, or just let auto do its thing and lock it.