Skip to contentSkip to conversation

emufxtool, formerly ld10k1

DISCUSSION Nicola Orru' 3 participants 13 messages Jul 30, 2003 – Aug 7, 2003 3 messages not in the archive

lore
Share & tools
lore
#0 lore raw

Hello,

I have a message for alsa-tools maintainers.

Several months ago I posted on

http://opensrc.org/alsa/index.php?page=emu10k1

an announce reporting I was developing an alsa-based tool to enable effect loading onto emu10k1 (Sound Blaster Live!), called ld10k1.

The project grew up to emufxtool, a multipurpose tool for emu10k1 DSP low-level programming, whose aim is to allow creation of sound effects, filters and so on. The project is currently alpha stage, but the assembler/loader is just working.

You can download a tarball of the project (that includes a presentation and some docs) at the following link:

http://www.itadinanta.it/~nicola/emufxtool-0.2.tar.gz

I would like to publish the project as a component of alsa-tools or someway integrate it into them, so I need to know who I should report to or ask about that. I need this feedback to plan further advancements of the project.

Please help me, even in private if you prefer. Any suggestion or advice will be *highly* appreciated.

Signature · 12 lines
Ciao,
Nicola
--------------------------------------------------------------------
* Nicola Orru' - Via Dei Tulipani, 9 - 09034 Assemini (CA) - ITALY *
--------------------------------------------------------------------


-------------------------------------------------------
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
#1 lore raw

At Wed, 30 Jul 2003 17:41:34 +0200,

Quoted 11 lines · Nicola Orru

Hello,

I have a message for alsa-tools maintainers.

Several months ago I posted on

http://opensrc.org/alsa/index.php?page=emu10k1

an announce reporting I was developing an alsa-based tool to enable effect loading onto emu10k1 (Sound Blaster Live!), called ld10k1.

Quoted 7 lines

The project grew up to emufxtool, a multipurpose tool for emu10k1 DSP low-level programming, whose aim is to allow creation of sound effects, filters and so on. The project is currently alpha stage, but the assembler/loader is just working.

You can download a tarball of the project (that includes a presentation and some docs) at the following link:

http://www.itadinanta.it/~nicola/emufxtool-0.2.tar.gz

I would like to publish the project as a component of alsa-tools or someway integrate it into them, so I need to know who I should report to or ask about that. I need this feedback to plan further advancements of the project.

yeah, it'd be greatly appreciated. i'd love to have this kind of tool in the standard alsa-tools package.

i'll take a look at the code, and put to cvs tree soon later.

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

#3 lore raw
In reply to Nicola Orru'

Hi, it's me again.

just a small notes:

- it'd be better to have GPL copyright notice in each file.

- definition of SNDRV_* and sndrv_ctl_elem_id should be removed. it's a bug of sound/emu10k1.h that it requires these definitions. well, this is not a critical issue, so i'll fix this later...

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

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#7 lore raw

At Wed, 30 Jul 2003 19:20:29 +0200,

Quoted 7 lines · Nicola Orru
Quoted 6 lines
      autoreconf --force --install
	....
	% ./configure --prefix=/usr/local
	% make
	% make install
Quoted 7 lines

the following sequence worked:

       autoreconf --install
       ./configure --prefix=/usr/local
       make

"--force" and "make install" didn't. But I could run emufxtool -h in the end. This is a good start.

don't know why --force doesn't work, but it's not important. "make install" should work, too...

Quoted 3 lines
Quoted 1 line

on cvs, i'll put cvscompile script for convenience.

Great. It runs auto* in the correct sequences, doesn't it?

yes.

Quoted 3 lines

May I have a pointer to a page (I'll RTFM!) that contains the "protocol" to apply when working on alsa cvs, to create, pack and send patches to maintainers?

yes, documentation is always nice :)

Quoted 1 line

Do you think this thread should be moved to the list?

to alsa-devel, do you mean?
i think yes, and now Cc'ed again.

Quoted 1 line

BTW: I am receiving your posts (only yours!) on the list twice.

ah, it's because my MUA adds To: and Cc: automatically...

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

#8 lore raw
Quoted 5 lines
Quoted 3 lines

May I have a pointer to a page (I'll RTFM!) that contains the "protocol" to apply when working on alsa cvs, to create, pack and send patches to maintainers?

yes, documentation is always nice :)

Humm. I'm Sorry :(

I suppose I did not express myself clearly :P.

I don't know how to access that information, I would like to get it in some way. In a word: can you send me a link to the docs?

Any help appreciated from anyone.

Thanks AGAIN for your patience.

Signature · 12 lines
Ciao,
Nicola
--------------------------------------------------------------------
* Nicola Orru' - Via Dei Tulipani, 9 - 09034 Assemini (CA) - ITALY *
--------------------------------------------------------------------


-------------------------------------------------------
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
#9 lore raw

At Wed, 30 Jul 2003 20:04:08 +0200,

Quoted 5 lines · Nicola Orru
Quoted 5 lines
Quoted 4 lines

May I have a pointer to a page (I'll RTFM!) that contains the "protocol" to apply when working on alsa cvs, to create, pack and send patches to maintainers?

Quoted 7 lines
Quoted 1 line

yes, documentation is always nice :)

Humm. I'm Sorry :(

I suppose I did not express myself clearly :P.

I don't know how to access that information, I would like to get it in some way. In a word: can you send me a link to the docs?

oh, sorry, i misread the sentence above.

well, there is no protocol for that.
so far, cvs write access is limited to ALSA core developers.

i'll need to integrate the whole emufxtool tree to alsa-tools cvs tree (after modified to suit with the alsa-tools tree) at first. after that, you can get them from anon cvs.

once after the tree is there, you can make easily patches via cvs diff. then please send me or Jaroslav (or alsa-devel ML) the patch, so we'll commit it soon.

if you'd like to keep the different cvs tree on sf, go ahead. please give us the patch sometimes to keep the trees in sync.

so, the first step is to make a final tarball for inclusion. as already mentioned, it's better to have GPL notes in each file, and have configure stuffs.
if these changes are finished, please let me know the URL (or send me the tarball). i'll merge it to alsa-tools tree ASAP.

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

#10 lore raw
Quoted 11 lines · Takashi Iwai

At Wed, 30 Jul 2003 20:04:08 +0200,

Quoted 9 lines · Nicola Orru
Quoted 6 lines
Quoted 4 lines

May I have a pointer to a page (I'll RTFM!) that contains the "protocol" to apply when working on alsa cvs, to create, pack and send patches to maintainers?

yes, documentation is always nice :)

Humm. I'm Sorry :(

Quoted 8 lines
Quoted 3 lines

I suppose I did not express myself clearly :P.

I don't know how to access that information, I would like to get it in some way. In a word: can you send me a link to the docs?

oh, sorry, i misread the sentence above.

well, there is no protocol for that.
so far, cvs write access is limited to ALSA core developers.

If I understand correctly, is emufxtool an extended version of ld10k1
(http://ld10k1.sf.net)?

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
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

#11 lore raw
Quoted 17 lines · Jaroslav Kysela
Quoted 15 lines · Takashi Iwai

At Wed, 30 Jul 2003 20:04:08 +0200,

Quoted 12 lines · Nicola Orru
Quoted 6 lines
Quoted 4 lines

May I have a pointer to a page (I'll RTFM!) that contains the "protocol" to apply when working on alsa cvs, to create, pack and send patches to maintainers?

yes, documentation is always nice :)

Humm. I'm Sorry :(

I suppose I did not express myself clearly :P.

I don't know how to access that information, I would like to get it in some way. In a word: can you send me a link to the docs?

Quoted 7 lines
Quoted 4 lines

oh, sorry, i misread the sentence above.

well, there is no protocol for that.
so far, cvs write access is limited to ALSA core developers.

If I understand correctly, is emufxtool an extended version of ld10k1
(http://ld10k1.sf.net)?

Replying to myself: No, it is not.

Takashi, I suggest to postpone the integration of the emufxtool to alsa-tools. We have a bit duplicated work. But I think that ld10k1 code (linker side) from Peter Zubaj is better. He followed my directions and used the client/server mechanism. So linker can accept the DSP code from more different applications (resp. DSP code compilers or other generators) while maintaining the static image in the DSP instruction RAM.

If it is possible, can you guys settle details about linker communication (and probably finish it)? We can integrate both projects then.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
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

#12 lore raw
Quoted 2 lines

If it is possible, can you guys settle details about linker communication (and probably finish it)? We can integrate both projects then.

I didn't know about Peter's ld10k1 existence, but it seems to be what I thought initially of emufxtool, before starting to improve the assembly/disassembly core and the file format.

I think it is a good idea, at least there will not duplicated code and, if I understand correctly, emufxtool might use ld10k1 as a "backend" to load patches onto the DSP.

I am just downloading ld10k1 from sf. Will take more than a look at that.

...stay tuned...

Signature · 12 lines
Ciao,
Nicola
--------------------------------------------------------------------
* Nicola Orru' - Via Dei Tulipani, 9 - 09034 Assemini (CA) - ITALY *
--------------------------------------------------------------------


-------------------------------------------------------
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
#13 lore raw
Quoted 8 lines
Quoted 2 lines

If it is possible, can you guys settle details about linker communication (and probably finish it)? We can integrate both projects then.

I didn't know about Peter's ld10k1 existence, but it seems to be what I thought initially of emufxtool, before starting to improve the assembly/disassembly core and the file format.

I think it is a good idea, at least there will not duplicated code and, if I understand correctly, emufxtool might use ld10k1 as a "backend" to load patches onto the DSP.

I am just downloading ld10k1 from sf. Will take more than a look at that.

I took a look at ld10k1/lo10k1. Its architecture is well thought and offers lots of possibilities.

I can remove from emufxtool the "direct" access to the driver by IOCTL and use the pipe to communicate to ld10k1 server. Before doing that, maybe we should define well the "communication protocol" between clients and server, as suggested by Jaroslav.

This system solves also the problem of multiple patch loading and code relocation, which my emufxtool solves at compile time (to use more than one patch you have to compile and load them as a whole). The same method could be used by the disassembler code to fetch DSP content (or loader server-side DSP "images").

The next step could be a MIDI based loader, that allows you to store/fetch patches using SYSEX messages sent to /dev/sequencer or alsa midi virtual ports, or anything else (a new device that replaces the pipe?), maybe requiring some work on the modules... (Not a choice I can make, anyway...)

I ignore if Peter Zubaj can receive this message, but I think it would be a good idea if we merged our projects into a single one ( : ). A good start may be the definition of the "protocol" above.

The protocol can be "message based", each "message" may be defined, for instance, by primitive types and surrounded by a header/footer standard pair (containing a message id, the length of the message, and something like a checksum to avoid "garbage").

Client and server "speak" through a sequence of "Request"/"Response" message pairs, usually initiated and closed by the client.

I.E. Message: SET PATCH

Offset   Length (in bytes) Type                Value
   0     2                 unsigned short (*)  0004 (ID_SET_PATCH)
   2     4		   unsigned (*)        total length of message
   6     30		   character string    name of the patch
  36     2		   unsigned short (*)  number of DSP instr.

....
length+36 4 unsigned checksum

(*) endianness to be defined

and so on...

Signature · 12 lines
Ciao,
Nicola
--------------------------------------------------------------------
* Nicola Orru' - Via Dei Tulipani, 9 - 09034 Assemini (CA) - ITALY *
--------------------------------------------------------------------


-------------------------------------------------------
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
#14 lore raw

Hi,

sorry for the late response. i'm back from the conference at Edinburgh now...

At Wed, 30 Jul 2003 23:50:51 +0200,

Quoted 18 lines · Nicola Orru
Quoted 9 lines
Quoted 3 lines

If it is possible, can you guys settle details about linker communication (and probably finish it)? We can integrate both projects then.

I didn't know about Peter's ld10k1 existence, but it seems to be what I thought initially of emufxtool, before starting to improve the assembly/disassembly core and the file format.

I think it is a good idea, at least there will not duplicated code and, if I understand correctly, emufxtool might use ld10k1 as a "backend" to load patches onto the DSP.

I am just downloading ld10k1 from sf. Will take more than a look at that.

I took a look at ld10k1/lo10k1. Its architecture is well thought and offers lots of possibilities.

I can remove from emufxtool the "direct" access to the driver by IOCTL and use the pipe to communicate to ld10k1 server. Before doing that, maybe we should define well the "communication protocol" between clients and server, as suggested by Jaroslav.

Quoted 5 lines

This system solves also the problem of multiple patch loading and code relocation, which my emufxtool solves at compile time (to use more than one patch you have to compile and load them as a whole). The same method could be used by the disassembler code to fetch DSP content (or loader server-side DSP "images").

yep, this sounds nice.
we can add a start-up script for this as well as the auto-loading of soundfonts. (/etc/alsa.d/emu10k1 is started from alsasound init script.)

Quoted 5 lines

The next step could be a MIDI based loader, that allows you to store/fetch patches using SYSEX messages sent to /dev/sequencer or alsa midi virtual ports, or anything else (a new device that replaces the pipe?), maybe requiring some work on the modules... (Not a choice I can make, anyway...)

i don't think it's a way to go although it's doable.
once if we have a good patch manager daemon, we should concentrate on it for the job. the midi effects can be managed by it eventually.

Quoted 3 lines

I ignore if Peter Zubaj can receive this message, but I think it would be a good idea if we merged our projects into a single one ( :
).

yes, definitely.

Quoted 17 lines

A good start may be the definition of the "protocol" above.

The protocol can be "message based", each "message" may be defined, for instance, by primitive types and surrounded by a header/footer standard pair (containing a message id, the length of the message, and something like a checksum to avoid "garbage").

Client and server "speak" through a sequence of "Request"/"Response" message pairs, usually initiated and closed by the client.

I.E. Message: SET PATCH

Offset   Length (in bytes) Type                Value
   0     2                 unsigned short (*)  0004 (ID_SET_PATCH)
   2     4		   unsigned (*)        total length of message
   6     30		   character string    name of the patch
  36     2		   unsigned short (*)  number of DSP instr.
Quoted 6 lines

....
length+36 4 unsigned checksum

(*) endianness to be defined

and so on...

the idea looks nice. it's a standard way to do such a work in the client/server system.

is the development going on now?

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

#15 lore raw
Quoted 4 lines

the idea looks nice. it's a standard way to do such a work in the client/server system.
is the development going on now?

Still no answer from Peter Zubaj. I wonder if someone could send me his address...

Signature · 5 lines
Ciao,
Nicola
--------------------------------------------------------------------
* Nicola Orru' - Via Dei Tulipani, 9 - 09034 Assemini (CA) - ITALY *
--------------------------------------------------------------------