Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


mdmayfield last won the day on July 30 2022

mdmayfield had the most liked content!

Profile Information

  • Gender
  • Location
    Clearwater, FL
  • Registered Products

Recent Profile Visitors

1,247 profile views

mdmayfield's Achievements

Community Regular

Community Regular (8/14)

  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter Rare
  • Reacting Well Rare

Recent Badges




Community Answers

  1. I have experienced this kind of issue twice over the last 7ish years with my Helix and JTV-69, so I don't think it's the firmware update causing it. Both times, I never was able to figure out the cause, and after some days, the problem went away. Since I mostly play with the instrument volume at 10 at all times, it wasn't a complete dealbreaker. I still don't know exactly why it happened nor why the problem went away both times.
  2. To even begin to guess at the source of the problem, someone would need to see the actual error :-) Otherwise, maybe start here: https://opentechschool.github.io/python-beginners/en/getting_started.html
  3. Exactly - this particular concern is basically hypochondriac in nature. They're not talking about anything that will affect the sound. They're talking about stuff like consolidating the low-level electrical functionality of two chips into one. The input is still the same 6 L.R. Baggs piezo pickups routed into a high-quality multichannel A/D converter, and the DSP math is identical. If anything, why wouldn't one assume that the newer circuit boards are more economical and efficient, and therefore cheaper and flimsier? This is a non-issue.
  4. Oh OK. I didn't mean to call you out; my point was that it wouldn't be very easy to implement a quality, robust Undo, especially if they haven't architected the software in preparation for that all along. For example, what counts as one step of undo - adjusting a parameter? If the user made several quick small adjustments, they'd think of that as one change so it would be annoying to have to Undo a dozen steps to get back to where it was. Maybe it would require some logic to account for small changes within a certain window of time, with a "knob untouched" timeout that would register an actual state change. But that's hard to fine-tune to get exactly right for a wide variety of people and workflows. An Edited/Compare mode might be a good "80/20" solution since a lot of people are familiar with that - then only two edit buffers are needed, and at any point the user can toggle back and forth between the original patch and the WIP, and if they want to undo one specific change they could either refer to the original parameters or maybe copy/paste from Compare mode to Edited mode.
  5. I'm guessing you don't develop software for a living... :ph34r:
  6. If coming from traditional amps to a FRFR setup, whenever you are dissatisfied with your sound, investigate overall volume first. (i.e. Channel Volume, Gain at the output of the Helix, Master Volume, the volume controls on your speaker.) Our ears play tricks on us when it comes to overall volume - the exact same signal can sound very different at different levels, and yet it often doesn't seem to be because of volume (even though it is).
  7. You could create a blank patch in the HD500, connect the Variax to it via VDI, and send the raw Variax signal to your computer via USB. This would be as clean (and at the same amplitude level I believe) as running the Variax into a hardware Helix, with the major disadvantage that Helix Native still cannot control the Variax's model or tone. (Helix hardware can, just like the HD500)
  8. I would love to see a guide like this, being in transition from macOS to Linux and moving to REAPER from Logic. Incidentally, have you had any luck getting HX edit (or Variax Workbench HD for that matter) running under Wine?
  9. OK, I'm probably wrong about the MIDI Thru option then; it was one of many things I tried but I don't remember the whole story. Otherwise, regarding your MIDI signal path, the first thing I'm wondering is, where exactly does IAC come in here? It seems to me that there are 2 separate signal paths here that don't need to (and shouldn't) interact at all: 1. Fishman USB dongle ----MIDI notes and patch changes----> Mainstage --> audio signal 2. Helix ----MIDI notes----> DMXIS software --> DMX lighting control Neither of those should involve IAC; introducing IAC may well be what's causing the feedback loop. Also I don't believe DMXIS uses MIDI Bank or Program Change messages; the only way I've ever used it is to send MIDI Note Ons on channel 15 to select a bank, and Note Ons on channel 16 to choose the scene within that bank. Maybe they added Program Change support since I used it. Either way, you can get deeper visibility into what's going on by using a program called MIDI Monitor. It's free to use and you can find it here: https://www.snoize.com/MIDIMonitor/
  10. I've seen this before. You probably have a MIDI feedback loop somehow between the computer and the Helix, such that whenever a MIDI instruction like a note on or program change is sent, it goes round and round in infinite copies, which quickly overwhelms the Helix's MIDI processing and causes a hang. If I recall, I fixed it by disabling MIDI Thru in Global Settings; not sure though, that was a long time ago. I can't give much more advice without knowing a lot more details about your exact setup EDIT: MIDI signal path. I'm not clear on why Mainstage and DMXIS would need to talk to each other through IAC at all in your setup, for example.
  11. This is almost certainly not an issue with the firmware update per se, but something in your Global Settings that got changed (back to default). For example, check your 1/4 and XLR output settings to see if they got switched from Line to Mic.
  12. I saw you were using a bassoon with the Helix.... Times have changed a lot since New York Counterpoint huh? :-D
  13. There is already a hidden power amp stage in the Helix. It's simple to activate! Just wire up a custom AC-mains-to-XLR plug, and attach it to L6 Link. With standard USA wiring, the connections are Green (safety ground) to Pin 1 / shield, Black (120V live) to pin 2 / hot, and White (neutral) to pin 3 / cold. Easy! In the UK and other 240V regions, you may need to attach a Power Soak or similar to achieve the desired result. Don't actually do this, or you will cause fire and explosion and be killed by electrocution. Worse, you will damage your Helix.
  14. At about 2:00 in that video, they show holding the button down to change the pitch. You can already do this in the Helix by assigning a pedal to a parameter or snapshot controlling the interval. At 2:37, there are delay effect arpeggios, which are also doable in the Helix easily using a 50% Mix on a delay in the top path plus 100% on another delay in the bottom path. This pedal doesn't appear to have the ability to automatically mix, say, 3rds and 4ths for different notes within a scale (as would be necessary for licks like The Boys Are Back In Town). The Helix can't do this either, but you can assign a pedal to Momentary mode and coordinate feet with hands. Also, being a pedal, it's hard to put after the amp in order to get a nice studio double-tracked sound. At best you can put it in an effects loop. On the Helix you can actually harmonize the post-amp sound. On the other hand, the actual pitch shifting algorithm does sound better to me than Helix's. It sounds like TCE is doing some sort of formant correction which the Helix does not (Helix pitch shifts can get a little "chipmunk"-y). Personally, I only use harmony on a song or two here and there, and from the video at least, this pedal doesn't seem enough of an improvement to me over the Helix's built-in pitch shifters to be worth lugging around and putting in a Helix effects loop. It looks more like something specifically for people who want to stick entirely with individual pedals instead of programmable multi-FX.
  • Create New...