tascam gives a go for us428 @ alsa ...

tascam gives a go for us428 @ alsa ...

[karsten]

... if I understand this
http://www.tascam.com/forums/showthread.php?s=&threadid=28584
correctly.
please have a look at administrator Jims post near the bottom and tell me,
if you agree to include our us428 driver in alsa.
we would split the driver in two parts then, audio/midi handling and firmware.

karsten




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: tascam gives a go for us428 @ alsa ...

[Takashi Iwai]

Hi,

At Wed, 30 Apr 2003 13:56:34 +0200,
karsten wrote:
> 
> ... if I understand this
> http://www.tascam.com/forums/showthread.php?s=&threadid=28584
> correctly.
> please have a look at administrator Jims post near the bottom and tell me,
> if you agree to include our us428 driver in alsa.
> we would split the driver in two parts then, audio/midi handling and firmware.

great!

could you send the patch again (the one to the latest cvs version is
preferred)?  the current ALSA usb-audio driver has more generic layer
to absorb the device specific part, so perhaps we can integrate the
tascam driver more smoothly.


thanks,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Karsten Wiese]

[-- Attachment #1: Type: text/plain, Size: 2354 bytes --]

Am Montag 05 Mai 2003 15:14 schrieb Takashi Iwai:
> Hi,
>
> At Wed, 30 Apr 2003 13:56:34 +0200,
>
> karsten wrote:
> > ... if I understand this
> > http://www.tascam.com/forums/showthread.php?s=&threadid=28584
> > correctly.
> > please have a look at administrator Jims post near the bottom and tell
> > me, if you agree to include our us428 driver in alsa.
> > we would split the driver in two parts then, audio/midi handling and
> > firmware.
>
> great!
>
> could you send the patch again (the one to the latest cvs version is
> preferred)?  the current ALSA usb-audio driver has more generic layer
> to absorb the device specific part, so perhaps we can integrate the
> tascam driver more smoothly.
>
>
> thanks,
>
> Takashi

this is part 1 of usbus428 0.0.7 patch against release alsa-driver 0.9.6.
i hope 0.9.6 is still pretty close to CVS.
this works for me on a planet ccrma rh9 box with 2.4.21-ck3 kernel.
so far only on a laptop with bx440 chipset. my via pIII box has shown 
usb-problems and crackling sound with this. (anybody any ideas?)

new here is:
- both firmware-downloads are handled now by the snd-usb-us428-dl module (this 
functionality should move further on into userspace via libusb ? volunteers?)
- pcm capturing using one device with all 4 channels works -> good for jack
- beginning of an userspace application interface for controll communication. 
(there is a very early implementation that can start & stop ardour using 
those knobs; erm actually not in this patch..still needs some polishing..)

my working configure invocation was:
"./configure 
--with-cards=via82xx,msnd-pinnacle,usb-audio,usb-us428,usb-us428-dl,es1968 
--with-kernel=/home/ka/kernel/linux-2.4.21 --with-debug=full"

and it will most propably not run on one of the other tascam usb devices.
and yes, the midi i/o should also still tick by virtue of snd-usb-audio :-) 

i agree that its a reasonable goal to integrate the us428 audio part into ALSA 
usb-audio. is there such a mechanism to syncronize the playback-pipe by the 
capture-pipe allrteady in usb-audio.c? the us428 definitly needs such a 
beast.
for now its easier for me to keep a seperate module: source is smaller and i'd 
like to do more on the knobs, sliders & lights part of the us428.

none the less i'd greatly appreciate if you'd submit the path ;-) 

part2 of the patch in next mail.

[-- Attachment #2: alsa-driver-0.9.6+usbus428.1.diff.tar.bz2 --]
[-- Type: application/x-tbz, Size: 20582 bytes --]

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Takashi Iwai]

Hi Karsten,

At Wed, 30 Jul 2003 21:33:37 +0200,
Karsten Wiese wrote:
> 
> [1  <text/plain; iso-8859-1 (7bit)>]
> Am Montag 05 Mai 2003 15:14 schrieb Takashi Iwai:
> > Hi,
> >
> > At Wed, 30 Apr 2003 13:56:34 +0200,
> >
> > karsten wrote:
> > > ... if I understand this
> > > http://www.tascam.com/forums/showthread.php?s=&threadid=28584
> > > correctly.
> > > please have a look at administrator Jims post near the bottom and tell
> > > me, if you agree to include our us428 driver in alsa.
> > > we would split the driver in two parts then, audio/midi handling and
> > > firmware.
> >
> > great!
> >
> > could you send the patch again (the one to the latest cvs version is
> > preferred)?  the current ALSA usb-audio driver has more generic layer
> > to absorb the device specific part, so perhaps we can integrate the
> > tascam driver more smoothly.
> >
> >
> > thanks,
> >
> > Takashi
> 
> this is part 1 of usbus428 0.0.7 patch against release alsa-driver 0.9.6.
> i hope 0.9.6 is still pretty close to CVS.

thanks!


> this works for me on a planet ccrma rh9 box with 2.4.21-ck3 kernel.
> so far only on a laptop with bx440 chipset. my via pIII box has shown 
> usb-problems and crackling sound with this. (anybody any ideas?)
> 
> new here is:
> - both firmware-downloads are handled now by the snd-usb-us428-dl module (this 
> functionality should move further on into userspace via libusb ? volunteers?)

yes, definitely it's the right way to go.

> - pcm capturing using one device with all 4 channels works -> good for jack
> - beginning of an userspace application interface for controll communication. 
> (there is a very early implementation that can start & stop ardour using 
> those knobs; erm actually not in this patch..still needs some polishing..)
> 
> my working configure invocation was:
> "./configure 
> --with-cards=via82xx,msnd-pinnacle,usb-audio,usb-us428,usb-us428-dl,es1968 
> --with-kernel=/home/ka/kernel/linux-2.4.21 --with-debug=full"
> 
> and it will most propably not run on one of the other tascam usb devices.
> and yes, the midi i/o should also still tick by virtue of snd-usb-audio :-) 
> 
> i agree that its a reasonable goal to integrate the us428 audio part into ALSA 
> usb-audio. is there such a mechanism to syncronize the playback-pipe by the 
> capture-pipe allrteady in usb-audio.c? the us428 definitly needs such a 
> beast.

i'm not sure what you mean here, but i guess it's not implemented.
(is it a standard USB audio feature? if not, we don't have it :)

> for now its easier for me to keep a seperate module: source is smaller and i'd 
> like to do more on the knobs, sliders & lights part of the us428.
> 
> none the less i'd greatly appreciate if you'd submit the path ;-) 

i'll check the code and try to merge to cvs.
as a start-up, i'll put all of them.  later on, we can reduce and
integrate the common parts and remove the firmware stuff to
user-space.

so, please be patient for a while.  it will be finished likely in the
beginning of the next week.  i've been quite busy for these days...


ciao,

Takashi


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Martin Langer]

On Thu, Aug 07, 2003 at 04:44:08PM +0200, Takashi Iwai wrote:
> At Wed, 30 Jul 2003 21:33:37 +0200,
> Karsten Wiese wrote:
> > 
> > new here is:
> > - both firmware-downloads are handled now by the snd-usb-us428-dl module (this 
> > functionality should move further on into userspace via libusb ? volunteers?)
> 
> yes, definitely it's the right way to go.
> 

I've looked into my US122 and there I've found an EZUSB chip. The US428
might be the same.

I think the first download step which also changes the ID has to be the ezusb
firmware. 

After comparing that sniffed log with some available windows binaries from
Tascam, I finally found the data in US122DL.SYS/US428DL.SYS/US224DL.SYS.
Instead of loading the sniffed file it could also be an extract from 
USx2xDL.SYS (it should be similar to the MidiSport firmware extract and
loading procedure).

That could be an easy way to move the first firmware part away from the driver
directory. And we won't need another ok from Tascam for including
sniffed us224/us122 firmware...

I will check it on us122 if I've little bit more time.... 


martin



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Takashi Iwai]

At Mon, 11 Aug 2003 01:26:09 +0200,
Martin Langer wrote:
> 
> On Thu, Aug 07, 2003 at 04:44:08PM +0200, Takashi Iwai wrote:
> > At Wed, 30 Jul 2003 21:33:37 +0200,
> > Karsten Wiese wrote:
> > > 
> > > new here is:
> > > - both firmware-downloads are handled now by the snd-usb-us428-dl module (this 
> > > functionality should move further on into userspace via libusb ? volunteers?)
> > 
> > yes, definitely it's the right way to go.
> > 
> 
> I've looked into my US122 and there I've found an EZUSB chip. The US428
> might be the same.
> 
> I think the first download step which also changes the ID has to be the ezusb
> firmware. 
> 
> After comparing that sniffed log with some available windows binaries from
> Tascam, I finally found the data in US122DL.SYS/US428DL.SYS/US224DL.SYS.
> Instead of loading the sniffed file it could also be an extract from 
> USx2xDL.SYS (it should be similar to the MidiSport firmware extract and
> loading procedure).

it's nice.  could you compare the stuff with the one in Karsten's
patch?

> That could be an easy way to move the first firmware part away from the driver
> directory. And we won't need another ok from Tascam for including
> sniffed us224/us122 firmware...

yep.  that would be far much better.


while we're in here: i'm looking at the code now and have some
questions / suggestions to Karsten:

* the comments in usbus428.c looks like the GPL/BSD dual license but
  MODULE_LICENSE() is defined as GPL.  is it correct?

* what's the reason of the independent snd-usb-us428-dl module?
  this module seems doing only feeding the firmware to the interface,
  so why not in snd-usb-us428 itself?  this will reduce the use of
  inter_module_* stuffs which are obsolete in 2.6 kernels.

* usbus428ctls.c defines mmap & co.  they still be needed?
  could they be replaced with the standard ALSA control API?
  (btw, P_us428ctls_sharedmem_u may be unalighed to the page
   when allocated via kmalloc().  so the mmap code looks buggy for
   me anyway.  also, please avoid virt_to_phys() as much as possible.
   this is architecture dependent, and won't run on non-x86 well.)

* 64bit division macros can be found in pcm.h.
  the asm codes in usbus428audio.c can be removed.

* there are still GCC-style of structs initialization in some parts :)

* please follow the coding style described in linux/Documentation/
  CodingStyle.  spaces after a (open) parenthesis are not common...
  (i know it's a matter of tastes, but we should keep the consistent
   style if possible.)
  also, debug codes which are obviously unnecessary any more should be
  removed in the release source codes.

* you don't need to modify configure stuff but just add the following
  to alsa-driver/utils/Modules.dep and run cvscompile again:

	%dir linux/sound/usb
	snd-usb-us428-dl 
	|snd-usb-us428 snd-usb-audio snd-usb-us428-dl


thanks!

Takashi


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6

[Clemens Ladisch]

Takashi Iwai wrote:
> * the comments in usbus428.c looks like the GPL/BSD dual license but
>   MODULE_LICENSE() is defined as GPL.  is it correct?

I don't think so. Apparently, the comment was copied from usbmidi.c,
while the MODULE_LICENSE came from another file.


Regards,
Clemens




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Martin Langer]

On Tue, Aug 12, 2003 at 06:38:22PM +0200, Takashi Iwai wrote:
> At Mon, 11 Aug 2003 01:26:09 +0200,
> Martin Langer wrote:
> > 
> > I've looked into my US122 and there I've found an EZUSB chip. The US428
> > might be the same.
> > 
> > I think the first download step which also changes the ID has to be the ezusb
> > firmware. 
> > 
> > After comparing that sniffed log with some available windows binaries from
> > Tascam, I finally found the data in US122DL.SYS/US428DL.SYS/US224DL.SYS.
> > Instead of loading the sniffed file it could also be an extract from 
> > USx2xDL.SYS (it should be similar to the MidiSport firmware extract and
> > loading procedure).
> 
> it's nice.  could you compare the stuff with the one in Karsten's
> patch?
> 
> > That could be an easy way to move the first firmware part away from the driver
> > directory. And we won't need another ok from Tascam for including
> > sniffed us224/us122 firmware...
> 
> yep.  that would be far much better.
> 

Success. US122 behaves like a normal ezusb device. And the whole USx2x
family is using the same loader. I think we are at a point where we can
remove that firmware stuff of "us428fw8000.h" and use fxload with an
extracted firmware. Ok, a final test on us428 should be done before.

Pedro's Tascam USx2x extractor/loader is already here and Clemens is on the
way to create an sf project for this wonderful ezusb stuff for MidiSport,   
Tascam devices (and maybe more in the future).

> 
> * what's the reason of the independent snd-usb-us428-dl module?
>   this module seems doing only feeding the firmware to the interface,
>   so why not in snd-usb-us428 itself?  this will reduce the use of
>   inter_module_* stuffs which are obsolete in 2.6 kernels.

I think the main reason was a different PCI ID for loading us428fw8000.h.
And the other firmware part was originally in snd-usb-us428 IIRC!
Ok, removing the sniffed ezusb firmware is a good reason to forget the 
snd-usb-us428-dl idea completely! I agree.


martin


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Karsten Wiese]

Am Donnerstag 14 August 2003 22:20 schrieb Martin Langer:
> On Tue, Aug 12, 2003 at 09:19:40PM +0200, Martin Langer wrote:
> > Success. US122 behaves like a normal ezusb device. And the whole USx2x
> > family is using the same loader. I think we are at a point where we can
> > remove that firmware stuff of "us428fw8000.h" and use fxload with an
> > extracted firmware. Ok, a final test on us428 should be done before.
> >
> > Pedro's Tascam USx2x extractor/loader is already here and Clemens is on
> > the way to create an sf project for this wonderful ezusb stuff for
> > MidiSport, Tascam devices (and maybe more in the future).
>
> Hi us428,
>
> here you can find that Tascam EZUSB firmware extractor prerelease:
> http://langerland.de/us122/tascam-firmware.tar.bz2
>
> martin

Success with US-428 here ( @ PlanetCCRMA 2.4.21-ck3 PIII BX440 laptop) also!    
a summer breaze :-)   usbus428 0.0.8 patch soon to follow.

karsten



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Karsten Wiese]

> while we're in here: i'm looking at the code now and have some
> questions / suggestions to Karsten:
>
> * the comments in usbus428.c looks like the GPL/BSD dual license but
>   MODULE_LICENSE() is defined as GPL.  is it correct?
i mean "MODULE_LICENSE() is defined as GPL". example solely GPL header please?
>
> * what's the reason of the independent snd-usb-us428-dl module?
>   this module seems doing only feeding the firmware to the interface,
>   so why not in snd-usb-us428 itself?  this will reduce the use of
>   inter_module_* stuffs which are obsolete in 2.6 kernels.
since Pedro's tascam-firmware loader works, there is only one reason to have a 
separate module: it can be unloaded to free memory.
i'll reentegrate the 8001 firmware into the usb-us428 module for 2.6 reasons.
maybe with the FPGA downloader stuff, Martin has mentioned, we can get rid of 
firmware in module at all?
for now: which is the (2.6-)way to tell the kernel that a module's static 
const variable "is pageable" / "can be swaped out" to preserve memory?
>
> * usbus428ctls.c defines mmap & co.  they still be needed?
>   could they be replaced with the standard ALSA control API?
>   (btw, P_us428ctls_sharedmem_u may be unalighed to the page
>    when allocated via kmalloc().  so the mmap code looks buggy for
>    me anyway.  also, please avoid virt_to_phys() as much as possible.
>    this is architecture dependent, and won't run on non-x86 well.)
notice please the us-428 knobs/sliders events can only be received by an 
application in a sense like a users interface. so we have a difference here 
to standard mixer-like controls (opposite direction)?
mmh yes: they are comparable to the laptop's volume knobs..except most of them 
would trigger some app's filters instead of a chip's hardware directly... 
should i investigate that further? alsa-lib can help ?
or: how do i register/operate an alsa-sequencer midi-port from userspace?
which is the kernel function to obtain aligned memory for mmap?
>
> * 64bit division macros can be found in pcm.h.
>   the asm codes in usbus428audio.c can be removed.
>
> * there are still GCC-style of structs initialization in some parts :)
>
> * please follow the coding style described in linux/Documentation/
>   CodingStyle.  spaces after a (open) parenthesis are not common...
>   (i know it's a matter of tastes, but we should keep the consistent
>    style if possible.)
>   also, debug codes which are obviously unnecessary any more should be
>   removed in the release source codes.
>
> * you don't need to modify configure stuff but just add the following
>   to alsa-driver/utils/Modules.dep and run cvscompile again:
>
> 	%dir linux/sound/usb
> 	snd-usb-us428-dl
>
> 	|snd-usb-us428 snd-usb-audio snd-usb-us428-dl
will obey.
>
> thanks!
>
> Takashi

lots of ?. thanks!

Karsten




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Martin Langer]

On Thu, Aug 07, 2003 at 04:44:08PM +0200, Takashi Iwai wrote:
> At Wed, 30 Jul 2003 21:33:37 +0200,
> Karsten Wiese wrote:
> > 
> > i agree that its a reasonable goal to integrate the us428 audio part into ALSA 
> > usb-audio. is there such a mechanism to syncronize the playback-pipe by the 
> > capture-pipe allrteady in usb-audio.c? the us428 definitly needs such a 
> > beast.
> 
> i'm not sure what you mean here, but i guess it's not implemented.
> (is it a standard USB audio feature? if not, we don't have it :)

Stupid question: Why do we need synchronisation??

Isn't it the job of the FPGA? We know that each signal is routed across the
FPGA and that's why the config data should be loaded into for standalone
usage or nothing will work on our USxxx. Without an internal
synchronisation there would be no standalone usage possible or do I make a
mistake here.

What about removing synchronisation stuff and replacing it with some 
talking to the FPGA buffer??? I guess that will not fit into USB AUDIO
class, but anyhow my USxxx is vendor specififc.


martin


-------------------------------------------------------
This SF.net email is sponsored by Dice.com.
Did you know that Dice has over 25,000 tech jobs available today? From
careers in IT to Engineering to Tech Sales, Dice has tech jobs from the
best hiring companies. http://www.dice.com/index.epl?rel_code=104

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Karsten Wiese]

Am Mittwoch 20 August 2003 19:58 schrieb Martin Langer:
> On Thu, Aug 07, 2003 at 04:44:08PM +0200, Takashi Iwai wrote:
> > At Wed, 30 Jul 2003 21:33:37 +0200,
> >
> > Karsten Wiese wrote:
> > > i agree that its a reasonable goal to integrate the us428 audio part
> > > into ALSA usb-audio. is there such a mechanism to syncronize the
> > > playback-pipe by the capture-pipe allrteady in usb-audio.c? the us428
> > > definitly needs such a beast.
> >
> > i'm not sure what you mean here, but i guess it's not implemented.
> > (is it a standard USB audio feature? if not, we don't have it :)
>
> Stupid question: Why do we need synchronisation??
to avoid crackles in Audio Out. goal: feeding Audio Out exactly as many frames 
as it can digest.
>
> Isn't it the job of the FPGA? We know that each signal is routed across the
> FPGA and that's why the config data should be loaded into for standalone
> usage or nothing will work on our USxxx. Without an internal
> synchronisation there would be no standalone usage possible or do I make a
> mistake here.
What do you mean with standalone usage?
>
> What about removing synchronisation stuff and replacing it with some
> talking to the FPGA buffer??? I guess that will not fit into USB AUDIO
> class, but anyhow my USxxx is vendor specififc.
how would you do that? You have the 122s circuit diagram?
What I know so far is: there are no crackles in audio anymore if we feed 
"Audio Out" at exactly the frame-rate we have received from "Audio In" just 
before.
this is what I mean by synchronisation. 
would you try the us428 audio part on the us122? I could send you a special 
version for 2 Audio Ins & 2 Audio Outs. We could then build a snd-usb-usx2x 
module ;-) None the less you'd first have to extract the second stage 
firmware. have you already?

karsten






-------------------------------------------------------
This SF.net email is sponsored by Dice.com.
Did you know that Dice has over 25,000 tech jobs available today? From
careers in IT to Engineering to Tech Sales, Dice has tech jobs from the
best hiring companies. http://www.dice.com/index.epl?rel_code=104

Re: usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Martin Langer]

On Wed, Aug 20, 2003 at 08:29:12PM +0200, Karsten Wiese wrote:
> Am Mittwoch 20 August 2003 19:58 schrieb Martin Langer:
> >
> > Stupid question: Why do we need synchronisation??
> to avoid crackles in Audio Out. goal: feeding Audio Out exactly as many frames 
> as it can digest.

I see.

> > Isn't it the job of the FPGA? We know that each signal is routed across the
> > FPGA and that's why the config data should be loaded into for standalone
> > usage or nothing will work on our USxxx. Without an internal
> > synchronisation there would be no standalone usage possible or do I make a
> > mistake here.
> What do you mean with standalone usage?

I can use my us122 in a direct mode. There I can receive the audio signal
from Audio-In on the Audio-Out jacks. But I have to load both firmwares and
some USB power is neccessary. And without firmware there is no signal on
Audio Out.

> You have the 122s circuit diagram?

No, I don't have a circuit diagram. But lots of fantasy;-)

> What I know so far is: there are no crackles in audio anymore if we feed 
> "Audio Out" at exactly the frame-rate we have received from "Audio In" just 
> before.
> this is what I mean by synchronisation. 

Thanks for explaining it. Now I know what you mean here.

> would you try the us428 audio part on the us122? I could send you a special 
> version for 2 Audio Ins & 2 Audio Outs. We could then build a snd-usb-usx2x 
> module ;-) None the less you'd first have to extract the second stage 
> firmware. have you already?

Yes, we should try out this possibility of a common snd-usb-usx2x! 

Sorry, Tascam FPGA firmware loader development is still not finished: 
More (cvs/mail) on http://sourceforge.net/projects/usb-midi-fw/


martin


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0

usbus428 0.0.8 patch against release alsa-driver 0.9.6

[Karsten Wiese]

[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]

this one relies on the tascam-firmware downloader 
http://usb-midi-fw.sourceforge.net/tascam-firmware.tar.gz
to be installed.

the following issues should have been improved.
tell me, where I still miss :-)

have fun, 
Karsten

Am Dienstag 12 August 2003 18:38 schrieb Takashi Iwai:
> while we're in here: i'm looking at the code now and have some
> questions / suggestions to Karsten:
>
> * the comments in usbus428.c looks like the GPL/BSD dual license but
>   MODULE_LICENSE() is defined as GPL.  is it correct?
>
> * what's the reason of the independent snd-usb-us428-dl module?
>   this module seems doing only feeding the firmware to the interface,
>   so why not in snd-usb-us428 itself?  this will reduce the use of
>   inter_module_* stuffs which are obsolete in 2.6 kernels.
>
> * usbus428ctls.c defines mmap & co.  they still be needed?
>   could they be replaced with the standard ALSA control API?
>   (btw, P_us428ctls_sharedmem_u may be unalighed to the page
>    when allocated via kmalloc().  so the mmap code looks buggy for
>    me anyway.  also, please avoid virt_to_phys() as much as possible.
>    this is architecture dependent, and won't run on non-x86 well.)
>
> * 64bit division macros can be found in pcm.h.
>   the asm codes in usbus428audio.c can be removed.
>
> * there are still GCC-style of structs initialization in some parts :)
>
> * please follow the coding style described in linux/Documentation/
>   CodingStyle.  spaces after a (open) parenthesis are not common...
>   (i know it's a matter of tastes, but we should keep the consistent
>    style if possible.)
>   also, debug codes which are obviously unnecessary any more should be
>   removed in the release source codes.
>
> * you don't need to modify configure stuff but just add the following
>   to alsa-driver/utils/Modules.dep and run cvscompile again:
>
>         %dir linux/sound/usb
>         snd-usb-us428-dl
>         |snd-usb-us428 snd-usb-audio snd-usb-us428-dl

[-- Attachment #2: alsa-driver-0.9.6+usbus428-008.diff.tar.bz2 --]
[-- Type: application/x-tbz, Size: 35692 bytes --]

usbus428 0.0.7 patch against release alsa-driver 0.9.6 (was Re: tascam gives a go for us428 @ alsa ...)

[Karsten Wiese]

[-- Attachment #1: Type: text/plain, Size: 48 bytes --]

this is part 2 of the patch: the firware files.

[-- Attachment #2: alsa-driver-0.9.6+usbus428.2.diff.tar.bz2 --]
[-- Type: application/x-tbz, Size: 28261 bytes --]