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

silverhead

Line 6 Expert
  • Posts

    12,047
  • Joined

  • Last visited

  • Days Won

    367

Everything posted by silverhead

  1. Something with your computer/browser I suspect. Have you tried the usual - restart browser/computer, clear cookies, clear cache......
  2. That's odd. I can access it (I answered in it earlier but I just tried again - no issue). And it's not a critical thread at all........
  3. I haven't tried that so can't say for sure, but I find a simpler setup to be very good. I connect an acoustic guitar directly to my L3t Channel 1 input, enabling the Acoustic Body modeling of the L3t. I find I get better results doing that than by going through an HD500 acoustic patch. I also have an electric guitar connected to an HD500 and then to the L3t either by L6 Link or by the Line inputs on the rear panel. I used to use the rear panel inputs because the L6 Link connection ignored the HD500 Master Volume. That may also be why people preferred to use the L2/3 Channel Input XLRs. But this was fixed in the most recent firmware release so I'm going to try the L6 Link again. So I simply switch guitars when I want acoustic vs. electric and everything is set up with no need for cabling adjustments or complex HD500 acoustic preset setup and tweaking - and the acoustic sound is better imho. You just have to be careful about feedback from the acoustic sound hole, especially while playing electric; a standard rubber sound-hole insert works great. While playing acoustic you just zero the volume on the electric. I suppose your suggested setup could be useful if you are using a JTV guitar for both acoustic and electric guitar modeling, but in that case the JTV already has acoustic body modeling built in. Having said that, in my experience it's not as good as my Martin D-28 connected to L3t Channel 1. Or at least my JTV/HD500 preset setup isn't skillful enough to beat that sound. :P
  4. You should expect them to continue to be supported (and perhaps, if we're lucky, further upgraded) for a long time yet, imho. They won't be discontinued very soon I don't think - they're only a couple of years old. Of course that's just my opinion - I have no inside info. Eventually there will be newer improved products. There always is with technology. But your current best-I've-ever-used sound won't change until and unless you find something better and switch to it.
  5. There's no way to adjust footswitch sensitivity with the device. However, I've heard of a home-made solution to a similar problem - unintentionally engaging the Looper. In that case, people have used ordinary rubber bands wrapped around the base of the switch to prevent it from engaging easily (or at all). You could experiment with this technique to see if you can get just the right amount of resistance for your purposes.
  6. Yes - either by renaming the Setlist or by drag/dropping individual HD500 presets into HD500x edit.
  7. Does Monkey recognize the HD500x when it is connected via USB? When connected, you should not have to choose it from the list.
  8. You need to use the line 6 License Manager to license your UX device and authorize your computer. You will find the License Manager in the Downloads section of this website. Also, your original UX2 purchase probably does not include a license for the latest version of Pod farm. You will be able to use a previous version, though. Line 6 Monkey will help you install the version you are licensed to use.
  9. Are your speakers/monitors connected to the UX1 outputs? They should be. Also turn off the Monitoring feature in Cubase. Configure Cubase to use the UX1 and its ASIO driver as the audio input/output device.
  10. I would keep using the Line 6 ASIO driver, not ASIO4ALL. In the Line 6 Audio-MIDI devices control panel, experiment with your buffer size settings to get rid of the Superior drummer stuttering.
  11. I think you'll find there's little or nothing to do. In my case, a brand new FBV MkII worked straight out of the box with my HD Pro. All default settings were appropriate. Make sure you update your HD Prox to the latest firmware; it fixes at least one previous bug in working with the FBV. The one thing you should do for sure is use HD500 Edit to back up all your setlists while you still have your HD500 device. Then, when you get your HD Prox run the patch converter to make your HD500 setlists directly compatible with the HD Prox. You will then bea able to use HD Prox Edit to restore your presets to the HD Prox device. The converter is here. Credit and thanks to community user jzab. http://www.jzab.de/content/pod-hd Have fun!
  12. No - the HD Prox sound quality is excellent imho. You could always try the HD Prox out as an interface, and if you think the quality is inferior then you could spend the extra $$. My guess is that you you will find you don't need another interface.
  13. It sounds like a loss of synchronicity between the Pod device and the Edit program. This happens when you use both the device and the editor to make changes, with unpredictable results. The only way to be sure you avoid these anomalies is to avoid touching the Pod HD device while using the Edit program. Yes - avoid touching it. Don't hit a footswitch to change presets or turn an FX on/off, don't use the SAVE button on the device. Make ALL changes using the editor. We could debate whether this is a bug or not, but it definitely happens and imho it is due to data loss/conflicts over the usb connection. Anytime a change is made on either device they try to stay in synch, and their ability to do so depends on the stability and speed of the usb connection. Very fast, nearly simultaneous changes on both devices will almost certainly cause confusion - especially if there is lots of other usb traffic going on with the computer. Once synchronicity is lost anything can happen. The reason I say it's arguably not a bug is that maintaining synchronicity under all circumstances would (I think) require both devices to be running real-time embedded operating systems. But only the Pod HD device is doing that. The computer is not a real-time OS and hence can not be guaranteed to keep up with the POD in terms of USB communications. So, whether a bug or not, the safest thing to do is avoid touching the device when the editor is running. The bug-or-not debate is academic. The behaviour is not likely to change.
  14. Yes, you are limited to one model selection in each FX block.
  15. 3- step process: Support tab at top of this page Contact technical support on next page, then Open support ticket.
  16. silverhead

    Wha Wha

    REALLY hard! Especially when newer, the toe switch is very stiff. You usually need to stand up on it (can't operate it sitting down) and use all your weight on the very toe/tip. Don't worry - you won't break it.
  17. The HD300 has no XLR Mic input. The XLR connections on the HD300 are for output. You cannot effectively use the HD300 for vocal processing. You could try connecting a dymanic mic to the 1/4" guitar input but I doubt that you'd get decent results.
  18. Here's some potentially helpful info for you....from the FAQs on the Model Packs pages. How do I return my purchased license? Each Line 6 license (except iLok) includes a 30-day money-back guarantee. You can log on to your Line 6 account, visit the Purchase History page, click the Details link for the order and click on "Return". You must have fully deauthorized all of your devices using License Manager before the return process can begin. After deauthorizing your devices and completing the return process, you can re-authorize your devices to use with any remaining licenses.
  19. Yes, you just bought something you can not use. Model packs are not compatible with the Pod HD series. Perhaps it's not too late to return it - I would call Line 6 at the number you find under the Contact Us link at the foot of this page.
  20. I suspect that there is at least one corrupt or incompatible preset on your HD device. This can happen sometimes with a firmware upgrade where the user chooses to keep existing presets. I agree that a firmware reinstallation could be helpful. But this time make a backup of your existing setlists/presets beforehand, and choose to replace existing presets during the installation process. Test the unit without restoring your presets. If the problem remains then your unit probably needs servicing. If the problem appears to have been resolved, restore your saved presets and be aware of which preset is being used if/when the problem reappears. Discard that preset and recreate it manually.
  21. The general procedure and button-pushing sequence is outlined in the manual in the sections on creating and saving tones. The overall approach is much the same as you would do with a series of analog pedals and guitar amps. Select your amp and make desired adjustments to the knobs. Then select desired FX boxes and place them in the order you want. Adjust their parameters as desired. You'll find the manual in the Product Manuals link under the Support tab at the top of this page.
  22. What happens when you power on while holding the left nav key down?
  23. I have seen very little commentary on the Tonecore kit since I joined this forum in 2009. I notice that the most recent Tonecore product update was in 2008. On the other hand, it was not among the products that were recently listed as no longer being supported as of Jan. 2014. So I guess the answer is that it is technically still supported, but I think it is no longer being actively developed. Personally, I would not expect a 64-bit update. I can't see a product that hasn't been update in 5 years suddenly getting development attention.
  24. I use this. https://www.globalfulfillment.net/gfsnet/line6/10Expand.aspx?ProductCode=98-030-0045
  25. Almost. I think the difference would be in the expected incoming signal level. The hd500 aux input is probably designed to accept instrument level while the HD prox line inputs would likely expect line level.
×
×
  • Create New...