Control interface to generic frontendsThe generic remote interface allows frontends to easily controlmpg123 by commands through stdin/stdout. To start the genericremote interface, start mpg123 with parameter -R.In case of a frontend that starts mpg123 with the -s option to read the audio from stdout, you may want to specify --remote-err to send responses to stderr so that stdout stays clean for audio.(Still the case?)As an example it's used by IRMP3, a tool that allows you tocontrol mpg123 with a standard infrared remote control. Seehttp://www.fasta.fh-dortmund.de/users/andy/irmp3/ for moreinformation.COMMAND CODES-------------You can get this info via the control command "help"HELP/H: command listing (LONG/SHORT forms), command case insensitveLOAD/L <trackname>: load and start playing resource <trackname>LOADPAUSED/LP <trackname>: load and start playing resource <trackname>PAUSE/P: pause playbackSTOP/S: stop playback (closes file)JUMP/J <frame>|<+offset>|<-offset>: jump to mpeg frame <frame> or change position by offsetEQ/E <channel> <band> <value>: set equalizer value for frequency band on channelSEQ <bass> <mid> <treble>: simple eq setting...SILENCE: be silent during playback (meaning silence in text form)RESPONSE CODES--------------Note: mpg123 returns errors on stderr, so your frontend should      look not only at stdout but also at stderr for responses.@R MPG123			Startup version message@I ID3:<a><b><c>			Status message after loading a song (ID3 song info)			a = title (exactly 30 chars)			b = artist (exactly 30 chars)			c = album (exactly 30 chars)			d = year (exactly 4 chars)			e = comment (exactly 30 chars)			f = genre (string)@I <a>			Status message after loading a song (no ID3 song info)			a = filename without path and extension@S <a> <b> ...			Stream info at beginning of playback, meaning			S <mpeg-version> <layer> <sampling freq> <mode(stereo/mono/...)> <mode_ext> <framesize> <stereo> <copyright> <error_protected> <emphasis> <bitrate> <extension> <vbr(0/1=yes/no)>@S <a> <b> <c> <d> <e> <f> <g> <h> <i> <j> <k> <l>			Status message after loading a song (stream info)			a = mpeg type (string)			b = layer (int)			c = sampling frequency (int)			d = mode (string)			e = mode extension (int)			f = framesize (int)			g = stereo (int)			h = copyright (int)			i = error protection (int)			j = emphasis (int)			k = bitrate (int)			l = extension (int)@F <a> <b> <c> <d>			Status message during playing (frame info)			a = framecount (int)			b = frames left this song (int)			c = seconds (float)			d = seconds left (float)@P <a>			Playing status			a = 0: playing stopped			a = 1: playing paused			a = 2: playing unpaused@E <a>			An error occured			Errors may be also reported by mpg123 through			stderr (without @E)			a = error message (string)Info about the equalizer control:Cold Feet Audio Patch for MPG12310.07.2002This is a dirty little hack to enable the equalizer in mpg123'sgeneric_control interface.  It works like this, there are twodifferent channels on the equalizer and 32 frequencys.The hack just enables mpg123's built in equalizer to run real-time.We haven't built in any capability to save the eq, you're frontendwill have to handle that part, and init the eq on the startup ofmpg123.K, it works like this:#./mpg123 -R -  <---- This command will start mpg123 in 'frontend' mode.If you want to send it some eq values you'd send it:eq X Y V[ENTER]X = The channel.  It can be either 0 or 1.  I haven't put any error checking    in, so it probably wouldn't be a good idea to go out of bounds. (integer)Y = This is the frequency, it can be 0 to 31.  0 being closer to treble and    31 being closer to bass. (integer)V = The raw value of your equalizer setting.  I've found that the values work     best between 0.00 and 3.00.  When mpg123 starts up, all of them are set    to 1.00.OK, have fun!  If you have any questions or found some bugs, please contactnutcase@dtmf.orgThanks,nutNote by Thomas Orgis: The contact appreas to be dead.