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

silverhead

Line 6 Expert
  • Posts

    12,445
  • Joined

  • Last visited

  • Days Won

    415

Everything posted by silverhead

  1. My studio needs and use are very similar to yours, and the Pod Pro works well for me. The vocals sound fine (from a purely technical perspective 😜). I have prepared a couple of presets to support simultaneous wet & dry recording as well as simultaneous guitar & vocal recording. If you want to try them out search Customtone under my username. They were prepared on an HD500 but can easily be converted to the Pro. Note that recording a dry signal using the Pod as the audio interface is not truly dry due to the A/D conversion at the inputs. The HD Pro does provide a truly dry output tapped from the guitar input, and sends it in analog form to the Dry Output on the rear panel. However, you would need a separate interface to get that into your DAW, and the conversion needs to happen somewhere. I have not bothered with that; the dry signal using my preset works fine for me.
  2. One reason to install both would be to ensure full transferability and compatibility of tones between the X3 and Pod Farm. With PF v1 the tones are fully compatible in both directions. With PFv2.5 you can upload X3 tones into PF but you can't necessarily download PF tones into the X3. That's because there were improvements in PFv2.5 (e.g. additional routing flexibility) that render tones taking advantage of those improvements incompatible with the X3. So if you record songs using PF and want to be able to reproduce the tones exactly when playing live with the X3, it might be worthwhile to use v1.
  3. Are you applying any processing to the sound of the GS Mini in Garageband? If so, what processing are you using? How are you monitoring the sound? You may be experiencing latency caused by the time it takes for your computer to do the audio signal processing .
  4. I suggest you open a support ticket to work directly with Line 6 tech support on this.
  5. I'm not aware of any issue. Are you getting any error message? If so, what is it? Check your usb connection. Try different ports and avoid using any usb hub.
  6. The HD Pro MIDI is not a full midi interface. It won't be recognized as a MIDI device by your DAW. You can't record, for instance, midi keyboard sequences or drum triggers. It is only used for midi program change and CC controller info; no key on/off midi events are recognized by the Pod products.
  7. There has been no mention of that in any of the marketing material or announcements so far.
  8. Yes, that setup will work and will replace the other equipment as you describe. My simplest studio setup is exactly that - HD Pro to studio monitors and to DAW, recording electric and acoustic guitars, bass, and vocals. If you want to add midi at some point you will need a midi interface.
  9. You will need a foot controller like the FBV MKii to replace the HD500 controllers if you want to easily change things while playing live. Other than that the HD ProX offers more i/o for studio use.
  10. Right - no point in buying one. I just thought you might have a standard XLR cable lying around.
  11. silverhead

    HD500X

    I think it depends on the preset. If you are going for a very clean acoustic or vocal sound your preset may have no amp and minimal FX. You might need the boost in such cases.
  12. silverhead

    HD500X

    That's right. Good suggestion. It appears in the Control Panel item called Line 6 Audio - MIDI Devices.
  13. silverhead

    HD500X

    I believe that Audacity by default uses a non-compliant ASIO driver called ASIO4ALL. It is known to sometimes cause problems with devices like the PodHD that depend on a fully compliant driver. Make sure you reset Audacity so that you are using the Line6 ASIO driver.
  14. If you are talking about the L6 Link cable, you can try using a standard XLR microphone cable while you wait for the LIne 6 cable to arrive.
  15. Reaper definitely does have a loop feature. Select the dry track and section that you want to loop, engage the loop feature, apply the Pod Farm VST to the track, and tweak as playback occurs.
  16. Sounds like you are solo so there probably aren't many inputs. Try using the Fader view in Performance mode and individually panning the channels. Using this view you can see and pan all channels in the same page.
  17. You can save 512 presets in the HD500X, organized into 8 setlists of 64 presets, each in turn organized into 16 banks of 4 presets. Within a setlist the banks are numbered 1 - 16, with 4 presets in each bank, A through D. All of them are available for recall using FS5 - FS8 as described above, which will recall presets A through D respectively in the currently active bank of presets.
  18. I'm not sure exactly what you mean. The Pod does store alternate Variax (JTV) tuning and model with each preset. So does the Firehawk. Neither supports changing these things without changing presets (is that what you mean by 'channel'?). I don't think there's any difference between the Pod and the Firehawk in this respect, unless I misunderstand you.
  19. ... and periodically store a backup offsite.........anytime you have something you REALLY don't want to lose.
  20. Yes, the same update will be available for the HD500 as well, but it will come a little later than the HD500X update.
  21. Yes, it will be in Hz and db. Someone from Line 6 (forget exactly who) confirmed that in another thread within the last couple of days.
  22. Fyi.... They're not my dates. I am not a Line 6 employee. And forget the 2 months. I was only saying that IF the forecast date had been 2Q that means end of June. And if you understand that it's an estimated date... Well, that's what it means. Subject to change. Relax.
  23. First, make sure you have the latest firmware update on your Pod HD 500(x) or Pro(x). Then you must manually change the L2m speaker mode (that's the only setting that can be saved) to the desired setting. Then manually SAVE the preset on the Pod HD device.
  24. Note that it is the retailer providing these dates to the public, not Line 6. The retailer wants to be prepared to receive the product, so they need, and Line 6 provides, an estimated shipping date. But that is intended for retailer planning purposes only. If they then provide that date to the public as if it were an official release date, it is they who are disappointing you.
  25. If a firmware reinstall did not fix the problem it is likely a hardware issue. Since you've only had it a short time, take it back for replacement. Or if you bought it used take it to an authorized Line 6 service centre for repair.
×
×
  • Create New...