BarkingSpiders

Hi there, I'm considering getting the Boss RC 500 for looping and a drum machine (although it would be great if Line 6 could actually add some drum loops in a future update... :)). The problem with the looper on all Line 6 products seems to be that it's very very basic. For instance, there is no quantization against the current tempo. But then again, I don't want to manually set the tempo on my Pod GO AND on the RC 500. Hence my question: would it be possible to use MIDI to let the Pod Go send out the tempo (and other sync related info) to the RC 500, which has a TRS Midi mini jack (Type A)? If anyone here knows if that's even possible, and if so on how to set it up: please let me know! Thanks!

Thanks a lot for this! I fiddled around with the JSON file and created a simple empty patch with 9(!) empty effect blocks. I axed the Wah Pedal, FX Loop, EQ, AMP, and Cabinet. I kept the volume control as 10th block, although that one can be axed too. For anyone that don't need these things, enjoy the extra blocks ;) Please find it attached EDIT: So far I managed to let 8 blocks work together (6 effects and a looper + the volume pedal), the remaining 2 blocks seem to be bypassed. It's a DSP processing limit. So picking the another combination of blocks might give you an extra block. ------.pgp

Actually I do sometimes like the cabs/amps when plugging the pod go into my laptop and recording it. But in live situations, those things just get in the way imo. Also I like the wireless feature. So I'm kinda fond of my Pod Go, it would only be even better if I'm able to replace the amps with an effect ;)

I know I can complain a lot for things that don't go well here. But first and foremost, I want to thank you for keeping the updates coming. So many companies these days are releasing a gadget, with support for just a few months and then expect you to buy a newer version. Not you. And that's much appreciated. Thanks! PS. hopefully this comment will age well ;)

Can someone at Line 6 fix this issue? I have a ton of these popups every time I boot up Pod Go Edit.

Hi all, I've problems getting the AMP/PREAMP and CABs to work nicely with physical amps when I play somewhere. The sounds just doesn't sound right and I'm not sure if the 4 cable method is doing a much better job. Also I find it too cumbersome to setup; I want to plug my Pod Go in an amp and be done with it. So I'm basically only using the effects. However for some reason the CAB/AMP always need to be in the signal chain, even when I switch them off. Would it be possible to remove them so the freed up CPU cycles could be used for an extra effect?

So I tried the 4 cable method, and I'm not sure I did it right, so I have some follow up questions. Here is my setup Presets * Cabs are always off * I use PREAMPs instead of AMPs * Signal chain has delay and distortion before FX Loop * PREAMP and reverb are after FX Loop 2 cable method (2CM) * Connection: MAIN OUT left -> AMP GUITAR IN * Preamps are switched off * FX Loop is off 4 cable method (4CM) * Connections: (1) POD RETURN-> AMP SEND (2) POD FX SEND -> AMP GUITAR IN (3) MAIN OUT left -> AMP FX RETURN * With a single footswitch I switch on/off the FX Loop and PREAMP POD Go Global Settings * Guitar In Pad -> Off * Main Out Level -> Instrument * Amp Source Out -> Main Out * FX Loop Level -> Instrument * Return Type -> Return Observations * Sound with 2CM is good, but I don't use any AMP/PREAMP modeling. * It's nice to have PREAMPs with 4CM for more control, though I'm still not sure if it all sounds that much better than simply 2CM with no PREAMP/AMPS. * Unfortunately there is a significant volume difference between the two setups, meaning I have to tweak presets based on whether or not I use 2CM or 4CM. * When accidentally switching off FX Loop with 4CM, the sound becomes really loud. You do not want to mistakenly do this during live performance. * Not sure if the extra cables + complexity + accidental volume screw up, outweigh the benefits of amp modeling at this point. Questions - Are all settings for 4CM correct? - Since not all amps have FX SEND/RETURN channels, I want my setup to be easily switchable between 2CM and 4CM. However the POD GO doesn't seem to feature a global setting for this. Meaning that I manually have to adjust the presets based on the situation present on the floor, right? And since switching off the FX Loop during 4CM produces a LOT of noise, this is kinda easy to screw up. - Is there some global setting that simply ALWAYS ignores the AMP/PREAMPs/CABS and FX Loop? I.e., reducing the possibility of accidentally stepping on disable FX Loop? - Is there a way to always disable CABs? I find it quite annoying that everytime I select a new AMP, automatically a CAB is selected with it, and worse: is switched on as well. Even though I switched it off before. That's it for now. Thanks for all the feedback guys! Cheers, Martijn

Thanks a lot for your help! Going to try this. My amp at home has 2x2 jacks for send/return (two mono jacks for each). Can I just use a single channel (eg left?) for 4CM?

Thanks for you reply. I'll go study it again :) For now, could you take a look at my current setup and let me know if you spot anything that isn't correct? My current setup: Cables Cable from guitar to Pod Go Cable from AMP OUT or MAIN LEFT out to physical AMP. (I prefer MAIN because I can then use the volume knob to control master volume) Global Settings Main Out Level: Line Amp Out Source: Main Out Signal chain Disabled CAB in all presets Use PRE AMPs as opposed to AMPs for all my presets *** Thanks again!

Hi all, I’ve seen too many videos and read countless documents about how to connect a pod go to an amp, but… I just don’t get it. There are instructions for 4 cables, send/return fx, pre cab sim on/off etc etc. It dazzles me. look I just want to connect my pod go as if it is a pedalboard to my amp. My amp can either be a tube amp or a modeler (solid state amp) that’s it. I’ve tried a lot of combinations, but the sound just sounds bad. Should I use AMP or MAIN OUT, and feed that directly into the guitar in on my amp? What should my global settings be? Do I need to switch off the amp and cab in my signal chain? Or change amp to pre amp? Any help would be greatly appreciated! thanks

Haha, for me it's a nice puzzle. The goal is not to decompile the code (MainCode and Boot sections), but to see if I'm able to decode the data sections. My guess is that that should be doable and that in those sections we'd be able to find the various settings (probably in some JSON or BSON format). But for now I'm just in the dark on the used compression/encoding technique.

Thanks for your reply. And I know the risks that are involved with modifying firmware. So first of all I limit it to simply understanding what's going on in that file. If and only if I fully understand the format, would I attempt to modify it. This is what I found yet: https://github.com/MarByteBeep/podgo Feel free to help me out decoding some of the missing parts (indicated with ??).

I'm currently also trying to reverse engineer the firmware (.hxf file), as I'm still trying to be able to rename the amps and stompboxes. I managed to identify various chunks and archive sections, but I don't seem to recognize the used encoding for the various archive sections. If anyone here is interested in helping out, let me know and I'll post my findings on GitHib.

Thanks! I actually am a bit further with decoding the PGB file format. It's a little bit different than the HX one as it seems to have only 2 zlib sections: one containing the global settings + factory preset information. And the second section contains the user presets. ledcolor is actually defined in this information: "footswitch" : { "dsp0" : { "block0" : { "@fs_enabled" : false, "@fs_index" : 9, "@fs_label" : "Fassel", "@fs_ledcolor" : 196619, "@fs_momentary" : false, "@fs_primary" : true } and also the ledcolor in snapshots: "snapshot1" : { "@ledcolor" : 0 I've attached the two decoded sections as json files. Might be interesting to take a look at it. Up next would be to modify it and store it as a PGB file again :) section2.json section1.json