UPDATE: The New Raspberry Pi imager gives you the option of setting up WIFI and SSH and other operating system parameters during the initial burning of the SSD card. His video is accurate for Raspberry PI imager 2 years ago.
Behind The Scenes (BTS) ======================= Different style video for me again. This one required a certain hand/eye coordination between the talking and the typing. I used ShareX software to record the monitor whilst I used a Panasonic S1H with a Sigma 20mm Art lens (f2.4) at 24fps 4k, set to manual focusing. Audio is provided by a Rode Lavalier plugged into the S1H. I have a SmallHD monitor mounted on top facing me to help with focusing. There's also a Panasonic S5 with a 20mm-60mm kit lens for B-roll clips (typing etc). Lighting is from one light, being reflected from a large white card. Background lighting provided by the AtomCube RGB LED light at the back of the room. I mentioned the hand/eye coordination. My first attempt, required that I adlib (with some outlining) into the camera whilst typing. I had to set the screen to record and then the S1H. Invariably, something 'happened'.. eg, I messed up the words, but not the command input. So I would have to redo the sequence. However, what happened frequently was that the Raspberry would be successfully configured, so I could just re=issue the commands again because they would fail. So retakes became challenging, and I had to rebuild the Raspberry Pi many times. Finally gave up. The new approach was to just record the keyboard input/interactions with Windows/Raspberry Pi using ShareX, and then later, overdub it with the video/voice of me apparently typing to create the illusion that all was good on the first take :-) Editing as usual in Adobe Premiere. I've had to re-live typing the same commands many many times :-)
Great videos. Well organized and clear. Thanks! But I'm left with a big question: Why can't we do all the development/debugging on the RPi without using Windows?
Good question. You could.. develop on the Raspberry Pi with something like Visual Code, etc.. However, you would need to load up a desktop/UI on the Raspberry Pi. I was striving for keeping my Raspberry 'headless' specifically for IoT applications and keep memory use down to a minimum. That said, I've never loaded up the desktop on the Raspberry, so not aware of the implications. Also, I keep all my projects (WPF, Cloud/Web, IoT, etc) on my Windows PC, knowing that that's always backed-up. Let me know if you go the Desktop/Visual Studio Code route, maybe it's easier than I thought :-) Also, Microsoft brought out Version 1.74 of Visual Studio Code and made the remote-tunnel extension available. Again, this introduces the concept of using Visual Studio Code on your Windows system as a thin-client communicating over a tunnel to something called the Visual Studio Code Server. You can think of the VS Code Server as a Command Line Interface (CLI) version of Visual Studio Code. Functionally, the development environment will reside on the target machine (the Raspberry Pi), including extensions, and all that is required on the Windows machine is the remote-tunnel extension. I'm working on a TH-cam to bring this approach to life. Thanks for watching!
Nice video serie. I notice that you are using a Zero 2 W. I have the first version of Zero Wireless bought in 2017. Will it be possible to do the same on my board?
I don't believe so. My understanding is that .NET Core is only available from the 2W onwards. I remember stumbling across this article github.com/dotnet/iot/issues/998 which also alluded to the same outcome, but with workarounds using "Mono". Hope that helps.
UPDATE: The New Raspberry Pi imager gives you the option of setting up WIFI and SSH and other operating system parameters during the initial burning of the SSD card. His video is accurate for Raspberry PI imager 2 years ago.
Behind The Scenes (BTS)
=======================
Different style video for me again. This one required a certain hand/eye coordination between the talking and the typing. I used ShareX software to record the monitor whilst I used a Panasonic S1H with a Sigma 20mm Art lens (f2.4) at 24fps 4k, set to manual focusing. Audio is provided by a Rode Lavalier plugged into the S1H. I have a SmallHD monitor mounted on top facing me to help with focusing. There's also a Panasonic S5 with a 20mm-60mm kit lens for B-roll clips (typing etc). Lighting is from one light, being reflected from a large white card. Background lighting provided by the AtomCube RGB LED light at the back of the room. I mentioned the hand/eye coordination. My first attempt, required that I adlib (with some outlining) into the camera whilst typing. I had to set the screen to record and then the S1H. Invariably, something 'happened'.. eg, I messed up the words, but not the command input. So I would have to redo the sequence. However, what happened frequently was that the Raspberry would be successfully configured, so I could just re=issue the commands again because they would fail. So retakes became challenging, and I had to rebuild the Raspberry Pi many times. Finally gave up. The new approach was to just record the keyboard input/interactions with Windows/Raspberry Pi using ShareX, and then later, overdub it with the video/voice of me apparently typing to create the illusion that all was good on the first take :-) Editing as usual in Adobe Premiere. I've had to re-live typing the same commands many many times :-)
Amazing content
Appreciate the feedback. Thank you. Please let me know if there is further episodes you'd like me to develop/explore.
Great videos. Well organized and clear. Thanks! But I'm left with a big question: Why can't we do all the development/debugging on the RPi without using Windows?
Good question. You could.. develop on the Raspberry Pi with something like Visual Code, etc.. However, you would need to load up a desktop/UI on the Raspberry Pi. I was striving for keeping my Raspberry 'headless' specifically for IoT applications and keep memory use down to a minimum. That said, I've never loaded up the desktop on the Raspberry, so not aware of the implications. Also, I keep all my projects (WPF, Cloud/Web, IoT, etc) on my Windows PC, knowing that that's always backed-up. Let me know if you go the Desktop/Visual Studio Code route, maybe it's easier than I thought :-)
Also, Microsoft brought out Version 1.74 of Visual Studio Code and made the remote-tunnel extension available. Again, this introduces the concept of using Visual Studio Code on your Windows system as a thin-client communicating over a tunnel to something called the Visual Studio Code Server. You can think of the VS Code Server as a Command Line Interface (CLI) version of Visual Studio Code. Functionally, the development environment will reside on the target machine (the Raspberry Pi), including extensions, and all that is required on the Windows machine is the remote-tunnel extension. I'm working on a TH-cam to bring this approach to life.
Thanks for watching!
Nice video serie. I notice that you are using a Zero 2 W.
I have the first version of Zero Wireless bought in 2017. Will it be possible to do the same on my board?
I don't believe so. My understanding is that .NET Core is only available from the 2W onwards. I remember stumbling across this article github.com/dotnet/iot/issues/998 which also alluded to the same outcome, but with workarounds using "Mono". Hope that helps.
Less music please, annoying!
Appreciate the feedback. Will try to be more conscious of the music. It's probably inappropriate for this style of video. Thanks for watching.