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

phil_m

Line 6 Expert
  • Posts

    9,303
  • Joined

  • Last visited

  • Days Won

    180

Everything posted by phil_m

  1. phil_m

    7/8 expansion

    You mean like physically attach the switch to the POD Go? I don’t know... You could possibly mount it on the space above the expression pedal, but I don’t know if that would get in the way or not.
  2. There are some delay models that have lower maximum delays times. The HX BBD delays, for instance, max out at 400ms, I believe. So even you tap longer time, the maximum delay time will be set to the next smallest note division that works with the tempo you tapped in. The longest tempo you can tap in is 40 BPM, so if you have the delay time set to 1/4 notes, that translates to 1.5 seconds. If you want longer than that, you’d need to select a longer note subdivision.
  3. The Mic Distance parameter is essentially the Z axis. The Early Reflections parameter is kind of the equivalent of using an IR with more samples. It’s not really related to the mic placement.
  4. The Helix doesn’t have that feature. The cab and mic models in the POD Go are exactly the same as they are in Helix. Regarding the OP, you wouldn’t necessarily need 3 axes... Since a speaker is symmetrical, you would really only need one axis parallel to the speaker face to go along with the current mic distance parameter that’s currently there.
  5. phil_m

    Mac Catalina OS

    Yeah, well, Apple doesn't control the world... There's tons of 32-bit software out there still in all sorts of applications. 64-bit is desirable for sure, but Apple isn't pushing innovation. It's just inconveniencing its users. As far as the Line 6 software that's 32-bit, I don't expect any of it to be updated that hasn't been. I suspect that the SKUs that depend on Line 6 Monkey will made to be compatible with Line 6 Updater.
  6. You just need to increase the level of your preset in the Helix. The easiest way is by adjusting the Level parameter at the Output Block. You could also raise the Channel Volume parameter in the amp block. I'd say, though, that looking at those waveforms, you're probably recording a little too hot with the Firehawk. It's looks like your peaking pretty close to 0.0dB there. Really, for 24-bit recording, peaking between -12dB and -6dB, or even a little lower, is fine. You don't gain anything by recording hot. It just makes it more difficult to mix and use plug-ins down the road. The USB out level is the raw level from the preset itself in Helix. There's no other level adjustment elsewhere. If there were, that could actually make things trickier because it means having another level to worry about.
  7. Given that you're able to swap the amps and the same amp is still the one having issues, it seems pretty clear that it's something with that amp, although, what it is, I don't know. When you say sound is cutting out, how much is it? Can it compensated for by adjusting the Send level in the Helix's FX Loop for that amp? What happens if you disconnect the cables from Amp#2's FX loop? Is it still getting a good signal from the Helix's Send?
  8. Are you monitoring the recorded tones through the same speakers that you used while recording them? The playback should be identical to what you were hearing while playing. One thing that can affect that is the Global EQ, though. The Global EQ doesn’t affect the USB out, so if you have it on, it would affect the sound coming from your speakers, but not the recording.
  9. You only need to use the single stereo FX Loop 1/2 block in your preset. You don’t need a separate Send block. As far as connections it would be: Helix Send 1 —> DD-200 Left In Helix Send 2 —> DD-200 Right In DD-200 Out Left —> Helix Return 1 DD-200 Out Right —> Helix Return 2 All the paths in the Helix are stereo, but in order for stereo separation to be maintained, any blocks, if any, you use after the FX Loop block would need to be stereo. You
  10. That might be a hardware test mode. I'm pretty sure there isn't a calibration page, as the pedal should auto-calibrate whenever you power cycle.
  11. There’s no such function, no. What sort of issue are you having?
  12. Using Updater is probably your best bet. You can still install it even though Apple gives you that warning. If you right click on the icon wherever it’s saved, you can choose to run it.
  13. Well, you may want one a solution, but there isn’t one... The best you can do is try to recreate your XT tones with the amps and effects on the POD Go. There isn’t any compatibility between the two platforms.
  14. It works how I said it works. You have to assign parameters to the Snapshot Controller to have their values changed per snapshot. Once a parameter is assigned to the Snapshot Controller, you’ll see the value in white brackets on the screen. So you only have to make that assignment once. Once it’s made, editing the values isn’t any different than any other parameter. It’s just now the value is saved per snapshot. This is how it works across all the Helix/HX devices. It really becomes more evident why it’s necessary when you’re dealing with the Helix, as there’s a potential for up to 32 blocks in a preset. It would slow preset changing time down to unacceptably long if all those values had to be saved and recalled for 8 snapshots. You’re taking hundreds of parameters in that case. With the POD Go, there are fewer blocks, so I can see why someone might assume that it works differently... There would be a downside to having all parameter automatically controlled by snapshots, though. That would be in the case if you wanted to adjust a parameter for the entire preset and not just the snapshot. That would mean you’d have to change it in every snapshot. It would actually be more time consuming, considering you typically only change a handful of parameters in a snapshot per snapshot basis.
  15. No, it's a Windows setting. Right click on this little speaker icon, and then follow the instructions I listed above.
  16. They are exactly the same except for some minor aesthetic differences (the MKII has different knobs, for instance). For all intents and purposes, doing the firmware update turns an MKI into a MKII.
  17. If you've tried again with HX Edit and are still having problems, try downloading and installing Line 6 Updater and running the update with that.
  18. Click on the speaker icon in the lower left hand corner of your screen, and select "Open Sound Settings". There you should see a pulldown menu that says "Choose your output device". You can select your other interface.
  19. Perhaps try downgrading to the version of HX Edit you were using and creating a backup that way first. If you're able to create a backup with that version of HX Edit, you could do a factory reset before doing the update. When you say Line 6 Updater doesn't work, what are you seeing with that?
  20. Many amp tone controls are actually rather limited in their range in real life, so it might just be that. Sometimes they’re interactive with other controls. Like they might give you more pronounced results at higher gain settings or something like that. If you’re wanting to make more drastic changes, you’d probably want to use the EQ block.
  21. I have no problem with people asking questions... It was hard to actually discern the questions you were actually asking between the rants, though. I'm not a Line 6 employee, so I have no power to say what changes and what doesn't. But I wouldn't expect fundamental changes to the basic UI functions at this stage in the game. I'd just say though, that, I don't know how well I'd react to your "suggestions" when they're wrapped in what are really insults. Anyway, I think people here are totally willing to answer questions. Fire away...
  22. I probably shouldn’t bother responding to you because you seem to only want to complain... With the amount of energy you’ve spent writing these diatribes and posting memes, you probably could’ve figured this out a while ago. You can complain about the basic UI decisions all you want, but the reality is they aren’t changing them at this point in the game. The POD Go’s interface is essentially the same as the Helix interface, so tons of people are familiar and used to it by now. Rather than actually looking at it, you seem to be projecting your expectations on it. It’s really not hard to use. It’s the easiest interface for any multi-FX device I’ve ever used, that’s for sure.
  23. Hmmm... Well, when you have the Trails parameter turned on in the FX Loop, the Return stays active even when you bypass the loop. But that doesn't explain why it would go away when you turn the loop on. I'm not sure what's happening there. Any chance you could put a screenshot of your preset up?
  24. I don't usually do videos, but I figured what the heck... It's what the kids want nowadays... This is a Litigator preset I made. I just was trying to make something relatively versatile. I wanted to see what kind of range of sounds I could get out of a single Vintage Delay block, for one, and I was pretty happy with this. There's basically four snapshots - Clean, Crunch (using the Legacy Classic Distortion, or RAT), Delay 1 and Delay 2. Oh, and my POD Go is on the floor here even though you see the Helix Rack in the background... This is all recorded via the PG's USB out. I had a few people ask me for the preset, and it can be found here: https://line6.com/customtone/tone/5107626/ I didn't think about it when I made the video, but I used an Ownhammer IR for this preset originally. I replaced the Ownhammer IR with the Dr Z 212 in this preset so I could share. I think I was able to get them sounding pretty darn close.
  25. You'll need to open up a support ticket: https://line6.com/support/tickets/add.html If you activate the tuner, does it respond to the guitar plugged into the input?
×
×
  • Create New...