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

codamedia

Members
  • Posts

    3,253
  • Joined

  • Last visited

  • Days Won

    106

Everything posted by codamedia

  1. Good catch... thanks for the reminder!
  2. Glad it's working for you... I really don't want to setup an account on the forum you linked to.... any chance you can share that excel spreadsheet here?
  3. The settings will mirror what is stored in the guitar at that moment. If somebody changed the patch, you will only see their changes. Any changes you make in Workbench are auditioned in real time, but need to be sent to the Variax to be retained. Take a search on these forums for a "Factory Default" patch. I know I found one for my 300 when I got it used... I just loaded the patch in Workbench and uploaded it all to the guitar. It's a nice clean slate. If the 500 uses the same patches, I could share my "default" patch... but I would hate to give you something that is incompatible. Maybe someone else will know for certain if I can share my 300 patches with a 500. Workbench warns you... many times. When the guitar is updating (eg: when you are sending patches, or updating the firmware) DO NOT change anything on the guitar! When I am updating I don't move! My biggest concern is that the VDI loses it's connection during mid update... that has the potential of being disastrous. That said - I have NEVER had a problem with any updates... and I've been using/tweaking the 300 regularly (several times per year) since I got it in 2012.
  4. For the 80hz cut I would try an HPF set to 100hz cut by about 3 db. That may seem high, but an HPF is gradual and by starting at 100 it will emcompass the "Q" that is fixed on the graphic EQ. I like the suggestion above as well.... fix that low end in the cabinet parameters. I would still recommend a 3db cut starting at 100hz. With the other frequencies.... as I allude to in my first sentence there is a fixed Q on the graphic and it is pretty wide. The default Q on the global is likely too narrow, you will need to widen it a little (not drastically) to get the same results. Sorry I can't give you any exact numbers.
  5. There are two things that come to mind for me.... If I were using your chain, why bother separating the paths? Just insert SEND 2 right before the IR (don't use a loop, use a send as it doesn't need to be returned). Use the "send" to your amp, and use the output to your DAW/PA. To preserve the Loop for other use... place the IR last and drop it to path B. It should become the only item in path B at the very end. Next, head over to the output Y and hard pan the paths LEFT and RIGHT. Send Path A to your amp and path B to your DAW /PA. You will have to compromise on your output setting. You can set it to LINE and turn down the output going to the amp... or you can set it to Instrument and turn up the signal going to the DAW/PA (both volumes are in the Output Y with the pans). Using the latter would be my preference... as a DAW/PA will have more options to deal with input gain than an amp does (IMO), but this is something to experiment with to get the best results. Good luck....
  6. I am pretty sure it's scheduled to be out during the 2nd quarter 2018... that means any time between March 21st and June 21st. The HELIX is the flagship... I suspect it will always take precedence. However, once EDIT is setup to fully communicate with the HX I think it will be much easier for them to keep all updates together. This is pure speculation on my part :)
  7. Thanks.... the chain looks like it is setup correctly... but I think I see the problem. The entire point of using 4cm is to include your amp in the sound. You didn't do that when setting up your sounds. When you have the HX Effects "effect loop" turned off, all you are getting is the HX Effects direct to your amps "return"....only the master volume and power amp are being used from your amp not the pre-amp. When you have the HX Effects "effect loop" turned on , that will include your amp. This is what you really want. If you setup all of your overdrives with the loop off then you didn't include your amp in the tone! You have to get a good tone from your amp, then build your sounds around that... not the other way around. IMO: 1:) Turn on the loop and leave it on. 2:) Turn off all effects (other than the loop) and dial in a great amp tone. 3:) Setup your effects to that tone! It will sound great!
  8. Can you chart your signal path so we can all understand your setup? I am asking this because in a 4cm setup you need to have a loop on the HX and one on the amp... I'm not sure how you are comparing the sounds to know why you think the loop is at fault.
  9. This is the route I took ... and it's created a very versatile platform that has really extended the life of my HD500. Some ask why I didn't just buy a Helix, simple answer - I don't always want, and often cannot carry a full size board... the HX Effects was a perfect combination of features and size. Yes... all of them are relevant. The only difference between them is the "x" has more dsp power and nicer footswitches. The programming and tones are the same.
  10. That shouldn't happen. I suggest you clean the jacks on both the XPS and the Variax. Do not spray cleaner directly in... spray the jack then plug it in/out several time and repeat. Find quality cleaner (deoxit or similar) and NEVER use WD40. Although I have an XPS mini... I most often power mine through a VDI cable connected to my HD500. The VDI is extremely useful for much more than power, but you do need a VDI compatable (XT, X3, HD) device for it to work.
  11. As far as I know every sound in those 3 pedals you mention are already built into the HD500 so it would be completely redundant. If you want to extend the HD500, I would suggest some analog overdrive pedals either before the unit, or in the loop. Take the time to really learn it... it's a great unit. I recommend starting with an empty preset and build a sound one pedal at a time, and watch the output volume. Every effect you add should be kept at, or near unity gain or the output level will get out of control.
  12. I have found that a used XT LIVE or X3 LIVE is easier to find and about the same cost as the interface when you do find them. I would suggest going that route. Keep in mind the "Beans" do not have a VDI port and will not work... you need the LIVE version, or the X3 Pro. FYI: The older version of Workbench still installs and works fine on a Windows 10 machine... the website just doesn't show it as supported. I have it running on both a Windows 10 laptop and desktop. If you encounter any JAVA errors, you need to install the latest version of JAVA (java.com) to your computer because the installer can't do it automatically anymore. This problem will exist with any Windows operating system.
  13. TRS does not transmit or receive any midi... that jack on the footswitch is likely dedicated for use with the Bugera Tri-Rec amps. This footswitch works as a midi controller only when you use the midi ports... and by the looks of it, it doesn't even have a MIDI OUT (it has a through) so I think it only received messages to control the Bugera Tri-Rec. IMO: I don't think it can send anything to the Helix. If you find a footswitch with MIDI IN & MIDI OUT/THROUGH you should be able to make it work... Helix Out > iPad In iPad Out > Controller In Controller Out/Through > Helix In Then you need to setup appropriate midi channels to make sure the right device talks to the right sections on the Helix.
  14. codamedia

    Reverbs

    There are a couple of "spring" reverbs under legacy... they should be the easiest to get setup. As stated already, set the pre-delay higher for more note definition. I find the 35ms is usually enough... but you may want more. Setting it in a parallel path helps, and adjusting the lo & hi cut can also help to keep it out of the way of the guitar.
  15. IMO - you don't need them all, you need a few.... at most. If you are new to this, trial run 10 at a time. Pick your favorite and keep it... discard the other 9. Add in the next 10 and compare it to the one you kept. Keep the ones you really like... discard the rest.... repeat as necessary. I have a solid understanding of cabinets, speakers, microphones and position. I can safely discard 295 out of 335 before I begin. SURE - there might be a gem in there that I am discarding... but I'd be sure to miss it anyway with that much choice :)
  16. You can think of sends as additional outputs, and returns as additional inputs. This allows you to route multiple instruments to different locations, or different tones to different locations. Assign a switch to them and you can think of them as A/B/Y boxes. Anybody that is juggling multiple instruments, has multiple amps, or needs to send a different signal to PA than they do to their amp will find these options very beneficial. With a little imagination they can solve problems you don't even know you have yet :) OK - I know that doesn't really answer your question - LOL! Here are a couple real world examples that barely scratchy the surface of possibilities. 1: If you run an IR Cab sim you will want to send that to the PA.... but if you are using a guitar amp on stage you will not want that IR directed to the amp. Assign a SEND in block 8, and send that to the guitar amp. In block 9 can be the IR - send the output to the PA. 2: I have an acoustic patch that also work well with my mandolin. I keep my mandolin plugged into a "Return". When I need to play my mandolin I turn down my acoustic, grab the mandolin and hit 1 switch. That switch un-mutes the mandolin and turns on an EQ to help tweak the tone a little.
  17. SOLVED! When I did my initial test I was in controller mode on the HX setting up the communication between the two devices. In that mode - there is latency.... lots of it. But as soon as I exit that mode to another view (patch mode, stomp mode, even signal flow) the latency completely disappears and the combination is very responsive. So the latency problem is only in "controller mode"! That doesn't matter one bit to me... I'm just glad it actually does work as it should.
  18. Thanks to both of you for confirming... it's not a big deal, I was just checking to see if there was a trick I wasn't aware of. I can certainly find something I can use with the pedal steel for one block... surely I can make do with 8 effects in path A - LOL!
  19. Judging by the embedded thread below, as of Rev 2.5 the HX will not recognize a toe switch. There is an "auto engage" option for the wah that you may be able to incorporate... but I'm not sure how you would go from VOL to WAH with that without dedicating another switch.
  20. I just see it as another option... especially since they have given it the "taper option". You only need to utilize a Volume Pedal block if it is important to you. I believe you alluded to this already, but I'll expand. If you don't have a spare block, you can always assign an expression pedal to the output of any given effect which will pretty much accomplish the same thing... but that will always be linear! If that works for a particular user... great, but if a user needs a LOG taper, the volume pedal block is a great option.
  21. Good suggestions to try... thank you. To be honest, I don't know if the latency is introduced by the HX or the HD. I won't have access to either for a few days but I will do some troubleshooting as soon as I get a chance.
  22. OK, I see the "why" now :) There is no way the trem can "feel" your playing and pick a start time from that... it is locked to a clock that either begins when you engage the trem, or it begins when you change your patch. I don't have the unit with me to test this right now, but you need to figure out which one triggers the timing clock. 1: If the clock is locked to turning on the trem, you need to practice turning it on in time with the drums. It should begin when pressed, not released. 2: If you are really struggling with it when you turn on the trem... then the clock could be tied to the patch change. While the drummer is counting in the tune, change the patch on time with the drummers count. If you need to be in at the very beginning, you may need to double the length of the count so you are all coordinated. 3: Ditch the preset tempo and try setting the trem to TAP TEMPO and tap in the time when needed. A tap will reset the start time so it is easier to lock in with an existing speed.
  23. Turn off "Bank Changes" and "Program Changes". I see it in the manual, but don't have the device in front of me to tell you exactly where it is. I believe this will eliminate any automatic program changes while you change patches, but will still give you the ability to set it up for each switch while in "stomp mode".
  24. Pretty sure there is, but I don't have my HX or manual in front of me at this time. Check the manual, or the HX FAQ on this forum. It's there somewhere!
  25. IMO, Tremolo is not an effect that sounds best "in time"... a little loose isn't a bad thing. My tremolo is set to a fixed tempo (no idea what is is off the top of my head) and I use that for everything. In the studio I may be a little more picky :) Have you tried "tap tempo"? In my experience.... there are very few drummers in the world that will nail a tempo to a fixed preset! Get the song started and tap in the tempo... I think you will find it much more reliable. (FWIW: I don't do that with tremolo, but I do it with syncopated delays all the time)
×
×
  • Create New...