-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Failed on startup with multiple monitors (USB Monitor) #1
Comments
Could you please paste the output from $ ./ffscreencast --list |
I see, the problem is, that Please also dump the output of: /ffscreencast --slist --dry |
hey! thanks for the feedback... and sorry for my terse dump up there... I had to hit the road and thought I'd log it before i left... here's the dump from your original request:
and here's the next dump:
and I don't think it matters, but I'm running |
hey... fyi - taking a closer look at the dumps, I wonder if maybe it's because I might have grep and sed aliased in some way? I have the following: grep='grep -I --ignore-case' I'm sure you're aware, but you can force it to use the non aliased version in your scripts by preceding it with a slash, like: \grep etc... |
Could you also... a.) try it on a shell (possibly bash) where u don't have any aliases |
Can u pull the latest master code and try again. |
i pulled the latest and still the same issue. I also tried running it with a clean shell using the approach detailed here (bash --noprofile --norc) http://stackoverflow.com/a/9357501 and I get this:
I tried another monitor with the same issue as well. I'm just thinking it over and realize that maybe the problem comes from the fact that one of my monitors is a USB based monitor? http://www.amazon.com/StarTech-com-USB-VGA-Adapter-USB2VGAPRO2/dp/B009L14FHI I've never head any other problems with it.... sorry for not mentioning it earlier.... but I don't think that's the issue anyway as I get the same error no matter which monitor I try... |
Maybe it's something to do with my ffmpeg? here's a dump of it's version info:
|
No, it is simply that
So the error must be with $ system_profiler SPDisplaysDataType Could you run the above command and paste the output of it. |
hey... i just ran that command and see that only 2 monitors are shown, though I have 3.
and maybe this is what's missing? I can see USB info by dumping all system_profiler output to a file:
Not sure if that's helpful. And definitely don't feel you have to chase this down for me... My use case (if the problem is the USB monitor) is probably < 5% of users, I'd think.... |
OK I see. The USB Display does not show any information about screen resolution, so the whole regex fails. I have added a check to remove the I pushed the changes, hope they work for you too. Could you also provide the following output with all three monitors attached: $ ffmpeg -f avfoundation -list_devices true -i '' 2>&1 |
And btw also when there is no privacy related output, could you paste (very long output) $ system_profiler |
and for what it's worth I ran ffscreencast without external monitors attached on my laptop and it worked fine. |
and here's a dump of
|
Thanks for the dumps. Anyway, the current build |
Sure... thanks for the effort... much appreciated! |
As it should work now with external USB monitors (with the drawback to not be able to get the screen resolution) I am closing. If there is still a problem on your side, please re-open. |
$ ./ffscreencast
Available devices:
[1] Capture screen 0
[2] Capture screen 1
[3] Capture screen 2
Enter device number: 2
ffmpeg -hide_banner -loglevel info -thread_queue_size 512 -f avfoundation -video_size -i "2" -c:v libx264 -crf 0 -preset ultrafast -threads 0 "/Users/bparks/Desktop/Screencast 2015-10-26 at 12.33.37.mkv"
Option thread_queue_size (set the maximum number of queued packets from the demuxer) cannot be applied to output file 2 -- you are trying to apply an input option to an output file or vice versa. Move this option before the file it belongs to.
Error parsing options for output file 2.
Error opening output files: Invalid argument
Using FFMpeg 2.7.2 on OSX Yosemite (10.10.5)
The text was updated successfully, but these errors were encountered: