ShowMIDI is a multi-platform GUI application to effortlessly visualize MIDI activity. This application fills a void in the available MIDI monitoring solutions.
Instead of wading through logs of MIDI messages to correlate relevant ones and identify what is happening, ShowMIDI visualizes the current activity and hides what you don't care about anymore. It provides you with a real-time glanceable view of all MIDI activity on your computer.
Uwyn ShowMIDI (MiDi Activity Monitor Plugin) v1.0.1 VST VST3 AU CLAP LV2 STANDALONE LiNUX WiN MAC [FREE] screenshot
Usage:
To use it, simply double-click the application to launch it.
To pause the MIDI data stream, press the spacebar, to un-pause, press it again.
The plugin versions can be used in any DAW that supports MIDI effect plugins. Some plugin formats, like VST3, might filter out certain MIDI messages and not present a fully accurate view.
This application fills a void in the available MIDI monitoring solutions.
Instead of wading through logs of MIDI messages to correlate relevant ones and identify what is happening, ShowMIDI visualizes the current activity and hides what you don't care about anymore. It provides you with a real-time glanceable view of all MIDI activity on your computer.
Cab-Lab 4 with DynaCab™ makes it quicker, easier, more intuitive, and more fun to achieve great tone, allowing you to customize and mix cabs, mics, and more. An Impulse Response, or “IR” can be thought of as a sonic “capture” — essentially the “fingerprint” of a tone over time. Fractal Audio is known for industry-leading amp modeling, but was also the first to allow installable Impulse Responses in a guitar product. This set a new industry standard. Suddenly, guitarists could to recreate the sound of their favorite mic’d speaker cabs in a portable format, for both studio recording and live performance.
CAB-LAB is FREE. Download Below!
Standalone and Plugin Versions
Cab-Lab 4 comes with both Standalone and Plugin Versions. The Standalone uses your Axe-Fx III, FM9, FM3, or another audio interface so you can select, position, and mix mics while listening in real-time. The plugin version processes audio in your compatible DAW or host and can be used both to “re-cab” raw amp recordings. Features include a 4-channel IR mixer, plus tools to EQ, align, and more. Cab-Lab can export IRs for your Fractal Audio hardware product, save files to your computer.
DynaCab™ Technology
For decades, artists, producers, and engineers have carefully positioned and mixed mics on guitar speaker cabs in the pursuit of great tone. DynaCab™ replicates this process in a revolutionary way, allowing you to hear results in real-time while moving a virtual mic on a virtual speaker. Compared to previous techniques, DynaCab™ makes it faster, easier, and more intuitive to find the tone you’re looking for without sifting through so many individual IRs. In fact, the DynaCab system in Cab-Lab 4 offers even more resolution and flexibility than our hardware products, with 360° of placement at variable distances, the possibility of additional microphone choices, and more.
DynaCab Packs
DynaCab Packs are like plugins for Cab-Lab. Each pack contains a “3D” set of speaker IR captures made with multiple microphones. For example, packs might be based on a vintage 4×12, modern 2×12 or boutique 1×12. With a DynaCab Pack installed, you have complete access to the vast array of tones that the captured speaker and available microphones are able to produce.
Ripchord is a free MIDI plugin for creating and remixing chord progressions. You can create custom chord presets from scratch, load expansion packs, or import any MIDI file that contains chords and Ripchord will automatically create a preset from it. Ripchord helps you easily compose progressions by playing single notes to trigger full chords. You can watch the tutorial on YouTube: Ripchord Overview
Expansion Packs
Anyone is welcome to make expansion packs for Ripchord, and give them away or sell them, without any further permission required. We don't sell any expansion packs directly, or take any kind of cut from third party expansion pack sales.
Open Source
Ripchord is open source under GNU GPLv3. You can check out the source code on Github: Source Code
Plugin Formats
Ripchord is avalailable as an AU or VST3 for Mac, and a VST3 for Windows. We get a lot of requests for a VST2 version of Ripchord. Actually the first version of Ripchord we made was a VST2, and then we found out that Steinberg would not let us give it to anyone. Steinberg stopped granting any new VST2 licenses in 2018 because they are trying to retire the format, so unfortunately that is the end of the story. This also means that whatever DAW you use must support the full VST3 MIDI spec in order to use Ripchord. More details can be found here: VST2 is Discontinued
Play Mode
Ripchord has two modes, play and edit. Most of the time you will be in play mode, in which you can either play an external MIDI keyboard, or click on the input keys with a mouse, in order to trigger the chords in your preset and compose progressions.
1.
(Button) Favorites or unfavorites the currently loaded preset.
2.
(Button) Opens the menu.
3.
(Button) Allows the chords to be enabled or disabled while maintaining the MIDI routing.
4.
(Button) Contains any MIDI that has been recorded. When it is fully illuminated you can click and drag the MIDI from this button into your DAW.
5.
(Button) Switches between the presets view and the keyboards view.
6.
(Display) The name of the currently loaded preset will be displayed here.
7.
(Arrows) Select the next or previous presets in your collection. You can also use the left, right, up, and down keys on your computer's keyboard to trigger these buttons.
8.
(Button) Switches between play and edit mode.
9.
(Button) Clicking once enables MIDI recording. When enabled, recording will begin the moment the first input note is recieved. Clicking this button a second time will disable MIDI recording.
10.
(Button) Switches the direction of the velocity strum between always LTR, always RTL, LTR then alternate, or RTL then alternate. It can only be clicked if the velocity strum knob has been engaged.
11.
(Knob) Increases the velocity strum, which is the difference in velocity between the first and last notes of a chord. The difference will be spread evenly across all of the notes.
12.
(Knob) Increases the velocity humanization, which is random variation in velocity between all of the notes in the chord.
13.
(Button) Moves the transpose keys to the left on the input keyboard. It can only be clicked if the transpose button has been engaged.
14.
(Button) Engages the transpose keys. When engaged, the bottom two octaves of the input keyboard will operate in latch mode to transpose the chords in the preset up or down one full octave.
15.
(Button) Moves the transpose keys to the right on the input keyboard. It can only be clicked if the transpose button has been engaged.
16.
(Knob) Increases the note humanization, which is random variation in timing between all of the notes in the chord.
17.
(Knob) Increases the note strum, which is the difference in timing between the first and last notes of a chord. The difference will be spread evenly across all of the notes.
18.
(Button) Switches the direction of the note strum between always LTR, always RTL, LTR then alternate, or RTL then alternate. It can only be clicked if the note strum knob has been engaged.
Edit Mode
Edit mode can be used to create a new preset from scratch, or to edit an existing preset. In edit mode, when you mouse click on the input keys, instead of triggering the chord, it will select the input key so that you can assign or modify the output keys that are mapped to it. You can still trigger the chords in edit mode if you have an external MIDI keyboard hooked up, that way you can preview the chords as you edit them.
MIDI 2.0 is an extension of MIDI 1.0. It does not replace MIDI 1.0 but builds on the core principles, architecture, and semantics of MIDI 1.0.
A foundational architecture for MIDI 2.0 expansion is defined by the MIDI Capability Inquiry (MIDI-CI) specification. MIDI-CI allows Devices with bidirectional communication to agree to use extended MIDI capabilities beyond those already defined in MIDI 1.0, while carefully protecting backward compatibility.
MIDI 2.0 is not a stand-alone specification. Manufacturers and developers must have a thorough understanding of MIDI 1.0 in order to implement MIDI 2.0.
MIDI 2.0 Core Specifications:
These documents make up the MIDI 2.0 Core Specifications. Please click on individual name to access details for document:
MIDI 2.0 Specification Overview
MIDI Capability Inquiry (MIDI-CI)
Common Rules for MIDI-CI Profiles
Common Rules for MIDI-CI Property Exchange
Universal MIDI Packet (UMP) Format an MIDI 2.0 Protocol
MIDI Clip File Specification (SMF format for UMP)
Protocol
The MIDI 2.0 Protocol is an extension of the MIDI 1.0 Protocol. Architectural concepts and semantics remain the same as MIDI 1.0. Compatibility for translation to/from the MIDI 1.0 Protocol is given high priority in the design of the MIDI 2.0 Protocol.
Compared to the MIDI 1.0 Protocol, MIDI 2.0 Protocol messages have extended data resolution for all Channel Voice Messages. New properties have been added to some Channel Voice Messages, and new Channel Voice Messages have been added with greatly improved Per-Note control and much more musical expression.
Property Exchange
Property Exchange is part of the MIDI Capability Inquiry (MIDI-CI) specification and MIDI 2.0. Property Exchange is a method for getting and setting various data, called Resources, between two Devices. Resources are exchanged inside two payload fields of System Exclusive Messages defined by MIDI-CI, the Header Data field and Property Data field. This document defines only the contents of the Header Data and Property Data fields. For information on how to transmit and receive these Resource payloads inside MIDI-CI System Exclusive messages, see the MIDI Capability Inquiry specification and Common Rules for MIDI-CI Property Exchange specification.
Profiles
A Profile is a defined set of rules for how a MIDI receiver device implementing the Profile shall respond to a chosen set of MIDI messages to achieve a particular purpose or to suit a particular application.
Included:
1. MIDI 2.0 Core Specifications
- MIDI 2.0 Specification Overview
- MIDI Capability Inquiry (MIDI-CI)
- Common Rules for MIDI-CI Profiles
- Common Rules for MIDI-CI Property Exchange
- Universal MIDI Packet (UMP) Format an MIDI 2.0 Protocol
- MIDI Clip File Specification (SMF format for UMP)
2. Protocol
- Universal MIDI Packet (UMP) and MIDI 2.0 Protocol Specification
- MIDI 2.0 Bit Scaling and Resolution
3. Property Exchange
- Core Property Exchange
- Property Exchange Foundational Resources
- Property Exchange Channel Resources
- Property Exchange Programlist Resource
- Midi-ci Property Exchange Controller Resources
- Property Exchange Get And Set Device State
- Property Exchange Mode Resources
- Common Rules For Midi-CI Property Exchange
- Property Exchange Localon Resource
- Property Exchange Externalsync Resource
4. Profiles
- Common Rules For Midi-ci Profiles
- Midi-CI Profile: Default Control Change Mapping
- Midi-CI Profile For Midi Polyphonic Expression
- Midi-CI Profile For Note On Selection Of Orchestral Articulation
- Midi-CI Profile For Drawbar Organs (Single Channel)
- Midi-CI Profile For Rotary Speaker
- Midi-CI Profile For General Midi 2 (Function Block)
- Midi-CI Profile For General Midi 2 Single Channel
