For best performance your OBS settings should match the parameters of the 3rd party apps. I experimented with the -rtbufsize figure, 100M seemed enough, it might be too much but most people have plenty of RAM. Output from OBS will get matched with the active resolution, fps, and sampling rate of the drivers (as set by 3rd party apps). The bit -f dshow -video_size 1280x720 -rtbufsize 100M -i video="DroidCam Video" -thread_queue_size 512 -f dshow -i audio="Microphone (DroidCam Audio)"Īnd -pix_fmt nv12 covers the different input compared to virtualcam. With a bit more thinking about it this worked better with the intel encoder, having removed some of the nvidia specific switches and also got the aspect ratio and resolution right.Ĭ:\ffmpeg\bin\ffmpeg -f dshow -video_size 1280x720 -rtbufsize 100M -i video="DroidCam Video" -thread_queue_size 512 -f dshow -i audio="Microphone (DroidCam Audio)" -vcodec hevc_qsv -bf 0 -pix_fmt nv12 -b:v 220k -r 15 -preset slow -profile:v main -acodec aac -aac_coder twoloop -ar 48000 -ac 1 -b:a 32k -f mpegts -muxrate 325k -streamid 0:256 -streamid 1:257 -metadata service_provider="G0MJW" -metadata service_name="Mike" -max_delay 2500000 -pcr_period 40 -pat_period 0.4 "udp://127.0.0.1:1234?pkt_size=1316" I just used the same ones which isn't likely to be right but surprisingly works.Ĭ:\ffmpeg\bin\ffmpeg -f dshow -i video="DroidCam Video" -thread_queue_size 512 -f dshow -i audio="Microphone (DroidCam Audio)" -vcodec hevc_qsv -s 1280x720 -bf 0 -pix_fmt yuv420p -b:v 220k -r 15 -preset slow -profile:v main -rc cbr_hq -rc-lookahead 5 -acodec aac -aac_coder twoloop -ar 48000 -ac 1 -b:a 32k -f mpegts -muxrate 325k -streamid 0:256 -streamid 1:257 -metadata service_provider="G0MJW" -metadata service_name="Mike" -max_delay 2500000 -pcr_period 40 -pat_period 0.4 "udp://127.0.0.1:1234?pkt_size=1316" I doubt it is as good but it comes for free. Note I have no idea what the optimum settings might be for the intel vs nvidia. Extensible by Plugins/Extensions OBS Studio can be extended with add-ons, plugins and extensions. It seems to be working fine with the intel codec on my laptop. Information : You can do similar things on Linux by this experiment project now. Change build system to visual studio 2017. Increase directshow interfcae(obs-camera 2-4) for sink. I didn't have my Nvidia PC to hand to test this so I am using hevc_qsv, the intel codec build into modern CPUs. Add virtual-cam filter for source output, inspired by ndi-filter plugin.(Only support obs-studio 21.0.0+ ) Deprecate crop feature. I have discovered a possible solution in DroidCam. OBS record almost does what we need, but it doesn't pass all the parameters to the codec and multiplexer. There is an example on the ffmpeg TS output. I don't know how to write an OBS plugin and don't have time to learn how at the moment. What is really needed though is a DATV plugin for OBS that implements natively all those things we use the virtual camera and a script/DATVEasy to do and simply streams the data for the pluto. Perhaps if a lot of us posted about this on the OBS forum it might happen as I expect it isn't a huge addition. My fear is the plugin development will stop now there is an official plugin. You can stretch or shrink the image to fit.OBS has its own virtual camera, but when I queried this the developers didn't understand the need to virtual sound to go with it. A plugin that provides a DirectShow Output as a virtual webcam for OBS Studio. The output will appear in OBS studio as the sender size( 640x360 in this case) within the canvas (1280x720).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |