gbbaker

. . . . . . and now you know the rest of the story! . .. .

=+ 1

Well, . . . .. I would guess that there are messages being sent back and forth. I base this on the fact that the "Helix Editor" is a USB connected devise and has to be able to receive "Status" updates. Now, that does not mean that the messages are pure MIDI CC messages and could very well be "System Exclusive" type messages ( i.e. NOT CC# messages) or hard coded MM API calls in C, C# or C++. Once Native is out we should be able to "intercept" the transmissions back and forth and decode the messages even if they are SysEx. A program like MIDIOX or even the "Edit MIDI Messages" view in many DAWS may be able to tell you what is being sent. I'll see what I can find in a day or two. Perhaps a Line6 support agent can lead us on a better path. You will need to be sure and have the MIDI Thru parameter set on the Helix in any case. Good Luck, Bo

Machine is a "Drum Controller". These are normally, by default, set to communicate on channel 10. Not channel 1 which is a typical default channel. Just saying . . . . . . Good luck Bo Baker

HI, I think the Tap Temp CC#64 will work since it is a "published" interface. It use to be that Manufacturers would publish a "Midi Implementation Sheet" that would show the MIDI in/outs that were "public" implemented commands. That seems to have gone by the way-side as of late and we only get "Here's what you can do" type lists. If you have a program that can capture MIDI Messages between your control and the PC and display them in a readable (ie. not hexadecimal) format you can most likely reverse engineer most of the commands. Since L6 has their own Editor and are in the process of creating the NATIVE software program, it appears that "All?" the parameters can be controlled with MIDI or MIDI type commands. However, in most cases these are SysEx (System Exclusive) commands and not simple CC# type commands. That means your "controller" would need to send sysex type messages. There are controllers that will do this but the learning curve can be steep unless it has a "MIDI Learn" function. I am not sure what you are trying to accomplish, but you may wish to check out my MIDICONTROLL1 preset template on CUSTOMTONE. It is several pages down at this point but will give you some pointers on how to set up HELIX as a foot controller to send MIDI messages to "RECORD, PLAY, PAUSE, STOP, REWIND using foot-switches 7 through 10 Once NATIVE is out I'll be more likely to dig a little deeper into the MIDI implementation as it should be easier to capture some of the "behind the scenes" MIDI processing. Good luck, Bo Baker . . . listed as Gary Baker on CUSTOMTONE

Next time you do an update - after you do the update BUT before you reload your saved setlists save a copy of one of the setlists that are totally empty and call it "Empty setlist". Then reload any saved set lists you want and use the "Empty setlist" to clear out ALL THE CONTENTS of any "SCRATCH PAD" setlist you use for trying out sounds or just want to start over. The only way to get rid of ONE preset is to load in a BLANK preset over it. Good luck, Bo

Yes you can - The HELIX is a full featured MIDI/Audio interface. When you set up your Audio/MIDI drivers note that the HELIX has 8 input and output ports. I use input 1 and 2 for the HELIX MIDI/Audio info and inputs 3 and 4 for the "BIG SKY" MIDI interface. Best to keep the CC# commands separated! I like the Big Sky for the reverb and the Librarian and Editor make the interface a breeze. Good luck, Bo Re: Phil-M You are correct that there is not much that the HELIX can do as an "off-board" Controller other than sending MIDI Play, Stop, Pause, Rewind and Record to a sequencer/DAW and a few CC# numbers. BUT . . . .The OP has the software to do all the Editing (Nixie) and Big Sky patch Save/Recall (Librarion). He just wanted to know if the HELIX will act/replace the required MIDI hardware interface - which it will. Bo

You're getting good advise from gunpointmetal and datacommando and he is spot on with the picture. It sounds like you are new to DAWs and REAPER (great choice by the way!). I'd suggest you watch several of the on line VIDEOS at this site http://www.reaper.fm/videos.php to get a great introduction on the way you can utilize REAPER. IN a nut shell: You record your own track of music on one track or drop a wave/mp3/mp4 file that is on your computer on to a REAPER track. That becomes your "Play Back Track". Once it is recorded or dropped onto the track, you can adjust the "OUTPUT SOUND" with the faders in REAPER. You feed the REAPER output into the HELIX USB Input - usually inputs 3/4. But the volume of track 3/4 is controlled by REAPER's faders - not HELIX. Once that is done you are ready to play along with the backing track by connecting your instrument into HELIX. If you just want to play along and not record what you are playing that is it. Adjust the Instrument's volume as you always have in HELIX. Balance the backing track to your instrument with the faders feeding the backing tracks into HELIX. If you want to record what you are playing so you have a "Song" with backing tracks and your instrument - well - best to watch some of the above video's which will get you going in no time. Good luck! Bo

Not sure if this will help but . . . . I am assuming that you are using HELIX as your Reaper's digital input/output source. You are sending two different signals into REAPER. One is the playback signal from REAPER into your headphones and the other is your guitar input into REAPER and then back out to your headphones. You should not be using any latency compensation and the output from the REAPER Tracks will need to be balanced (in REAPER) to match the guitar signal going into and out from ) REAPER.. You need to turn "monitoring" off in Reaper as you are listening through HELIX (right?). It may be an issue with the headphones, It might help to know the "hardware" configuration you are using to get the input/outputs from REAPER. Is everything running on HELIX only or is there another USB interface sending the REAPER backing track into the HELIX? I'd suggest playing around with the "REAPER monitoring" settings and the Playback settings in REAPER. I think your headphone are fine since they work in all cases except when you go to record. Good Luck, Bo

OK well glad you came up with a workable solution. I guess you tried inserting some extra time (measures in the songs) to give the Helix time to send and receive messages. Best regards Bo

Another day, another thought . . . . in reviewing the documentation I ran across this little gem on page 11 in the second pinned NOTE: "While in Stomp mode, stepping on the Bank Up or Bank Down temporarily enters Preset mode. Once you have selected a preset, Helix returns to Stomp mode." Perhaps this is what is happening to you. When your DAW sends a BANK Change while in STOMP MODE the Helix is waiting for a Preset change as if it is in Preset Mode. Therefore, none of the Stomps are able to receive a message. Then when you manually change the preset it returns to stomp mode and all is well. If this is the case than a second Preset message after the first Bank/present message from your DAW should return you to the stomp mode. In other words - send two bank/preset messages. The first changes to the correct bank, the second chooses which Present in that new bank and returns control back to the Stomp switches. Rather convoluted - but that is how the Helix is set up to work. Good luck getting this all sorted out. Bo

Humm . . . . I have everything working at my end On REAPER. My set up is HELIX and REAPER send to channel 1. Only one recorded track with Songs identified with 'Markers" to jump to next song. Markers are numbered 1,2,3,4 which in MIDI terms is 0,1,2,3. The NEXT and PREVIOUS stomps send CC#19 and CC#20 and the other Stomp switches are set to MMC commands PLAY and STOP. I think you need to identify why you are getting two CC commands AND make sure if you have not already that you give the HELIX some time to capture and post the Marker command before sending you next song's patch changes. I still think that it is a timing issue between the computer and the HELIX. Also could be caused by the less than high quality USB cable that ships with he HELIX. If you have other USB chords try a few and see if that helps. Other than that, I guess it''s time for a post to Line6 support. Good luck! Bo

Hello. OK Well refering to pages 57 and 58 of the HELIX User Manual on MIDI; the CC # 1,2 and 3 are "reserved" commands for the EXP 1,2,3 Pedals. Several other CC# are reserved (refer to the MIDI Chapter in the User Manual.). I would suggest changing the Next/Previous Marker CC Commands to CC#77 and CC#78 as these are not "reserved" according to the HELIX documentation. Let me know if that gets it working! Also, remember to put some distance in time between the "NEXT command" from the Helix Footswitch and the return Patch/Snapshot commands from the DAW. The HELIX needs some time to grab those commands and will most likely get "confused" if it is left "hanging". Bo UPDATE: 2/25 I now have everything working between the HELIX and my REAPER DAW. My foot switches go to Next or Previous Marker in the DAW and the other switches work fine. As mentioned above, I used CC# 19 and CC# 20 to make the Next/Previous jumps. Going to creat a few "songs" in the DAW today and use the Markers to jump to the start of each song and see what happens. You having any luck in getting your set up to work? Bo

Had another thought: On the foot switches that send the " Next/Previous" CC# ( sending a "Marker") what are you sending in the way of CC# messages? Bo

Hello, OK I thought that that might be the case. So . . . . one BIG MIDI File with "Measure Markers" (most DAWS can do this) for the separation of "Songs". So it is really just a "jump" to next marker. I am guessing that there is not enough "time" between sends of data back and forth. Place a few measures of time between sending the "next marker CC and the CC to HELIX for patch change. That should do it. You have the right process and the fact that when it's done "manually" tends to lead to a "timeout" type of issue between the two units. Let me know how that works out. Bo

Hello: Well I have everything working as far as sending and receiving Present changes, MIDI control messages and Snapshot changes after a DAW send. All switches are working after the DAW send. What I am not clear on is how you are using the Helix to "send" jump to next song" messages. What foot switch are you using and what command(s) and what channel are you sending the message. I can use the Helix Preset up/down to change the presents manually but have not attempted (yet) to use that switch to send "song" messages to a DAW. Since a "Song" is a file to your DAW not sure how to call up a new file using MIDI unless you are in a "juke Box" type of program which just goes from song to song. Any help?? Here are the Globals I am using.: Present Mode = Snap/Stomp Stomp Mode = 8 switches Mnapshot Mode = Manual MIDI Base = 1 Midi thru = ON, Midi over USP = ON, Midi PC = On Bo

If not, you should be using the "BANK/Program" setting for the Program changes and the CC commands for all the other. If I have time I'll try to replicate this although I'll be using REAPER rather than Cubase 9. Also, you might try taking a working program, do a copy/pase of that program - change Only the AMP type in the copied program and then see if all goes well. If it does, than that would indicate that there is something MIDI wise different between the two. (or there is a bug in the switch process.) Good luck. Also, it would help to know your GLOBAL settings for the switches as that may have an effect on what is "active" after a program change. Bo Baker UPDATE ON 2/21/2017 What I am seeing using REAPER as a DAW is that a program change PC sent from Reaper will change the Bank/Program and default to the Snapshot that is the Snapshot saved with the preset. In order to change to a differennt snapshot a new CC#69 with the snapshot's number must be sent (noet this is an offset number i.e. 0 = 1, 1 = 2, 2=3. etc. Your Globals/Preferences setting for Snapshots should be set as "Discard" so any changes to that's Snapshot will be discarded when you leave the Snapshot. Everything else seems to work OK for me. I'll see if I can get it to break tomorrow. Bo

Good point DI! Copy/Paste will work great on creating a new patch, But I don't think this will work very well on any "current" patches that use stompswitchs 7,8,9,10 and 11. Correct me if I am wrong, "please!", but if you assign a Block Command in Helix to a stompswitch AND you assign a MIDI Command to the same switch, HELIX will execute BOTH of them. Thus, a Block ON/OFF assigned to Switch 8 and a MIDI RECORD command assigned to switch 8 also would start record (assuming the track is armed for record) but alternate between ON/OFF for the Block assigned to switch 8. Thus my strong caution not to assign anything other than MIDI Commands to switchs 7,8,9,10,11 in my MIDI COMMAND1 patch. If I am wrong, that would be great. DUNCANN: Yes, that is exactly what I am doing! ReaControlMIDI is just one more reason I luv REAPER! LAUREN: Well not ALL your patches - just the ones you want to have MIDI Control over by using Stompswitches. You can mix-and match presets in the same setlist. This is a "per preset" process. So, "yes" if you want MIDI Control using the stompswitches you need to program it in at the Preset level for that particular Preset. But it ony effects that Preset - not all others. What will effect ALL your Presets are the GLOBAL SETTINGS as outlined in the notes for this Template until you switch them back to any other GLOBAL settings. You don't loose anything, they may just be "covered up" due to the way you like to have the Preset/Stomp/Snapshot views show up. Really, when you are in "I'm going to work on recording something" mode, use my Preset MIDI COMMAND1 with the GLOBAL Settings as outlined. Then when you are done, just switch back to your GLOBAL Settings of choice. That is how I invisioned the Template being used. Hope that makes it clear. Doing this will not effect any other Presets you have. (((( Unless you edit current Presents and they already have Block assignements to switches 7,8,9,10 and 11.)))) Thanks for all the comments - Bo Baker One last comment. I have chosen to prefix all the Presents that I programs with MIDI Commands with a small "m". That way I can quickly see which Presents I can use for recording. You could also just set up a separate Setlist but I doubt you would need that many Presents with this functionality.

Hello Ralph, Yes, the MIDI control switches are only programable at the Patch level. Thus, you need to start with this template or review/edit your current patches to re-assign your control blocks. Not elegant but it is where we are at for now. Also remember that the Line6 template does not have a RECORD function - which was the reason I posted the MIDI CONTROL1 Template. I have spent a little time setting up Patch triggers in REAPER and it works great. Just remember that you must do it in a MIDI track. I record Audio in 3 or 4 tracks and set up a MIDI track under that on track 5. Then program any patch changes/CC changes I want to try anywhere in the song's MIDI track ( one or many changes) and play back the tracks. If you have a pedal to send MIDI INFO you can program it to make the same changes "on-the-fly" for live use. Of course HELIX can do a lot of this but this extends the type/number of contol messages you can send on a "per patch" basis. As a side note - don't forget that the Helix can pass through MIDI messages so you can use this same method to control external devices also on other MIDI channels. As for your idea for "layouts/pages" that would be a "biggie" as the footswitches are either "on or Off" so if they are assigned as MIDI controlers on a "page" you would loose their use as "stompswitches" (just like now.) Never say never, but it would be a MAJOR rethink of how the switches work. Having said that - IF you want to invest in a separate MIDI controler then MAYBE there is a way to make it work on ALL patches. I'll have to give that a little more thought. The biggist issue is that the "Command Center messages are tied to a HELIX controler" and that negates their use as anything but MIDI control once assigned. Now the RECORD command is a CC# number so you could send RECORD with an external MIDI controler or use up just one Helix switch (programmed at the patch level); but you would have to have a PC or external MIDI controler near by to send all the other messages. In any case, I think a lot of players just use a looper to do most of what we used to do with MIDI so it may all bel a moot point.

Delete might be nice . . . as for me . . . I'll vote for better REVERBs. Best of luck on the "delete thing". Bo

Well, as I think about it, that's pretty much what happens when you "delete" something on a computer. Yes, you just press "DELETE" option and the file is "tagged" deleted and dissapears (it's still there - you can just write over it"). Since the "patch" files are sequential, you can't just have a "hole" in any slot. It has to have something for the Helix to "read". These files require a certain "format" and if it hits a "hole", bad things happen. I'll grant you, L6 could program a "Delete" option and automatically fill the hole; but how many of us would unintentionally delete the wrong file? I know I have! Personally, I like the idea of not "deleting/erasing" a Preset - but rather going the one step extra to "copy/paste" over the unwanted patch with a "fresh" NEW Preset. With 1027 Presets you should not run out of one last slot - but that's what the "Export" function is for. Just keep a "New Patch on your Apple/PC when you want to add that to open up a new slot. Don't forget, you can Export an entire Setlist and load a totally different one at any time. So really, you are only limited to the number of Presets your Apple/PC will hold. I have different setlists for different types of music and even different guitars and just load whichever I need for that day.

Right you are. The one thing missing from the Line6 Template is the "RECORD" function - which is an important function if you are a one man shop! LOL. I made this so you can begin the "RECORD" MIDI function "Hands Free" and not rely on a "pre-roll" count in, in order to be prepared to begin recording. The Record function, as you know, is not a MMC code and does not show up in the MMC options in Helix. Rather it is a different CC# for each DAW and thus the comments on reading the DAW's documentation for the RECORD implementation. This works, as is, for the REAPER DAW as that is what I tested it on. Helix is a great product and I can't say enough great things about it. Way to GO!!!! Bo Baker

Just posted a Custom Tone to the CUSTOMTONE site called "MIDI CONTROL1" to show how to set up your floor unit to use as a Transport control in a REAPER DAW. It has been tested in REAPER only but may/should work in most MIDI compliant DAWS. The one issue is the "RECORD" command which is not universal but determined by the DAW'S creator. The Code should be notated in their documentation. Here are the notes as entered on the download page: This is NOT a sound Patch file although I have added six blocks in path 1 A and B. This is a TEMPLATE to use as a startng point to build a patch that has MIDI TRANSPORT CONTROL for the REAPER DAW and possibly other DAWS as well. Delete the Blocks in Path A and add your own! Using Footswitches 7,8,9,10 and 11 in STOMP MODE you can transmit REWIND, RECORD, PAUSE, STOP and PLAY commands to your DAW. PLEASE, PLEASE, PLEASE note that Footswitchs 7,8,9,10, 11 must not be assigned to any Blocks or you will cause a real mess! In the GLOBAL settings the MIDI/TEMPO settings to make this happen are: Midi Base Channel = 1; Midi Thru = On: MIDI Over USB= On; MIDI PC Send/Receive = On Set the FOOTSWITCHS Global settings to: Preset/Mode switches = Preset/Stomp; Stomp Mode Switches = 10 Switches; Up/Down Switches = Banks Of Course, you may want to set these to someting else when not working with a DAW which is fine. I have a Bank set for DAW patches and others set for "LIVE" i.e. not recording patches. Switching back and forth on Globals in no way effects your patches Once these Global settings are made: The MODE Button (6) will switch between: Bank Mode: switches 1 and 7 provide Bank up/down + switches 2,3,4,5 provide patch A, B, C, D AND switches 8,9,10,11 provide RECORD, PAUSE, STOP and PLAY as it is in "Stomp" MODE). The Stop Mode: Switches 1,2,3,4,5 provide Block select On/Off in either Path 1 or Path 2. What matters is that NO BLOCKS ARE ASSIGNED TO SWITCHES 7, 8, 9, 10 11 Switches 7, 8, 9, 10, 11 are now assiged to the the REWIND, RECORD, PAUSE, STOP and PLAY functions. You can go to the Command Center in either the HELIX or the HELIX Editor and see the commands and assignments. All the command messages are "MMC" (MIDI MACHINE CODE) except the RECORD command. That code is a "CC toggle Command Code-toggle). This code is defined by the DAW and is defined as CC#28 in REAPER. Other DAWS may have a different code and you will need to refer to that DAW's documentation and change the number in order for the RECORD switch to work. Good Luck - Bo Baker ( listed as Gary Baker on CUSTOMTONE)

So . .. I checked out the IRs on the Celestion Digital Downloads web site, found two to try . . . Entered the info on what I wanted and applied the CODE NAMM17 for the 50% off and . . . . it shows full price of $29.99 for each . . . and . . I can not find anywhere on their site to set up a "log on" account. Can anyone point me in the right direction . . . I must be missing something. Thanks. Bo Baker So I finally figured it out: The FULL price is $60 for a "bundle" ( 5 cabs ) and the 50% discount makes it $29.99. which is the amount showing on the web site. So they are showing the price after the 50% discount. To me a $60 price seems to be hight base on the others I have purchased. So, Now I'll give them a try And you have to go through the entire purchase procedure before you can set up a new account. No way to start a new account without going to the "Check out" screen . Wow!