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

codamedia

Members
  • Posts

    3,239
  • Joined

  • Last visited

  • Days Won

    102

Everything posted by codamedia

  1. Thanks for the tip... I will try this in real time.... For the record, this is what I have been doing to this point. OK, this is a step I have never tried. Reverse of what I want, but let's see what happens. NOPE: Same results. When recalling the patch, the LED is lit up showing the state of the COMP (in this case, lit up)... I would like the patch to recall showing the state of the overdrive. (yes, the overdrive was the block showing when I saved)
  2. Well - no luck with this at all. Now it never works as I expect... I'm not sure how I ever got it to work to begin with - LOL! To clarify.... I am combining a "Teemah" and a "Red Squeeze" on one footswitch I want the "Teemah" ON, and the "Red Squeeze" OFF when I save the patch. (loading the patch will always have the "Teemah" on) I want the LED to show the state of the "Teemah"... therefore when I recall the patch the LED should LIGHT UP. This is never happening... it always shows the state of the "Red Squeeze" which is LED off. Extras I have tried... I have reversed the order of the two effects in signal flow. I have reversed the states hoping that might help... but the LED still loads showing the "Red Squeeze" state. I have tried this on blank patches, and existing patches I have tried this on a few different footswitches I have tried this with different effects.... it always wants to default to just one of them whether that state is ON or OFF. As a final note... it's minor, just an irritation. I don't want to name the switch "Comp"... I want to name it "Overdrive"... and I want the LED to come on when the overdrive is ON. But it is not working... Any further suggestions?
  3. I can't assume anything - LOL After saving the patch, are you sending it to the HD? I ask because it's not enough to just save it in Edit alone. If you are, then this could be another EDIT bug.... it has a few. Try making the change on the HD500 itself and saving it.... does that solve the problem?
  4. I hope this doesn't get me banned... but I'd like to try and politely point out that most people that don't live in the USA find a comment like this very offensive, arrogant and ignorant in the purest sense of the word. It's not based on jealously, it's because they live in great countries as well :)
  5. I'm with the others... I'd love to see a separate forum for the HX Effects. Lumping the HX Effects in with the Helix is the equivalent of lumping the M5/M9/M13 in with the POD HD... which is something they didn't do!
  6. ^^^ THIS ^^^ That will confirm whether it is the HELIX having a latency issue... or if it is something further down the XLR chain (mixer, effects, speakers, distance, etc... etc...) causing the problem.
  7. This is an old thread, but since it's been re-opened I'll add my thoughts on the MIC input. For some people the HD is their primary Audio Interface for recording... having the mic input is no different than having a MIC input on any other interface. It's great for someone doing a single act. Carry the HD and a powered speaker... that's all you need. Setup a dual path (one for guitar, the other for the mic) and send them to the powered speaker... no need to carry a mixer. As a multi-instrumentalist I find it never hurts to have another input. None of my additional instruments use mics but that doesn't matter... I often plug my mandolin or dobro into a direct box, then run an XLR from the DI to the mic input.... adjust trim as needed. Added features are never a bad thing... even if you don't see the immediate value in it.
  8. Unfortunately, there is no way to assign the MIC input to a return only. What you are looking to do can be done using dual paths but it will be MONO only (each path uses one side of left/right) and you will need to be careful not to create a loop by properly adjusting your pan controls in the HD mixer. EXAMPLE: Upper path set to guitar input.... add effects to taste, send that side to the amp/iso cab. Lower path set to mic input (adjust trim for appropriate gain) .... add processing to taste, send that side to the Board/Monitors. WARNING: The 1/4" outputs collapse to MONO if only one side is plugged in. If you are sending to Board/Monitors via XLR, you need to insert a dummy jack into it's 1/4" output or the mic will also get sent to the amp and the results will be a continuous feedback loop - it could hurt :)
  9. The difference between a Floor Pod and an HD500 is that the exp pedal and toe switch are not "fixed" to anything on the HD500. You can assign these to anything you want making it extremely flexible. More options can make it more difficult to figure out at the beginning, but it is worth the effort. What you are trying to do is possible... and it does work flawlessly. Close.... very close. But why assign the WAH to a footswitch. Assign it to the TOE switch that is located under the pedal.
  10. Sorry, I don't own a Kemper and can't give specific examples, but I'll try to help. If you are new to midi then you will want to keep this simple. You can do a lot with MIDI but my advice is to walk before you run. By default, devices will usually setup MIDI to listen on all channels (omni mode) and program changes will be on. If you hook up a midi cord from the "midi out" of the HX to "midi in" on the Kemper every time you change a patch on the HX the Kemper should follow. That is the easiest way to line things up... just store your amp presets in the corresponding patches that follow the HX. If the Kemper does not follow the HX program changes, you may have to set the midi channel. You will need to check the Kemper documentation to see if you can turn on Omni Mode.... if not, just set it to channel 1 and make sure the HX global Midi is also set to communicate on Channel 1. The HX Effects operates very similar to the Helix... so if you can find videos or topics about controlling the Kemper with the Helix most of it will apply.
  11. Do these L6 forums have a policy about starting new accounts with new handles for the sole purpose to troll the forums? It doesn't take much effort to figure out that "northerntwang" is "ddmilne".
  12. Can the editor do this yet for the HX Effects? I didn't think it could... Be careful with presets... they are created with different guitars, different amps, different monitoring situations, etc... etc... With past devices I have NEVER succeeded in finding something I like from someone else's preset. Even with the HX - the moment I got it home I loaded a blank patch into every location so I could start fresh :) I don't mind seeing peoples chains and settings as a guideline... but I'll use that info to build my own patches because I know "their settings" will not work with my gear! I was just looking at the settings in a text editor and see Variax settings, two DSP's, etc... etcc.... Isn't that a Helix preset? I thought the OP was asking about the HX Effects?
  13. An FX loop with nothing connected to it should produce a dead signal (no sound) unless you set the mix control to allow the dry signal through. If you were to patch a short cable between the send and return there should be no difference in the sound when engaged. No added noise, no lost signal, etc... etc... I'm confused because this contradicts what you said earlier "I dont even have anything connected to it". That's a very logical assessment... I just want to share my past experience with loops. A loop with just a small patch cord is a very transparent cut/boost when you adjust the in/out levels... and it uses very little (pretty much zero) DSP power.
  14. I'm using the HX Effects with Pedal Steel. What you are asking about is certainly possible. There are two options. 1: Insert one of the loops where you want it in the chain and connect your volume pedal to that. This is perfect if you have a really nice volume pedal such as a Goodrich or a Hilton, not to mention this method is foolproof and will work every time. 2: Insert a volume pedal block where you want it in the chain, and connect your volume pedal as an expression and assign it to control the volume pedal block. This works well if your volume pedal isn't high end or if it has a dirty pot (scratchy) since no audio passes through the volume pedal. NOTE: Not all pedals are compatible with this method. Myself.... I use a 250k VP and connect just the output to EXP2 and it works perfectly.
  15. Yes - that is exactly what I am doing... glad to know my approach is suppose to be right. The problem is that out of nowhere the patch (during recall) will reflect the state of the comp rather than the overdrive which inverts the meaning of the LED and scribble strip. I will troubleshoot this a little more today and see if I can narrow down the problem.
  16. I use a toggle to switch between a compressor and a light overdrive (Timmy). They both assign to the toggle no problem, and the toggle works fine. BUT - the LED is inconsistent as to which state I should be in. I give the toggle a custom name of "Light OD" so the thought is when the LED is off the compressor is engaged and when it is on the Overdrive is engaged. The problem is... the HX has a mind of it's own which state it will show. I get it working right, save it. Come back to that patch later and it shows "OFF" yet the overdrive is the one engaged. I know that by touching the toggle I can show the states of the two effects... but I would think after saving the patch it should always RECALL the way I saved it. For the record, I am not using snapshots. Any idea's why it is behaving this way? The HX Effects is up to date with firmware version 2.54 EDIT TO ADD (this is one of my post further down the thread, but may get missed)
  17. First, I use an HD500 not a 400 so I'm just trying to help out here... I really don't have any way to test this :) According to the manual, dual mode should do what you need.... plug your 1/4" out(s) to the power amp in on your amp, and the XLR to the PA. Based on this statement below, I would EXPECT (expect is the key word) the XLR output to use the cabinet/mic modeling from the HD, and the 1/4" outputs to discard the cabinet/mic modeling. Are you saying that the cabinet and mic modelling is still being sent to the 1/4" outputs in this mode? From the manual "When set to dual, direct signal meant for a guitar amplifier will be sent through the UNBALANCED L/R Outputs, and mic and speaker simulation meant for a mixer or recorder are sent through the BALANCED L/R outputs."
  18. Yes - that is what I was referring to... Auto Save was a poor choice of words :) Thanks for the detailed clarification of how the two modes operate. I agree the discard would likely be the most common and least confusing but recall certainly has it's advantages as well. It always depends on the workflow of the player.
  19. Late spring was the announcement. So - most likely anytime between now and June 21st.
  20. The HD500 volume pedal is fixed to linear taper which is actually very unnatural. Most people prefer an audio taper for a volume pedal. The Helix has the option to set the taper to linear or audio and that is likely what you are experiencing from patch to patch. Find the setting used in the patches you like and go with that for all the others. The same way you would have on the HD500.... insert a volume pedal block and assign the exp pedal to it.
  21. I could be completely wrong on this... but I'm throwing it out there anyway. Aren't snapshots "auto save" by default? If it isn't default, maybe it got changed? This could cause a lot of confusion. Example 1: Setup snapshot 2, save it. Now If you edit that and save it to Snap Shot 3, both 2 and 3 will be the same because 2 auto saved and won't recall as expected. To get around this, you would need to switch to snapshot 3 before editing and so on. Example 2: You play snapshot 2, move to snapshot 3 and play a bit.... maybe turn on/off an effect or two, move an expression, go back to 2 - all fine, come back to 3 and it is the state you last left it, not the perceived "saved state". Now, that said.... it should reset to the "saved state" if you leave the patch and return to it. If that is possibly the problem, there is an option to change it so it won't auto save. Off the top of my head, I don't recall where.
  22. In the output section of the unit (in the menu, not a switch on the machine) there is a setting for Output Mode. Make sure that is set to Studio/Direct. They always will. No two sets of headphones sound the same, no two sets of speakers sound the same, and no two PA's will sound the same. As long as the quality of each item is sufficient, and as long as nobody has EQ'ed the PA system to death (eg: big smiley face EQ) you should get good sounds. Is your sound too thin, or is his sound too thick! It is important for guitar players in a double guitar band to work with each other on developing tones. Your friend is likely steeling all the headroom from the system, leaving nothing for your tone. A BASS will do this in the heartbeat if the system can't keep up... but I full bodied guitar tone turned up to loud can also eat up the space.
  23. This shouldn't limit your routing. The worse case scenario should be that you have to use up 2 blocks. If DSP is an issue you could just load 2 x 1024 IR's. I could be wrong about this... but I'm pretty sure that any stereo effect prior to the path split would just separate to left/right down the two paths. At the end of the path you will have to set the output pans to keep it stereo.
  24. I just want to add one more option to the table... If you try a Variax and don't like the neck, you might be able to replace it. I don't know about the 500 (original Variax) but the 300 and 600 necks can be swapped with a regular Tele or Strat neck. I believe this can also be done on the JTV, but not on the Standards. About 8 years ago I bought a 300 just to test the waters of a Variax. The sounds in the 300 are the same as the sounds in the 500, 600 and 700 - but the guitar itself is a much lower quality. I found a nice Fender Tele neck from the 80's, bolted it on and that changed everything.
×
×
  • Create New...