22 Dec
2002
22 Dec
'02
12:53 a.m.
The symptom of breaking up file name arguments that contain spaces is
produced by the original shell script and is not produced by the
modified one. Either you didn't really replace the shell script file
(changing all $* to "$@") or something else is also breaking arguments
at spaces. Anyway so long as falling back to something else when jackd
isn't running isn't working, the script doesn't really bring you any
benefit, does it?
On Saturday 21 December 2002 10:36 pm, Mark Knecht wrote:
Hi,
I played with this a bit more today. Thanks a lot for the
suggestion, but this is still not working. This change did not help
at all with the spaces problem. (Assuming I'm doing this correctly,
but it seems straight forward enough...)
My means of saying it doesn't work is that if I have a song called
"Chillin processed.mp3", and I click on the icon, alsaplayer starts,
but then doesn't play anything. I then look in alsaplayer's playlist,
and I see 'processed.mp3', so it looks like it dropped all of the
first part of the name. This repeats if I have a name with two spaces
like "Bills Chilling processed.mp3". I still just see the
processed.mp3 part and nothing plays. I can rename the mp3 to an
arbitrarily long name without spaces and it works fine.
As far as falling back if jack is not running, that still does not
work, so that may be an alsaplayer issue. Does Andy watch this list,
or should I report this question elsewhere? As I remember it his
email server blocks most everything that I've tried to send him
directly.
If someone can recommend a tool that supports jack and non-jack
audio, and plays wave, mp3 and CD's, please let me know and I'll try
that also.
So, still a frustrated normal user.
Cheers,
Mark
On Sat, 2002-12-21 at 10:06, Speaker to Vegetables wrote:
> Spacey filenames should be handled ok if you change $* to "$@" as
> shown below.
> ---- cut -----
> #!
> alsaplayer -o jack "$@" || alsaplayer "$@"
> ---- cut -----
>
> > 2) It doesn't fall back to alsa if jack is not running. I tried
> > changing the script to -o alsa, but that didn't work. Trying it
> > from the command line it complains about jack not running:
>
> This feature of the script depends on alsaplayer exiting with a
> nonzero "status" (aka "$?") if it is told to use jack and jackd
> isn't running. If this isn't happening, it could be considered a
> bug in alsaplayer (or perhaps in jack if jack isn't returning an
> appropriate failure indication to alsaplayer).
> --
> "Can you remember the future? Forget it!"
--
"Can you remember the future? Forget it!"