vault backup: 2026-08-15 15:07:24

04-guides/Helix plugins-08-08-2026.md

@@ -0,0 +1,26 @@
+As of August 2026, Line 6 (and its sister brand Ampeg) offers a tiered ecosystem of audio plugins ranging from massive, do-it-all sound design sandboxes to highly specialized, genre-specific tools.  
+The biggest recent shift is the introduction of **Helix Stadium Native**, which represents the next generation of Line 6's flagship software.  
+Here is how these four plugins compare and contrast.
+
+## **High-Level Comparison**
+
+| Plugin | Primary Focus | Core Modeling Tech | Interface & Routing | Standout Features |
+| :---- | :---- | :---- | :---- | :---- |
+| **Helix Stadium Native (1.3.3)** | Flagship All-in-One | Agoura \+ Legacy HX | Freeform grid (48 blocks max) | Graphical mic placement, sidechaining, 192 kHz support |
+| **Helix Native (3.82)** | Legacy All-in-One | HX Engine | Freeform grid (32 blocks max) | 1-to-1 preset compatibility with older Helix hardware |
+| **Metallurgy Collection (1.0.3)** | Metal Guitar | HX Engine | Photorealistic, fixed flow | Curated for Modern, Thrash, and Doom metal |
+| **Ampeg SVT Suite (1.12)** | Bass Guitar | Ampeg Emulation | Photorealistic, fixed flow | Dual-cab/IR modes, 3 legendary SVT heads |
+
+## **The Flagships: Helix Stadium Native vs. Helix Native**
+
+With the August 2026 release of Stadium Native, Line 6 split its flagship offering into two distinct paths. Both are massive sandboxes for guitar, bass, and synth, but they serve entirely different purposes moving forward.
+
+* **Helix Stadium Native (1.3.3):** This is the new powerhouse. It introduces the "Agoura" generation of amp modeling while retaining the older HX channels for backward compatibility. It vastly expands the DSP limits by allowing up to 48 block locations (up from 32), supports sample rates up to 192 kHz, and introduces highly requested features like sidechain support for ducking delays and envelope filters. The UI has also been upgraded to feature graphical mic placement and nested folders for preset management.  
+* **Helix Native (3.82):** This plugin is now considered the "legacy" version. It tops out at 96 kHz and 32 blocks. However, Line 6 is keeping it alive and updated for a very specific reason: **archive safety and hardware compatibility**. If you own an older Helix Floor, LT, or HX Stomp, Helix Native 3.82 ensures 1-to-1 preset compatibility so you can seamlessly transfer patches between your DAW and your physical pedalboard. Stadium Native installs as a separate plugin so it won't overwrite or break your older Helix Native sessions.
+
+## **The Specialists: Metallurgy vs. Ampeg SVT Suite**
+
+While the Helix plugins offer a "blank canvas" approach that requires building signal chains from scratch, Metallurgy and the SVT Suite are designed for musicians who want immediate results without menu-diving. Both feature photorealistic, analog-style interfaces with fixed signal flows (Pedals \-\> Amp \-\> Cab \-\> Post-FX).
+
+* **Metallurgy Collection (1.0.3):** This suite is laser-focused on metal guitarists. It is actually three separate plugins (Modern, Thrash, and Doom) that package Line 6's HX modeling technology into curated, easy-to-use rigs. Instead of scrolling through hundreds of amps, you get four specific amp models per plugin, paired with eight cabs and a tailored selection of pre/post effects (like polyphonic pitch-shifting). It eliminates option paralysis while maintaining top-tier sound quality.  
+* **Ampeg SVT Suite (1.12):** Built specifically for bassists, this plugin bypasses generic HX modeling in favor of dedicated, brand-endorsed Ampeg emulations. It features three of the most famous SVT heads (the Heritage 50th Anniversary, Heritage SVT-CL, and SVT-4PRO) and eight Ampeg cabinets. It offers unique bass-centric features that Metallurgy lacks, such as a parallel room mic blend, dual-cab/IR modes, and specific Ampeg pedals like the Rocktaver and Phasifier.

04-guides/Hollywood Git Master Guide.md

@@ -0,0 +1,111 @@
+# **The Complete Guide: Local and Remote Git Workflow**
+
+This guide walks through the exact operational process used to create, configure, sync, and push a repository named **hollywood** between your local development machine and a self-hosted Oracle VPS.
+
+## **Part 1: Server-Side Preparation (Oracle VPS)**
+
+Before your local machine can push code anywhere, the destination bare database must exist on the remote server.
+
+### **1\. Connect via your SSH Shortcut**
+
+Instead of typing out long IP addresses, use the custom alias configured in your \~/.ssh/config file:
+
+ssh oracle
+
+### **2\. Create the Bare Repository Vault**
+
+On the remote server, create a dedicated directory ending in .git inside the git user's home directory and initialize it as a bare repository (meaning it holds only version history without an active working directory):
+
+mkdir \~/hollywood.git  
+cd \~/hollywood.git  
+git init \--bare  
+exit
+
+## **Part 2: Local Machine Setup (Windows / PowerShell)**
+
+Now, configure your local workspace so it knows how to securely talk to your private server without hardcoding keys or raw IP addresses every time.
+
+### **1\. Configure Global Git Identity**
+
+Ensure your commits are properly attributed to your developer profile:
+
+git config \--global user.name "Your Name"  
+git config \--global user.email "your.email@example.com"
+
+### **2\. Set Up the Windows SSH Config File**
+
+On your Windows machine, ensure your C:\\Users\\medic\\.ssh\\config file contains your connection details (without any file extension):
+
+Host oracle  
+    HostName 129.213.172.214  
+    User git  
+    IdentityFile C:\\Users\\medic\\.ssh\\ssh-key-2026-08-06.key
+
+## **Part 3: Creating and Linking a Local Project**
+
+If you are starting a brand new project or linking an existing local folder to your Oracle vault:
+
+### **1\. Navigate to Your Project Workspace**
+
+cd C:\\000\\00-vaults\\00-hollywood
+
+### **2\. Initialize Git (If it's a brand new project)**
+
+git init
+
+### **3\. Link Your Remote Server Vault**
+
+Point the local origin nickname to your Oracle alias and bare repo path:
+
+git remote add origin oracle:da_new_shit.git
+
+*(Note: If you ever need to check where origin is pointing, run git remote \-v)*
+
+## **Part 4: Daily Workflow — Pushing and Pulling**
+
+Once your project is linked, managing updates follows a clean, reliable loop.
+
+### **1\. Saving Local Changes to the Server**
+
+When you edit files locally and want to sync them to your Oracle vault:
+
+\# Stage all modified files  
+git add .
+
+\# Commit changes with a clear message  
+git commit \-m "Update project notes and structure"
+
+\# Push the updates to the server (tracking the main branch)  
+git push \-u origin main
+
+### **2\. Pulling Updates from the Server**
+
+If you worked on another device (like WSL) and pushed updates to Oracle, download those changes into your current workspace:
+
+\# Fetch history changes without altering files  
+git fetch origin
+
+\# Merge changes into your active branch  
+git pull origin main
+
+## **Part 5: Alternative Environment Setup (WSL)**
+
+If you switch over to WSL and want to clone or work on the same repository:
+
+### **1\. Secure Your Private Key Permissions in Linux**
+
+WSL enforces strict OpenSSH key security requirements:
+
+chmod 700 \~/.ssh  
+chmod 600 \~/.ssh/ssh-key-2026-08-06.key
+
+### **2\. Configure WSL SSH Config (\~/.ssh/config)**
+
+Host oracle  
+    HostName 129.213.172.214  
+    User git  
+    IdentityFile \~/.ssh/ssh-key-2026-08-06.key
+
+### **3\. Clone the Remote Vault Down to WSL**
+
+git clone oracle:da_new_shit.git