Pod Hd300 And Audio Interface

[the29band]

I am recording my guitar using just the hd300 plugged into my computer. After recording i like to listen using my monitors which are plugged into my audio interface. So I have to keep switching between the hd300 and the audio interface. I know I can connect the hd300 to the audio interface using xlr or 1/4" cable and record via the interface. However, if i do that i cannot access the pod edit software. Is there a way around this. I create/modify presets on the edit so i like to have access to that. I guess the other option is to have the hd300 connected to a second computer that can be used to modify just the presets but it's still a pain.

 

Any suggestions? Thanks!

[bjnette]

You could just connect your monitors to the 300 and select it in your DAW as well. Pretty much making the interface obsolete.

 

Recording several tracks at once the next best would be a stereo selector device. Get a good one, they can be gotten from hifi stores but basically you hook your monitors to it.

 

The 300 and the interface to their own stereo pair and its just a matter of sliding the switch. Better than using a patch bay to do it.

[the29band]

You could just connect your monitors to the 300 and select it in your DAW as well. Pretty much making the interface obsolete.

 

Recording several tracks at once the next best would be a stereo selector device. Get a good one, they can be gotten from hifi stores but basically you hook your monitors to it.

 

The 300 and the interface to their own stereo pair and its just a matter of sliding the switch. Better than using a patch bay to do it.

Thank you for your reply. So even if I get the selector selector I'd still have to switch the USB cable on the PC to select the interface vs hd390, right? Or is there a way to bypass that as well?

[still_fiddlin]

Most DAW software allows you to specify the inputs and outputs as different devices.  For instance, on Audacity, I can set my input to my HD 400, and the output to my audio interface.

 

Now, I cannot *monitor* the recording with the interface (well, I could probably get a feed back, but there'd be latency), but when I play the recorded track back, it goes to the interface and out to the powered monitors.

 

This doesn't work well for recording multiple tracks. Then, you'll want to specify the POD as the output device so you can hear the previous tracks while recording a new one.  But even then, it's just a "preferences" setting in your DAW, and not cable switching or anything, unless I'm missing your point (always possible).

[silverhead]

Most DAW software allows you to specify the inputs and outputs as different devices.  For instance, on Audacity, I can set my input to my HD 400, and the output to my audio interface.

.....

This is a property of the audio driver being used rather than the DAW. Audacity uses (by default) a driver called ASIO4ALL, and this driver does, as you say, allow you to specify different input and output devices. Unfortunately this is not compatible with true ASIO driver implementation; true ASIO does not permit this - it requires that the same device is both the input and output device. Hence, using ASIO4ALL with devices that faithfully implement the ASIO protocol (like all Line 6 ASIO devices) can lead to problems. Many DAW-related problems reported in these forums have been traced to the use of ASIO4ALL, and its use is not supported by Line 6.

 

The only ASIO driver that should be used with Line 6 devices is the device driver provided by Line 6.

[still_fiddlin]

Interesting.  Why does my POD HD 400 show the Line 6 driver in Device Manager?  I cannot find another ASIO driver in the Windows\INF directory.  So, installing Audacity installed this ASIO4ALL driver at the same time?  These are the only drivers I can find with "ASIO" in their INF file:

ASIO POD HD400 - 09/07/2010,4.1.1.7

ASIO POD HD400 - 04/28/2011,4.2.4.4

ASIO POD HD400 - 06/21/2011,4.2.4.9

ASIO POD HD400 - 06/05/2012,4.2.5.7

 

I didn't see another audio device active at the time Audacity was recording from the POD, BTW. (Image in the HD 300 problem thread.)

 

I'll be happy to remove ASIO4ALL and try again, if you can direct me to it.  In the meantime, I'll go see how this works on OSX...

[silverhead]

I believe ASIO4ALL would have been installed along with Audacity, but I have never used Audacity so can't confirm that, and I don't know where it would have been installed. My knowledge in this area is based purely on driver/DAW-related problems reported here, and their diagnosis/solution.

 

What I can say is that if Audacity is using the HD400 driver then there should be no ASIO4ALL-related problems, since it is not in use. However, if Audacity is showing different input and output devices then it is in fact using ASIO4ALL (or some other non-ASIO compatible driver). If the HD400 driver is being used there is no possibility of assigning different input/output devices.

 

Also, many users have reported that they are successfully using ASIO4ALL with their Line 6 device. Not everyone has problems with it, but those that do will not get support from Line 6, other than to say 'use the Line 6 driver, not ASIO4ALL'.