voxman55

What version of Pod Go Edit did you originally have installed on your Mac? Did you get the link from the official page here - if so, are you upgrading from v1.11? If you had an earlier version of Pod Go Edit installed (or no Pod Go Edit installed) then you need to install v1.11 first, and THEN upgrade to v1.21 - you can't upgrade straight from eg v1.01 Pod Go Edit (or no installation) to v1.21. I'm guessing the downloader has possibly detected you weren't on v1.11 and is taking you through that upgrade first. Thereafter, you need to repeat the process and v1.21 should then be installed: ?

This might just be a minor software path corruption. First thing is to make sure you've updated to v1.21 using Pod Go Edit v1.21. (If you don't see the new models you may need to reboot your computer). If you are on the latest firmware, I'd suggest you save your patches using Pod Go Edit backup, then reboot back to factory settings by holding buttons C and D whilst powering up, then reinstalling your back up ( note: you won't lose the firmware update, it will still be v1.21). If you still have problems, then raise a ticket with Line 6 support, and attach a copy of your back up for them to look at.

Sounds like you've reached the DSP limit. If you're using heavy DSP effects such as spring reverb that use up a lot of DSP, Pod Go will only give you access to effects that are within the DSP you have got left. See the Benvesco table here (not updated yet re new models in Helix v3.0 and Pod Go v1.21). When building patches there are always exchanges you can make for lower DSP effects that will give largely the same results. The Princeton is a very detailed model so likely to be at the higher end of the percentages in the amp model list. https://benvesco.com/store/helix-dsp-allocations/

Suggest you raise a ticket with Line 6 support, and they will sort it for you.

Interesting. Does the acoustic IR simply load into the usual speaker cab block?

This is just a friendly, intelligent discussion about Pod Go, it's just a piece of gear. It's not life or death and certainly not intended to be personal ...apologies if you took it as such. I always respect your views @silverhead but I think we'll just have to agree to disagree on this one.

Thanks @silverhead but I don't think my experience and knowledge is anything special and based on my interactions here, YouTube and other boards it suggests that there are a large number of users who have a pretty good understanding of how Pod Go works. But even if your point had some validity, I still don't buy it. And that's because it would be a very simple matter for Line 6 to say that Pod Go is designed to be most flexible for new users with up to 4 blocks. But for more experienced users who have a deeper understanding of DSP useage and who are prepared to make trade offs on models selected Pod Go now has ( at least) 2 additional slots that can be pulled down if required but provide no extra processing power. So, both types of users catered for with a simple explanation for 'newbies' and kids playing in their bedrooms who just want to make some noise and those who want to maximise their options. But the solution is easy. I fully agree with @grdGo33 that you need to give users DSP info in the unit and not make it mysterious. Is it any wonder if newbies don't understand about DSP when Line 6 gives them no information? It took a dedicated third party to publish what Line 6 should have done. What better way can you have for newbies to learn and understand about DSP useage than give them a simple, visual reference. As a case in point, the new Zoom G6 ( aimed squarely at the Pod Go market) does exactly this - by each and every model listed is a %age of the DSP cost. How difficult can that be to do and how easy is that to understand, even for novices? Now, if Zoom recognises that users need information to get the best from their G6 product and can treat it's customers like grown ups, surely should Line 6 be doing no less? I know that Line 6 says every decision is meticulously thought through and pros and cons weighed. But I do wonder if their market leading status has perhaps made Line 6 a little shortsighted or even dare I suggest perhaps even a tad blase here with regards to what users need. The lack of snapshot naming and multi footswitch naming are further examples where their omission seems to convey that 'that's good enough for Pod Go users and we don't need to bother with these' - yet these are the two biggest things users have been asking for...did this not come out in research? With all its knowledge and experience, I can't help feeling that Line 6 might not know it's customer base for Pod Go quite as well as it perhaps might like to think. And regardless of what Line might allude to publically, I again agree with @grdGo33 that if Line 6 made Pod Go too good, it would potentially deflect from Helix sales and it is in their interest to keep a sufficient level of differentiation from their flagship products. On this point, it's perhaps interesting that following the commercial failure of its G11 unit that Zoom has positioned the new G6 as it's flagship processor and perhaps that has encouraged it to come up with some genuinely interesting features. It therefore has no potential conflict of interest with other of its product lines. And whilst I'm sure Line 6 would vehemently defend any suggestion of there being any conflicts of interest between any of its product lines, I think its difficult to totally disregard that possibility.

@silverhead I'm intrigued. Why do you think Line 6 won't add additional user blocks ... there is a LOT of untapped processing power that's available in Pod Go ... as demonstrated per my recent post in another thread. It would also follow what Line 6 did in HX Stomp. Line 6s original 'concerns' at overplaying Pod Go's processing power were based on customers not being used to how DSP was allocated, but with so much easily available information now going around the internet and YouTube it's time to take the training wheels off. Do you have inside information on this??

Sorry @silverhead but with all due respect, I think that to suggest that Pod Go doesn't have enough DSP for more than 4 blocks is complete & utter nonsense. So allow me to debunk that right now! If you look at the DSP table prepared by Benvesco there is clearly a lot of scope to use one and even two additional blocks. For example, having selected a reverb, delay, modulation and distortion, there is plenty of room to add e.g. a compressor and a second distortion or modulation or delay, provided you make sensible selections ie not opting for jumped amp models and spring reverbs. Now I realise that Benvesco's chart may not be 100% accurate, but it's going to be pretty darned close even by Line 6's acknowledgement, so let's look at a typical example of DSP useage - and I'm intentionally not going for all the cheapest DSP, I'm mixing in a reasonable selection of DSP useage items - nor am I using pre-amps that will reduce your amp DSP considerably. And I'm going for 6 blocks for which you still have a surprising amount of choice - 5 will give you even way more options: Marshall Plexi 100w Super Lead - 34.88% Cab (Stock) - 0% Any 'standard' reverb (room, plate, hall, tile, chamber, echo etc) - 13.61% Delay - Line 6 Simple Delay - 7.66% (2nd cheapest but an eminently practical & versatile standard delay) Heir Apparent 12.33% Modulation Deluxe Phaser (Line 6 original) - 10.63% Second distortion (for gain stacking) Teemah! - 9.36% Compressor, 3-band comp, Line 6 Original - 8.51% Total DSP with 6 blocks = 96.98% - and I've used one of the more popular & medium expensive full amp models. The cheapest DSP cost models? Supro (full amp) - 17.86% Delay - Line 6 Original 'Ping Pong' - 6.81% Any 'standard' reverb (room, plate, hall, tile, chamber, echo etc) - 13.61% Distortion (I'm discounting Megaphone - impractical & not a proper distortion) - 3 options (Vermin 'ProCo Rat', Hedgehog D9, Top Secret OD) all at 7.66% Modulation - Tremolo 4.25% Chorus (Line 6 Original) 11.91% Dynamics - Deluxe Comp - 4.25% IR (1024) instead of stock cab - 10.85% (This percentage looks suspect - IR's should only be about 2-3% extra DSP cost in Pod Go - See below) Total DSP with 6 blocks 66.35% - and even with an IR that's still only 77.2% !! Heck, you could even add Filter -Eventide smart harmony 12.76% (not the cheapest) Synth - Roland Synth String 9.78% (not the cheapest) And with 8 blocks plus an IR you'd still be under 100% at 99.74%!! (Actually about 90.74% based on a 1024 IR - the 10.85% looks wrong, see below) My point is that whilst yes of course you need to be sensible and pick your targets as it were, there is a TON of tonal flexibility even at 6 user blocks. And even sticking with stock cabs there is a 30% range of DSP allowance/choices between the two examples above !! If you want heavier DSP models in some areas, there's always scope to compromise in others - choosing a pre-amp for example (which I didn't even go with) is yet another option. Every patch I've created in Pod Go has full amp models and 4 blocks, and loads have an IR too - even those with spring reverb. I'll typically have a reverb, a delay, a modulation, and a distortion. I'd love to be able to add a compressor and a second distortion or second modulation to some patches. The point is that giving users choice gives us more potential flexibility. So c'mon - Line 6, it's past time to take the training wheels off the bicycle & give us 6 user blocks in Pod Go - give us, your customers, the choice of how much our bikes can carry, and how steep a gradient we can pedal up before we fall off - treat us like sensible adults, not kids. Caveat it by all means ie it doesn't give more DSP and you still might only have scope for 3-4 blocks if you select several heavier options etc - but give users the option to maximise Pod Go's DSP useage because a lot of processing power is going to waste! UPDATE I'm puzzled by Benvesco showing an IR as an extra 10.85% - IR's should only be around 2-3%. So I did a test with heavy DSP models: Brit Trem Jump 40.83% Spring reverb 34.03% 70's Chorus 15.74% Simple delay 7.66% TOTAL = 98.26 ie 1.74% spare In theory, I shouldn't have had enough to add an IR (1024) - but I can! Which means that re my examples with an IR, there's probably actually an extra 9% spare on top of what I've shown. IDEA To give users the most flexibility from Pod Go, why not allow 2 or 3 or even 4 voluntary/optional user blocks that can be inserted if required on top of the 4 standard blocks'? That way Line 6 can say up to 4 blocks for optimum selection choice, but up to an additional 4 to cater for more restricted options.

Before buying Pod Go I researched it so that I pretty much knew it's good points and it's restrictions. I watched the Line 6 videos, read the manual and read user feedback. Whilst not perfect, it met my fundamental needs and I bought it based on what it could do now, not what it might be able to do going forward. I could have picked up a used Helix LT but I wanted something light, compact and easy to use and for me Pod Go's advantages outweighed its disadvantages and has been a good choice. So @Samdbl before buying any gear its always important to do some research first to ensure it will fundamentally meet your needs. Now, lets be fair, right from the off, Line 6 was completely up front as to how Pod Go was designed especially the mixture of fixed blocks and user blocks which was key to its design and is why Pod Go (even though it utilises Helix modelling) was specifically positioned as a 'Pod' and not a 'Mini-Helix'. Pod Go is a great unit but in your case it sounds like it wasn't quite what you expected and so unfortunately might not be the best fit for your needs. That's OK, gear is personal and we can all get things a bit wrong sometimes. But your post (repeated 'wtf') kind of gives the impression you feel you were misled. Lets be absolutely clear about this, you weren't!! You made assumptions and didn't do your homework, which is fair enough, but only as long as you take ownership of that - it's not fair to put your frustration at Line 6s door which is what seems to be coming across from your post. Sorry if this sounds a tad harsh but I think its appropriate to say how it is. Now, putting that aside, it is possible that going forward Line 6 might (and I certainly hope they do) add one or possibly even two extra blocks to Pod Go. Helix Stomp was updated from 6 to 8 user blocks so it's at least possible. As I commented on elsewhere, I can understand that Line 6 chose 4 user blocks originally because most of the time users can have 4 blocks, and it didn't want to mislead those that lacked experience with this type of DSP allotment. But through the internet, boards, YouTube etc there is now a ton of info on DSP useage. Therefore in my view I think Line 6 should now take the training wheels of the bicycle by giving greater freedom so that users can get the most from the available DSP. So, fingers crossed we will hopefully see enhancements in the next firmware upgrade that will improve user functionality. In addition to more blocks as a gigging player I'd like to see snap shot and multi- switch naming, visibility of F7/F8 external pedals on screen, and the option to use F7/F8 for patch up/down so you can still have 6 blocks visible. I'm aware that at least some of this is on Line 6's 'to do list'. If you want some or all of these features to be added to Pod Go, I'd therefore suggest voting for these on ideas scale which is the Line 6 site for fielding ideas for them to consider, here: https://line6.ideascale.com In the search bar on the right, type in 'Pod Go' and then just scroll through the Pod Go ideas. All the above (and more) are on there (some several times as different folk have posted the same request - in which case vote for each!).

Whilst I think @grdGo33 has made a good post here, one of the key advantages of Pod Go is that you are not restricted by 'real life' and you have way more options. All that matters is that you create a tone you like. Whether you prefer the natural sound of your cab and want to turn off amp/cab models, or keep them on, there are no rights and wrongs here..it's just what sounds good and works for you. All I'm saying is you should learn about EQ, not be afraid to experiment, and not be a slave to 'conventional thinking'.

Pleasure. See also my comment 're global EQ in above reply. In your circumstances, if you found the right patch settings for your set up, if you went to a gig and plugged into a different cab, global EQ could help change your overall EQ quickly.

As I mentioned, the type of EQ is less important but a simple parametric might be good to start with and then try a simple graphic. 're placement, it's experimentation. The preset settings on Pod Go EQs are set neutral so don't expect them to change your tone straight off. Lots of good YouTube videos on EQ. As I also mentioned, I can't give you a quick fix. We all have different ears, gear and play different types of music..it's a learning curve and you need to spend some real time on this. Btw...I'd avoid the global EQ, which is for something different. It isnt for patch setting, its for balancing global EQ e.g. to adapt for a different cab ( e.g. not yours) or room environment, and where you want to set it back once you are back to normal.

Do you mean the 20w Joyo Bantamp Meteor? Personally, I don't put multi Fx pedals through amps because generally I don't like the tone, even through the FX loop return. Although you're using it as a pure power-amp, so you don't get all the preamp colouring, it still colours your tone. Some amps are better than others obviously, and ditto cabs you go through. So, here's a common fallacy - 'I've got a real cab so I need to turn the cab model off' - right? Well, no - it's all down to personal taste and there are no absolute rights & wrongs. . When you are hearing your Pod Go through headphones, with a good set you should be getting close to a flat response so that when you have the cab models turned on, you are hearing much closer to how eg a mic'd Marshall Plexi through a 4x12 Greenback cab will sound. Plus you can fine tune the cab to taste with mic type, distance, frequency adjustments, and even boosting the dB output. But when you go through a real cab, it will sound very different because it's completely different to the cab model you've been using ie there is no Randall 4x12 cab in Pod Go! But especially if you want to turn cab models off and hear your real cab tone at its best, the single most important tonal tool you have in your Pod Go to get the best out of an external cab is...(drum roll...) an EQ. It's already a fixed block in Pod Go, so use it to your advantage, to shape your tone. If it's too bassy, raise the higher and mid frequencies and lower the bottom end. Learning to use EQ, choosing the best type for your needs, setting it, and experimenting with its position in the signal chain, output levels etc, is ABSOLUTELY KEY. EQ type is less important eg although a graphic v parametric EQ work a little differently they both do pretty much the same thing albeit in slightly different ways. Really investing some time to learn about EQ and tone shaping will be, I promise you, the number one best time investment you can make. Whilst not exactly the same thing, a cab model or IR is essentially just a type of EQ. So, my first recommendation - with cab models off, use an EQ to help shape your tone from your real cab. Second recommendation - try putting the cab models back on, raise the dB output to eg 2-3dB for a 'bigger' feel, add on say 15-25% early relic, start with a 57 dynamic mic and experiment with distance, and mic type. And you'll get a way nearer tone to your headphones than turning your cab off. And still use your EQ to shape your tone. As I said, I don't generally put my MFX through an amp, but when I do, I tend to leave the cab model on. This is why Pod Go is not plug and play. Pod Go is a tool - and a very sophisticated & powerful one. But it is incredibly versatile - you just have to invest time to learn what it can really do. Too many users expect instant gratification, dial in high gain amps and distortions and effects, and then wonder why it sounds dreadful and blame the MFX unit. For gigging, I don't use an amp - I put my MFX straight through the FOH PA. If I need a monitor, or for rehearsals or smaller gigs, I have a powered speaker cab - a Headrush FRFR108. FRFR = full range, flat response - so I'm hearing as close to how the amp/cab model are intended to sound with virtually no colouring from the Headrush amp or speaker. There's no right or wrong here, it's whatever works for you.

Thats odd. Mine never did that, the typeface never changed? I'm on Windows 7 so its possible the operating system or whether you are on PC or Mac may be a factor here.

Try rebooting your computer

There have been a few reports of folk having similar problems, but mostly with mac rather than PC. Try rebooting your PC first - for some reason I was 'asked' to do this on mine (also W7). Then re-connect Pod Go, open up PGE v1.21 & see if they are now there. If you are still having problems, when you start Pod Go what firmware version does it show in the kidney bean at start up?

Not on this update but I've had similar behaviour pop up. Line 6 support recommended I back up my patches and reset back to *factory settings by pressing switches C&D and holding these when powering up Pod Go, then re-importing my patches back. Worked perfectly after that. *You won't lose the v1.21 update btw.

There's also bugs in Pod Go Edit v1.21. Although Line 6 put Acoustic sim in the EQ section, it appears to have too much DSP to replace a fixed EQ and has to be loaded into a user block. However, Line 6 locked it as if it was a fixed EQ and there is no 'x' to delete it in Pod Go Edit. You have to replace it with something else in the block and use that 'x' to clear the block. There's also some odd intermittent connection problem with Pod Go Edit v1.21.

"Very fun delay! :D " But with very little practical value - there's more than enough amp, cabs, & fx already in Pod Go such that most users have option paralysis as it is, and I hope that having satisfied the masses who are mostly bedroom players and just want more toys to play with by adding some extra fx, amps, cabs, that in the next firmware upgrade Line 6 focuses on improved functionality to make Pod Go more of a gigging friendly tool.

In which case I stand corrected as I was completely unaware that Helix could do that. However, Pod Go can't switch external amp channels.

All on by me and or others.

Gotcha, I was just thrown by it. The problem is that Line 6 has gone with the masses who just want more fx, & more amps. But aside from the acoustic simulator, there's so much in Pod Go already that you really don't need more of all this - most folk have option paralysis as it is and amps & distortions do get to sound samey. I'm therefore hoping that the next upgrade will focus on functionality. It's supposed to be Pod 'go' ie take it anywhere for rehearsals, gigs - yet it's not yet as gig ready as it should have been. There are 5 key things it needs purely from a functionality perspective: 1. Snapshot naming 2. Multi footswitch naming 3. At least one extra user block (2 would be great) to be a bit more flexible so that provided your selections were less DSP hungry, you could have some additional flexibility - particularly useful for creating a stomp pedal board for gigging where you could add eg a compressor and a second modulation or distortion etc. It wouldn't give more DSP, but Line 6 upped HX Stomp from 6 to 8 slots, so it is doable. 4. Ability to see F7/F8 on screen 5. Ability to use F7/F8 to switch up/down so you could still still scroll through patches in 6-view stomp-mode If Line 6 can get those things added to Pod Go, then as far as I'm concerned it's then a bona-fide gigging unit and anything else is a bonus. But then I'm a gigging player & home players don't need these.

Anything you want. I tried it with the new Princeton model set clean & it was very nice

No it can't - no Line 6 MFX can control an amp I'm afraid