I finally finished this awesome game called Photoshop, let me send you a video
blogs.msdn.microsoft.com
blogs.msdn.microsoft.com
I'd like to see them expand this to not be Xbox branded and to just be like the "snipping" feature (which I use all the time.)
Welcome to the abysmal implementation of interactive controls. For some awful historical and technical reason, most standard UI controls - such as dropdown menus - are laid out on top of your application's window by the operating system. That UI control is not part of your application; it is implemented as a separate window by the operating system which positions it on top of your application window in the requested x/y location.
The screen capturing is designed to capture a single window, and so only captures your application without these separate windows that display elements like a dropdown menu. It really is a disgusting hack. In any reasonable implementation, these controls would be inlined within your application, not outsourced to the operating system.
This is the same reason why it took so long for browsers to support styling of form elements, such as changing the background color of a dropdown. The operating system simply provided no way to allow for this. I'm not sure if the modern browser implementation with styled form elements still works with the operating system, or if they are required to bundle their own controls in order to have full control over their rendering.
My Google-fu is failing me. Does anyone know why standard operating system controls are laid out by the operating system, rather than by the application using a standard library that keeps them inline to the app itself?
I tried doing this at one point early after the Win10 release (I think just to record a browser session) and there was something I didn't like about it. Sadly I forget what it was. Maybe it was that the Xbox app/recorder would always want to launch or run now that it thought that program was a "game" or maybe it was some hotkey conflict.
Either way I disabled it and await it someday becoming a more useful feature.
I thought clicking "Yes, this is a game" was a joke, not that you actually have to tell the app that the program is a game...that's very confusing from a UX perspective. Why do they do that?
edit: on a side note, why doesn't this work in the file explorer or when not focused on a program?
Well done Windows.
QuicktimePlayer -> File menu -> New Screen Recording
https://www.google.com/imgres?imgurl=http://etc.usf.edu/tech...
For fullscreen audio and video recording, I would suggest simply running OBS. It might seem overkill, but it gets the job done.
I'd be curious if anyone has a JACK success story. It sounded like exactly what I was looking for, but in practice the thing was so arcane and impractical it seemed like too much trouble.
Using huffyuv for the initial capture is going to start stuttering at higher FPS (the example uses 15, presumably because anything higher would result in massive file sizes given GIF's terrible compression ratio), because the disk won't be able to write fast enough. x264 with the ultrafast preset is a better option in my experience.
I don't understand the purpose of the ffcast tool - it seems to be as or even more verbose than just use ffmpeg directly.
Ffcast also integrates selection of the capture area, which is a rather finicky argument to pass from xrectsel to ffmpeg. No need for it if you're capturing fullscreen.
On using things for other than its original purpose:
1) http://www.tedunangst.com/flak/post/file-considered-harmful
Edit: Question I've suddenly realised. What happens in either case (Microsoft recording or Steam) when you're playing a copyrighted video?
Video: H264 - MPEG-4 AVC (part 10) (avc1) Audio: MPEG AAC Audio (mp4a) at 48000 Hz
Sadly it maxes out at 1080p.
From what other commenters are saying, it often misses things like tooltips and menu dropdowns.
On my PC, it says “There’s nothing to record. Play some more and try again”.
NVidia ShadowPlay records good here.