Triode, I'm trying to get my Arcam rDac working with an embedded Linux
platform. Can you give me the patch that you made in the kernel and/or
ALSA modules in order to get it detected properly?
Right now I just get the infamous "cannot get freq at ep 0x1" message. I
do see it listed when I use "ap
My Furutech GT40 should arrive on Monday and I will report back when set
up. I just received a technical data sheet and understand that it's a
USB Audio class 1 with adaptive USB based on Tenor TE7022L USB chip
limited to 24/96, so if I understand correctly should not need external
USB hub (though
I'm sure if I spent 500 quid on a cable I'd hear a difference too I
was thinking more, is it worth spending £30 rather than £1, but I think
I got the message :-)
BrynClarke's Profile: http://forums.slimdevices.com/membe
BrynClarke wrote:
> Many thanks. Any special cables? or bog standard USB 2.0 (with the
> right style of connector)?
> Also, when connecting Furutech GT40 USB DAC/ADC to computer to record
> vinyl, any idea if I can just plug computer into another port on the hub
> which links the SBT & GT40, or
googleli wrote:
> My first post here - thanks for the patch. Works perfectly with my
> Antelope Zodiac Gold. If anyone has some 384/32 bit material I will test
> if the SBT can output this format to my Zodiac Gold via Coax.
Anything above 192k will need to be resampled on the server.
-
My first post here - thanks for the patch. Works perfectly with my
Antelope Zodiac Gold.
googleli's Profile: http://forums.slimdevices.com/member.php?userid=55753
View this thread: http://forums.slimdevices.com/showthread.p
Triode wrote:
> SBT is the host and the dac is plugged in as a usb device to the hub.
> The shape of the plugs should prevent you plugging the wrong way round?
Many thanks. Any special cables? or bog standard USB 2.0 (with the
right style of connector)?
Also, when connecting Furutech GT40 USB
BrynClarke wrote:
> Does it matter which way round the USB hub is connected? (main plug into
> SBT or into DAC?)
> And are basic USB cables sufficient or are fancy cables desirable?
> Thx
> Bryn
SBT is the host and the dac is plugged in as a usb device to the hub.
The shape of the plugs should
Does it matter which way round the USB hub is connected? (main plug into
SBT or into DAC?)
And are basic USB cables sufficient or are fancy cables desirable?
Thx
Bryn
BrynClarke's Profile: http://forums.slimdevices.com/memb
thanks to trioide for this, just applied the 0.7 kernel and feeding data
through to the NuForcce ICON2's only digital input, the USB port
will report more findings as they come along but thanks for this, SBT is
sounding good!
--
Thank you Triode - this is amazing. I am streaming 24/192 to my receiver
and it sounds wonderful. Fantastic!
paulcordingley's Profile: http://forums.slimdevices.com/member.php?userid=52867
View this thread: http://forums.sl
Triode wrote:
> I'm not sure that it is yet - its something for the tweakers to tweak...
> It should be off by default, but you can enable it and let me know if
> you notice any difference.
Interesting...
A few weeks ago I started using Inguz and for some reason have had a
specific re-buffering
Triode wrote:
> I'm not sure that it is yet - its something for the tweakers to tweak...
> It should be off by default, but you can enable it and let me know if
> you notice any difference.
Option enabled! I'll let you you know if I hear any difference.
Bob
---
bobertuk wrote:
>
> What is the 'Kernel Idle Option' meant to do?
> I understand that it is intended to prevent the Touch CPU from idling
> when playing music. But why is this advantageous?
>
I'm not sure that it is yet - its something for the tweakers to tweak...
It should be off by default,
cfv wrote:
> Hi Triode,
>
> I found an old powered hub in my electronics graveyard and now the CDQ
> plays high bitrate files without pops, just to let you know. What I
> would like to know is whether there are any advantages if I go with the
> hub even though I only need 44.1/48 support. Would
Hi Triode,
I found an old powered hub in my electronics graveyard and now the CDQ
plays high bitrate files without pops, just to let you know. What I
would like to know is whether there are any advantages if I go with the
hub even though I only need 44.1/48 support. Would really appreciate
your f
Hi Triode,
What is the 'Kernel Idle Option' meant to do?
I understand that it is intended to prevent the Touch CPU from idling
when playing music. But why is this advantageous?
Bub
bobertuk's Profile: http://forums.slimd
Triode wrote:
> I have added the new applet to the main 3rd party list so people should
> see it without needing to add the special repositories defined on the
> first post here. Once there are a few more positive install responses,
> I'll start a new thread to discuss the new applet without the
Triode wrote:
> Please try and report here that it installs ok for you...
Hi Triode,
it works flawlessly with my CDQ. I did a firmware update, installed it
and tried it with both Coax and USB. Coax plays my 96kHz test files
perfectly, USB works great with the no-hub workaround and Red Book
FLA
I have added the new applet to the main 3rd party list so people should
see it without needing to add the special repositories defined on the
first post here. Once there are a few more positive install responses,
I'll start a new thread to discuss the new applet without the confusion
of the test
cfv wrote:
> I bought my SBT a week ago and stumbled across it the same day. Since
> then, I've been using Kernel #1 with my 8200CDQ for flawless Redbook
> FLAC playback without a hub. If I install the new applet, will this
> option still be available? So far I don't need higher bitrates and
> th
Triode wrote:
> Thanks for testing. I've just added a new applet to my usbaudio
> repository - Enhanced Digital Output.
>
> The aim of this applet is to provide a user friendly way of installing
> the custom kernel and selecting the output device. I've posted here to
> get a few people to test
Thank you triode! With a hub, now there is no ticks with my MF V-link
II.
terra27's Profile: http://forums.slimdevices.com/member.php?userid=55374
View this thread: http://forums.slimdevices.com/showthread.php?t=93310
terra27 wrote:
> Hi Triode,
>
> Thank you for all your contribution for the USB support. I tried a few
> kernels (including the most recent #6) and wanted to report my issue.
> The USB output works wonderfully with my XMOS based DAC. Unfortunately,
> it has an issue with my MF V-LINK II. There i
Hi Triode,
Thank you for all your contribution for the USB support. I tried a few
kernels (including the most recent #6) and wanted to report my issue.
The USB output works wonderfully with my XMOS based DAC. Unfortunately,
it has an issue with my MF V-LINK II. There is a tick sound every 5 to
10
Hello Triode,
thank you very much for your effort. I have installed the applet this
morning the "old way". Using the coax from Touch, finally I can send
176,4 and 192khz to my ASUS Xonar Essence One.
USB, I still didn`t try. I guess I need a hub? Well, I am happy. It
works great via coax.
Tha
Triode wrote:
> Look at the processes running on the server - for 192k playback normally
> you will see a sox process for resampling assuming you are playing a
> flac.
OK :)
Had to disable Inguz as sox is running all the time with that!
At first play, the 192k sample did nothing. The DAC has a
bobertuk wrote:
>
> I'm using a Lavry DA10 DAC connected via optical but have no way of
> telling if it's playing 24/192 or is being downsampled by sox. Is there
> any way of seeing what is beng played?
>
Look at the processes running on the server - for 192k playback normally
you will see a s
Hi Triode,
I got hold of a 24/192 sample from LINN and it does play.
I'm using a Lavry DA10 DAC connected via optical but have no way of
telling if it's playing 24/192 or is being downsampled by sox. Is there
any way of seeing what is beng played?
Thanks
Bob
-
Triode wrote:
> The applet also supports 24/192k on the coax digital out. [It may work
> with the optical out, but optical interfaces are often not specd to run
> at 192k] Note that the internal analog output is disabled when using
> it as it does not support 192k.
Wonderful :)
I'll give it
bobertuk wrote:
> Sorry to butt into this thread with something not directly related to
> USB DAC's...
>
> This seems to be saying that you completely bypass the Touch internal
> DAC and can send 24bit/192K data to a USB DAC. If this is so, can it be
> done for any other external DAC via optical
Triode wrote:
> Hey that's good...
>
>
> Yes this is added by the applet - it seemed to me to be where the output
> selections should be.
>
>
> Afraid not - that means audio needs to go through the software layer
> which replicates the streams, this causes quite a bit of additional
> processi
indypants wrote:
> Hi Triode,
> Seems to be working like a dream.
> I did a factory reset, then a firmware update, then I installed your
> applet. Everything worked just as you described.
>
Hey that's good...
>
> I notice there is a "Digital Output" option in the audio settings.
>
Yes this i
Hi Triode,
Seems to be working like a dream.
I did a factory reset, then a firmware update, then I installed your
applet. Everything worked just as you described.
USB audio is still working brilliantly, and 24/192 still fine from the
optical/coax out.
I notice there is a "Digital Output" option
Thanks for testing. I've just added a new applet to my usbaudio
repository - Enhanced Digital Output.
The aim of this applet is to provide a user friendly way of installing
the customer kernel and selecting the output device. I've posted here
to get a few people to test it and if positive will
Triode;698973 Wrote:
> Could you reinstall kernel #6 and try again? I think it is working now
> with 192k playback and usb.
It must be late where you are?!
Anyway, 192kHz SPDIF working perfectly with the latest kernel #6.
(Linux SqueezeboxTouch 2.6.26.8-rt16-332-g5849bfa #1[usb] PREEMPT RT
S
Could you try kernel #6 again? I think it is working now with 192k
playback.
--
Triode
Triode's Profile: http://forums.slimdevices.com/member.php?userid=17
View this thread: http://forums.slimdevices.com/showthread.php?t=
Looks like I'm not doing very well with kernel #6 - please use #5 for
the moment...
--
Triode
Triode's Profile: http://forums.slimdevices.com/member.php?userid=17
View this thread: http://forums.slimdevices.com/showthread.
Running into an Audioengine D1, which is actually asynchronous (although
its makers say otherwise).
44.1kHz CD rips: checked for sound quality (excellent) and observed
switching between 44kHz and 44.5kHz
88.2kHz Linn Records download: checked for sound quality (excellent)
and observed switching
Sorry for the delay replying...
USB is now working fine, but I'm seeing problems with 192K over
optical/coax. MDAC has trouble locking on at all, and the CDQ locks on
but is suffering constant dropouts. I tried swapping back and forth
between kernel#5 and #6, and I could consistently get 192K to
indypants;698778 Wrote:
> Just tried kernel#6 with the MDAC and CDQ and I'm not getting anything
> from the USB. 192K is working OK from optical and coax though.
> Reloaded kernel#5 and everything is working again.
Could you try this again - I've updated kernel #6 to a new version
which removes
indypants;698778 Wrote:
> Just tried kernel#6 with the MDAC and CDQ and I'm not getting anything
> from the USB. 192K is working OK from optical and coax though.
> Reloaded kernel#5 and everything is working again.
With the hub? It should be the same - I need to look at it again :(
--
Triode
Just tried kernel#6 with the MDAC and CDQ and I' mnot getting anything
from the USB. 192 is working OK from optical and coax though.
Reloaded kernel#5 and everything is working again.
--
indypants
indypants's Profile: http
I've just added a new kernel (Kernel #6). This supports usb and the
192k digital ouput as kernel #5, but the non working 192k analog
output is removed.
I intend to release this with a simplified installer applet, so am
looking for people to test this out to see if it works ok. Please
could a
indypants;698736 Wrote:
> Intersetingly, I notice that the USB buffer on the MDAC is more stable
> now, being rock solid at 50% with the hub in. On kernal#1 and no hub,
> is was going up and down a lot.
Yep - this is the way it works with other players. The hack in kernel
#1 exploits the fact t
Fair comment :-)
The Hama hub has just turned up and it's now in place with kernal#5
running absolutely fine. Tested into the MDAC over USB with 96K and
192K. I wasn't expecting the 192K to work, but it gets downsampled to
96K, which is cool.
Sounding good!
--
indypants
--
indypants;698728 Wrote:
> So what are your thoughts on the effects of the Isolator?
> Placebo or not?
Must admit I've not spent a long time listening to the differences. I
have spent more time building new kernels and trying to get the usb
support to wotk in the first instance. I must get back
indypants;698727 Wrote:
> Thanks John. I must admit, it had already been my intention to put the
> Isolator between the hub and the DAC, but probably for the completely
> wrong reason. I was under the (false?) impression that the Isolator did
> something to stop the power feed getting through, an
Triode;698629 Wrote:
> Same isolator I have and I think you our ordering the Hama hub - I can
> confirm this combination is working for me.
So what are your thoughts on the effects of the Isolator?
Placebo or not?
--
indypants
-
JohnSwenson;698626 Wrote:
> If using Triode's approach of a high speed hub in front of your async
> DAC do NOT use the isolator between the Touch and the hub, put the
> isolator between the hub and the DAC.
Thanks John. I must admit, it had already been my intention to put the
Isolator between t
Triode;698676 Wrote:
> Looks like it - though I remember the price being slightly different,
> but I think the comments look like those against the one I bought.
> [key point is it needs to be a high speed hub with an internal
> transaction translator]
someone in the comments reckons it has a s
gh0st;698672 Wrote:
> thanks - is this the fella?
> http://www.amazon.co.uk/Hama-USB-2-0-Hub-bus-powered/dp/B0017X0R20/ref=sr_1_1?ie=UTF8&qid=1333146208&sr=8-1
>
Looks like it - though I remember the price being slightly different,
but I think the comments look like those against the one I bough
Triode;698670 Wrote:
> Anything other than kernel #1 will need a hub. Kernel 1 has a
> workaround specifically for this, but is limited to 44/48k sampling
> rate and only works with some dacs such as MDAC.
>
> If you want to play higher resolution I suggest getting an external
> hub, otherwise
gh0st;698666 Wrote:
> another field report...
>
> setup:
> MDAC (latest beta firmware)
> SBT with TT3.0
> source material 16/44.1 & 24/96 flac and 320k spotify (thanks Triode,
> highly superior to the official plugin :)
>
> results:
> Kernel #1: works fine provided the buffer in TT3.0 is set to
another field report...
setup:
MDAC (latest beta firmware)
SBT with TT3.0
source material 16/44.1 & 24/96 flac and 320k spotify (thanks Triode,
highly superior to the official plugin :)
results:
Kernel #1: works fine provided the buffer in TT3.0 is set to 5000. I
haven't tried every graduation i
indypants;698597 Wrote:
>
> I used this one http://electronicsshop.dk/?id=1038
Same isolator I have and I think you our ordering the Hama hub - I can
confirm this combination is working for me. As John says, connect the
hub to the player and the isolator between it and the dac.
--
Triode
--
A note on this (and other) USB isolator, it cannot run at high speed, it
will run full speed but it will NOT run at high speed. Thus you cannot
use it with a DAC that is running at 192 (which requires high speed
mode). Some of the DACs which support 192 will "downgrade" to using
full speed mode if
For anyone interested, I've just been playing around with a USB galvanic
isolator between the SB Touch and the DAC (Audiolab 8000CDQ). Here are
the comments I posted over at Pink Fish. I'm wondering if this is
simlar to the effect that others have reported by installing the
soundcheck mods?
> My
Hi Trode,
I've just got my SB Touch back from JohnW having been itching to try
out your modifications for weeks now...
Well, your kernal#1 is working brilliantly with 44/48K and HDCD
material into both the MDAC and 8200CDQ. I also had a quick try with
Kernal#4 and was able to get 192K over SPDIF
Triode;697101 Wrote:
> I've tested again, 176/192 is broken on the internal dac (wrong speed),
> but I believe works on the spdif output [which is what I was testing
> with mostly and was my real target for this]. Please constrain testing
> to the spdif output at present.
Looks like 176/192 doe
jackocleebrown;696803 Wrote:
> Just updated to the latest applet and kernel.
> On the "DAC info" page I don't see the Momentary freq changing (it is
> just at 44104Hz all the time) but if I ssh into the touch and "cat
> /proc/asound/DAC/stream0" repeatedly then I very occasionally see it
> flick
JohnSwenson;697100 Wrote:
> Aha! I was playing a 192 WAV file which of course streams PCM. I'll
> change it and send flac for the wav.
>
> Thats a strange limitation that SP will not receive 192 PCM. Is that an
> explicit limitation or just that it can't keep up?
It needs a change to lms and sq
I tried with Kernel #5 into the Rega DAC at 192kHz, and it sounded
great. It's the first time, I ever was able to light the 192kHz LED, so
it was quite an exciting moment, exciting enough for me to splash out on
a whole album to celebrate my new-founf freedom!
http://www.linnrecords.com/recordin
JohnSwenson;697007 Wrote:
> I tried the latest applet and kernel, I could not get 192 on the
> internal DAC to work. I currently don't have anything that can read 192
> S/PDIF so I couldn't try that either.
I've tested again, 176/192 is broken on the internal dac (wrong speed),
but I believe wor
Triode;697024 Wrote:
> Can I check - you need to use flac with client side flac decode as
> squeezeplay does not support 192k for pcm playback. Are you doing
> server side flac decode? Also this is with hw:CARD=fab4 as the output
> device?
>
> There's special code in the kernel for 0404 - if y
dsdreamer;696999 Wrote:
> I've had an AudioEngine D1 plugged into a USB2.0 hub and thence into the
> Touch, and it has been working very well for 44.1kHz ripped CDs and
> 24/96kHz FLAC downloads. Today I tried to play a low quality stream
> from a local radio station and got a "Pinky and Perky" i
JohnSwenson;697007 Wrote:
> I tried the latest applet and kernel, I could not get 192 on the
> internal DAC to work. I currently don't have anything that can read 192
> S/PDIF so I couldn't try that either.
>
Can I check - you need to use flac with client side flac decode as
squeezeplay does no
I tried the latest applet and kernel, I could not get 192 on the
internal DAC to work. I currently don't have anything that can read 192
S/PDIF so I couldn't try that either.
With the internal DAC I get a LOUD pop, then silence. The player thinks
its playing but nothing comes out. LMS must have g
I've had an AudioEngine D1 plugged into a USB2.0 hub and thence into the
Touch, and it has been working very well for 44.1kHz ripped CDs and
24/96kHz FLAC downloads. Today I tried to play a low quality stream
from a local radio station and got a "Pinky and Perky" impression.
Nevertheless, the USB
CardioFitness;696818 Wrote:
> I got a Nad M51 2.0 usb which needs to install the 2.0 USB drivers on
> windows but not on iOS because supposely already has them. So any
> chance it will work with the touch ?
> Also so far only up to 96 is working right ?
If it works with linux and osx uac 2.0 the
I got a Nad M51 2.0 usb, can I be a tester ?
I will need a external high speed hub right, what do you suggest ?
--
CardioFitness
CardioFitness's Profile: http://forums.slimdevices.com/member.php?userid=54730
View this thr
Triode;696686 Wrote:
>
> The new kernel includes:
> - possible work around for the rDAC issue (based on my option 2, it
> ignores the parameter from the dac and uses a smaller parameter - the
> question is whether the dac likes this..?)
PietB;696786 Wrote:
> No high speed usb hub, tried hires
MWelschenbach;696794 Wrote:
> I observe the frequency alternating between 96005 and 96006 Hz or
> between 192010 and 192011 Hz respectively about every second, sometimes
> even two or three seconds. Is this as it is supposed to be?
Yes it should alter as it's a feedback mechanism - this is what
Triode;696789 Wrote:
> So the key issue for async is that the momentary frequency should change
> based on the feedback from the dac. Sometimes it will be too high then
> too low, but I would expect it to update about once per second when
> working correctly. This probably does need an external
Thanks Triode for quick response
I don't have a high speed usb hub, but will try tomorrow for sure
--
PietB
PietB's Profile: http://forums.slimdevices.com/member.php?userid=39880
View this thread: http://forums.slimdevices
PietB;696786 Wrote:
> No high speed usb hub, tried hires 96000 hz now and is playing fine, no
> hickups
> Only resetted the touch and rDac before playing.
> playing another song and switching to 16 bit 44, hickups
> Switching back to 24/96 agan playing fine, also 24/88
> Info menu for the dac sh
Triode;696776 Wrote:
> Hum - that's a pity. Do you have a high speed usb hub between the dac
> and the touch? Does the momentary frequency update when it is playing
> on the info menu for the dac?
No high speed usb hub, tried hires 96000 hz now and is playing fine, no
hickups
Only resetted the
Kernel #5 and plugin 0.7 play fine with the Eximus DP1. Occasionally I
get dropouts for a couple of seconds but only with 192kHz files, though
the touch is connected to my NAS via ethernet. All other material plays
flawless.
--
MWelschenbach
-
PietB;696768 Wrote:
> Just tried, the touch didn't loop-reboot and my rDac is playing now over
> usb-out, however not constantly but hickups
Hum - that's a pity. Do you have a high speed usb hub between the dac
and the touch? Does the momentary frequency update when it is playing
on the info m
ste1;696725 Wrote:
> Hi Triode,
>
> I have tried this with a Musical Fidelity V-Dac 2. This is an asynch
> dac however I do not know if it is USB 1 or 2.
> http://www.musicalfidelity.com/products/V-Series/V-PSU/v-psu.asp
>
> I followed the instructions on page 1 of this thread last night and
MWelschenbach;696722 Wrote:
> Triode, what exactly do you mean by reset the output device?
Go into the usb dac menu and set the output device back to default.
--
Triode
Triode's Profile: http://forums.slimdevices.com/mem
Triode;696686 Wrote:
>
>
> The new kernel includes:
> - possible work around for the rDAC issue (based on my option 2, it
> ignores the parameter from the dac and uses a smaller parameter - the
> question is whether the dac likes this..?)
>
Just tried, the touch didn't loop-reboot and my rDac
Hi Triode,
I have tried this with a Musical Fidelity V-Dac 2. This is an asynch
dac however I do not know if it is USB 1 or 2.
http://www.musicalfidelity.com/products/V-Series/V-PSU/v-psu.asp
I followed the instructions on page 1 of this thread last night and
both applets insalled OK.
Problem
Triode;696686 Wrote:
> Best installation process is to: reset the output device, update the
> applet and then update the kernel. Then select your chosen output
> device.
Triode, what exactly do you mean by reset the output device?
--
MWelschenbach
I've just added a new kernel and updated the output selection applet.
Please try these two together as the kernel includes some changes which
require the new applet. Best installation process is to: reset the
output device, update the applet and then update the kernel. Then
select your chosen o
MWelschenbach;696681 Wrote:
> Kernel #3 and applet 0.6 are playing via Eximus DP1 dac (UAC2) material
> up to 24/192.
>
> Thank you very much Triode, I am deeply grateful for this.
Hey that's great news - and good to get another test case for uac 2.
--
Triode
---
Kernel #3 and applet 0.6 are playing via Eximus DP1 dac (UAC2) material
up to 24/192.
Thank you very much Triode, I am deeply grateful for this.
--
MWelschenbach
MWelschenbach's Profile: http://forums.slimdevices.com/mem
JohnSwenson;696600 Wrote:
> The internal DAC and S/PDIF is probably going to be more difficult.
> Their drivers have tables which take the desired sample rate and set
> processor registers appropriately. Unfortunately these tables only go
> up to 96. I did a quick look at this a couple years ago
Mnyb;696576 Wrote:
> Thanks, but being curios have you managed to do it now ?
As I mentioned previously, using kernel 4, 192kHz from the touch is
definately working with the UAC2 dacs I've tested with. A great piece
of work!
Regarding 192kHz over wi-fi - I'm not sure how representative my test
Triode;696572 Wrote:
> Answering this specific question. 192k playback is possible if the
> output device reports it as an avaliable rate. Squeezeplay (the
> playback app) queries alsa for the max samplrate supported by the
> output port and reports this to the server. The server then
> automa
Triode;696565 Wrote:
> I believe I know what is going on. I suspect it is because your dac
> asks for frequency reports every 128 ms, whereas other dacs we know
> work ask for them more frequently. There is a known limitation in the
> kernel usb scheduler code where infrequent requests get refu
Triode;696572 Wrote:
> Answering this specific question. 192k playback is possible if the
> output device reports it as an avaliable rate. Squeezeplay (the
> playback app) queries alsa for the max samplrate supported by the
> output port and reports this to the server. The server then
> automa
Mnyb;696022 Wrote:
> Is not 192k converted to 96k by the server ( with the eminent help of
> SoX ) .
>
> Even with this special kernel ?
Answering this specific question. 192k playback is possible if the
output device reports it as an avaliable rate. Squeezeplay (the
playback app) queries als
jackocleebrown;696408 Wrote:
> Using kernel 1 and 2 I get:
>
> asyc-dac hack: changing datainterval from 0 to 1
> 2:1:1: cannot get freq at ep 0x1
> iso: int: 2 usec: 12 c_usec: 0 maxp: 585 raw_mask: 000f tt_usecs:
> 464
> enable_periodic
> iso: int: 128 usec: 1 c_usec: 1 maxp: 3 raw_mask: 0
jackocleebrown;696409 Wrote:
> lsusb -v on my laptop returns:
>
Thanks - will look at this and get back to you.
--
Triode
Triode's Profile: http://forums.slimdevices.com/member.php?userid=17
View this thread: http://for
Triode;696383 Wrote:
>
> Do you know what bRefresh is for the syncpipe? (can you post the
> output of lsusb -v from another linux machine)
lsusb -v on my laptop returns:
Code:
Bus 006 Device 004: ID 0c56:0002 Billion Bright, Ltd
Device Descriptor:
bLength
Using kernel 1 and 2 I get:
asyc-dac hack: changing datainterval from 0 to 1
2:1:1: cannot get freq at ep 0x1
iso: int: 2 usec: 12 c_usec: 0 maxp: 585 raw_mask: 000f tt_usecs:
464
enable_periodic
iso: int: 128 usec: 1 c_usec: 1 maxp: 3 raw_mask: 1c01 tt_usecs:
12
fsl-ehci fsl-ehci.0: requ
jackocleebrown;696359 Wrote:
> I've not found a combination of parameters to get playback with aplay
> working from the touch. There is an entry for every attempt in DMESG:
>
> checking quirk table for id: 0c560002
> ALSA sound/usb/clock.c:227: 2:1:1: cannot get freq at ep 0x1
> ALSA sound/usb/u
Triode;696342 Wrote:
> Its using the alsa kernel driver so it would be good if you can make it
> play via aplay. I don't see what it wrong there - can you narrow down
> which hardware params don't work?
>
> Edit: can you also check any entries in dmesg?
I've not found a combination of paramete
jackocleebrown;696339 Wrote:
>
> is this down to the version of alsa? or are you bypassing alsa
> completely? I was trying to get it to work by fiddling with the aplay
> command line options.
Its using the alsa kernel driver so it would be good if you can make it
play via aplay. I don't see wh
101 - 200 of 318 matches
Mail list logo
