Open JeremyRand opened 11 years ago
It should "save settings" on startup, but I suppose you'd like it to automagically select things, based on...executable it's running in? What are you proposing exactly? Thanks! -r
On Sun, Oct 14, 2012 at 12:36 AM, JeremyRand notifications@github.comwrote:
Any chance this could support multiple instances running simultaneously, with different associated settings and DirectShow device names? E.g. I'd like to have one DirectShow device showing part of a Firefox window, while another DirectShow device shows a video chat window. Or maybe this is already possible and I just haven't found how?
Thanks.
— Reply to this email directly or view it on GitHubhttps://github.com/rdp/screen-capture-recorder-to-video-windows-free/issues/10.
I would like it to create more than 1 DirectShow virtual device simultaneously (I should be able to select how many), and have the ability for each of those DirectShow virtual devices to correspond to a different desktop region simultaneously. Right now as far as I can tell, only 1 DirectShow device is created. (Sorry if I'm being unclear.)
So what you want is "several devices appear, with different names" or something?
(my work around described before was to set registry values, then new up one device, then change them new up another, etc.)... -r
On Mon, Oct 15, 2012 at 1:01 AM, JeremyRand notifications@github.comwrote:
I would like it to create more than 1 DirectShow virtual device simultaneously (I should be able to select how many), and have the ability for each of those DirectShow virtual devices to correspond to a different desktop region simultaneously. Right now as far as I can tell, only 1 DirectShow device is created. (Sorry if I'm being unclear.)
— Reply to this email directly or view it on GitHubhttps://github.com/rdp/screen-capture-recorder-to-video-windows-free/issues/10#issuecomment-9435940.
Yes, I think that's an accurate description of what I'd like. Thanks!
That sounds reasonable. No you can't do that yet :) I probably wont' get around to it for a bit... -r
On Mon, Oct 15, 2012 at 1:16 AM, JeremyRand notifications@github.comwrote:
Yes, I think that's an accurate description of what I'd like. Thanks!
— Reply to this email directly or view it on GitHubhttps://github.com/rdp/screen-capture-recorder-to-video-windows-free/issues/10#issuecomment-9436187.
That's fine, I'm a patient person. :-) Seeing as it's free, I'm certainly in no position to want things done quickly. Thanks.
So it would need config files containing...the executable name? the hwnd? the window class? -r
On Sun, Oct 14, 2012 at 12:36 AM, JeremyRand notifications@github.comwrote:
Any chance this could support multiple instances running simultaneously, with different associated settings and DirectShow device names? E.g. I'd like to have one DirectShow device showing part of a Firefox window, while another DirectShow device shows a video chat window. Or maybe this is already possible and I just haven't found how?
Thanks.
— Reply to this email directly or view it on GitHubhttps://github.com/rdp/screen-capture-recorder-to-video-windows-free/issues/10.
I'm not sure what the best implementation method would be. (This isn't my most knowledgeable area.) I'll let you figure out the best implementation. :-)
Hi, is it possible to do multiple instances now? I want to use one for the window source as input to an opencv program, then I will process that and have another output window. The processed output window I want skype to see as the source. Right now Skype can only see the original source window before processing.
No, but funding welcome! :)
On Mon, Mar 30, 2020 at 1:45 PM GrushBrush notifications@github.com wrote:
Hi, is it possible to do multiple instances now? I want to use one for the window source as input to an opencv program, then I will process that and have another output window. The processed output window I want skype to see as the source. Right now Skype can only see the original source window before processing.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rdp/screen-capture-recorder-to-video-windows-free/issues/10#issuecomment-606206492, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAADBUEPXIDREDEOLSFVSI3RKDZDTANCNFSM4ABTESTQ .
I hear you man. It's possible for me to just hack at the source to have multiple dll with different names and handles and registry areas? Could I make 4 simultaneous capture devices bound to 4 different HWND CLSID in this way?
Yeah multiple registry areas would work. I think I may have added it in there so it can pull from a .ini file as well... Good luck, if you feel adventurous feel free to PR!
On Mon, Mar 30, 2020 at 10:27 PM GrushBrush notifications@github.com wrote:
I hear you man. It's possible for me to just hack at the source to have multiple dll with different names and handles and registry areas? Could I make 4 simultaneous capture devices bound to 4 different HWND CLSID in this way?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/rdp/screen-capture-recorder-to-video-windows-free/issues/10#issuecomment-606391685, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAADBUFNNKKJK4UXEJ72NGLRKFWJ3ANCNFSM4ABTESTQ .
Any chance this could support multiple instances running simultaneously, with different associated settings and DirectShow device names? E.g. I'd like to have one DirectShow device showing part of a Firefox window, while another DirectShow device shows a video chat window. Or maybe this is already possible and I just haven't found how?
Thanks.