First up, please excuse me if this message looks weird or badly
formatted. I am posting from Google Groups (old layout, it's faster)
because OrangeFrance's NNTP server is a dodo. Again. :-/
On Mar 11, 3:27 pm, Jim Lesurf <
no...@audiomisc.co.uk> wrote:
> I presume the situation isn't helped by having what seems like more than
> one 'stack' around, etc...
I don't imagine that would be a big problem, for there's one stack
unlikely to be further developed for a system unlikely to be further
developed... and there's the other one. ;-)
Though, if you follow the ROOL forums, I've had an interesting time
getting USBMIDI working. Both the Beagle and the Pi play perfectly, my
Maestro hack is testament to that.
Reading in MIDI data, on the other hand, works without a problem (zero
byte stuffing aside) on the Pi, but consistantly fails on the Beagle.
Looking at the source for some guidance as to what may be different, I
gave up. Looks like completely different base source to me!
It remains to be seen how compatible DavidS's replacement will be.
This isn't to say audio devices will run into the same problems, I
just think for some stuff a lower level than DeviceFS might be better.
> I accept that and quite understand it. But do contrast it with the Linux
> situation. Yes, people like Red Hat, Canonical, etc, do inject a lot of
> money and paid-time work. But there are also a large number of enthusiasts
> who make real contributions out of interest, etc.
Yes, there are. Now if we pick a figure out of the air and say for
every 250 users we have one person willing to donate their time; you
can see how there would be dozens and hundreds for Linux (big
userbase, wide deployment) and the few we have for RISC OS. The ROOL
guys, those who worked on NetSurf, the various Unixy ports of things.
The people who help out along the way with utils, tools, or maybe just
suggestions. Statistically we aren't short of people, it just looks
that way because we have fewer people overall.
So you pretty much can't compare RISC OS and Linux. It's like
comparing processor instructions, you can make lots of charts and
powerpoint slides, but at the end of the day they're just different
things.
I'd like RISC OS to have the deployment and support that is offered to
Linux. I'd also like to win the lottery...
> The quibble I'd make is with your use of the term "professional audio" and
> the assumptions that gives to people
[...]
> High quality audio playback in the home isn't a "professional audio" task.
> It is something many thousands of people have come to take for granted.
I don't want to cause you to cry man-tears here, but I suspect the
*majority* of people are waking up to the fact that 128kbit MP3 is
crap.
For my video recordings, I use 128kbit AAC+ (the max the firmware
offers, sounds a lot richer than 128kbit MP3), for my own audio I use
256kbit; or 160kbit for stuff transcoded from YouTube/Youku.
My audio appears on the end of (analogue) phono sockets, or a 3.5mm
headphone jack.
Given the vast range of mobile phones, PDAs, tablets, etc and the less
impressive range of codecs supported out of the box, I would not
imagine people's ideas of audio quite match up to yours. In fact, the
stuff most people listen to is quite possibly painful for you - which
might explain why "pop" sounds markedly different to the way it did
when I was young. Oh, I'm not being elitist here, I have stuff like
Deacon Blue, Erasure, The Cure, Tears for Fears, etc etc in my
playlist and you can spot an '80s track a mile off. It is quieter and
it sounds "richer". Hard to describe, maybe something lost in analogue
recording tech is ultimately something gained?
> And one of the off-putting features users in this area face is the wish to
> have a small, compact, easy-to-use and *mechanically silent* device to play
> the audio as they *they* choose rather than being tied into or limited by
> what someone else (Apple, etc) decided you can do - and can't!
With our choice of crappy codecs and piles of MP3s, we can do exactly
this with no add-on hardware. Load OS, load MP3 player, point it to
playlist, plug speakers into the headphone jack. That's pretty much
what the *domestic* market is asking for - look to mobiles/tablets/
webradios to see the audio output is not an item of great importance
despite a lot of use of them as audio players.
> But as things stand it is doing so by-passing RO.
Ditto a number of things. Modern script/HTML5 support. Video codecs.
Proper support for Unicode. Shall I go on?
> Thus meaning one area which leaves RO looking lame and old-fashioned to many
> potential users.
...but, I'd wager, possibly not for its (lack of) audio support, in
the eyes of many.
> what will a RO system look like if it is limited, say, to analogue outputs
> only, stereo, 48k only,
Just like my eeePC.
You might be able to get a plug-in USB thingy for 5.1 audio. But that
will require *manufacturer* *provided* drivers to get it to work. As
it is I have a "Realtek HD audio" device inside, and it is hit and
miss as to whether or not it is "seen" by some software.
> No HDMI or optical or USB audio.
HDMI would be chip specific. For starters, does HDMI audio on the
Beagle/Pi work under Linux? If so, is there sufficient documentation
to do it under RISC OS (OMAP3, ought to be; Pi, not so sure). Once you
have the hardware capable and the spec to code to, you just need to
find somebody willing to do it - if not yourself, that is.
Optical - I don't think this is relevant. Is there anything RISC OS
runs on that has an optical audio output?
USB - copy'n'paste what I said for HDMI except the complication of the
fact that I don't think USB audio runs in realtime like the RISC OS
sound system, so it may need more work.
In programming, there is a WORLD of difference between:
"We need this!"
and:
"Here's the specs, datasheets, and hardware. Is anybody willing to
take on this?"
> It will keep RO systems in the "Toy" category I fear.
I think of RO more as an embedded platform. And yes, you might say
"perfect for an embedded media player" in which case I would counter
with "cheap, cute front end UI, and phono sockets would probably be
enough to please the masses". Maybe a self-switching headphone jack on
the front for private listening.
> Many people simply don't know what they don't have.
Which is, perhaps, why we put up with rubbish.
> If someone hasn't heard really good audio they may have no concern out
> of lack of experience...
I have heard supposedly good audio. I use MP3s and listen with €30
headphones (proper headphones, not those ear-buds, unless I'm
outside). Why? The proper audio was the gold-plated special. I was
supposed to swoon when he mentioned the name of the manufacturer. I
was supposed to be entranced with a thingummy (eq box?) that had more
buttons and indicators than the Shuttle. Perhaps more than every
Shuttle ever added together.
From this, I took home three things:
1. Holy Hell that cost a bomb. I simply cannot justify dropping a
grand on a flippin' SPEAKER. Even after winning the lottery, I
wouldn't be able to justify those sorts of prices for something to
install into a living room. A theatre, perhaps. A living room? No.
2. It didn't distort when the sound was cranked up enough to feel like
a physical assault. I could actually feel the bass kicking me in the
gut. But it didn't distort.
It didn't impress much either. What is it with cranking the thing up
for a demonstration? It is like teenagers in the '80s that spent
endless hours outside revving their Ford Cortinas, because a revving
engine gives you such a hardon. Well, that's about the only thing I
can think to justify revving for hours and hours. Ditto blasting my
ears with rock. A much better test would have been an orchestral piece
that crosses the octaves to see how well fidelity is handled - bass
and treble together.
3. What a twat. For both of the above reasons.
So, I stick with audio stuff I can afford and I don't lose sleep if it
isn't absolutely perfect. I'm far more bothered by the massive number
of (to me) highly visible artefacts in HD pictures than with the
bitrate of my sound. Just so long as it is better than 128kbit!
> The pool of existing RO users is small.
...which is why you are finding difficulty in getting this done.
> But am totally out of my depth when it comes to things closer to the
> real hardware layer like a USB stack, etc.
I think many are. There are few people that understand the magic
incantations that gets USB working. Because it isn't just USB you are
talking about. It is the RISC OS sound system, how RISC OS deals with
interrupts, USB, and a ton of glue to get it all talking. This is, of
course, assuming that your request is even possible without a complete
rewrite of how audio is handled by RISC OS.
> module... As thinks stand I have no idea how to get a version of that
> working on an ARMiniX. Even given the sources, no idea how to adapt it. So
ARMini - that's basically a Beagle, right? IIRC the audio is handled
by the "helper" chip, the TPS65950 [TRM:
http://www.ti.com/lit/ug/swcu050g/swcu050g.pdf
] Audio input is hooked to AuxL/AuxR. Good luck, it looks kinda
complicated to set up. I'd imagine it'll interrupt every so often so
you just read data as requested.
Take a look at the audio output to see how to address/talk to the IC.
> just like I wish I was able to still climb around on top of volcanos, etc. :-)
*Still*?!
> With Linux I can get somewhere with ALSA and things like the HID libraries.
Where the hard work has already been done.
> So a chance to draw in people becomes a silence because
> what I'd have to say would put them off! :-/
Makes sense, if they're looking for something RISC OS doesn't do.
Maybe, someday...
Best wishes,
Rick.