On Sat, 07 Feb 2015 22:08:19 +0100 (CET) Richard Levitte <[email protected]> wrote:
> In message <20150207211921.6161324b@md-DOTS-E2> on Sat, 7 Feb 2015 > 21:19:21 +0100, Maurizio Dall'Acqua <[email protected]> said: > > mau.h20> > mau.h20> On Fri, 6 Feb 2015 20:09:21 -0600 > mau.h20> "Matthew D. Fuller" <[email protected]> wrote: > mau.h20> > mau.h20> > On Thu, Feb 05, 2015 at 03:13:16PM +0100 I heard the voice > of mau.h20> > Maurizio Dall'Acqua, and lo! it spake thus: > mau.h20> > > > mau.h20> > > I would like to know if there's someone willing to help > me solve the mau.h20> > > problem that I have with rplay. > mau.h20> > > mau.h20> > I suspect rplay expertise is pretty thin; it's largely a > pretty mau.h20> > historical bit of software at this point[0]. The > latest release of it mau.h20> > is from 1999. The ctwm patches to > use it came in 3.1 which was more mau.h20> > than 20 years ago, and > haven't been meaningfully touched since. mau.h20> > > mau.h20> > But, you can start with testing with rplay(1). That'll at > least tell mau.h20> > you if your rplayd(8) config is working. > Possible a firewall could be mau.h20> > blocking it, though I > wouldn't expect to find such on localhost (and mau.h20> > while > rplay's big feature is running over the network, how many people > mau.h20> > are running their WM remotely as SOP?). mau.h20> > > mau.h20> > rplayd does have a big pile of options; it's not clear how > many of mau.h20> > them it only needs in special circumstances. If > it turns out not to mau.h20> > be working, it does appear to have a > --debug mode that might point you mau.h20> > in the right direction. > mau.h20> > > mau.h20> > > mau.h20> > > mau.h20> > [0] Of course, some would say the same about ctwm... but > this is our mau.h20> > playground, so we wouldn't stand for > that :) mau.h20> > > mau.h20> > > mau.h20> > mau.h20> In my installation rplay can't play any sounds. This is > because rplayd mau.h20> isn't properly configured. When I run rplayd > I get this error message: mau.h20> > mau.h20> rplayd: bind: Address already in use > mau.h20> > mau.h20> I don't think this error is due to the firewall. Moreover, I > have mau.h20> launched rplayd with debug option and only two more > clues are given. mau.h20> That is : > mau.h20> > mau.h20> rplayd: running as group audio (29) > mau.h20> rplayd: running as user nobody (65534) > mau.h20> > mau.h20> and if I change group and user the result is always the > mau.h20> address-already-in-use error message. > > Well, yeah. The address in use is about the TCP port, not the group. > 'man rplayd' might help. Usually, rplayd binds 5555/UDP and 5556/TCP, > so if there's another program listening to those ports, rplayd will > not be able to play. You need to figure out what other program is > listening to those ports. > > > Cheers, > Richard > I've found the process that was listening to port 5555/UDP. It was rplayd itself! I mean that I found the process rplayd already running at start-up. That explains the address-already-in-use error message, but it still remains the problem that by typing: rplay /some/file.wav rplay doesn't emit any sounds at all :/ Maurizio
