paul- wrote: > the pCP compiled version of squeezelite defaults to the same model, so > certain things know it's pCP. We have to be careful with model > name.....I know somethings depend on it. (I forget which things though > :) > > I think I could easily make a standard model name, that would allow you > to grab it in material.....
A standard model name would be great, Basically, just anyway to know this is a BT output, as opposed to the regular output. I guess, you could also have SqueezeLitePCP for the standard output? Then I could look for a ico to use for pCP (perhaps tux?). Squeezelite has model (squeezelite) and modelname (SqueezeLite). Only modelname is configurable, via its -M commandline option. Are you sure things don't depend on the *model*, and not *modelname*? *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. ------------------------------------------------------------------------ cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=111972 _______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
