Yeah, I'm not sure that terminology in that sense has been defined yet. I would discount previous prototypes that aTc has received; in this context we're only really interested in the ones sent out in the past month or two, and to my recollection this is the first one out of the small dozen or so ED was planning to build. Good news in any case though, of course.Yes. I'm not sure what the terminology is, but (rightly or wrongly) see this as a first release candidate iteration.
From the comments it sounded like the claim was that nothing has been accomplished until this current version has been sent out
Well my point is that people have had prototype units for quite a while and hardware and software development hasn't been totally been hindered with having less that optimal units.
From the comments it sounded like the claim was that nothing has been accomplished until this current version has been sent out.
They don't want to say, because people may be disappointed if there are delays.this question has probably been asked alot but how much longer would you say till mass production?
PulseAudio does not support any kind of hardware mixing, though. The daemon only configures a single ALSA instance for all incoming audio data - all the conversion and mixing work is literally forced onto the CPU.Would save a few % of CPU power (though using ALSA, the mixing seems to have about 1 - 2% CPU usage).
It has in the past, from what I understand. Changes in kernel versions tend to fix or break things...Is pulseaudio working in pyra prototypes ?
Mixing is basically just adding samples together, so not really a hard task for such CPU, even if it needs to do it 48000 times per sedond. Don't know about the conversion though.PulseAudio does not support any kind of hardware mixing, though. The daemon only configures a single ALSA instance for all incoming audio data - all the conversion and mixing work is literally forced onto the CPU.
If you "basically just add samples together", you'll end up with lots of clipping and distortions. It takes a lot more math to mix audio samples together without thrashing them, especially if you need to mix more than just two streams together. Many implementations use dynamic compression, exploiting the ability to look ahead for a few samples. Hardware mixers usually just throw more precision at the problem to keep things relatively simple and lossless.Mixing is basically just adding samples together
PulseAudio has a wide selection of available resampling algorithms - you can throw a LOT of CPU cycles at this task if you want a good audio quality.Don't know about the conversion though.
God knows. It's not something we need to ship units, so I don't think anyone's looking at it at present.So - how do we get the TI DSP driver back into a current kernel?
Prayers, shady money sent to Ti employees, begging and maybe a notaz and a few clones of notaz.So - how do we get the TI DSP driver back into a current kernel?
Agreed. But - it would be nice to have a plan?God knows. It's not something we need to ship units, so I don't think anyone's looking at it at present.
I'm all for cloning of Notaz - but I'd not want to wait 15-20 years for them to become useful. So, we're going to need a time machine first - and you have a sci-fi puppet robot for an Avatar, so you can get to work on that part.Prayers, shady money sent to Ti employees, begging and maybe a notaz and a few clones of notaz.