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

codamedia

Members
  • Posts

    3,298
  • Joined

  • Last visited

  • Days Won

    107

Everything posted by codamedia

  1. That's not how it works.... going back to snapshot mode simply gives you the options to choose a snapshot, it doesn't automatically load one. That is the behavior you will get if you set the stomp(s) in question to ignore snapshots. When you set "snapshot bypass" to OFF, the stomps on/off state maintains separation from snapshots. Page 47 of the V3 manual explains "Snapshot Bypass".
  2. It's the Waylon Jennings sound... Phase I don't get their the authentic way, but I just throw on a Script Phase and turn the mix down (between 30% & 50%) so it blends with the original tone.
  3. For troubleshooting, eliminate anything that can adjust volume... If you have a volume pedal block (often assigned to the EXP... disable it) As stated above, disable the big volume knob from your outputs I would also disable the Global EQ if you are using it... Make sure you try the 1/4", XLR and headphone out to see if the problem is everywhere, or just on one set of outputs.
  4. My steps are already detailed, and they are also in every update instruction Line 6 issues. I don't know how to make it clearer. You said that the problem occurred after an UPDATE! The simple question is... did you follow the update instructions and did you restore your "global settings" after the update? If not, that is likely where your problem occurred. Silverhead tells you how to restore your global settings... give it a try.
  5. There is no bug... bugs are unintended... this is by design. As far back as I've owned my Helix (2018), the update procedure has been as follows Full backup of the Helix (this is forced when updating through HX Edit) Update the firmware... this will restart the helix and rebuild the presets Perform a factory reset... (also restarts the Helix) Restore what you require from your last backup Global Settings (I do these) IR's (I do these) Presets/Setlists (I have 2 setlists I import where I do all my work... YMMV) Restart one last time and let the Helix rebuild the presets! Not part of the update notes... but I also do one more restart to make sure it starts without rebuilding again. I set aside 1 hour for the full procedure... it often takes much less. I never update the day of a show... or anything else that may be important. Since 2018 I've done a lot of updates... I have never encountered an issue. I'm not saying others have never encountered issues, I'm just saying I haven't!
  6. If you insert a "SEND/RETURN" as a single block... you can only set it to "Instrument level" or "line level". The problem is... often the send will go to the input of an amp which would be instrument level. But the amps effects send will be line level, therefore it won't match the return settings. Line level into something set to instrument level will be very loud.... there is an option to lower the return level on the block to compensate. This is not a "one adjustment works for all" solution... everyone needs to know how their various pieces of gear operate, and set/adjust things accordingly to accommodate.
  7. Since you don't want an on/off state on the volume pedal.... set it to none. @datacommando pointed you (and me) to the right page in the manual.... your volume block will be assigned to one of the EXP pedals positions, you want to set it to "none"
  8. I don't use an HX Effects so I can't really direct you... but it is part of the "bypass assign" area for the block. Locate that and you will see EXP is assigned... remove the assignment.
  9. That sounds to me like the ON/OFF state of the volume block is assigned to the exp value. That is often great for a WAH, but not a volume pedal. Locate that assignment and remove it.... then make sure the volume block is on when you save the preset and/or any snapshots depending on your snapshot global settings. The volume pedal block will always remain on, and will obey the global settings of the EXP pedal.
  10. I embrace the separation of presets when switching amps. I rarely find that the same effects settings work across different amps, tweaks are often required. I work on a master preset... then save that preset to multiple locations so all the pedal assignments and effect layouts are consistent. When I swap the amp in one of the presets I then make the tweaks to those effects to accommodate the change. This works for me because I only use a few amps. I really only have 3 live presets... a Fender, a Vox and a Marshall. Those have been in tact for several years now with minimal change. For those times where I decide I have a new favorite effect or effect setting, I simply save it as a favorite and load it in each preset rather quickly. Studio is a different game.... effects are kept minimalistic, and I'll tweak the amp models and cabs a lot more to get the source tones right.
  11. Create a parallel path with the split block.... insert a separate preamp on each path then merge it back together with the paths hard panned. From that point forward everything needs to be stereo... including the cabinet block. If running IR's, you may need to add those in the parallel paths individually. After the merge, If you insert a mono effect/IR/cabinet everything will collapse back down to mono... that is why you need to use stereo effects after the amps. Mono Effects > Split > one amp on each path > merge > stereo everything all the way to the output Pay attention to the warning from "theElevators"... make sure the signal collapses elegantly to mono or you may be in for some horrible surprises on some gigs. Also keep in mind, in order to monitor this in stereo on stage, you still need a stereo power amp and cabs, or two monitors and a monitor mix that allows stereo.
  12. That is exactly how it would operate if you didn't ASSIGN the parameter to snapshot control. By default, nothing is controlled by snapshots other than the on/off state of the block. If you want a parameter to be controlled by snapshots, you need to assign it as such - then set it accordingly from snapshot to snapshot. If you want the on/off state of a block to be ignored by snapshots, you need to assign it as such
  13. It is a valid solution. The Helix does not have a PAD on the XLR's like a good DI does, so using the Global EQ (assigned to XLR only) is a great way to repurpose it as a pad. That said... you say a -20db. WOW, that's a lot. A PAD is usually about a 6db - 10db cut. I agree with others that say your preset(s) may be too loud.
  14. The fact that is sounds completely different is exactly what I would expect. They are completely different monitoring situations. As with any setup, it starts with the amp model. Start by getting a great tone through the FRFR with just the amp/cab model, then add the effects.
  15. I had to go find this older post of mine from 2018.... 3 post in on this short thread https://line6.com/support/topic/35963-using-a-300-variax-with-a-helix/ But here it is again for quick reference... Bottom line, it works, but it takes some getting used to. -------------------- For anyone interested in connecting an older Variax and a Helix... take the time to learn how they will interact with each other, or you will be left scratching your head in confusion... especially if you came from an HD500 or earlier POD XT Live or X3. The two most important things to understand... when you use "force mode" to load guitar models from a preset or snapshot change.... You can only set the model access from the HELIX... You cannot change the model on the guitar, then save on the Helix like you used to with an older POD The HELIX can only access the FACTORY Variax Models, Custom 1 and Custom 2 locations. Read that carefully! Here's why! If you customize your variax guitars in Workbench, then store them over their original location the Helix cannot access those. You can call them up on the guitar itself, but the Helix cannot load them through preset or snapshot! Any custom guitars you need instant access to from the Helix (ie: loaded with a patch/snapshot change) must be stored in a CUSTOM 1 or CUSTOM 2 location. If you change guitar models via snapshot... and are in the habit of changing pickup positions on the fly... I strongly suggest you set Snapshot behavior mode to "discard". If not... it won't take long to learn why :) IMO: The reward of having guitar model changes available via snapshots more than makes up for any inconvenience of learning a few quirks. My Variax 300 has new life under the HELIX... now that I've learned it's new personality :) --------------------
  16. I don't believe this is possible internally... but you might be able to do a midi loop back and set the EXP pedal to send the required midi message(s). There is an audio gap when changing presets so I don't believe that will yield any usable results, but snapshots may work.
  17. Submit a ticket to Line 6 and include an export of your preset along with the details you provided here. If it's a bug, they will be able to reproduce it which is the first step to bug fixes! They can't fix it if they are not aware of it. There are thousands of configuration possibilities in a Helix... you have stumbled on one that affects you.
  18. "Sounds" very flat? Have you plugged into a tuner to see if it "is" very flat? That will quickly confirm if the guitar is the problem, or if it is just the environment (ears, room, volume, perception, reflection, etc...) Next time I get a chance I'll check my JTV...
  19. That video is a good example.... you simply can't use the same settings on the effects, they need to be altered to make it work for a similar result. FWIW... I prefer delays "before" the dirt... I find it more dynamic and interactive. Reverbs are not something I use a lot... just a natural sounding room to create a little space.
  20. You are likely correct on your 2nd assumption... which would be a software bug not a impending DSP failure. Also, the fact that reloading the preset solves the problem also points to software.
  21. Set your Helix to a specific midi channel... then make sure Logic is not sending on ALL channels. If you lock LOGIC down to a default of channel 1, and the Helix to Channel 2... the Helix will never hear any of those messages. NEXT: If you want to send a message to Helix from Logic, send that specific message on CHANNEL 2 (or whatever channel you set the Helix to)! Most people forget (or don't realize) MIDI has 16 channels. Keep your devices separate and make the instructions very detailed. That prevents unpredictable results!
  22. I'm quite surprised you are getting the results you are getting. The added impedance on the guitar input usually "rounds out" the tone making it "less ice picky" than going into a RETURN input or Audio Interface. Perhaps the added impedance is messing with the capacitance of your cable. Have you tried different cables...
  23. If you are thinking of buying a Helix Floor or LT... this is not an issue as there are 32 blocks to work with. If you are planning on buying a STOMP or STOMP XL... that's when it may be a concern. That said... I use an LT and have a Stomp as a backup... I have no problems laying out useable presets on a stomp, I just can't cram everything into one preset.
  24. My LT presets go direct to FOH/Monitor and do not require any sort of high end roll off. I also don't roll off any high end in the preset itself. I use an MBritt IR that I found many years ago but the new cab engine in the Helix (which did not exist when this thread was started 4 years go) is also quite capable - I record with those all the time. Admittedly, I did struggle with the original cab engine on the Helix because they were all "center mic'd" and didn't give us the ability to move the mic around the cone at all. That was what led me to find an IR I really liked.
  25. Did the problem start with the "new battery"? Is it a genuine battery, or third party? I see in the video you show a full charge... but you do that with the modeling turned off. Check the status with the modeling on since that puts the load on the battery. Do you have anything with a VDI port so you check to see if the modeling is working there? Also, @psarkissiansuggests using a TRS cable, not a TS.... the cable in the video looks to be a standard TS (but I could be wrong).
×
×
  • Create New...