Jump to content

stephane_dupont

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

5 Neutral

About stephane_dupont

  • Rank
    Just Startin'
  1. Thank you for this information. But unfortunately, already tested it (with TRS cables) and it was picking way more static noise from the computer than using the XLR out. That being said, to use for monitoring, should not be a problem. Will do that. Thanks.
  2. You are talking about audio degradation, I'm talking about picking electromagnetic hum, static noise, etc. Any unbalanced cable used near a computer will be picking up all sorts of these. Not an option for a recording environment in a typical small/home studio setup.
  3. Thank you @rd2rk, but as I'm using this in a recording environment, using unbalanced sends are out of the question. The whole setup is about avoiding anything unbalanced actually.
  4. Hi, For a recording I'm using the following preset: The Digital out of the path 1A is sent to a Kemper, and I get the signal of the Kemper back via the S/PDIF input block on the path 2A. Problem is I want to hear what I'm doing while recording so I need the XLR output, but also record the Wet signal at the same time by sending the signal to USB 1/2 (or 3/4, ...). But if I set the output to Multi, it also sends the signal to the S/PDIF out and it creates a feedback loop. I know that I can first record the dry guitar then reamp later, but is there a way to have both the Wet sound sent to the XLR output and USB X/Y without sending it to the S/PDIF out? Thanks.
  5. I don't know what the hell @Robert is saying, but they are not.
  6. Since firmware 2.10, MIDI for the Helix Looper is broken (and it has broke my setup...) Indeed, we can't send two "looper MIDI messages" anymore. For example, we can't send two MIDI messages like "Looper:Stop" and then "Looper:Rec" anymore. Only the first message is taken into account, following messages are ignored. I guess it's an unexpected behavior resulting to the "When sending/receiving Looper MIDI CC messages through external devices, MIDI feedback could occur - FIXED". Note: it's really easy to reproduce this bug, just take any MIDI controller that can send several MIDI messages with a footswitch, and send messages like: [CC#61 0] [CC#60 127] : supposed to stop the loop playing and launch the rec of a new one, doesn't work. Only the stop command works. [CC#61 0] [CC#61 127] : supposed to stop the loop playing and play the loop again, doesn't work. Only the stop command works
  7. If it's the case with Helix (not saying it is, but if), the HUGE difference is Fractal warns about it and Fractal users know about that. That would indeed be inacceptable if upgrading Helix results in a change of tone without any warning from Line 6.
  8. Not at all. Conceptually maybe, tone wise, absolutely not :)
  9. There's a lot of effects on M5 not available on Helix. The two I miss the most: Lo-Res delay Growler For the MIDI thing, I don't use it like that, but in case it can work for you: I use instant commands on the Helix with a MIDI channel dedicated to the M5. The advantage is you can change it by snapshot, so each snapshot can call a different preset on the M5.
  10. Yeah, but isn't it strange that 3 switches are dead? I mean, 1 footswitch, it's a faulty one, but 3 faulty switches out of 12 seems really high, so I suspect it might not only be the switches :(
  11. (and yes, these problems should not appear on 1500$ boards, especially when the repair center can't give you a temp Helix while waiting or making an exchange!)
  12. I've got 3 switches that are doing the same (recognized as double presses 10% of the time), and I can't send the Helix in repair, because here in Europe, it will take at least several weeks, and I can't find a time where I don't need the Helix for a few weeks (rehearsal, gigs, studio, ...) Can you keep me posted if you got more infos on it? (software, hardware, if hardware how has it been repaired, ...) Thank you very much!
  13. Line 6 know this problem since May 18, when I submitted this bug and they acknowledged it. And yes, they still didn't resolve it after almost 4 months. It drives me mad that an annoying bug like this one take that long to be fixed. By the way, I think you're using MIDI over USB? In my experience with the Helix, MIDI via USB is far less stable than MIDI via MIDI cables, and that particular bug doesn't occur with MIDI cables in the MIDI In/Out ports. Also, if the Helix is connected to a computer to send MIDI signals via USB, and the computer is connected via an USB soundcard to the PA to launch samples, use virtual instruments, etc, if your electric system is not top notch, there will be a lot of noises. And those noises are disappearing when using MIDI cables instead of USB. (Also, on a not-so-far topic, I'm pretty pissed right now, because I found plenty of these bugs, and I lost a lot of time because of them, and now I've got two options: loose lot more time by trying to reproduce them, identify them, and then submitting them one by one to Line 6 - Line 6 that doesn't seem to be quick to fix them anyway, so why bother? -, or selling the Helix and try another setup. People at Helix team: you've got a great concept, you should not allow that many bugs - better test procedure? -, or at least, you should be really quick for fixing them. At this price point, part of your customer base are professional musicians, when you can't save a preset and restore it because when it's restored the snapshots are not restored correctly and it destroy your preset, and even in some cases make the Helix freeze, for frack's sake!)
×
×
  • Create New...