Blazor webapp
Nginx and a Microsoft Blazor Webapp. Had this on a Linode Server running Ubuntu
20.04 LTS but wanted to do away with that monthly cost. Maybe I'll set it up again somewhere. Got much from
this tutorial.
Create and edit a Blazor webapp (blazorwasm) in a folder, for example
"wasm", on your local computer. Make sure that you have the same version of dotnet on the local computer as on the server.
Open a terminal and run:
dotnet new blazorwasm -o wasm
or use Visual Studio.
Transfer the files in the folder to the /home/thomasa/wasm folder on the
server.
To start the webapp, open a terminal on the server and go to:
cd /home/thomasa/wasm
Now run:
dotnet run
If you want "auto update", run:
dotnet watch run
To run the webapp in its own terminal instance, you may want to use the screen command:
screen
- Press ctrl-a c to create a new window.
- Press ctrl-a " to list all windows.
- Press ctrl-a [0-9] to switch to window [number].
To restore screen after new login, use:
screen -r
Smart Lights
A smart light system installed at home:
-
A
Philips Hue
Router.
Controls lamps and switches at home through different apps working
through my home router (wifi or cable).
- A couple of Hue LED's (expensive).
-
Lots of
IKEA Tradfri
LED's (not expensive). Connects great to the Hue system.
-
A
Raspberry Pi
running Linux and
Node-RED connected
to my home router. NodeRed interacts with the Hue router and makes
possible connecting to Blynk.
-
Blynk is used to
control the lighting at home from anywhere through internet.
Description
The Raspberry pi is connected to the local network through the home
router. The Rasperry Pi is running the Linux distribution
Patchbox which actually is
an audio distribution but works for this cause as well.
Node-RED is running on Patchbox and controls and connects the Hue router
and Blynk.
An image of the connections:
The Raspberry pi is headless and its desktop can be controlled with
VNC Viewer from Windows.
Node-RED can be reached from a browser in Patchbox at localhost:1880 or
from anywhere else at the Raspberry pi:s address in the local home
network, for example: 192.168.0.148:1880
Linux audio applications
Running a Raspberry Pi headless over the local network and integrating Linux audio applications with Windows:
-
A
Raspberry Pi
running Patchbox Linux connected to my home router.
- A Windows computer for MIDI- and audio control.
- Multimidicast installed on the Windows computer for sending/recieving MIDI over the network. Multimidicast for Windows is not available any more, but a zip-file with some versions of multimidicast.exe can be downloaded here. Note: Multimidicast for Windows will not work if a Virtual Box network adapter is enabled. If you have one running – disable it.
- QMidiNet installed on the Raspberry Pi for sending/recieving MIDI over the network under Jack.
- loopMidi by Tobias Erichsen installed on the Windows computer for routing MIDI.
- Jack Audio Connection Kit installed on both the Windows computer and the Raspberry Pi for running the audio.
- Zita-njbridge installed on both the Windows computer and the Raspberry Pi for sending/recieving audio over the network under Jack.
Description
The Raspberry Pi is connected to the local network through the home
router and it is running the Linux distribution
Patchbox (currently the same installation that also runs the Smart Lights, see above). It is run headless, i.e. no keyboard or mouse, but is controlled from the Windows computer with VNC Viewer.
Start Multimidicast on the Windows computer and configure it to send MIDI. A typical command line can look like the following. You have to figure out what numbers relate to your MIDI equipment and the loopMidi ports.
C:\Program Files (x86)\Multimidicast>multimidicast.exe -in0 3 -out0 5
Start Jack on the Windows computer. A typical command line can look like the following. The portaudio string depends on your audio equipment.
C:\Program Files (x86)\Jack\jackd.exe" -R -S -d portaudio -d "ASIO::AudioBox ASIO Driver" -r48000 -p128
Start Zita-njbridge on the Windows computer. Use zita-n2j here for recieving audio. The IP-address is that of the Windows computer. The string "1234" could be anything but must be the same on both sending and recieving computer.
C:\Program Files (x86)\Jack>zita-n2j 192.168.0.109 1234
Start QJackCtl or any other Jack GUI on the Windows computer and make the connections.
Start Jack on the Raspberry Pi. If you use QJackCtl it will automatically start Jack. Make sure that Sample Rate is set to 48000 and Frames/Period to 128.
Start Zita-njbridge on the Raspberry Pi. Use zita-j2n here for sending audio. The IP-address is that of the Windows computer. The string "1234" could be anything but must be the same on both sending and recieving computer.
patch@patchbox:~ $ zita-j2n 192.168.0.109 1234
Start some audio application and make the connections in Jack on the Raspberry Pi.
The audio on the Raspberry Pi is now sent to and heard on the Windows computer.
Ambisonics
If the synthesized pipe organ Aeolus is started with the -B option it will output four channels of ambisonics B-format: W, X, Y and Z. There are two standards for how the four channels are ordered: FuMa (WXYZ) and AmbiX (WYZX). If using Waves NX Ambisonics to encode, be sure to order the channels according to the AmbiX standard: Connect Aeolus WXYZ to Waves WYZX. See Ambisonics Explained.
Microsoft Activation Scripts
MAS
A collection of scripts for activating Microsoft products using HWID / KMS38 / Online KMS activation methods with a focus on open-source code, less antivirus detection, and user-friendliness.
Download here: MAS 1.5 Password 1234.
Instructions: massgrave.dev.
Activation of Office 2019
An Office license with product key can be hard to activate. This works even when you have a product key (in Swedish):
Hur man aktiverar Microsoft Office 2019.
Or download here, unzip and run: ActivateOffice2019.zip.
Make Ledger Nano X work in Linux
Udev rules
If Ledger Nano X is not recognized in Linux, set up udev rules.
- Open a terminal.
- Set up udev rules using the following code snippet. Applies to a Debian system:
wget -q -O - https://raw.githubusercontent.com/LedgerHQ/udev-rules/master/add_udev_rules.sh | sudo bash
Got this from here: Ledger Support. Choose the Linux tab and click "Soloution 1. Setup udev rules".