russ5254

Unfortunately there is still a significant lag in preset switching (maybe 0.5sec) even with buffer size of 128.. on the bright side snapshots can respond immediately though.

Yes, arschr is correct. The controller must have midi host capability. The mvave chocolate plus has that capability (on top of the normal USB midi send). It can send both midi or sysex commands to another device via usb or Bluetooth. Hope this helps

I just had another thought. If I have 1 guitar track and 1 synth track for pads via midi guitar. With 2 live configs, I can setup preset control using same cc value to pair the presets selection of both tracks.. config#1 for track1, config#2 for track2. Can turn off one if not needed.. Live configs seems extremely versatile.

For context, I use helix native live. My setup is Audient Evo audio interface and mvave chocolate plus midi controller connected via usb to a laptop running Reaper with 1 track of helix native. For 10 presets + 8 snapshots per presets you technically need an 80 button midi controller... Lol So for my 4 button midi controller pedal it is programmed as follows: Bank1 snapshot 1 to 4 Bank2 snapshot 5 to 8 Bank3 presets 1 to 4 (set to ch1 cc1 0-3) Bank4 presets 5 to 8 {ch1 cc1 4-7l Bank5 presets 9 to 10 (ch1 cc1 8- 11) with 2 buttons being programmed but unused because my live configs "config#1" is setup until controller/cc value 9 only (10rows for 10 presets) A lot of tap dancing going on when changing between controlling snapshots and presets/songs.... lol Cheers!

Hi @rd2rk, here's the thread link I'm using reaper as my daw. My HxN plugin is vst3 not aax. Try n let me know if it works.

Hi all, I just posted my recent findings to make preset changes work for native using midi controller pedal. U can search for my latest post... Hope it helps

Hi all, Been a long time since I last posted. This a long post and for those really interested.. if native ver 3.8 has proper midi implementation then skip this post. Switching helix native plugin presets in reaper (daw) directly using midi was still not available for ver3.15 which I m using on my laptop running Reaper. But there is a very troublesome way. In a track with native as the FX, For every helix preset u want to use, you have to click the + sign (to the left of param button) in the helix FX window and save the preset. If you have 10 presets, you need to save it 1by1. It will appear under user preset list rpl in the drop down list. U now have created your preset list each with its own snapshots. (Look for my previous post in this thread on how to manage snapshots in a preset with midi). Also in the + sign drop down make sure you "link midi to program change" and select channel1. This is needed later to setup your midi controller button. Changing your helix presets for the track can be done using sws/s&m extensions' live configs. 1. Install sws extension (free). Just search for it. 2. On the reaper window menu bar Under extensions select live configs. 3. U will see a new window containing a table. Each row needs to have the following: a. The track that you want to control b. The presets. If u have 10 presets, you need to fill up 10rows and so on 4. How to fill it up E.g of row 0 (cc/controller value column value of 0) in this same row, go to the cell under "track" column, right click, set tracks, select the track number containing native. Go to the cell of the same row under "FX presets", right click, set preset, and select the helix FX presets u want from user presets rpl list. This takes care of setting up 1 preset for your native track. Repeat for every preset you want to setup in subsequent rows of live configs. You can skip rows too, doesn't matter as long as you know which row (controller/cc value) it belongs to. This is tedious if you hv many presets. I don't hv a better way.. maybe can do in excel and import it in?? 5. Ensure config#1 is turned on by ticking that checkbox at the top left of the live config window on the left of 'config#'. the checkbox will hv an "x" indicating is on. It starts at config#1. You can setup other config#s to do other stuff. But you're limited by number of midi buttons... 6. Now you setup your midi controller pedal as follows. Pick a cc number to use. E.g cc1(or any unused number). Program button 1 to channel 1 (remember link midi to program change earlier...) cc 1 value 0 for 1st preset, button2 to ch1 cc1 value 1 for 2nd preset, all the way to button 9 for your 10 presets. The value of cc1 is for each of your preset row numbers that u setup in step4 in live configs. 7. Click learn in live configs window and click any 1 of the midi buttons you setup for changing presets. Done! Now you hv buttons for switching presets and buttons for changing snapshots. It.... is.... tedious.. good luck!

hi frankenkeim, i had a similar problem with my Audient id4 interface. what worked for me was: 1. search for and open "manage audio devices", select Audient id4, click properties. 2. a new "properties" window pops up for my id4 and I select the "Advanced" tab. 3. I set "Default format" to the same sampling frequency as on the id4 settings (using my id4 app that came along with it for setting latency/sample rate/buffer size etc). In your case, i think you probably need to make sure the sampling frequency tallies with the the ASIO4ALL app settings. I was on 44.1kHz on my Audient id4 but the "Advanced" tab in the properties window was on 48kHz which resulted in a conflict when trying to play audio from both reaper and youtube at the same time. 4. i also disabled all my other audio devices and set my interface as the only default to reduce conflict otherwise the PC may try to output sound to both the usual aound card and you audio interface. I'm not sure if this will work for you, hope this helps.

hi l_sap120394, After reading "Command Center" in page35 of the HxFx manual, it looks like it has some degree of programmability: "Each of its Stomp mode footswitches ... can be used to send a variety of MIDI or External Amp commands to your guitar amps, vintage pedals, synths, or even other modelers." See if you can assign a fixed MIDI CC number & value to the stomp footswitches you want to use for snapshot changing in Native and then assign the appropriate values for each footswitch. e.g assign footswitch1 to MIDI CC# 71 and value =1; footswitch3 to MIDI CC#71 also & value=31. If need be, set min and max value of the stomp footswitch to be the same. Each snapshot is represented by a value interval of 15 If it works, footswitch1 will select snapshot1 and footswitch2 will select snapshot3. i suggested using MIDI CC#71 because the manual says that those are not being used/received by HxFx. Then MIDI learn "snapshot index" in reaper - which you probably did. I don't own a HxFx but you might want to give it a shot to see if it works.. good luck!

rsvette12, glad that you got it up and running. enjoy!

hi l_sap120394, The footswitches and knobs on your MIDI controller must be programmable to asign MID CC# and value for each footswitch. If HxFx board doesn't allow you to reprogram the CC# assignments for the knobs and switches then you wont be able to change snapshots with it. i use reaper+line6 FBV shortboard and can change snapshots. i just posted a reply to rsvette12 regarding how to program his Rig Control floorboard.

hi rsvette12, i am using helix native v1.6+ reaper + line6 fbv shortboard+ iD4 interface My FBV footswitches are programmed to change snapshots (see the MIDI CC# and values assignment in the pic). I use only 6 switches because some of the others are used for changing presets and arming/selecting tracks. I use this rig live. 1. So you need to program your footswitches by assigning each of them to CC#69 (i used to use CC#50 and it works too) and send out a single value. e.g. assign: footswitch1 CC#69 value:4 - this calls up snapshot 1 footswitch2 CC#69 value:20 - this calls up snapshot 2 footswitch3 CC#69 value:36 - this calls up snapshot 3 footswitch4 CC#69 value:52- this calls up snapshot 4 and so on... because snapshot1 CC values range from 0 to 15, snapshot 2 values is from 15 to 31... etc... interval of 16 (128values/8snapshots=16) From your screen shots it looks like Rig Control editor may allow you to custom assign CC3 and values. 2. in reaper, on your track1 FX window go to "param"->"learn"->"snapshot index", and the MIDI learn window will appear . 3. step on any of the footswitches so that reaper detects CC#69. 4. your footswitches now control snapshots depending on how you programmed them. i guess some of the steps above you probably know (like the MIDI learn part) but just thought i'd share it for completeness sake. hope this works for u.

Thx for the suggestions and help. i've set "Allow live FX multiprocessing on 4 CPUs" but it still crackles. I've also disabled "Anticipative FX processing" but no go. Reaper RT CPU is still at about 30%, armed and with no incoming signal. I've heard of reports that Native does take up a fair bit of CPU in Macs as well. As far as portability goes for me - it's just dumping my audient, shortboard and laptop all into a backpack.. lol! I don't gig heavily so this setup is simple and good enough for me. The FC1010 is rather long that's why i settled on the Line6 FBV shortboard instead.

hello, Nice setup!! I just setup mine running Reaper on WIndows10 too : guitar ->audient id4-> HP Elite laptop usb1. Line6 FBV shortboard MkII -> HP Elite laptop USB2. All powered by the laptop battery - lasts for at most 2hrs continuous use. (with High Performance power plan settings) Audient id4 and Line6 FBV will fit on a pedaltrain2 and should have more than sufficient space for a wireless too. Unfortunately Native spikes up to 50+% RT CPU on and off causing crackling. WIthout any signal in and track armed Native already runs at 30-35% RT CPU. Sample rate 44.1kHz, Buffer size 512. Crackling gets more frequent at 256/128. Fortunately latency is still acceptable at 512. CPU is 15-6300U 2.5GHz (2 core 4 thread)16G RAM. RAM usage was very low throughout -700MB max

Assuming you have successfully loaded Native in Mainstage and have tried MIDI learn/map before... Pg B.5 of the HD500X manual shows how you can assign a MIDI Channel and CC number to a footswitch and the values it will have, then you can use it to learn preset changes in Mainstage. I haven't been able to do preset changes via MIDI commands direct to Native so I "copy" the Native presets to Reaper 's preset list instead. I've assigned A & B footswitches of my Line6 FBV with MIDI CC numbers an value range to change the track FX presets in Reaper. I have also been able to assign different footswitches to handle the different snapshots. I don't use Mainstage as VST Host as I am running Windows but i think the principle should still hold. cheers!

hi guys, This thread has been extremely helpful. I have just recently forayed into playing guitar live using Reaper and Native on a laptop running Windows 10. I'm happily using Native with a line6 FBV shortboard running in Reaper. as VST host. The button assignment can be done using MIDI learn followed by the "Automation/Controller Assign" tab. I am able to : 1. change presets by using Reaper's preset list - unfortunately the Native presets need to be saved into Reaper's User preset (.rpl) and the sound cuts out on preset changes though. 2. control snapshots - I have currently setup the FBV for only 6 snapshots because of limited number buttons on the board. Each button has the same MIDI CC with different value range assigned to it. (as mentioned by Cruzfolmli) 3. assign buttons to turn blocks on/off. 4. assign button to tap tempo in Reaper - Native syncs to it. 5. select/arm/unarm tracks in Reaper. The functionality is limited by the number of buttons available. Currently I only use either the snapshot mode or the stompbox FBV setup. Floorboards with dual expression pedals (older Line6 model or the Behringer) would give more functionality especially for controlling some effects parameters like rate/depth/mix which are knob assignable. Hope this info is helpful. Does anyone know if Mainstage has a Windows version.. that may help me cut down on a few buttons' usage. 8-)