Please ensure Javascript is enabled for purposes of website accessibility Jump to content

phil_m

Line 6 Expert
  • Posts

    9,249
  • Joined

  • Last visited

  • Days Won

    175

Everything posted by phil_m

  1. This already exists, more or less. The Level parameter in the Output Block gives you this ability.
  2. phil_m

    Amp out

    So do you still have the amp model on? That’s still not going to be ideal going into the Princeton’s input. You’re best bet with that setup would probably be using the PG for effects only and worrying about the amp modeling.
  3. Open up a support ticket with Line 6 customer service. They should be able to solve it pretty quickly. Is your Helix new or used?
  4. It sounds like you’re just clipping whatever input you’re plugging into. What are you connected to?
  5. No, you can use one effect at a time (plus reverb).
  6. It’s a line level signal. Most mixers should be able to accept it. The key is to not have any gain added to the channel at the mixer.
  7. Hmm... If you found the screws of the correct length and thread pitch and gauge, I guess you could attach the pedal with screws. But I wouldn't recommend that. The bottom of the Stomp XL is flat, so it's very easy to attach it to a board with the typical methods - velcro or Dual Lock.
  8. The Helix is your audio device, so you need speakers connected directly to the Helix to hear the output. You won't hear audio through the Mac's speakers.
  9. Yes, you wouldn't want to have the Stomp sending its own MIDI clock signal if it's already passing the signal from the other pedal through.
  10. Yes - deauthorize and reauthorize your computer. The limit on authorizations can be extended if you run into issues with it. It’s an anti-piracy tool, not something that’s meant to limit how many time legit users can install the software.
  11. As long as you’ve has your Stomp for 180 days or more, you can keep Native.
  12. What does the sound coming out of the actual speaker sound like? Sounds like you may be clipping or something, but it’s hard to tell.
  13. I don’t think there’s any actual difference in the terms “preset” and “patch” any more. People basically use them interchangeably now.
  14. You can’t change the delay time from a note value to a millisecond value per snapshot. That’s a preset setting. You can change the note value per snapshot if you want, though. You can also change the tempo per snapshot if you want.
  15. The Helix uses component level modeling as well. The modeling teams for Line 6 and the Yamaha products are really two separate things. I believe most of the Yamaha development takes place in Japan with some in Europe. Pretty much all of the Line 6 engineering team is in California. There is a small contingent in Vancouver as well. But the way that Yamaha handles it subsidiaries is a pretty hands-off manner. There's been some cross-pollination, but that's kind of the exception, not the rule. I'd also add, though, that a lot of the dynamic perception you're talking about comes down to the playback system, perhaps even more than the modeling itself. So comparing a modeling amp to a standalone modeler isn't necessarily apples to apples.
  16. Not sure why you're getting that message, but M1 support was added in the 3.15 update. It could be the installer runs on Rosetta. I do believe HX Edit needs Rosetta to run, though.
  17. No. There are few products on the market that have attempted to allow that sort of thing, but they are pretty limited. It’s not a simple thing to port a VST plug-in into a piece of hardware.
  18. It’s not really that simple. It means a good bit of redesign, and it means updating the DSP tables for an updated device. It would add a good bit of complication to preset sharing and the Marketplace, as it’s possible that presets created on a “turbo” Helix or whatever might not work on the original… Anyway, I don’t think Line 6 has any plans for these sorts of incremental upgrades. Also, consider that Line 6 just gave everyone what essentially is a free DSP upgrade with the way the new cab and IR blocks are processed in the 3.50 update. The new single cab block uses about 10% of the DSP of what the Legacy cab block used, and the same sort of DSP savings goes for IRS as well.
  19. I am doubtful that there's a meaningful sound difference. Even if you have IRs that were actually shot at 96kHz (which is a big if, as it's very possible that IR makers work at 48kHz and upsample), what that means practical terms is you're increasing the bandwidth to include sonic information up to 48kHz. There's going to be very little sonic information from a guitar speaker above 10KHz, let alone above 20kHz... IR processing is a linear function, so things like improved aliasing performance, which can benefit from higher sampling rates, don't come into play.
  20. Native has been compatible with the M1 processors for a long time now.
  21. This is kind of a confusing post... Monkey is the updater for the HD Pro. I'm confused as to whether you're actually able to run Monkey or not, because in your second sentence you talk about downloading the software via Monkey, but then later on you say you can't find Monkey... But the long and short of it is - just run Monkey. It will guide you through everything you need to do.
  22. It looks like you have the old factory presets still. In order to get the new ones, you need to de-select the FACTORY1 setlist from the backup when doing the Restore from Backup part of the update process (this would be after you do the Factory Reset). That way the new presets in that setlist will remain while all the other presets in your other setlist will get overwritten with whatever was on your your unit prior to updating.
×
×
  • Create New...