Jump to content

rwandering

Members
  • Posts

    21
  • Joined

  • Last visited

Everything posted by rwandering

  1. Maybe this should be a sticky . . . I think the confusion stems from the fact that the PC never displays the speaker name. It displays the name of the preset which happens to have the same name as the speakers for the default presets. When you change the speaker on the Helix, you are changing the currently selected preset, but not its name.
  2. You probably aren't doing anything wrong. I posted about a related issue with USB, and regardless of the debate that came out of it, some levels coming in to the PowerCab, it is impossible to both get the recommended "yellow light" and not overload the USB output. This was clearly the case comparing XLR to USB where USB was much hotter. In my reading about other people's issues, this appears to be the case that XLR too can overload (as you are seeing). I view this as a design flaw, with a solution being that Line6 should add some controls to independently set the volume of the XLR/USB outputs. Of course this has to be before they overload! I would head over to IdeaScale. I added an item there, and I think there are many others too, this one I think specifically relates to your issue. https://line6.ideascale.com/a/dtd/Level-control-AFTER-the-virtual-microfon-for-XLR-Out-FOH/961037-23508#idea-tab-comments
  3. I just checked my LT with 3.10 and my PC 112+ and the L6 link is working as I expect.
  4. I'm sure interested in hearing where this goes . . . what did you do? Does it have the 2.0 speaker set or something else?
  5. Glad to hear it. I doubt they will. I can think of several "fixes", but not sure any of them really makes sense: Add the ability to set the PC preset from the Helix. The current capability is to have control over all parameters that would go into a preset, but not to set the preset itself. Echo the Helix preset name on the PC Instead of displaying the last preset on the PC with <edit>, replace that with static text (e.g., "Helix" or "From Helix"). Other ideas?
  6. I just tested it on mine and it worked as I expected. The preset name doesn't change (but says "edited"). The color does change. If literally nothing is changing, then I would suspect your cable.
  7. You certainly can do what you want with the AES/BEU cable. The only thing a little confusing about it is that the Helix doesn't switch different presets on the PC+. What it does instead is it allows you to select all of the PC+ settings from the Helix preset. This can be a little confusing, because the display on the PC+ won't be up to date. Note that you did need MIDI for this before AES/BEU was fully supported in firmware.
  8. And I didn't think you were. My reflective use of "psychic powers" echoed yours, as a prelude to my explanation. I certainly did not mean to offend.
  9. My first inference turned out to be correct. But if I'd looked at the notes, I wouldn't have had to guess. My bad. I stand by the second claim as being an implication (and not due to my limited psychic powers). If the 3.10 Helix Firmware makes no changes that a user would expect to be reflected in HX Edit, then there would be no urgency to update HX Edit to 3.01 before the 3.10 firmware is released. It would still be desirable for Line6 to get people to update to 3.01, but it wouldn't be urgent. Now, the urgency in the original post may be misstated, but I think the implication is there. And a question for the Helix historians that I don't know the answer to: does a jump to a .X version number ever come without a new model?
  10. I'm guessing that the "radically improved process" is that it forces you to update HX Edit to the version matching the firmware. That would save a lot of frustration for people -- and I'm sure reduce the number of support inquiries around the "I updated my firmware but I don't see any changes (in HX Edit)". If I'm right then the urgency of this update implies that 3.10 has new models or other changes that will be reflected in the future HX Edit.
  11. I downloaded them and compared them. They are identical. I'm not an expert on the WAVE file format, but it looks to me like all zeroes. So, unity.
  12. Thanks for sharing your impressions. Yeah, I can see the desire for a standby switch particularly considering it isn't "instant on" like a conventional solid state amp. Personally I stopped caring about standby switches when I started using a muting tuner, but of course that doesn't mute the cabinet. That said, if you generally do have your helix knob on max, zeroing it gets you the same result without having to touch the cab's volume. I think that is what rd2rk is suggesting.
  13. Actually no, I never said I wanted the volume knob on the cabinet to control the output of XLR/USB.
  14. The entire premise of my issue is that when the "signal LED" is yellow, the USB can be overloaded. Reducing the "Level" will impact the USB output, but this also lowers the signal into the speakers. It should be possible to independently control these. The fact that you can do this to your liking doesn't mean it isn't a design flaw. My previous acquiescence on this point was based on my being new to the Powercab. I'm certainly not new to DAWs, modelling, nor troubleshooting. I do not dispute your ability to fine tune the PC to your liking. I appreciate your help here, but you seem intent on disputing my desire to have the flexibility to do so to mine. It doesn't do what I think it should, and its your right to say it shouldn't do it but I can't for the life of me understand the rationale for that.
  15. So, Line6 support confirmed my original hypothesis (but aren't calling it a bug): Note that the support person said "turn it down within your DAW", but its too late for that . . . its overloading within the PC. In other words, the levels are all pre-processing. There already is an ideascale item on this: https://line6.ideascale.com/a/dtd/Level-control-AFTER-the-virtual-microfon-for-XLR-Out-FOH/961037-23508#idea-tab-comments Please everybody vote for it! It has hardly any votes! Thanks, Robert
  16. No problem, I can take fierce conversation! So clearly I was being dense here, but I get it now. The PC editor calls it "Level" and the manual calls it "Volume". My assumption -- and yes, I know what happens when I assume -- is that "Level" modified the signal coming in, but RTFM makes it clearer that this is output. I'd love a signal flow diagram for the PC. I expect this Level parameter impacts both XLR and USB output. That said, I would still expect similar levels between the two. Thanks for your help -- I appreciate your efforts!
  17. Thanks for putting this effort into this. Track 4 certainly looks overloaded, but assuming there is a lot of compression in the Revv Purple, maybe not. It does seem that I need to turn down the input into the Powercab. I'll play with it some more. Thanks again!
  18. Thanks for your help with this. My settings are the same as yours except for one major difference -- I'm trying this with a speaker model, not Flat. When I go Flat, I don't redline. There is no monitoring going back to the PC. I've captured the waveforms below. This is kind of meaningless in that I don't expect the XLR out and USB to be at the same levels, but the XLR output is usable, the USB isn't. Does using the Vintage speaker model make a difference? This is how it is set for me (this is just the default). And with full disclosure, I am increasing the level from the Helix to the PC. This is so I get some of the yellow LED when strumming the guitar. From what I've read that's what you need to do to get the best sound out of the PC. This was all just intended as a test, but when I'm doing recording while playing through the PC, I'd rather record that emulation than use a separate speaker cab from the Helix. Of course, different blocks and gain staging will of course impact the desirable level to the PC. Assuming you can reproduce this with a speaker model -- still a question of course -- my conclusion is that the PC isn't designed to sound its best *and* record through USB at the same time. Perhaps if I turn down the levels to the PC I'll get less desirable sound out of it but get a good USB level (assuming the speaker and mic modeling are linear). I'll have to test lowering the volume, but my hope was that I could follow the advice on the yellow LED and record. If you have other thoughts about this, they are much appreciated. Thanks again!
  19. Thanks for the suggestions. Playing with the Input 2 mode only makes a difference this if I set it to USB, in which case I get no signal. The USB Mode of Normal/Processed makes no difference. I guess the question is: should I expect the USB output to be usable if I follow the guidance on the input signal (i.e., targeting that the LED gets to yellow)? I just did a simple test comparing the XLR output (using line level and no gain in my interface) to the USB output (with the USB in Processed mode). At -12 DB on the XLR output I get a 0 DB on the USB. At this point, I'm guessing this is intended behavior, but I can't for the life of me figure out why it would be desirable.
  20. I picked up a used PC112+ the other day and have been playing around with it. This plus the Helix creates a crazy number of permutations! I tried to record the USB output to compare the speaker emulation out of the cabinet with the emulated output. The weird thing is that the USB output is redlining. Where I am only getting an occasionally yellow LED on the PC, I am getting frequent digital clipping from the USB. I have tried both normal and processed output, no difference. I then connected an XLR cable from the PC to my audio interface (and set for mic level output), and I'm seeing a more moderate signal. This is the firmware 2.00.1, but it seems like a firmware defect to me. Anybody else have this experience? Am I doing something wrong (I hope)?
×
×
  • Create New...