grdGo33

On 6/2/2025 at 5:26 PM, Eggzin said:

Anybody have any thoughts?

Did you check the guide I posted?  Guessing you don't have the same options available he does?

For channel 3/4 should be normal, as you likely don't have a stereo guitar.

On 6/1/2025 at 11:25 AM, Eggzin said:

Thanks for your suggestion.  From recent reading on the net, Pod Go is supposed to contain the drivers that Reaper needs to see the four channels.  I can try a search for Reaper usb drivers, but I've been down so many rabbit holes so far...   :>)

What do you mean USB drivers?  Pretty sure you mean Asio drivers instead.

There was some hallucination in that AI response as is appears that Reaper does not have its own native Asio drivers:

Quote

Reaper does not come with native ASIO drivers built into the software itself. Instead, it relies on ASIO drivers provided by your audio hardware manufacturer or third-party ASIO drivers like ASIO4ALL for generic soundcards.

 

Explanation:

•  ASIO Drivers Are Hardware-Specific: Most professional audio interfaces come with their own dedicated ASIO drivers developed by the hardware manufacturer. These native ASIO drivers are optimized for low latency and stable performance with that specific device. If you have such an interface, you should use its native ASIO driver in Reaper for the best experience2.
• Reaper Does Not Include Its Own ASIO Driver: Reaper does not include a built-in ASIO driver. If your audio device does not have a native ASIO driver, you can use ASIO4ALL, which is a generic ASIO "wrapper" that enables ASIO functionality on standard Windows soundcards by bypassing some of the Windows audio layers123.
•  ASIO4ALL as a Workaround: ASIO4ALL is commonly recommended for users who do not have an audio interface with native ASIO drivers. It is a free, third-party driver that allows Reaper to use ASIO on devices that only have standard Windows drivers. However, it is not a true native ASIO driver but a compatibility layer128.
• Alternatives to ASIO: On Windows, Reaper also supports other audio systems like WASAPI and DirectSound. WASAPI has improved over the years and can sometimes outperform ASIO4ALL in latency and stability, but ASIO remains the preferred choice for audio production due to its low latency12.

 

Summary

• Reaper itself does not come with native ASIO drivers.
• Use native ASIO drivers provided by your audio interface manufacturer if available.
• If no native ASIO driver is available, use ASIO4ALL as a generic ASIO driver.
• WASAPI is an alternative audio system supported by Reaper on Windows.

This means to use ASIO in Reaper, you need either a hardware device with its own ASIO driver or install ASIO4ALL for generic devices

 

The important part I thought for the previous AI answer was this: "However, Audacity is limited by its lack of native ASIO driver support, which is required to access more than two channels from many audio interfaces, including the Pod Go. As a result, in Audacity, you will generally only see and be able to record two channels at a time—either a stereo mix or a single mono channel—rather than four independent tracks".  

But it turns out the native Reaper ASIO drivers were AI hallucinations, likely not an Asio driver issues.

Just found this guide, watching it; might just be a settings/configuration issue, see here!  (make sure you select the same channel # as he does, and while AI said that it wouldn't work for Audacity, maybe should work too with the right channels selected?  No reasons it shouldn't if it isn't a driver issue...!)

On 5/28/2025 at 3:46 PM, Eggzin said:

The first is that, although Audacity shows the PG in both the recording device dropdown menu as well as the output device dropdown menu and I've successfully recorded to a track, I don't see anywhere where I can specify which of the 4 USB channels of the PG I can route to either the input or output in Audacity depending on what I want.

Quote

Reaper still didn't recognize all PG's channels.  Since then, I've downloaded and installed two separate drivers from the Line 6 website to no avail.  I'm pulling my hair out...

AI answer, (which could or could not be hallucinated...)

Quote

When using the Line 6 Pod Go as an audio interface with Audacity, you may notice that while the Pod Go technically supports four USB audio channels—two for the processed (amp/effects) signal and two for the unprocessed (dry DI) guitar signal—Audacity itself will typically only display and allow selection of stereo (two-channel) recording, not four discrete channels

.

Most DAWs (like Reaper or Cubase) can access all four channels, letting you record both the processed and DI signals separately

. However, Audacity is limited by its lack of native ASIO driver support, which is required to access more than two channels from many audio interfaces, including the Pod Go. As a result, in Audacity, you will generally only see and be able to record two channels at a time—either a stereo mix or a single mono channel—rather than four independent tracks

Summary:

• Pod Go provides four USB audio channels (2 processed, 2 DI)

• Audacity will usually only show two channels (stereo or mono), not four, due to driver limitations

• To record all four channels simultaneously, use a DAW with full ASIO support (like Reaper, Cubase, etc.), not Audacity

If you need to capture both the processed and DI signals from the Pod Go, consider using a different DAW or look into workarounds for ASIO support in Audacity, though these can be complex and are not officially supported.

But if it's not working with Reaper either, from AI response, there should be a native Reaper ASIO driver that you should be able to use for the 4 channels? 

In other words:  Don't use the Line6 Pod Go Asio driver, but instead using the Reaper native ASIO driver should work.

[edit]  It was all hallucinated AI garbage.  See guide below!!

Been using the fx loop with a mono pedal looper without any issue, other than losing stereo..  So I doubt there is any risk of damage, I'm not savvy enough as to guarantee it given the particular schematics of the Go...  My guess is that if you could blow it up by going mono/stereo cables there would be big warnings everywhere in manual and rear, so risk of shorts should be null;  Line6 engineers likely factored everything in their design.

On 3/21/2025 at 8:00 PM, kaiqueunder said:

I'm facing two problems.

1. When connecting my Stratocaster (single coil) I was looking for a more transparent drive tone that I could get. I really liked the "heir apparent" but even with the gain at maximum, it seems that there is very little drive in the pedal. I think it could be something related to my input gain, does anyone know how I can adjust this? I only found the master volume of the pedalboard.

2. When connecting my Les Paul, all the distortion pedals, even at maximum, also sound as if they can't reach a very high gain, and the distortions sound extremely digital or strange.

Two things:

1) Think it's just the nature of distortion.  There's the 3 main types, overdrive, distortion and fuzz.  But for OD & Distortion, even within a type, there are different types of sounds, which respond again differently.   So the Heir for instance isn't designed to sound like a metal zone..

Ex;

Quote

https://www.perplexity.ai/

There are several popular types of distortion pedals, each with its own unique characteristics and tonal qualities:

•  ProCo RAT: The RAT is a classic distortion pedal known for its versatile sound, ranging from light overdrive to heavy distortion. It features a hard-clipping circuit that produces an aggressive edge and has been used by many famous guitaristsKlon 
• Centaur: Although not strictly a distortion pedal, the Klon Centaur is a legendary overdrive pedal known for its transparent boost and subtle coloration. It's highly sought after and has inspired many clones due to its unique sound.
• Boss DS-1: Introduced in 1978, the DS-1 is one of the best-selling distortion pedals of all time. It uses hard-clipping diodes for an aggressive edge and is known for its gritty, warm tone
• MXR Distortion+: Released in 1974, this pedal has been used by a wide range of artists across various genres. It's known for its simple design and ability to produce everything from light overdrive to heavy distortion
• Ibanez Tube Screamer: While primarily an overdrive pedal, the Tube Screamer is often used to push tube amplifiers into distortion. It's known for its mid-range boost and smooth clipping characteristics
• Metal Zone: The Boss MT-2 Metal Zone is designed specifically for high-gain metal tones, featuring a powerful equalizer section for shaping the distortion.

These pedals represent different approaches to distortion, from the more subtle overdrive of the Tube Screamer to the extreme fuzz of the Big Muff, allowing guitarists to find the perfect distortion for their style and sound.

2) Two, for the 'high gain', again, I think it's the nature of distortion, what would you precisely define as 'gain' ?  Imho, gain refers more to volume, but gain when sitting in front of an amp results in more distortion, given the amp is hit harder.  But 'gain' on a clean amp wouldn't do much in terms of distortion.

So I'm again guessing that it's not the Go or the Go's distortion pedals which sound off or don't work just right, might be more a case of misconceptions of gain/distortion/pedals in general.

Remember that most guitarists see 'gain'/distortion as a combination of pedal gain/distortion + amp gain/distortion.  Hell, lets leave AI to answer again!  :D 

Quote

Gain, boost, and distortion are related but distinct concepts in guitar pedals:

• Gain: Gain refers to the amount of amplification applied to the input signal in a pedal or amplifier's preamp stage . It controls how hard the preamp is driven, which can lead to distortion when pushed beyond a certain threshold. Gain is often associated with the amount of distortion in your tone, regardless of the overall volume

• Boost: A boost pedal primarily increases the volume of your guitar signal without intentionally altering its character. It amplifies the signal cleanly, without adding distortion. However, when used with a tube amplifier, a boost can push the amp into natural overdrive by increasing the input signal beyond the amp's headroom

• Distortion: Distortion occurs when a signal is amplified beyond the capability of a circuit to reproduce it accurately, resulting in a compressed and altered waveform . While gain can lead to distortion, dedicated distortion pedals use specific circuitry to clip the waveform intentionally, creating a more aggressive and sustained distorted sound

     The key differences are:

• • Gain is a broader concept that relates to signal amplification and can lead to various tonal changes, including distortion when pushed hard enough.

  • Boost primarily increases signal level without intentionally altering tone.

  • Distortion intentionally alters the waveform to create a specific type of tonal coloration.

   In practice, these concepts often overlap. For example, many overdrive pedals combine gain and boost functions, allowing you to increase both the distortion and volume of your signal. Understanding these distinctions can help guitarists achieve their desired tones more effectively through pedal selection and signal chain arrangement.

Think the odds of being something wrong with the Go is very low, as described in OP it's just normal guitar behavior, especially with single coils & distortion.

Easy way to test is step away from electronics and testing, if the same thing happens, then yes, it's Go, but if it is significantly reduced or eliminated, it's normal.

Single coils I'm guessing?  I think it's normal behavior, but hard to tell not knowing the extent.  But basically, the signal pickups generate is quite faint, so it requires amplification and that's enough to pickup ambient electromagnetic noise from speakers or other electronic devices. 

Wax potting can help, but it's not a magical solution.  Shielded speakers can help, but again, not perfect.  Pickups vary a bit too.  Some humbuckers can be more noisy than others.  You could try shielding your guitar https://humbuckersoup.com/shielded-guitar-cavity-really-necessary/ but again, can help, but not a miracle cure.  No perfect solution exist imho

Also, try different Pod Go amps, some work fine for single coils but others behave similarly as you describe.  So just playing around in Amp/effects could help.

If single coils (Fender style) and you set your 5 way switch at position 2 or 4, does the issue go away?

On 1/22/2025 at 12:37 PM, daveaphotopod said:

Ah, interesting. 

I don't pretend to be a know-it-all, but what a random effect to be dsp intensive.....and a drive, at that! 

I mean I can think of about 4 drive pedals that have way more options/settings than the Prize Drive, so while I accept that the beta testing proved it to be too intensive, it just seems.....random, to me. 

Likely has to do with the complexity of the internal circuits, as that is what is being emulated

https://circuitlangtantqf.z21.web.core.windows.net/nobels-odr-1-schematic.html

http://guitarpedalbuilders.blogspot.com/2012/05/boss-od-1-overdrive.html

On 1/21/2025 at 4:57 PM, silverhead said:

The absence of the Prize drive was discussed during beta testing. It’s too DSP intensive.

It's more than that though, 3.7 also released between Go updates, and it had a couple of effects, plus 1 bass effect which I omitted.  Not the end of the world I guess, plenty of effects in the box already, but for accuracy's sake... 

- Prize Drive (Mono, Stereo), based on* the Nobels ODR-1

- Feedbacker (Mono), Line 6 Original feedback generator

- Dynamic Bloom (Mono, Stereo), Line 6 Original bloom reverb.

-  Nonlinear (Mono, Stereo), Line 6 Original nonlinear reverb with a variety of decay tail shapes (including multiple reverse reverb shapes).

Looking forward to trying out the new L6 amps though!  Nice we get new stuff, could even call it exclusive since those custom amps are not available anywhere else.  Pretty cool that L6 is innovating the amp field without being constrained by limits of the real world (if that's what it's doing!), but even just designing new amps that don't exist in the real world is something!  :D

Quote

Users were hoping it might be released by Christmas this year as its been over a year since v2.0 but nothing has yet been announced. Hopefully it's not too far away. 

At this point... I'm not so sure Line6 is very interested in keeping the Pod Go up to date.  It's been now 1 year and 1 month since the 2.0 update (Released 11/7/23) , and during that time, apparently the Helix got 3 updates (Version 3.70 - November 16, 2023, Version 3.71 - January 10, 2024, Version 3.80 - November 19, 2024) and with the new Plethora of Line6 products, I think the Pod Go is on the way out in terms of update priority.

So my guess would be that we might get 1 more update, then it's highly improbable we'll get more.  But that's just my guess, and I'd love to be pleasantly surprised. 

TLDR: IMHO, Go likely not a priority now for Line6.  Well... That's surely the impression given the number of updates it released in the last year, which is zero.

On 12/29/2024 at 5:42 AM, voxman55 said:

As Helix now has the 2203 model, it's anticipated that the next Pod Go firmware upgrade will have this as its not using an excessive amount of DSP and should fit into Pod Go. Users were hoping it might be released by Christmas this year as its been over a year since v2.0 but nothing has yet been announced. Hopefully it's not too far away. 

At this point... I'm not so sure Line6 is very interested in keeping the Pod Go up to date.  Anyway, rather than derailing this conversation I'll post in the firmware thread!

Btw @cortkx there's other amps which might be able to do what you want, but I'm not certain which exactly, you can read on amps here;  https://helixhelp.com/models/

Anyway, not sure how great/bad the model is, doesn't seem to be that bad, but that might not work for you! https://www.youtube.com/watch?v=cUNTHYwhdL4

https://www.youtube.com/watch?v=p7usTTOQixU

https://www.youtube.com/watch?v=gFON_Fuh-h8

Not possible if the GUI doesn't let you...  You could try to export the patch, change the value and re-import, and there's a possibility it could work, also a possibility it wouldn't and might even cause issues so how bad do you want it?

Otherwise, I think you could stack delays?  If your 1st delay is 2s, configuring a 2nd delay with also 2s would extend the 1st one by that much, although you'll likely have to play a bit with the volume of the 2nd to get it to match the natural decal of the 1st reverb.

Sh!t we missed the 2.0 one year anniversary guys..   Can't believe it's already been a year!  For myself, still rocking on the Go, but using mainly the same ~10 patches lol  Don't remember trying out the newer features of the 2.0 it's been so long, and I don't think I've been using any/most stuff from new patch like amps and effects...

Guess what I'm saying is that I came here to see what was happening with the next patch, but in practice, for me at least doesn't really matter in the end, Go still rocks!  

But hey, it's been a year, it's probably time I give a go to the new 2.0 features!  It'll surely feel like some new stuff for me!  LOL

https://line6.com/software/index.html?hardware=All&name=POD Go Edit&os=All&submit_form=set

Version 2.00     Released 11/7/23

Yep, looks like we missed the 2.0 one year anniversary.  Hopefully some time soon...   Sigh..

Btw, I wouldn't recommend anyone skip a used deal because of this issue.  The issue was subtle, took many many months before anyone noticed the issue, and even when comparing with and without, they're kinda hard to tell apart.  Not to mention that if you're running a pedal with a buffer in front of the Go, then the impedance issue completely goes away. 

I think the effect might vary too depending on the guitar, but the bottom line is, if you have a good deal for a used unit, likely worth getting.  I haven't bothered to get mine fixed, given I'm using a buffered pedal + as I said, really not a very significant issue!

On 9/30/2024 at 8:27 AM, silverhead said:

Problem? Maybe, but I suspect all real-world physical amps and analog pedals would also behave the same if it were possible to make those parameter changes simultaneously while continuing to play.

How?!  An analog pedal would not behave this way, and neither would an amp....  

For instance, say you had 3 settings on an analog pedal: 

Gain / Volume / tone.   

Dial settings 1:  5/5/5, results in volume = 50dB. 

Dial settings 2:  2/8/5 = 50dB.  

If you could instantly go from 1st values to 2nd values, you would go to/from 50dB to 50dB.  Your pedal output would send a ~50dB signal either way.  Your amp wouldn't know the difference.   You would not get SPL screw ups.  That's exactly what the Go should be doing.

The thing is like I was saying, Go seems like it doesn't do it instantly, it does it sequentially, so say you were at 2/8/5 and wanted to go to 5/5/5, it would go turn up the 1st dial: 5/8/5 then lower the 2nd dial 5/5/5, so the time between turning the 1st dial and the 2nd dial is where you're getting an massive offensive SPL gain; huge sound increase when switching snapshots.

The exact same thing would happen with an amp.  If you could instantly switch input volume & gain, you would get no volume discrepancy, but in the real world, if you had to adjust every dial sequentially; one by one; then you would inevitably get either SPL increase or SPL reduction during switching snapshots; which is exactly what we're getting with Go!

Adding a compressor would make no difference.  Ex: 

snapshot 1:  Compressor 2/5/3/8 settings + OD 5/5/5 = 50dB

snapshot 2:  Compressor 5/1/6/3 settings + OD 9/6/5 = 50dB

snapshot 3:  Compressor off + OD 9/9/5 = 50dB

If you were switching everything simultaneously, you would get no volume disparity.  But if you had to switch parameter by parameter sequentially, then you'd have to be careful in what order you would do so.

And to my knowledge, no way to control which parameter is changed first by PGO.  Feels entirely random, but in my experience; the greatest the volume disparities and the greater the values change, the worse it can get.  Maybe there's an order; 1st block to last block, or maybe it's last block to first block.. 

----------------------------

[edit]  To think more on that issue though, some effects might be problematic.  For instance...  Things that store inputs and whose outputs could be affected by change.  Like reverbs and delays...   Ex;   reverb dials = in/out levels, you've played a 50dB chord which it's going to play in the next 0.1s, if you then switch snapshot and change the in/out to -10dB/+10dB, then you're in trouble, because the 'recorded' chord was full volume, and now your reverb will play it with +10dB, your next chord will be fine though.

On 9/26/2024 at 9:53 AM, silverhead said:

It mimics exactly what would happen using real-world physical amps if such changes were applied instantaneously.

I don't think it does.  From what was able to gather from my experiments, it's like Pod Go switches each setting sequentially rather than instantly.  So if your block volumes vary a lot between snapshot, the worse it gets.  Ex; you could have 2 effects boost the volume significantly before the 3rd block reducing the volume, and this will result in an awful ear blowing during snapshot switching; the volume gets from 5 to 8 to 12 and then go back down to 5.

On 9/26/2024 at 6:10 PM, cdtreadwell429 said:

Thanks!

 

Yes, the clean snapshots are maxed on the amp channel level. And I’m out of free blocks, but I could probably move some stuff around. 

 

I didn’t think about adjusting the output block within a snapshot! I just defaulted to thinking it would affect all levels in the preset. You don’t think it would cause the same problem with the gain staging?

 

Great recommendations!

Any luck?  For myself, I wasn't able to determine exactly what causes the issue, some snapshots switch fine while others cause sound explosions of different degrees, but my conclusion is that ...   It's unpredictable and rather unfixable, it's just something Pod Go sucks at;  snapshot transitions.

That is, the more volume varies between the blocks of different snapshots, the more Pod Go will do stupid things during snapshot transitions.  If you want to minimize it, not sure how you'd do it...  But again, my personal conclusion = don't try to have a clean sound and a very dirty sound in the same patch, as snapshot transitions go haywire.

"Pump up"?  What did you pump?  Probably pumped something which you shouldn't have pumped.  Not all things should be pumped.  Best bet would probably to put everything back to the middle, and just switch one thing at a time, that way you'll figure out what ever dial does!  I'm guessing a high treshold or something prevents it from activating because it's too high!

https://helixhelp.com/models?categoryId=5

Quote

Ducked Delay

Based on: TC Electronic® 2290

Available Parameters

• TempoSync1
• Note Sync
• Time
• Feedback
• Low Cut
• High Cut
• Mix
• Level
• Threshold
• Ducking
• Dynamic Attack
• Dynamic Release
• Dynamic Type
• Trails

Have you tried without the FX  Loop?  I think the FX Loop might be the culprit; apparently can be configured mono or stereo, but I'm guessing that if it's configured mono or the issue is one of the effects in the FX Loop block, the FX might be receiving no signal in the FX Loop return and that's why it's outputting no sound for 1 channel.  Having 1 mono effect in FX Loop would kill stereo. 

So just testing with FX Loop disabled, are you getting anything?  Maybe test with just 1 amp + 1 stereo delay, to be sure it's not a mono effects block or something screwing things up!

Quote

I have 2 amps set up with 4 cable method

Ok so no stereo in your FX block, your stereo effects should be after your pod [amp / FX Loop], if you're using 4 CM you obviously can't send stereo to your amp.

Again, KISS, (Keep It Simple, Stupid), just try guitar + stereo effect, that'll confirm your L6 FX unit can indeed output Stereo correctly, then add 4CM and FX Block, which cannot be Stereo with 4CM, and but I guess could contain something like   [L6 FX Loop Out -> Amp out -> Stereo Effect -> L6 FX Loop In], but any stereo effect before the FX Block would get 'eaten' by the amp which isn't stereo.

On 8/20/2024 at 12:35 PM, theElevators said:

I personally don't understand the point of upgrading firmware.  On the Helix I'm on the same version 3.11 from a few years ago.  All I see is constant new bugs that get introduced.  If something is working, I don't want to risk messing up my presets that all work great, just so I could have a hypothetical ability to play around with a couple new effects. 

That's only because those who upgrade without issues don't make threads about it.  I had issues with my 1st update, years ago, but all updates since them have been working perfectly.  I'm sure a high % of people never had any issues at all.

In the case of Go, firmware has some bugfixes, but most appealing are obviously new features, like new effects or the cabs system.  I'm definitely with you with the if it ain't broke, don't fix it.  But software is typically a different beast.  The longer you wait, the harder it will be for you in the end.

On 8/18/2024 at 9:53 PM, jarablue said:

I am actually thinking of getting the HX Effect unit instead of sticking with the POD GO. I do not need the amp/cab sims at all. Do you guys think this would be a good move? Returning the pod go and getting the hx effects? I am thinking for my use case it would be the better way to go. Any ideas?

What does the HX Effects do that the Go doesn't?  I don't think it would make much difference.  The Effects is even more expensive than the Go.  Don't think it as many more effects; from memory, it might have more features (outputs, maybe DSP, maybe more blocks, etc.), but the effects themselves are largely the same.  https://line6.com/comparison/processors/  But maybe also the UI of the unit is more suited for your use case..

Quote

So if I get my amp clean, I can use the amp/preamp to simulate other amps/preamps on my ac15 amp? Just making sure I got that right?

Kinda.  You got a 'combo' amp.   "A guitar combo amp is a type of amplifier that integrates the amplifier head and speaker cabinet into a single unit. This design simplifies the setup process for guitarists by combining the necessary components—preamp, power amp, and speaker—into one box, making it particularly popular among beginners and those looking for convenience in their gear."

So yes, if in Go you have a cab block, you in reality will have 2 cab; the one in Go, and the real one.  So disabling cab in Pod Go is desired, since you're already using a guitar cab and don't need Go to simulate one (like if you were using Studio Monitor speakers).

For the amp, you can't bypass your Vox combo amp amp's section.  But if you set it so that it sounds 'neutral' (imparts little sound of its own; clean amp), then you can use Go to simulate another amp, and your Vox should sound like the other amp, with obviously the Vox Cab.

On 8/17/2024 at 9:07 PM, jarablue said:

Is there any reason I should use the fx loop block on the pod go? When I turn it on, it cuts off all sound to my ac15. Would I need to use the fx loop block on the pod go for any reason?

If you had other pedals you wanted to use with PGO, but didn't want to use them in front or after, so can place anywhere in your PGO chain.  Plus can turn on/off the loop so disable/enable series of external effects from Pod Go.

On 8/17/2024 at 9:07 PM, jarablue said:

Also I will turn off the cab/ir blocks on each preset then create my own presets with them turned off. Is there any reason I should use the amp/preamp block going into my ac15? If I am not using any distortion or any effects at all from my amp other than volume (no treble, no bass. Just volume)?? How do I disable the ac15 drive/distortion to get it clean as possible to use the pod go amp/preamp? Or would it be better to just disable them both on the pod go and use my amp fully with just effects?

 

Thanks again for the help!

Yeah largely, other than just amplifying signals, tube amps also distort the sound; they all do it kinda differently, so Fender, Marshall, Mesa, etc., all have their own attributes.  So if you want your Vox to sound like a different amp, that would be it!

For clean, largely depends on the amp, but typically reverb off, drive at 0, mids/lows/highs at 30-50% (depends on amp), etc.,  For the AC15, looks like the normal volume controls the drive, and the master volume just the volume, so likely normal volume pretty low.  But try it!  See what works for you :)

There's no best way, really depends on what effects you're going to use on both units.  Both seem to have FX loops, so you could use that, really up to your preference!

Does not seem like the Vox AC15 have an effects loop...  :\ 

So either

1) use the clean channel and make the amp as clean/neutral as possible.  Then you could use the Go's amps, but probably would be better off disabling the Cab block, that would allow you to almost fully use the Go's potential and full line of effects through the Vox.

2) If you use your amp drive/distortion, it'll distort the Go's output and might hinder effects such as reverb, delay, etc., typically effects that go after the amp. But if you'll use just Go's drives or pre-amp effects that would be good too!

You could also use your Go as PC audio interface and connect your speakers to Go, then both PC and Go will play through speakers/monitors.  And if you connect the Vox using Go's Amp out, it'll automatically cut off the cab & effects after the cab block, so both your patches should work for both PC and Vox amp!  (well you'd get double amps, so likely would need to manage that one way or another!)

On 8/11/2024 at 7:25 AM, olerabbit said:

I only need one more assignable block in my PodGo.

On 8/3/2024 at 10:36 AM, grdGo33 said:

You can download a preset which replaces many of the currently pre-assigned slots with empty slots, which gives you more flexibility.  [...] but if you want, bit of search will lead you to this 'hacked' patch!

On 8/5/2024 at 5:36 PM, theElevators said:

There are hacks to free up blocks: https://www.youtube.com/watch?v=JlDhCZOOv9U&ab_channel=HeyWorshipLeader