This issue is tricky, and it affects presets of a certain sort (I don't know exactly what sort) that were created using all versions HD Edit prior to the latest v1.08 and all versions of Pod HD firmware prior to the latest v1.43. These latest versions of firmware and Edit together fixed a serious problem caused by previous software versions that permitted invalid data to be stored in prestets, occasionally resulting in a very loud high-pitched squeal being emitted from the headphones/monitors.

This latest software/firmware versions fixed this problem with invalid data - but at the cost of refusing to load previous presets that contained such data. That's why you are getting the message and why the preset is being reset - the old preset contains the invalid data that causes the problem.

You can revert back to Edit v1.06 and load up the offending preset again - but you are then subject to the high-squeal issue again. And you will effectively be stuck at Edit v1.06, because future versions of Edit will retain the high-squeal fix. This means that you won't be able to use Edit to access the previously announced new features coming in firmware v2.0 (which will also have an associated Edit update).

My best suggestion at this point is to revert back to 1.06 temporarily, and run it offline (i.e.. no HD device connected). This will protect you from the potential high-squeal. Now load your saved copy of the preset and  manually copy (yes, write down!)  the detailed settings of your preset. Do this with all affected presets You can then update to the latest editor and recreate these settings manually, and go forward with your set of clean presets (no invalid data).

carlada wrote:

 

Ok, ok…it isn’t a disaster…but a half disaster?!?!?!

I know that Line 6 software developers are alive and well (thanks to GOD), and I suppose  they are under pression for  the problems there are…But from my point of view, the situation is disheartening... just reached an equilibrium point, sudden need to lose a lot of time to get everything working… and the future is no certainty.

I hope that you say it’s true and become reality…

Carlo

Nope   The word 'disaster' in any form doesn't come close.   I think that word is more reserved for things like earthquakes, famine and stuff of that ilk.

'Annoyance' is probably a better word.  Yes it's a bit disappointing that (hopefully) temporarily, because of unforeseen circumstances (squeal issue), the interim fix on the editors doesn't quite work as before, but as long as we take precautions to potentially protect hearing and equipment, it shouldn't hurt us to simply use the older editor in the short term to transfer tones should it?

I know it's already been raised directly for the people developing the new firmware to see as an issue, so until the new v2.00 firmware and editors are released, I think it's probably better to wait and see what happens   Line 6 do listen to their customers.  Let's not forget that.

Warfare wrote:

 

Hi Nick,

 

Thank you for the fast reply. Of course, we have big expectations for F/W 2.0 and the associated version of HD Edit.

 

Anyway, in my mind there are different level of needs, let's say basic needs and premium needs.

- New amps, new functions and so on are clearly premium needs, and it's the way Line 6 can increase Pod HD customers.

- Being able to create patch, to share them beetween Pod HD products (at least beetween Pod HD Dektop and Pod HD 500) and most of all being able to rely on the growing custome tones library is a basic need.

 

That's why I wanted to share my point of view here. Of course I know that Line 6 does great job, and I'm pretty sure that they're working hard on new updates. And I agree with you, rollling back to HD Edit solve the problem (at least temporary).

 

But, let's be realistic and take a look to the Custom Tone library (datas from today) :

 

Pod HD Desktop :                104 Patches   (including      0 compatible tones)

Pod HD Pro :                         63 Tones      (including      0 compatible tones)

Pod HD 300 :                        701 Tones     (including   273 compatible tones)

Pod HD 400 :                        701 Tones     (including   428 compatible tones)

Pod HD 500 :                      2602 Tones     (including       0 compatible tones)

 

This is the point. There are no compatible tones for 3 products of the range (Desktop, Pro and 500).

The biggest tone library is 500 one, and no compatibility with others ranges.

The Pod HD Pro and Desktop are not sharing any compatibility with others products, that's a pity regarding the fact they have the smallest library.

The smallest tone library is Pod HD Pro with 63 tones.

 

So, I really hope that Line 6 will be able to bring us a common platform for HD family patches (at least for HD Desktop, Pro and 500).

 

This is really frustrating to not being able to share patches with friends ... this is why Custom Tone exist, this is why Pod is so much popular.

I completely understand your perspective and that of Carlo in the post above yours.  However , like you, I hope this is only a temporary situation.  We can easily work around it for now with Edit 1.06 versions which means you can still share patches with friends.  I am 100% certain that the issue will have been brought directly to the attention of the developers, so they will be aware I'm sure, and hopefully by the time firmware version 2.00 is released along with probably a new set of editors, it will have been resolved

MerlinFL wrote:

 

use of the Old English spelling of "behavior" as "behaviour". 

Cry foul back at you dude!   This is an American English vs British English thing.  Nick is a Brit (of indeterminate age) and therefore on the side of the angels here.http://oxforddictionaries.com/definition/behaviour?q=behaviour .

Apologies to the OP.