Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by HonestOpinion

  1. Have you done the factory reset after updating the firmware? How to Factory Reset a Helix Family Device | Sweetwater
  2. Are we talking about the Powercab or Powercab+ here? I assume this is in reference to the PC+, and if so, make sure you are running the 2.00.1 firmware on the PC+ as this was when L6 Link support was added. If you have the PC+ the next thing I would check would be my connection between the L6Link output on the Helix and the L6 Link input on the Powercab+. Try a different cable if necessary, a standard XLR cable, rather than an AES/EBU cable, will work in a pinch for a test. Assuming from your post you already set 'Powercab Remote' = "Per Preset", and are also saving your PC+ speaker changes between presets on the Helix. Also, although it may not be the issue you are encountering, just a reminder, although the LED ring color around the selector knob on the Powercab+ may change when you dial up a preset from the Helix with a different speaker type, the preset name on the PCPlus display will stay the same. The preset name on the PC+ is essentially just a placeholder when you use the PC+ in tandem with the Helix and the L6 Link connection. All the changes are being directed from within the preset in the Helix. Is the LED ring changing color when you select different PC+ speaker types from the Helix? Can you hear anything change?
  3. A similar request has been batted around on the forum in the past so you may want to check for it on Ideascale. I can see why you might want this. I think many users start by selecting separate amp & cab/IR blocks from jump, just to avoid this issue and retain flexibility in their preset design. The only good reason to use a combined amp/cab block is if you absolutely require the block that would be used by a separate cab/IR, or perhaps if you need an extra sliver of memory. A combined block may use less DSP than two separate blocks (not sure?). If that is the case, and you were already maxed out on DSP, or if you are already using the max number of blocks in a path, the splitting function you propose would require logic to grey it out. One thing you can do if you are stuck with one of these combo amp/cab blocks in a preset, is assign the 'Mic' parameter to snapshots. Changing the mic type results in some fairly dramatic changes in the sound of the cab. For that matter you can assign all of the cab's parameters to snapshots. This at least gains you substantial flexibility in that cab's tone between snapshots. Btw, I think a feature that allowed you to combine two separate amp and cab (or even IR) blocks of your own choosing into a single customized amp/cab block to save as a 'Favorite' might be a nifty option. Particularly for HX devices with fewer allowable blocks, such as the HX Stomp.
  4. Have not tried it myself so I can't provide a confirmation of this from personal experience. Don't know if you find a video more convincing than a white paper but here is a video in French and English showing apps that generate beats and songs from an Android tablet.
  5. I would set up HX Edit on a different computer, at least for long enough to do a restore. Make sure the drivers are up to date on the computer you have been using, particularly the graphics driver.
  6. Ah, disappointing to hear it is not working, at least on the Stomp. Good move on using a shorter MIDI cable. I use one that is less than a foot long, no problems. Still feel like the solution is in there somewhere for the Stomp with just the right combination of cabling and global and preset configuration. Maybe someone else will solve it or Line6 will offer up a configuration option in a future firmware that makes this straightforward. Good luck and let us know if you get it figured out or come across a better solution.
  7. Shouldn't be affecting this scenario but if this setting exists on the HX Stomp, set Global Settings-> 'MIDI/Tempo' -> 'Duplicate PC Send' = "OFF". It is on the second page of the MIDI global settings. Is it possible you have a bad MIDI cable? The wah block blinking on and off almost seems as if a bypass CC is being sent constantly. Guess it could be something in the tip/ring settings or cabling as well. Does it blink when you don't have the expression pedal plugged in but still have the loopback connected? Also, the Tip/Ring settings under Preferences that you describe on the Stomp, don't appear to be available on the Helix. Is there an "EXP 1" setting available for 'EXP/FS Tip'? If so I might try setting 'EXP/FS Tip' = "EXP 1" instead of "FS7" under Preferences. If that didn't work I would try flipping the EXP 1 & 2 values for the tip and ring settings. Btw, to further help avoid funkiness make sure the Stomp XL is off when you connect the loopback cable.
  8. Here is a link for MIDI commands for the Helix. Perhaps there are other more up to date resources available for the Stomp XL. The Unofficial Helix MIDI Guide.pdf (dropbox.com) Globals look right to me although I will have to rely on your settings for the EXP FS/Tip and Ring as I don't have the Stomp to test on. Seems like you got it right if the EXP is flipping from 1 to 2. Downloaded your preset and made a few changes. Your MIDI command was being sent via Command Center from an 'Instant' (lighting bolt) command. You also had the CC set to "68". I changed it to "59" per my original "MIDI Loopback tricks.." post, and moved it off the instant command over to FS7 (per your intended setup). I also switched the active states such that hitting the footswitch labeled "Fassel" activates the wah while leaving the volume block active and on its most recent setting. That way the switch indicates visually when the Wah is active. Everything is working as advertised on my end although I am using a Helix to test, where EXP 1 & EXP 2 are operating with a built-in expression pedal. No guarantee it will work on the Stomp XL. I have attached the preset. Give it a try. I think you are close to getting this working, but I could be wrong, if this just can't be pulled off with the Stomp or without some arcane wiring for the cable to the EXP input. Good luck! Try the attached preset file below: Vol Wah swap HO.hlx
  9. Have no idea what the tip/sleeve combinations are for the 5150 Iconic, but I wouldn't go purchasing any additional hardware for switching until I had tried the 'Ext Amp' options for switching available from the LT's Command Center. The switching capability is already built into the LT if the amp has a compatible footswitching design. Probably best to wait for some info from Peavey support on the foot pedal's operation/schematic but if that is not forthcoming you could always try getting it working, proceed at your own risk(and under warranty :-).
  10. Although redundant the best advice has often proven to be - get a backup of as much as you can, export setlist by setlist, preset by preset if necessary, do a factory reset, restore backup. Best case scenario of course is if you have a successful previous backup. If that doesn't work, uninstall Line6 software, reinstall HX Edit 3.15(or latest version) and use it or the Updater to upgrade the firmware. Then rinse and repeat - get a backup, do a factory reset, restore backup.
  11. It appears that the CC is working to toggle from EXP 1 to EXP 2. Our overall strategy is to use a footswitch to activate/bypass the wah, leaving the volume block active, and simultaneously send a MIDI message via loopback to switch between EXP 2 and EXP 1. However, switching the EXP is only part of the equation. You must also get the expression pedal to control the desired block(Vol or Wah). This requires the correct 'Position' assignments for the EXPs (at least on the Helix/LT). Little confused here by your mention of both "footswitch 7" in the beginning of your post and then you mention FS8 later, from this quote - "Ring of my insert cable [exp2, fs8) Never passes from the volume block to controlling the wah block." That sounds like an assignment issue right off the bat. The loopback method I detailed only uses one footswtich assignment for 'Bypass' to the Wah as the volume block is never bypassed. As I don't own the Stomp XL, unfortunately I can't test this. As I mentioned earlier this loopback trick was intended for the Helix/LT. However, if you are getting the EXPs to change properly that is half the battle. It may be just that the expression pedal 'Position' assignments are not assigned in such a way as to change along with the 'Bypass' state to the corresponding block - volume or wah. If you have not already, take a look at the assignments list under the 'Bypass / Controller Assign' tab in HX Edit and recheck the assignments. If the behavior of the Stomp XL mimics the Helix or LT (maybe it doesn't?) they should look like the following: There should be three assignment entries only for both the volume and wah blocks - Wah Position = EXP1, WAH Bypass = FS7 (footswitch used in your example) and Volume Position = EXP2. Delete any other assignments for volume or wah blocks. Without having a Stomp XL to test on this is probably as much guidance a I can provide. The Helix and LT switch internally for the built-in expression pedal. There is no guarantee that the switching for the external pedal required for the Stomp XL will behave identically. Note: For any Stomp users that want to attempt this and don't want to track back through my old "MIDI Loopback Tricks..." post you will need to execute these two steps before trying this method: Set 'Global Settings' --> 'MIDI/Tempo' --> 'MIDI Thru' = "Off" (This prevents runaway infinite loop MIDI funkiness when you are looping MIDI back into the Helix) Connect a MIDI cable from your Stomp's MIDI output and loop it back to your Stomp's MIDI input
  12. Have you taken a backup, and then done the factory reset and restore, per the update notes? If not, this is likely causing the issue. If that doesn't solve the problem I would Uninstall the Line6 software and download and reinstall HX Edit 3.15. Also, did you update your firmware to 3.15?
  13. Not sure if the expression pedal switching method provided in the "loopback tricks" post works with a Stomp XL. It was intended for use with a Helix or LT. Maybe our resident MIDI expert @rd2rkcan weigh in on this.
  14. Cool, haven't seen that post in a while. Wonder if there is a more elegant way to do it in the most recent firmware version?
  15. My experience with guitar synthesis has been with the Roland GK pickups and a Godin guitar with a built in hex pickup. Both types of systems used the same cable for connection - the Roland GK cable (13 pin DIN MIDI). I started with guitar synthesis way back when Roland's first GK pickup became available. It was an aftermarket affair that had to be mounted either with screws(horrors) or adhesive to your guitar. You also mounted a clip to plug in the cable. Rather kludgy on the install, tracking was not great, and the cable while within the bounds of usability was still clunkier than a standard guitar cable. Tracking and mounting on later versions of the GK pickups got better but it still felt like blasphemy to mount those things on a quality guitar so they always ended up on one of my cheaper bangaround axes. My favorite implementation was the Godin which tracked well and had the advantage of being built from the ground up with the pickup properly and integrally mounted with an eye towards synthesis. That is the model I hope more guitars move towards in the future with a standardized and sleeker cable and jack. I was unaware of the crosstalk issues and I suppose that is something that would have to be resolved to improve the technology. I never attempted your more sophisticated use of multiple Amplitube instances and always used a Roland GR guitar synth, upgrading as new models appeared. That made for a fairly simple single cable connection from guitar to guitar synth, no breakout required. I can see where some of the potential processor overhead savings from not having to translate from a mono to poly signal when using a polyphonic pickup are simply moved over to, or even exceeded, by the demands that six separate streams place on the modeler/synth, but hopefully the hardware is moving in a direction where those demands can be handled. I understand that this is a pie in the sky hope to some extent, as @DunedinDragonpointed out, in that there may well not be enough market demand for guitar synthesis and polyphony to justify the extra cost to market them widely in the offerings from major guitar manufacturers. Add to that the fact that many instruments have remained pretty much unchanged for centuries and it is not a surefire recipe for seeing things leap forward any time soon. Still, it seems like it would be a natural progression as the modeling and synthesis worlds seem to be merging to some extent with the addition of polyphony to modelers. I hope that trend continues to the point where separate offerings of guitar modelers and guitar synths are no longer necessary. Polyphonic modeling and synthesis will be collapsed into a single device. Ideally this will be accompanied by a much broader choice of quality guitars fundamentally designed to be used with polyphonic processing and synthesis.
  16. Another user had a similar problem recently with the toe switch not working after upgrade to 3.15. He got it to work again by doing a backup, factory reset (press FS9 & FS10 on the Helix while restarting), and then restore your backup. Also make sure no cable is plugged into your EXP 2 input.
  17. Enhancements to MIDI may be able to more faithfully and efficiently capture the nuances of how a guitar is played in the 2.0 standard. Hopefully this will include improvements that simplify or even automate MIDI setups. @craiganderton's posts have been particularly informative regarding the new standard. Wanted to take advantage of the OP's topic title though to evangelize the piece of guitar innovation that IMHO has been lagging the most even if it has nothing to do with the subject of MIDI - pickup technology, or at least its implementation. We are seeing polyphonic processing finding its way into guitar processors. However, guitar pickups remain monophonic. That means that current polyphonic processing still requires algorithms that process the monophonic signal, make a best guess as to the fundamental frequency for each string, and then process it accordingly. This introduces processor overhead, latency, and tracking glitches; despite the fact that the current products on offer for doing polyphonic processing from a monophonic source do an impressive job given what they are working with. If guitar makers started offering more guitars with hex, polyphonic, pickups we might see a more rapid adoption of polyphonic processing in the guitar world with lower latency, better tracking, and lower demands being placed on the processor. For guitar players not using polyphonic processing those hex pickups could be summed. Polyphonic opens up a world of possibilities with its ability to process each string separately, and differently. It would seem that the guitar world should start moving towards making polyphonic pickups (and processing) the new standard. In addition to the obvious feature of being able to do advanced processing of chords properly, polyphonic pickups as a standard would enable every guitar to instantly dial up alternate tunings or apply different effects or parameters to individual strings. You could even do subtle and picky things such as micro-corrections on specific strings for tunings, allowing the player to correct for the inherent tuning and intonation issues caused by guitar physics or flaws or problems with neck and fret construction. The possibilities are endless. The closest analogy I can think of for the current state of affairs, is if the Hi-Fi manufacturers and record companies had persisted in producing monophonic equipment and recordings long after stereo had proved to offer a superior listening experience. It seems it is time to start moving towards more sophisticated pickup technology as a standard rather than an exception.
  18. Doesn't a 180 "vesting" period introduce a rather subtle risk to original owners when reselling their device? Let's say you resell your device within the 180 day vesting period, making it clear to the buyer that you are selling it without the Native discount - you intend to keep Native. The seller then transfers ownership of the resold device to the new buyer with Line6, and accidentally, knocks out the seller's Native license in the process. So, let's say Line6 blindly applies the 180 day vesting period policy for Native, regardless of the deal struck between buyer and seller. Caution to anyone reselling their HX device within 180 days. Caveat Venditor if you own a discounted version of Native. Even after informing the new owner that you are selling your device for less because you are keeping your Native license, you could still theoretically have that license yanked out from under you according to the vesting policy. I would hope Line6 would have some sort of method to remedy or prevent this scenario but perhaps not. Maybe it is as simple as the original owner of the device not transferring the serial number for 180 days to the new buyer. Seems like that could get messy if the new owner requires a warrantied repair within the 180 days, or if the new buyer was unaware they needed to wait out the vesting period before fully transferring ownership. If the post by @silverheadand @phil_m accurately describe how the policy works, it means there is a risk of losing your Native license, whether you return your device to the store, or resell it within 180 days to a third party. It just would appear to make more sense for the vesting period to apply only to device returns, not reselling. So tricky to enforce for reselling. Btw, does the 180 day vesting period clock restart if the second owner buys Native with an unused discount? I would assume not, since the new owner can't return it having bought it on the resale market rather than from a store, or can they? They are still within 180 days. Anyway, happy to have been able to add to the confusion :-)
  19. Great! I'll take weird but fixed any day of the week.
  20. You may want to uninstall your old Line 6 software first. Once you have HX Edit 3.15 downloaded and installed and have successfully connected to your Helix you will also want to get a backup and update the firmware to 3.15. After the firmware is updated be sure to do a factory reset and backup restore. Follow the update instructions carefully.
  21. Assuming that you have tried restarting the device and don't have any external expression pedals connected. As you just received your Helix you may want to double check your rear panel and make sure you don't have anything plugged into the 'EXP 2' jack just to be thorough. As @kduck advised, you'll want to test by pushing toe-down, quite firmly, on a hard surface to activate the expression toe-switch. No stomping required but stand up and put some weight on it. Just to be clear, couldn't tell for sure from the pictures, is the issue that it is not switching from volume to wah, or is it that it is not switching from 'EXP 1' to 'EXP 2' in the scribble strip? When functioning properly the scribble strip will highlight the selected EXP and dim the deselected EXP. Does this happen on all/any preset(s)? If the scribble strip is changing properly, you may just have an issue with your preset's assignments. If the scribble strip above the expression pedal never changes then you might have a hardware problem. However, before I opened a ticket with Line6, since you just got your Helix, I would probably try a backup, factory reset (hold down FS9 & FS10 upon restart for the Helix), and then restore backup. What version of the firmware are you on?
  22. Have you rescanned for plugins after installing Native 3.15? After looking for attached peripherals that might be causing an issue, at some point I would probably try reinstalling Native and then Reaper if required. Blunt force approach I realize but without more insight into specifically what is causing the problem this is probably how I would initially try to resolve this.
  23. I'm also a big fan of this functionality! It works well and I have played around with this at home but not used it during performance for one reason. It can be a little tricky to use if you are also a singer and are navigating a multi-page song. I have a tendency on occasion to accidentally stomp on my Pageflip MIDI Bluetooth pedal or double-tap it, and inadvertently switch to the next/previous song. Happens infrequently and usually no big deal if you are not switching presets via MIDI. You just tap back to the song and have the lyrics back in front of you. However, you have to be really careful not to do this when using Onsong to switch Helix presets as it can switch you quite audibly to another preset - right in the middle of a tune. Could be quite a bit more disruptive to your performance than just having a moment without the lyrics. Still, MIDI via Onsong is a far superior way to manage setlists on the Helix and I may eventually overcome my reservations about the above scenario and start using it for performances. If you are rock solid on your Onsong song switches or don't have to worry about paging thru lyrics, it is a great way to leverage Onsong's MIDI and setlist capabilities.
  24. Here are links to a couple of fairly impressive and absolutely free DAWs. Cakewalk Cakewalk by BandLab | BandLab Products Waveform by Tracktion Waveform Free | Tracktion Link to some others 21 Best Free DAWs 2022 – Never Pay For A Digital Audio Workstation Again (midination.com)
  25. Yep, my guess would be their lawyer told them to retain login stats so when/if some litigious user decides to sue Line 6 for their house burning down, L6 can pull up the database and say, "nope", that user pulled up that warning 68 times since last January and decided to ignore it.
  • Create New...