duncann
-
Posts
2,925 -
Joined
-
Last visited
-
Days Won
45
Everything posted by duncann
-
I've also noticed this effect sounds monoish. It does have a spread parameter, but I can't really tell that it's doing anything.
-
I noticed this right away as well. I'm already dreading the thought of targeting the mouse cursor on such a small area. Same with the preset list scroll bar.
-
Great to see pitch-blocks'-intervals-not-being-restored-properly-on-import fixed. Works now. The new LFO reset feature I think is something I could have used countless times in the past. Great! The stereo doubler effect looks very interesting. Could have done without the new amps. I hope they start spending less time on new amps, and more on features. HX Edit's window position doesn't seem to be remembered.
-
I'm sure they did know. I believe the actual device it's modeled from has this behavior as well, which is why it's there in the HD.
-
See post #41 and #57 above. Hopefully the dropouts will be gone in the next update, which should be very soon, or so I've read.
-
Guitar: Mark IV Lead Archon Clean Bass: SVT Bright But the amps to me are fairly inconsequential. More important are cabs and/or IRs.
-
Possibly at the cost of one's sanity though. I know I wouldn't want to look through 64GBs worth of presets! You might as well Count To A Trillion. I'm the same as you. I only keep presets if they're used somewhere in my songs. I do keep multiple versions of each preset, for each Helix firmware version going back as far as 1.04.3.
-
This whole thing is subjective, but for the most part, the effects in Helix are generally quite good. The delays I feel are noticeably better. The reverbs are currently fine, and are actually the same ones from the HD, ported from the HD. The modulations feel more dynamic and organic in Helix. Most of the wahs are ported from the HD; there have been a couple of new HX ones added throughout the updates. There are places where things are still lacking, the most noticeable is filters. If you use any of the wonderful and more obscure filters from the HD, plan on keeping your HD around, as there are only three filters on Helix, all basically a variation of an autowah. But the ones there are good. The other weak point is the pitch shifting, which I think most would agree it could be improved to track quite a bit better.
-
That's true in in some situations, but for me, I use the computer for other things and there are advantages to having a primary, dedicated audio interface (internal soundcard) that simply passes through the HD's, or Helix's, signal to the speakers or headphones.
-
Sorry. I don't understand the questions.
-
Helix does have MIDI over USB. It's very convenient. For the HD500X, you could always get something cheap like this: https://www.amazon.com/gp/product/B072B94W7Z/ref=s9_acsd_top_hd_bw_boEuh_c_x_3_w/132-5126778-4843321?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=merchandised-search-3&pf_rd_r=DH8M8EQWYK86F13WWBYC&pf_rd_t=101&pf_rd_p=c515cc61-1edc-59c3-aab2-673ee6fe243a&pf_rd_i=11973731 With that you could control the HD from the DAW, or you could control the DAW with the HD.
-
Yes. This is what I've meant. It is very useful for automating not only preset changes, but toggling a presets blocks and controlling the HD's expression controllers, etc., from your DAW.
-
I still think we must be thinking of different things, or the terminology Line 6 chose to use might be confusing. The HD is simply not capable of sending MIDI data over USB. It understands MIDI data, but only through the dedicated MIDI din connectors. The type of MIDI data I'm referring to is CC and PC messages. See appendix B of the manual. The picture you linked above is showing information about MIDI clock sync.
-
Perhaps we're thinking of something different. The HD is not capable of sending MIDI data over USB, or you can't control the HD from you're DAW via USB, and vice versa. The HD is only an audio interface.
-
The HD500X does indeed have midi ports, but they are only for connecting external gear, excluding a computer, unless there is another device between the HD500X and the computer, such as a USB-to-MIDI interface, or another audio interface with this functionality, which you mentioned above. When I used my HD500X, it was only in conjunction with Reaper, so it didn't have to be turned on all the time; no need to waste electricity. The digital output was used for monitoring. Never had a problem using it this way and am not sure what's inefficient about it. I use Helix now the same way.
-
Try purchasing a very cheap all in one amp/speaker, say ~$50 or less, and force yourself to play through that for a while. Then go back to the pod. Sometimes, maybe all one needs is a perspective readjustment or recalibration.
-
Probably wouldn't work too well, but you could possibly use the toe switch by plugging it into EXP3 on Helix Floor, which might allow for a clumsy, extra min-max switch.
-
Does the sound cut out for only a second or so, after Helix has been on for a while? Are you using a digital connection from Helix, probably AES/EBU since you mention a digital stagebox?
-
Recording the expression pedal movement is pretty straightforward. In your preset, go to the command center, select the desired expression controller, then adjust the parameters accordingly. Command: MIDI CC, MIDI Ch: x, CC#: x (I use 2 because when I send the recorded midi data back to Helix for reamping, 2 is the midi cc for expression controller 2), Min Value: 0, Max Value: 127. Then in your DAW (I use Reaper), have a track with its input set to MIDI: Line 6 Helix: Channel x (whatever MIDI Ch you set in the command center). In your preset, delay mix and feedback will both be assigned to the same expression controller. As far as using this recorded midi data as an input for Helix Native, I'm not certain. I think currently, Helix Native doesn't understand midi, so it may not be able to be used in this way. You might want to, at least for now, use your physical Helix for reamping in this case.
-
Sounds like a seeker or obi wah, both from an HD500X, in the filter category. Not sure if these are in the HD300.
-
Just quickly tried, editor v2.26.0, and it did indeed work, both with the HD turned on and off. And completely deleting an entry leaves behind a blank entry in its place.
-
If you use the editor for creating presets, it might be possible to edit the 'PODX4Edit.lang' file, located in the 'res' folder wherever you have hd500x edit installed. It's just a text file and when you look at the contents it should be obvious which entries you would want to change. Most likely you'd want to replace the offending amps with a blank ("") text description. The resulting list would still be the same length, but with some empty entries, making the amps (or effects) you want slightly easier to locate. You may even be able to delete the entries you don't want, however I'm uncertain what that would do. If you don't use the editor, then as silverhead said, there'd be no way.
-
I just realized that, oops :o, and have since installed v2.21 of the editor. Same result. I should also mention that the values are preserved, even making changes to the preset, as long as the preset is saved in the same location, using the editor.
-
Nerve racking bug this one: This preset: Lead.zip, firmware v2.21.0, makes use of a harmony delay where voice 1 shift and voice 2 shift values are changed via snapshots. However, these values are not preserved (regardless of the snapshot edits global setting) when imported by any method using the current editor, v2.21. Likewise, using the editor, a copy and paste to a different location does not preserve these values. Saving the preset to a different location using the device itself seems successful. For anyone looking to see the correct values, you can open the preset in a text editor and find snapshots named Harmony 1, Harmony 2, .. , Harmony 5. Then look for internalvoice1 and internalvoice2. The values should be: v1 shift, v2 shift -3, 4 -4, 3 -3, 5 -2, 3 -4, 3 I'm also changing key and scale and these settings are preserved correctly.
-
There certainly are situations where this is almost necessary. For example, with the dynamix flanger as the first effect, it can create a gnarly and raw sounding tone if you're going after an exaggerated flanger type effect. But using the flanger controls to tame the rawness can take something away from the intensity. An eq before the flanger could be a good solution to smooth things out without taking too much away. Other than situations like that, I usually don't bother with pre-eq, unless it's for a bass guitar with its active eq disabled.
