crkm wrote: > Hi Philippe > Here are a few observations of my current working system > Windows 7 (as Administrator), LMS 7.8.0 - 1395409907, squeeze2upnp > 0.2.0.0, Renderers currently working: Foobar2000 (1.3.5) on same PC > (connected through a plugin to Airport Express driving stereo), > CocktailAudio X10 on wireless Home Network. > > To get this going, the problem boiled down to the <buffer_dir> entry in > the config .xml file. According to Windows, access to all the example > directories given below are the same (Full Control, from running as > Administrator). I observed 3 different behaviours, the first two > resulted in no sound via Foobar > 1 sq_run_device:849 [00484BA4]: cannot access . in log file. Example > <buffer_dir>.</buffer_dir> (default) full address of squeeze2upnp > location (Downloads directory on disk G:). No sound > 2 No 'cannot access message' in log file but no sound. Example > <buffer_dir>\</buffer_dir> > 3 Full operation and sound via CA and Foobar. Example > <buffer_dir>G:\</buffer_dir> <buffer_dir>G:\Garmin\</buffer_dir> > I couldn't detect a pattern except the more complicated (long) the > directory name the less the chance of operation. > Normally, you should use '/' and not '\'. I will check later today, but '\' should work still without a need to double it '\\', but I need to verify. Meanwhile, it is better to use '/'. The log error "cannot access" happens when I do a system call that fails to verify that the directory is accessible for rw operation. The no sound very likley mean that just setting '\' means that there is a mixup with regard to where the temp files are stored so they cannot be retrieved when required by the upnp player. I do not understand well you conclusion wrt "long names".
> > A couple of other observations > In 0.2.0.0 the first time the config.xml is saved there are no entries > under the device category (With 0.1.4.0 entries appeared for both CA and > Foobar) > I can't stream to both Foobar and CA at the same time > I'm still playing around and have noticed a few of these lines in the > logfiles > CallbackActionHandler:639 Error in action callback -- -113 (cookie > 00000182) especially when streaming to the CA but it doesn't seem to > affect the stream. I've experienced several drop outs using Foobar, > along with the occasional CallbackActionHandler errors. > > Hope this helps and Thanks again for this great program > crkm The -113 error is not an issue. The can't stream to both in // is totally abnormal. I have 5 players to which I stream in //, for my tests LMS 7.7.2 - 5 radio, 3 Boom, 4 Duet, 1 Touch, 1 SB2. Sonos 2xPLAY:1, PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBMC, Foobar2000, XBoxOne (sort of) ------------------------------------------------------------------------ philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=102496 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
