Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About yrebrac

  • Rank
    Just Startin'

Profile Information

  • Registered Products
  1. As it says, are there any suggestions for virtual instruments that just output a basic DI guitar signal from MIDI that I can then amplify using the Helix native? I don't need the VSTi to have any in-built amplifiers. For quick demoing.
  2. Hmm, are you sure L6 link is even a different cable? I thought it was just referring to the line protocol being slightly modified. Pretty sure I'm just using an AES cable, controls everything perfectly, but digital out still works. I'd have to doublecheck on the current firmware though.
  3. This is something of an understatement! I get constant lockups on my HX Effects, and less frequent on my Helix when connecting to both through any USB hub (tried 4 different ones). This is definitely a bug that needs fixing.
  4. A hum might just be a ground loop. How are you powering the pedals?
  5. If you have still have the problem, after say dropping send by 3 and raising return by 3 to equalise the volume again, then the problem was not sending too much signal to the ODs, it will be something else. But you can isolate the problem to a particular spot in the chain in that way or by switching loops in and out. Try switching Loop1 to line level and you'll see what sending too much signal to your ODs sounds like!
  6. Hi there, You should be able to run the OD pedals in the HX Effects FX loop just fine, what are the exact problems you're having? You mentioned noise/levels/yada but more specifically? Anyway this cabling set up should work fine and give you a better overall solution, but you'll still need to get the levels right. The first thing to check is that your HX Effects FX loops is set to instrument level in the global settings. Even then you can sometimes overload the pedals, so try dropping the send level 3dB at a time until you get a good tone. Bad tone from sending the pedals too much signal should be pretty obvious. I think the level the of amp's FX loop depends on the amp, but set either to instrument or line in global settings, then perhaps adjust the return level down a bit if more headroom is required. Finally, the level of the output block. Just make sure it's the right signal level for the amp. Compare the amount of gain/level with just running the guitar straight into the amp to get this right. cheers, B
  7. I agree it's roughly 10dB difference between the models and the Flat modes, but it will depend on the amp as well. I have to adjust slightly for different helix presets
  8. But see my post above and show that it's not the helix that is badly adjusted - there's two points where a digital is converted to analgoue of vice versa. Someone with another digital cab would need to compare to be sure.
  9. Well to be accurate it's a much smaller pop but still a pop for me.
  10. Shall I repeat myself? I'm a bit shocked this information is not on product page, OR in the actual manual with the other tech specs.
  11. While a possibly useful post, I am not sure how this is related to clock signal getting to ground. An RF/EM inteference problem would be a different thing altogether.
  12. It's important to note this is NOT the same as the L6 Link carrying MIDI messages, it's probably a proprietary way of controlling the PC+. And no mention of MIDI above. What I suspect Line 6 are doing in 2.80 is creating a customised message format that will fit inside the existing AES frames. Unless AES already supports carrying MIDI messages (which a quick google suggests it doesn't) I would highly doubt Line6 would have the skills or the will to modify the AES protocol to carry MIDI all on their own. It's relatively simple though to send what looks like a regular AES message that carries PCM audio but has some special bit pattern that the PC+ will be programmed to recognise as a control message not an audio message. Or they may just use the existing 'sideband' capability with the protocol (there's already a way to send a low-fi audio e.g. like a push-to-talk message with the high-fi audio signal). Again this is roughly 1000 times easier than adding full MIDI to AES. Just a guess...
  13. Which style of input jack are you using on the powercab? For me the pop only happens on the analogue jacks.
  14. Good point, so the AES is not an option, but the XLR is still much more preferable being balanced - more resistant to noise and signal degradation.
  15. I fully agree with this, however I think there is a good point buried in the post. In helix we have a multi-output block that ties the output of the modeller to a single volume control knob, and then ties the output of the volume knob to the output jacks. The AES output jack simply takes the digital signal from the output of the volume knob and sends it. This signal has already been transposed by the volume knob (i.e. all 24-bit numbers adjusted up or down by the same amount). The XLR output takes the same digital signal but has to convert it to an analogue signal prior to sending it. There is no fixed way to convert the digital signals volume, however - it can be mapped to anything that conforms to the standard for that analogue signal. There's a lot of wiggle room there (but even at this point, there is no inherent "volume" in the signal. Both the analogue and the digital signal are only encoding differences in volume). So we now send both a digital and a converted analogue signal to the same device - a powercab in this example. The powercab does the reverse operation on the XLR signal and converts it to digital. Again it has a choice about how 'loud' it interprets the XLR signal in digital terms. It then does it's modelling thing and the modified signal is sent to the speaker for another round of analogue conversion in the form of moving a speaker. For the digital input it does nothing before modelling (assuming no input gain change), no conversion required. When the signal hits the speaker is the first time there's an inherent volume to the signal. Prior to this we were only encoding differences in volume. Now, all things being equal - all the volume settings on the helix, and all volume settings on the powercab - we SHOULD get roughly the same volume at the speaker whether we use the AES output or the XLR output on the Helix. Not for a technical reason but for a practical reason. But we don't. It doesn't make sense to have different signal transport methods produce wildly different results with all other things being equal. I agree with OP to an extent - I wouldn't expect the volumes to be totally matched but I wouldn't expect them to be totally different either (say by more than 6dB). So is this the fault of the helix or the powercab? It could be either, it's not possible to say as there are two places the signal is being converted where there's a somewhat arbitrary decision about how to translate a signal's volume from one form to another - before it's sent by the Helix and after it's received by the Powercab. But certainly it's fixable in the firmware of either. It's also totally fixable by the user. By adjusting the 'Digital Output Level' setting up or down to match to the level of Helix-XLR + Powercab-XLR conversion. Unlike all other volume controls, this setting will ONLY affect the AES output. I think this is the wrong way of thinking about however, I view this setting more as on offset for the XLR output, where there is some interpretation of volume going on. In short, I agree with OP that there's a questionable aspect of the implementation, but not that it needs to be fixed by Line 6. You figure out the difference once, you adjust the setting, then you forget about it. Now you can switch between digital and analogue outputs to your heart's content.
  • Create New...