mistermikev Posted May 9, 2019 Share Posted May 9, 2019 I guess you could classify this post as disgruntled customer. not really disgruntled... I like the pod hd pro x quite a bit. I bought it new about 2-3 years ago. there have been no updates... and that'd be fine if it weren't for this one BUG. steps to replicate... load in a new bundle. hist send all to sync them to your pod all is fine... set list names are accurate. turn off pod hd pro x turn back on all patches are there... but the setlists have the name of the last setlist that was loaded. so the only way to retain the setlist name after power off/on is to never load bundles and only load setlists. really don't wanna be "that guy" who swears off such a great product line over what should be such a simple fix (I'm a programmer so I do have some idea)... but it is an INJUSTICE. (ok, maybe just annoying) Quote Link to comment Share on other sites More sharing options...
phil_m Posted May 9, 2019 Share Posted May 9, 2019 So it's just the actual name of the setlist that's changing, and everything in the setlist itself is OK? Can't you just manually change the setlist name after the fact? I mean I get that it's a bug, but it might be one of the most inconsequential bugs in the history of bugs... Quote Link to comment Share on other sites More sharing options...
pianoguyy Posted May 9, 2019 Share Posted May 9, 2019 This isn't a "since the beginning" problem that was never fixed. It is a new problem that was purposely done. They had to remove some things in order to make room for others. Truth is, naming setlists is such a little thing to me that I don't even remember which methods work and don't work because I quit even trying. Just trying to recall the foggy memory, I believe that if you did a global reset after each setlist import, the names will stay. Which is just stupid, especially considering that manual changing them works. Quote Link to comment Share on other sites More sharing options...
pianoguyy Posted May 10, 2019 Share Posted May 10, 2019 21 hours ago, hurghanico said: Actually the Global Reset procedure resets the setlists names to the factory ones, but doesn't touch the patches: https://line6.com/support/page/kb/pod/pod-hd500-hd500x/after-pod-hd500x500-flashre-flashupdate-mandatory-global-settings-reset33-r160/ _______________________________________________________________________________________________________________________________________________________________________ All about POD HD500/X Yes, after a firmware install, the global reset will insert the default setlist names because those are the setlist names that were recently installed by the firmware. But what happens if you do the global reset after a setlist upload instead of a firmware install? Maybe you are right. I said that I have forgotten what the actual "remedy" was because it is such a little thing and the fix seemed like a bigger burden than it the issue. But I do recall it being some kind of overkill non-sense like uploading a setlist and doing a GR. Quote Link to comment Share on other sites More sharing options...
pianoguyy Posted May 11, 2019 Share Posted May 11, 2019 yes, manual works. but when you have a setlist saved. or a bundle (which has 8 setlists) saved. And you upload it to the device... it seems silly not to be able to see it named "patches used for x" - the way you named it. Think about it. Even if you name it manually, but then save it and reinstall it at a later date, the name won't appear. But, I find it works just as well always seeing "setlist 1" thru "setlist 8" Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.