gbakerjr

Wow...Interesting. I didn't try to load every IR in the second file, I just tried a half-dozen or so as a matter of trouble-shooting. So I don't know for sure if I loaded those two specific IR's or not, but I'll try them as soon as I get a chance. This is really friggin' weird! I don't have a drop box account. When I downloaded from the first link, I downloaded each file individually. When I downloaded from the second link, I downloaded all the files as a zip file, since there were so many of them. I'm going to download the files from the first link all at once as a zip file and see if that makes a difference. I can't imagine it would, but at this point I'm out of guesses....

Thanks HonestOpinion. I agree...Sounds strange, but stranger things have happened. It's worth a try. I'll let you know what happens. Gary

Hey all, I'm getting this error occasionally when trying to import a patch (preset) or IR. Not often, just once in a while. I was chalking it up to corrupt files, but the latest came when trying import a patch and two IR's from another thread, and those files have been imported by other folks, so the files are clearly good. I've made sure the filename extensions are correct (.wav for IRs, .hlx for patches), and tried importing from multiple computers, all Win 7 Pro 64 machines. I'm running the latest firmware (1.10.0), drivers (1.78), and Helix app version 1.11.1. Anyone else experience this? Any thoughts or ideas would be appreciated! Gary

It's definitely not the file extension being incorrect. I keep my file extensions viewable for just that reason, and they're named properly. Just for the heck of it though, I went in and renamed the two IR's and the patch file, making sure the extensions were .wav and .hlx respectively. Same result. I also tried importing from another computer, just to rule out any type of computer-specific hiccup. No go. The IR's in the second link load fine. Not sure what the deal is, but it's awfully confusing. The wording of the error is "URI is incompatible with data". I Googled that phrase and didn't come up with anything. I'm going to start a new thread with that in the title to see if anyone else has experienced it. I appreciate everyone's thoughts!

I'm on the latest firmware. I'm sure it's something on my end, but I have absolutely no clue what. I haven't tried the IR's in the second link, but I'll take a crack at it.

Nope...The file name extensions are correct, and I downloaded all three files (2 IR's and the patch) a second time just to make sure something didn't get corrupted in the download. Interestingly enough, I have the same problem with the bundle file that came with the most recent firmware update. Same error when I try to import it. I downloaded some Helix patches from the CustomTone boards just to make sure there wasn't something wrong on my end...They load fine. I ran through about a dozen of them. Weird. Incidentally, it shouldn't make a difference, but all of my machines are running Win10 Pro 64.

I can't get the patch or either of the IR's to load. I get that yellow strip across the top of the editor screen that says it's an incompatible file. Any thoughts?

Call me silly, but I prefer the PDF. First and foremost, if you have a paper manual, you're only going to wind up having to download the PDF update anyway every time the firmware is updated (assuming you want to have a current manual). Secondly, PDF's are much easier to search and get to what you want. Hit Ctrl+F, type in what you're looking for, and you're there. To me, that's faster than looking at a table of contents and the turning to the appropriate page. Also, if your eyes happen to be not as good as they used to be, you can zoom the PDF.

Well boys, it wasn't the volume pedal setting. However, it *is* the compressor at the end of the chain. I have the LA-2A at the tail end with just a touch of compression to glue everything up. It's not doing much, but it must be the way it's reacting to the differences in volume levels of the two amps blocks. I never thought to check that simply because it's a static setting....Nothing changes with it. Take it out of the chain, everything works as expected. Sorry to bug y'all with something that I should've researched more thoroughly before I posted. Gary

Dave - The volume pedal is definitely worth a look. I've noticed this behavior in more than one patch, so I'm thinking maybe not, but who knows. I'm coming from an HD500x, a HD500 before that, and a XT Live before that. The Helix editor is a bit different than the other three and I've caught myself several times unintentionally changing something because I was doing what I would've done on the HD editors. I save as I go along....So it's definitely possible that I could've inadvertently saved with the volume pedal in a different position. I'll try and check that at some point today. If that doesn't appear to be the problem, I'll upload the patches. If nothing else, I'm definitely setting the volume pedal up for the global remembering. Great idea! Gary

Hi Dave. It's not a volume difference between the two different amp models...I'm actually looking for a volume difference there. What's happening is whichever amp model is on by default when the patch is initially selected, when I switch to the second amp and then back to the first amp, the volume of the first amp is changing from what it was initially. None of the amp parameters have changed (the FS is just toggling between them), but the volume of the first amp is noticeably different. So if I select a patch, toggle to the second amp within that patch, then toggle back to the first amp within the patch, that first amp is louder after the toggle back and forth than it was originally when the patch gets called up. It's not quite as noticeable between the toggles (although it *is* noticeable), but once I'm back to the first amp, if I then recall the patch from the preset footswitch, you can really hear the difference. Gary

So what I'm trying to do here is to have two different amps in the same patch, but switch between them, not have them active simultaneously. Initially, I put two different amp blocks in the same path next to each other, and assigned both to the same FS, one on one off. The FS then alternates between the two amps being active or bypassed with a single press. When I go to the second amp via the FS, and then back to the first amp via the FS, the first amp winds up being about 1.5-2 db louder than what it is initially when the patch is selected. No tone change, just volume. Note that nothing changes in the amp settings, the FS is simply turning them on and off. I know there is a volume change because I can hear it, and I can see it on my mixer meters, but the amp settings do not change. I am going out to the mixer via XLR, but I tested using the 1/4's and also the phones...Same result. I thought maybe it had something to do with having two amps inline next to each other. So I tried the attached routing. Here I have the amp blocks in a 1A and 1B scenario. The volume block immediately in front of each amp block is the gain module, set at -120 db. I have both volume blocks assigned to the same FS, one on and one off, so the FS again alternates between the two with a single press. I tested this out, and it indeed does "mute" the respective path when a given volume block is turned on. Path 1B then merges back into 1A just before the cab block. Again, no changes to the amp settings...The FS is simply alternating between path 1A and 1B. Same result. The amp on 1A is the default amp when the patch is selected. When I move to the amp on 1B via the FS, and then back to 1A via the FS, 1A winds up being about 1.5-2 db louder than it was originally. Any thoughts or ideas? In case it helps, my goal here is to switch between a lead and rhythm sound with as little latency as possible. Either scenario works very well in that respect....The switch is instantaneous. It's just that pesky volume change that's throwing a wrench into the works. Lastly, note that I'm not complaining about the switch latency. There's going to be some degree of latency with modelling units like this, and the Helix is no worse in this respect than any other processor I've used. The normal latency is not a major issue for me by any means. I was just looking to see if I could improve it. Thanks in advance!

No one else experiencing this? I've had this happen with several other patches as well. The overall parameters as far as the audio chain goes stay consistent, but when I export to a PC and then import back to the Helix, the foot switches don't remain intact. Sometimes a FS is on when it should be off, sometimes a different control parameter is selected (when setting a FS up with multiple functions), which changes the LED color around the FS. I'm not sure if it's something happening during the save process, or the import process, but if I save a patch, and then copy/paste the patch to a different location from within the Helix (C&P from either the Helix itself, or from the app while connected to the Helix), all is well and maintained. If it goes to the PC and then back to the Helix, not so much. Not a deal breaker by any means, but I would like to understand what's happening.

Okay...I've only had my Helix a few days, so I'm obviously still learning. Here's a strange one. I'm creating patches in the editor. I've got one patch that if I copy from one location to another within the Helix, the patch remains identical. However, if I export the patch to a PC and then import, the audio parameters stay the same, but on the Helix itself, FS4 has a different color LED around it (I have multiple parameters assigned to the FS and different block is selected when I import the patch back into the Helix) and the scribble strip for FS4 has an outline to it. In the grand scheme of things, it's no big deal because the audio parameters are the same, but I am curious as to what's changing within the patch when I'm exporting to a PC. It doesn't matter if I drag and drop to export and import, or use the export and import commands, same behavior. What am I missing?

Thanks guys!

Great! Thanks for the quick reply. So, if I'm understanding correctly, I could basically swap out one block of Fx for another with a single press of a footswitch? For instance, if I have my pre-amp and cabinet structure, but want to use a chorus and short delay for rhythm patch, but then wanted a flange or different chorus and longer delay for my lead patch, I can set up two different Fx blocks, and assign the entire swap to one footswitch? Sorry if that's a dumb question. No one local to me stocks a Helix, so I don't have the luxury of playing around with one before I buy it. Gary

My apologies if this is covered in another thread. I did a quick search and didn't find anything. Additionally, I have the XT Live, HD500, and HD500x, and it appears the Helix programming is a bit different (specifically the blocks) than what I'm used to on those units. Is is possible to assign multiple functions to the same footswitch simultaneously? So, if I have the unit in stomp mode, can I have FS2 set up to toggle both a boost and a delay at the same time (say for a lead patch)? In reading the manual, it seems like that's possible, but reading the manual by itself, and having the unit in front of you are two different things. If so, is there a limit (within reason obviously) to how many functions can be assigned to the same footswitch simultaneously? Thanks folks! Gary

Hey all...Got GAS for a Helix, but I'm curious as to if I can get a decent acoustic simulation off of a mag pickup signal? Currently I run guitars with both mags and piezo's. My main rig is an HD500x. I run the signal from the mags into it, and then the piezo signal straight into the FOH board, adding a little Fx to it at the board. What I'd like to do, is to get some of my guitars that don't have piezos back into my play rotation. If I can get a decent acoustic simulation (doesn't have to be great, just reasonable. I'm the only guitar player in the band, so the acoustic sound is more to fatten things up than anything else) through the Helix, I'd like to split my mag signal once it gets to the Helix. Run one signal path like I normally would for my guitar signal, and then run a separate signal path within the Helix for an acoustic simulation, and then send the acoustic sim signal out an aux to the FOH board (I still want to keep the mag and acoustic sounds separate). I'd just build the acoustic sim into every patch, and then assign a footswitch to mute or unmute it. So....Can I do that with the Helix, and can I expect to get a reasonably decent acoustic sim out of the Helix? FYI....To give you a gauge on what I consider "reasonable", the Boss Acoustic Simulator pedal SUCKS! ;-) Thanks all! Gary