There's no recording of this lab. However, we do have an IoT MVA which covers the same material.
On-board LED on Pi3. We didn't use it for the lab. I know it's not accessible the old way, but I haven't checked on any update.
The WiFi driver for the on-board WiFi was not yet ready for Build, so we used WiFi dongles like you would on the Pi 2. It's coming, though.
Windows 10 IoT Core on the Pi does not have GPU accelerated video. The Pi has a very different type of video system that doesn't meet the required DirectX feature level. If you want HW accelerated video, I recommend using the Dragonboard or another IoT Core compatible board.
Not quite sure if this is what you're asking, but the intent with Windows 10 IoT Core for devices like Raspberry Pi is to provide an experience without any shell. Instead, your app owns the entire experience on the device.
You can remotely administer the device using Powershell or the web pages served from the device.
If you want a full Windows 10 desktop experience, you need to use a device like the Minnowboard Max (or a larger PC device) and the full Windows 10 IoT for Industry version. That gives you everything you see on the desktop, plus all the lock down capabilities and more. However, that's almost certainly overkill for maker and hobby applications.
FYI. The version of FL Studio Groove with MIDI is now in the Windows Store.
Remember: you must have Windows 8.1 Update 1 to run it. If you run into any issues with MIDI timing, device recognition, or anything else, please let me know directly, rather than rate the app (the MIDI API is preview, recall).
Huge thanks to Image-Line for getting this app out to the Windows Store!
The current plan is to have this remain as a preview while we get feedback. We may roll some of that feedback into API updates and release them via NuGet, still as preview. The final version of the API will come in the next version of Windows. There are a number of technical reasons why that's the case. For example, the requirement of having to pick an architecture instead of AnyCPU is not something we'd want in the final API, but it's a necessity on Windows 8.1. Another is that we want this to be the API to use going forward, desktop, WinRT, etc., but cannot make it available for desktop in Windows 8.1.
That said, we want the preview to be as useful and stable as possible.
So please, use the API, build and list some cool apps, and be sure to put your feedback in the pro audio forums on MSDN.
The issue is if anyone makes an app they want to sound like any sort of musical instrument they obviously have to have a way of generating a decent quality output- soundfont or VST in oldspeak. These apps will not mainly connect to external midi devices. Mark
The whole second part of the talk is about using WASAPI to create sound. Most app designers have their own sound synthesis.
Soundfont or similar support is an interesting request. That came up during the session as well. Luckily, even if not built into the core OS, this should be something that would be relatively easy to build up as a sample (or even a reusable package) using Jason's code.
VSTs and plug-ins in general would be great to have. Lots of security and UI layer things to consider there, though. Are you looking for VSTs specifically, or something similar, or ...?