Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Search the Community

Showing results for tags 'program change'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Support
    • Multi-Effects Units
    • Variax Instruments
    • Amplifiers
    • Computer Based Recording
    • Live Sound
    • Pedals/Controllers
    • Dream Rig - Line 6 Product Integration
  • General Discussion
    • Tone Discussion
    • Line 6 Lounge

Categories

  • General FAQ
    • Operating System-specific Information
  • Tutorial Videos
  • Effects/Controllers
    • HELIX/HX
    • DL4 MkII Stompbox Modeler
    • FBV Controllers (MKII / 3)
    • M5
  • Amplifiers
    • Powercab
    • Catalyst
    • Spider V
  • POD
    • POD Go
    • Pocket POD
    • POD Express
  • Guitars
    • JTV / Shuriken / Variax Standard / Workbench HD
  • Relay/XD-V Digital Wireless
  • Recording
    • Helix Native
    • Metallurgy
    • Echo Farm/Amp Farm
    • POD Farm 1/2.0/2.5
    • Computer Audio Set Up and Troubleshooting
  • Legacy Products
    • POD
    • Amps
    • 1st Gen Variax Guitars / Bass / Workbench
    • Effects and Controllers
    • AMPLIFi Series
    • Live Sound
    • Digital Wireless
    • Mobile Products
    • POD Studio / Tone Port / GuitarPort
    • Software
    • Dream Rig

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Registered Products

Found 14 results

  1. Hey all, I'm relatively new to MIDI and wanted to share some settings and menu dives that I've encountered in my research that got Helix Rack and the Hologram Electronics Microcosm talking to one another seamlessly and behaving the way that I intend it too. Looking over the internet, it's pretty easy to find direction on how to get everything set up but there isn't anything Helix Rack/Microcosm specific so I thought it would be handy to have all the information I've uncovered in one place to save on time for other Helix/Microcosm users. While this may be intuitive for more seasoned MIDI users, this took a moment for me to wrap my mind around. I'm by no means a MIDI expert and am only scratching the surface here. YMMV and if anyone wants to plug any holes, correct any mistakes and expand; I'm game.. You'll want a copy of your user manual for both Helix Rack and Microcosm. User Manuals Helix Rack: https://line6.com/data/6/0a020a3f63bf5fb6a4a7df95a/application/pdf/Helix Rack and Control 3.0 Owner's Manual - Rev D - English .pdf Hologram Electronics Microcosm: https://b82316c2-7eca-4286-9569-a4da8097c930.filesusr.com/ugd/74428b_c4e6e20555914198bdb59c12f9a9e4d4.pdf What I found easier for me is, rather than using HX Edit on a computer connected to Rack, use the Human Machine Interface (HMI, ie the front panel of Helix Rack) to navigate all the settings and save when you are finished. Let's dive right in. Connections I/O: The first thing you'll want to do is fairly obvious. Get everything hooked up. For my purposes I use 5 Pin MIDI Cable going directly from my audio interface to Helix Rack's MIDI input. I then connect another 5 Pin MIDI cable from Helix Rack's Out/Thru to the MIDI input on Microcosm. My understanding is that you can also accomplish some of these connections via USB but I've not explored these settings or connections. Beyond that I have Microcosm's audio routed into one of the effects loops on Helix Rack and have been experimenting with wet/dry (etc) signal flows. Global Settings: The first thing I wanted to do was be able to control tempo on Helix Rack via Ableton and then send that MIDI clock to Microcosm via Helix Rack. The thinking is that while recording, I'll be using a click and can have delays and other time based effects both internally on Rack as well as the delays and loops on Microcosm sync to click. This will also help when my guitarist (also a Rack user) is using delays or other time based effects and we will be more in lockstep with one another. Everything is slaved off of one master MIDI Clock. The hope is that this will have utility further down the road as we will be using Ableton to control clicks, backing tracks and samples for live performances. These settings are relatively straight forward. To control Helix Rack via an external Midi Clock, you'll want to navigate Menu > Global Settings > MIDI/Tempo and set "Receive MIDI Clock" to "MIDI". This allows Helix Rack to sense the click coming from the DAW (you'll have to play with the MIDI sync settings in whatever DAW you use to get Helix Rack and the DAW to "see" one another). You will know when Helix Rack syncs with an external clock as the Tap Tempo Switch on your Helix Foot Controller (if available) will switch from Red to Blue. My experiences is that Helix Rack only receives the clock from Ableton when you select Play or Record in Session or Arrangement mode of Ableton. To Send MIDI Clock to Microcosm via Helix Rack you'll want to navigate Menu > Global Settings > MIDI/Tempo and change "Send MIDI Clock" to "MIDI". "When [Microcosm] receives a MIDI Start Message, the pedal [Microcosm] will switch from its internal clock to the external clock signal. Upon receiving a MIDI Stop message, the pedal [Microcosm] will revert back to its internal clock" (Microcosm User Manual .pdf, p. 21 or p. 41 of the physical manual). My experience is that if you aren't syncing Helix Rack from an external clock such as a DAW, Microcosm will still Clock sync with Helix Rack via Tap Tempo (controlled either on the HMI or on the Foot Controller) provided you have "MIDI" selected on the "Send MIDI Clock" setting. While you are in Global Settings you will want to make a crucial change. This was the biggest bottleneck I was running into when setting up MIDI to behave in the way I intended it too. Helix Rack has a default set of Program Change messages that it sends upon preset selection and in order to defeat this default you will want to set "MIDI PC Send" to "Off" (on page two of "MIDI/Tempo" settings if memory serves). Doing this will allow you to customize; within Command Center, which Program Change messages you want to send without interference from Helix Rack's default PC messages. Big Ups to forum user rd2rk for cluing me into this setting here: https://line6.com/support/topic/52777-helix-program-change-midi-out/ Command Center Settings: The other behavior I wanted to effect was selecting which of 44 presets Microcosm loads when I load different presets in Helix Rack. Hologram Electronics conveniently includes a list of Control Change and Program Change messages in Microcosm's user manual. To change presets we will be interested in Program Change (PC) messages which you will find on page 21 of Microcosm's .pdf manual or on page 40 of the physical manual. We will use Helix Command Center to assign which PC messages we want to send upon Preset or Snapshot Selection. On Helix Rack; from the preset you wish to assign MIDI messages to, navigate Menu > Command Center. This will bring up a display of Lightning Bolts, footswitches, knobs and expression pedals. Select one of the Lightning Bolts as this will be your "Instant" location. From here change "Command" to "Bank/Program" and on "Program" select the numerical value you want Helix to send to Microcosm. My experience is that Helix Rack sends PC messages starting at the value of Zero while Microcosm receives commands starting at a value of One, so you will want to send a value from Helix that is one subtracted from the PC value listed in Microcosm's manual. For instance, if you wished for the Microcosm preset, "Mosaic C" to load when selecting a Helix preset you'll have to assign a preset value of 22 even though the manual lists 23 as the program change value for "Mosaic C". Essentially you are fooling Microcosm into thinking that Zero is One, One is Two, so on and so forth. I discovered this on this HX Effects user's Youtube Video here. The user goes over it at around the 2:12 Mark. https://www.youtube.com/watch?v=LUZN5hl8QPo&t=202s My experience is that you have to change these values in Command Center for each of your Snapshots as well although there may be a way of not having to do this (in other words the Helix preset selects the Microcosm preset that's consistent for each Snapshot automatically) that I have yet to uncover. The utility of this is using Snapshots to select different Microcosm presets within a Helix preset. Make sure to Save your presets frequently. I find it helpful to save after every little change I make. Bonus points for figuring out how to assign CC messages to control certain parameters on Microcosm such as "Mix" and "Activity" via Expression Pedals. You can assign CC and PC commands to control Microcosm's parameters to the Foot Controller's footswitches within Command Center but this hasn't proved useful to me just yet. This process is way more straight forward and has been covered ad nauseam on YouTube, at least with other MIDI capable devices. This is by no means exhaustive, I just wish this information was a little more easily searchable for Microcosm specific questions. No doubt this can apply to other MIDI Capable pedals and devices. Learning how to program and use Helix Rack as a MIDI controller in addition to controlling Helix Rack with external MIDI is a total game changer for me. Hopefully someone out there finds this scratching at the surface useful.
  2. I'm having a tough time getting my TC-50 head to respond to my Helix LT for amp control via MIDI. This is my first time attempting to use MIDI. I'm connected to the amp via 4cm, with the MIDI connected from the out on the helix to the in on the amp. I'm running the helix in snapshot mode. What I'm specifically trying to achieve is channel changes on the amp, along with standard effect/parameter changes in helix. Example: Footswitch 1: CLEAN on TC-50 with Helix reverb + delay Footswitch 2: LO on TC-50 with Helix overdrive + reverb Amps midi CC numbers/values for channels: CLEAN = CC 20 w/ value 64 - 127 LO = CC 21 w/ value 64 - 127 HI = CC 22 w/ value 64 - 127 Things to note. The amp also responds to midi program changes - I've noticed that if I scroll through the presets menu that my amp changes channels with varying features coming on and off. So for some reason helix is sending program changes when loading a preset. If I could isolate that function to snapshots I would also be happy, as I could use the amp's solo/reverb/fx loop options as well instead of just singular purpose CC messages. Any help much appreciated.
  3. My setup : Computer sends program change to a master footswitcher (Decibel 11- Switch Dr). Then the Switch Dr sends program changes to a HX effects and another unit (TC nova drive). When I hit a preset on the Switch Dr, everything work perfectly. Hx changes to the right patch. But, if the Switcher receives a program change from the computer, then, everything still react accordingly except the Helix that now switch to the wrong patch. Now, I had a M13 in my original setup and everything was fine. Once I've upgraded from a M13 to a HX effects, I can't use a computer to change programs. I did numerous shows with that setup and the only difference is the HX effects. Any idea?
  4. I made a two-button footswitch for changing Helix patches up and down, using a generic (Elegoo) Arduino Nano board. It sends MIDI program change messages, and is endlessly customizable. Complete parts list: Hammond 1590a enclosure Elegoo nano (set of three for cheap https://www.amazon.com/Arduino-Elegoo-ATmega328P-without-compatible/dp/B0713XK923 ) two SPST momentary (normally open) switches LED and 220 ohm resistor (optional) panel-mount MIDI jack panel-mount 9v jack (optional, easy to power from 9v battery--Nano draws only 25mA, and only 37mA while LED is lit) hookup wire My code is pasted below. Entire project took less than two hours, and cost less than dinner. // midi.controller // Sends midi program change // Aaron Lyon April 2018 #include <MIDI.h> MIDI_CREATE_DEFAULT_INSTANCE(); byte patchNum = 0; #define BUTTON_PIN_1 2 #define BUTTON_PIN_2 3 #define LED_PIN 13 void setup() { pinMode(BUTTON_PIN_1, INPUT_PULLUP); pinMode(BUTTON_PIN_2, INPUT_PULLUP); pinMode(LED_PIN, OUTPUT); MIDI.begin(MIDI_CHANNEL_OMNI); } void loop() { if (digitalRead(BUTTON_PIN_1) == LOW && patchNum < 99) { // Next Program digitalWrite(LED_PIN, HIGH ); patchNum++; MIDI.sendProgramChange(patchNum, 1); delay(200); digitalWrite(LED_PIN, LOW ); } if (digitalRead(BUTTON_PIN_2) == LOW && patchNum >= 1) { // Next Program digitalWrite(LED_PIN, HIGH ); patchNum--; MIDI.sendProgramChange(patchNum, 1); delay(200); digitalWrite(LED_PIN, LOW ); } }
  5. Hi everybody, not sure if this is the right forum, but anyway: I have been trying to remote my Helix with Cubase (Pro, 9.5) an ran into different problems. My setup is like that: We are a band with guitar (me), keyboards, and bass. Drums are programmed in Cubase with Addictive Drums and the like (on an iMac in the studio, on a MacBook Pro when playing live). Everything is nearly complete »virtual«, guitar via Helix, bass via POD X3, and keyboards all into the mixer into an 6x headphone amp. So we can practice nearly silent alltogether except the vocals anyway. In Cubase I have not only the drum tracks but also some playbacks for vocals, guitars, fx etc. For live playing, I have set up »long« Cubase tracks which contain up to 9 songs each, one after the other. I can navigate between those different segments by using »cycle markers«, which are mapped to keyboard numbers 1-9. So if I press »4« on the keyboard, Cubase jumps to the beginning of song 4, pressing »space« starts the playback. This is very, very handy. See picture. Now I had been thinking of remote controlling my Helix (connected via USB) by setting up an extra MIDI-part for every »song-segment« going out to the Helix. In this part I have (momentarily) only two controllers: one »Program Change« that sends a PC message to switch between Helix presets, and one controller »cc57« that toggles footswitch 10 in stomp mode on the Helix. Footswitch 10 is always assigned to a kind of distortion/boost fx on the Helix, used for guitar solos etc. So, when I jump to a »song« via keyboard, the Helix should the select the correct preset at first, and when it comes to my solo part and »cc57« jumps from somewhere below 64 to somewhere over 64, footswitch 10 should be activated … and when my solo part is over (and »cc57« jumps under 64) it should be de-activated. So all I send to the Helix is a Program Change and a controller message. AND IT WORKS! BUT the following problems occur: 1. When I press the space bar (start/stop) inbetween a song segment, footswitch 10 toggles as well, regardless of the »cc57« value. So it inverts the state of the footswitch, making it »de-activated« when it should be activated. 2. When I press the space bar inbetween two songs, the Helix becomes completely MUTED (no sound). When I jump to the next (or another) song start, Helix gets unmuted and live again. This might by useful for live situations but is not wanted here. What am I doing wrong? Footswitch 10 is set to »toggle« … »latching« does not work anyway. Cubase is set up to use continuous controlling and event following. Thanks in advance, best regards Opti/Alex
  6. I have the Helix set up to send midi program changes to my Bias Amp to switch amps per snapshot. Problem is, when I switch presets on the HX EFX, I still have to go in and hit a snapshot to send the program change. I would like to change the amp when I change presets. Is there any way to send a PC message on preset change?
  7. I am using the Helix to control a bank of external pedals using the VooDoo Hex. I control the VooDoo Hex loops using CC messages. Of course, I can use the command center to do this, but manually assigning multiple channel / CC messages to control each loop for each snapshot (or foot controller) is tedious. I doubt live programming the Helix directly using an external app (midi or FBV) is easy (please tell me if I am wrong). Is there documentation on the .hlx JSON format? I could write an GUI editor to facilitate editing the .hlx files then upload to Helix with the Line 6 editor. I can try and use samples to reverse engineer, but it would be better to get official docs. thanks, mark
  8. Hi Guys Im having problems using Helix to control MainStage. I have set up Helix to have a preset for each song in my set, I want MainStage to have a playback and metronome click for each preset. I have successfully got Helix and MS synced up so when I change presets it changes patches on MS using an instant command in command centre. I also set up 2 switches on my Helix for each patch, one to turn on the metronome, the other to turn on a playback in MS. That works fine. However when I change presets using the Helix it also immediately fires either the metronome or the playback neither of which I want to happen. Ive tried all sort of combinations in MS but can't seem to stop it happening. Im no expert in midi so maybe my commands are wrong - Im using CC toggle commands for the playback and metronome but have no idea what CC# means so have tried different numbers which does nothing. Then I read on this forum that when Helix sends PC commands it also send all the other commands as well so Im wondering if this is the issue. Any help on this would be appreciated
  9. Hi, Here is what I would like to do : I want my HX effect to send Program changes when I press a switch which is programed to do so, but I don't want each time i recall a preset, that the unit send a PRG CHANGE command according to its number. How can I do that ? In global pref ? Thanks for your help !
  10. Hi, I just installed new firmware 2.50 for my Helix LT and it looks as though the midi messages sent from the Helix when changing preset are now wrong... When I switch preset, a midi message is sent out but Cubase recognises it a aftertouch? When I playback the midi track Helix won't aknoledge the incoming message (since it doesn't respond to aftertouch) and it won't change preset. Also, If I copy/paste the recorded messages from aftertouch to program change on my midi track in Cubase, the preset changes on Helix happen exactly as they should (which is how I patch the problem so far). Is there something wrong with Helix sending the wrong midi messages since I updated the firmware? Should I try a factory reset? I did try reinstalling cubase (didn't fix it) but I noticed the midi messages being sent from Helix are the same with another midi monitor software... Thank you!
  11. Hello I am trying to implement a channel change in Ableton Live 9.5 with M9, i.e to make M9 send some MIDI program change or another message that will switch between the channels. I tried using the MIDI mapper to assign Scene Change mesages from M9 to the Session Recording buttons (works perfectly with KEY mapping and a normal computer keyboard). However all I'm getting is a weird mapping interpreted as Pitchbend messages (see attached image). When trying it out nothing really happens. In the M9 Advanced Manual there is a MIDI map for scene select in Appendix A but I can't say I understand it: Scene Select Memory Location Program Change # Scene Selected Scene 1A (Fldr 1; 3) 0 (Fldr 1); 12 (Fldr 3) 1A (Fldr 1); 1A (Fldr 3) Scene 1B (Fldr 1; 3) 1 (Fldr 1); 13 (Fldr 3) 1B (Fldr 1); 1B (Fldr 3) Scene 2A (Fldr 1; 3) 2 (Fldr 1); 14 (Fldr 3) 2A (Fldr 1); 2A (Fldr 3) ... Any suggestions how to go on about this? Yuval
  12. I have en external synth Is it possible to send Program Changes to Gearbox so the presets change automatically? Greetings Raymond ;)
  13. Don't know if it's ok to post in two threads (moderators, sorry), but will try my luck. Hello everyone, I'm quite new to the MIDI thing. Say we have two PODs (X3 Pro and HD Pro) in a band and we want the DAW to change programs/presets automatically on both units. From what I've learned I need two midi tracks in my DAW. One set to Channel 1 (X3 Pro), one set to Channel 2 (HD Pro). Corresponding channels are set in the System settings of both PODs. The routing is the following: DAW (Logic Pro X) --> USB to midi cable --> X3 Pro midi in --> X3 Pro midi out --> HD Pro midi in. Problem Markers in midi track 1 (X3 Pro) do make changes on Pod X3, but markers in track 2 (HD Pro) do nothing. The only way it works is setting HD Pro to Channel 1 as well, but then changes are made simultaneously to the same preset (1A on both with program value set to 0, for instance), which is not quite usable. Any ideas?
  14. Hello everyone, I'm quite new to the MIDI thing. Say we have two PODs (X3 Pro and HD Pro) in a band and we want the DAW to change programs/presets automatically on both units. From what I've learned I need two midi tracks in my DAW. One set to Channel 1 (X3 Pro), one set to Channel 2 (HD Pro). Corresponding channels are set in the System settings of both PODs. The routing is the following: DAW (Logic Pro X) --> USB to midi cable --> X3 Pro midi in --> X3 Pro midi out --> HD Pro midi in. Problem Markers in midi track 1 (X3 Pro) do make changes on Pod X3, but markers in track 2 (HD Pro) do nothing. The only way it works is setting HD Pro to Channel 1 as well, but then changes are made simultaneously to the same preset (1A on both with program value set to 0, for instance), which is not quite usable. Any ideas?
×
×
  • Create New...