Changes

== Output Modes, Cabs, and IR's ==

The whole Output Modes setting is confusing and unnecessary. The Line 6 forum sees countless posts solved by setting up the unit correctly - most don't know these settings exist, and when they select a cab/mic when setting up their patch, they expect cab/mic simulation OR they accidentally apply cab/mic modeling when running to a real amp, since by default when you select an amp it automatically applies a cab/mic combination. Get rid of output mode altogether and replace it with the following components:

•Global EQ - replaces the "front" modes which use EQ controls to adjust the EQ at the end of the digital signal chain. Adding a bass boost switch replaces the difference between Stack/Combo modes.

== Amps ==

Separate the pre-amp and power amp components of the amplifiers into separate blocks. This would allow mixing pre-amps with other amps power amps, as well as being able to place effects between pre-amp and power amp (otherwise known as an effects loop).

== Utilities ==

Include a clip meter for anytime the signal exceeds the max resolution in the chain or at the input, preferably indicating exactly where in the chain the clipping is occurring.

== Routing ==

The routing is a bit confusing. There should be better care to document how it actually works. Additionally, it would be nice to display how the signal lines are actually stereo signals and are mixed down for mono effects. Or otherwise, indicate in either Edit or the onboard editor whether an effect is mono or stereo.

== EQ's ==

* A dual Parametric EQ without the "lows" or "highs".

* Include the EQ from the XT/X3 - two shelves, and two peak/valleys, all with adjustable gain and frequencies. If 8 parameters is not possible, do two shelves and one peak/valley.

== Footswitches/controls/Midi ==

Allow footswitches to toggle effects between two sets of parameters, not just on/off. Similarly, allow footswitches to always turn effects on or off, independent of their current state, rather than just toggling them.

== Effects ==

Spend some more time on the Screamer. It's not very accurate, and it's one of the most commonly used effects in the Pod.

== DSP Saving Features ==

Have stripped down versions of effects, so DSP is not consumed for features that aren't often used. For example, have a Parametric EQ without the "lows" or "highs" shelves and have a delay without tone controls.

== Devkit ==

Create a devkit for the community and developers to create their own firmware. I envision there would be two API's. One would be used to create and compile amp models or effects - anything that would be used to process the audio signal(s). This API would compile this code down to machine code and wrap it in an information and interface layer (to access data about the object and manipulate accessible parameters) used by the other API. The other API would handle the system-level functionality of the unit, including manipulating the display, controlling how footswitches and other user input are handled, routing audio signals, placing audio-processing-elements in the signal chain, etc. If done properly, Line 6 would not have to divulge its existing amp models' and effect models' code beyond at a machine code and interface level; but it would provide enough power to developers to implement all the requests listed above.