I think they're the same in edit as they are on the unit.  i almost always edit on the unit itself.

the graphic eq you have to turn your head sideways to "see" the EQ curve like a graphic eq is designed to do, but it at least tells you the frequencies (they're fixed though).  of course I feel it should be at least a 5 band.

the parametric is complete guesswork at this point.  all line 6 has to do is put out a spec sheet on this effect.  of course, it'd be better if you could actually adjust in HZ/KHZ

i have figured out that 38% is ~700 HZ and 65% is about 2 KHZ.  I often cut and boost at those frequencies, respectively, and it works out pretty well.

thanks tubealot, i'll try those out.  the two i've tried out so far weren't helpful at all.  I set the Q quite high and slowly panned through all the frequencies, while the looper played back some ringing chords, and I definitely didn't see a corresponding moving spike in the analyzer - it seems to more or less always show the same frequency curve - it only got louder as I went through the midrange frequencies.  The effect on the sound, however, was quite blatant.  Maybe I'm not using these correctly?

as of now my plan is to run an X3 in the FX loop and get the EQ's on both units to produce the same sound, then record the frequency from the X3.  I want to create a mapping for every 5%'s on the HD.

nice research - i trust your analysis over my own.

it's complete garbage the thing maxes out at 4.5 khz.  the uber amp seems to have a fizzy spot above 8 khz, but it sounds crappy to use the studio eq and cut all the 8 khz + freqs.

Hey Don,

I have to agree with people who are requesting frquencies here. Beginner users theoretically may not understand, but they should also start to think this way as it is the way it is normally done. Experienced users simply can't use the tool because they know what they're trying to do and the tool makes it difficult. Percent is a relative, not absolute measure. 50% of what? It is confusing at best, unusable at worst. Even beginner users understand higher frequencies and lower frequencies so I must confess, I don't understand how % could have ever been considered for these parameters. Hopefully this will be addressed in an update.

Cheers,

David.