DISCLAIMER: FOR THE AXE FX 2, NOT AXE FX 3
The setup is as follows:
- Install Axe-Edit in a WINE prefix.
- Install USB firmware that configures the AxeFX II as a FX2-style device instead of a generic audio device.
| desc:MIDI Clock Generator | |
| slider1:120<20,300,1>BPM | |
| @init | |
| ppqn = 24; | |
| phase = 0; | |
| bpm = slider1; | |
| @slider |
Seldom will you get worse documentation than trying to use the Azure ServiceBus emulator in a real-world scenario. To spare you the frustrations, here's how I translated their docker-compose.yaml reference implementation to something you can actually use as a test fixture in a .NET project.
First, we need 2 containers, one for MSSQL, one for the ServiceBus emulator. ServiceBus emulator uses MSSQL as a backing storage solution. To make things neater, we'll also follow the example docker-compose.yaml file and add an internal network between the two so they don't need to communicate directly over the host's network.
ServiceBus emulator's official
docker-compose.yamlexample file usesazure-sqledge, but it makes no sense to use since it is deprecated and is being phased out. The MSSQL server image works just fine.
This guide is mostly for my own sanity and help me troubleshoot down-the-line. Feel free to read along, though. Some things may be misconceptions, I'm just trying as best I can.
Pre-requisites:
The goals for my system:
| echo "------------------------" | |
| echo "--- Loading autoexec ---" | |
| echo "------------------------" | |
| // -- Viewmodel | |
| viewmodel_offset_x 2 | |
| viewmodel_offset_y -2 | |
| viewmodel_offset_z -2 | |
| viewmodel_fov 68 | |
| // cl_bob_lower_amt 30 |
The guide on Cogin's website for installing on "Linux" actually means installing on a Debian-based system. This guide Arch-ifies the process. This could be made into an AUR package, but I don't have the knowledge or time to maintain such a package, so here's the (hopefully) not outdated way of installing it.
sudo pacman -S wine cabextract| # Get all PackageReferences from a project or solution | |
| # Does NOT include transient dependencies | |
| # Example A: Get-PackageReference ./MySolution.sln | |
| # Example B: Get-ChildItem -Recursive *.csproj | Get-PackageReference | |
| function Get-PackageReference { | |
| [CmdletBinding()] | |
| param ( | |
| [Parameter( | |
| Mandatory = $true, | |
| ValueFromPipeline = $true, |
Should work on Windows, Linux and MacOS. I've only tested Windows so far.
VanillaOS's APX tool is quite neat since you can export desktop-entries with apx export <program>. However, if you like to run CLI tools on your host system without apx enter it's a bit trickier. Here's a little guide on how you can get around this using she-bang scripts.
Create a folder somewhere in your home-directory structure that you'd like to contain shebang scripts. I'm just going to use ~/scripts as a starting point.
Add the folder to your shell's PATH environment variable: