Re: [Protux-devel] Fwd: Re: Article about Protux for O'Reilly Network (www.oreilly.com)

[Martin Herren]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Luciano Domenico wrote:

| hi guys.. I received this this morning, I plan to answer it today
| yet, but if you guys want to answer some of the questions, please
| send me ASAP, I will be adding the names for each answer I receive.
| I will create answers for all, and when I get your answers , I will
| somekind of merging them. I will be answering "as-a-team", so you
| dont have free time, dont bother about this :-).


ok... even if i'm really not too active at the moment, i still give my
opinion... if it's not too late  ;-)

| 1) Simple information about you is needed to include into the
| article: Your age, job (or student?), where you live (city,
| province/state, country), and what your main contributions to
| Protux are.

28, engineer, Lausanne, Switzerland
contribution: mainly autostuff... little UI stuff

| 2) What is the current status of Protux? (For example, its
| feature-set, or the progress of its development.)

usable enough that i regularly use it for 'real' work

| 3) What is the history of Protux? How did it begin?
|
| 4) Was Protux inspired by any other program?
|
| 5) There are a lot of music production applications that have been
| developed specifically for Linux. What are your thoughts about
| this? Why do you think there has been such active development in
| music applications for Linux?

More and more music related stuff moves to computers... why should
Linux refuse this fact ?
And stability is a really important criteria for music production...
and most of all: Penguins like to dance

| 6) So how would you differentiate Protux from other Linux music
| applications that are similar to it?

More powerfull that smaller applications, lighter and faster than
bigger applications... No, more seriously, I think Protux has its own
niche regarding this.
Furthermore Protux has an unique user interface based on JMB, love it
or hate it, but you'll have to admit that once you learned the basics,
you are fast using this interface.

| 7) What programming language(s) was used to write Protux? Any
| reason why this was chosen?


C++

| 8) Does Protux use code or libraries which you/the Protux team did
| not originally develop? Why were these chosen?

Qt mainly for the user interface, Alsa for the audio drivers.

| 9) Was any technology specifically created for Protux?

JMB / Mustux... but Luciano will be better to explain more about it

| 10) What are the technical limitations of Protux, thus far?

Partial Multichannel card support, not many filters yet... not many
import/export file format availlable yet...

| 11) What have been the biggest technical challenges you have faced
| in developing Protux?

one was the lack of documentation, and the evolving API from Alsa...
should become better now

| 12) Perhaps related to Question #11, what are the inherent issues
| one should keep in mind when developing code that deals with sound
| under Linux?

You'll need to dig inside Alsa ;-)

| 13) What features do you plan to add to the next immediate
| version(s) of Protux?

Undo engine... more import/export file formats, more filters, use of
LADSPA plugings

| 14) What would you like others to pay notice to the most about
| Protux?

It's fun, works, and has a great UI

| 15) If somebody wants to contribute to your project (and you're
| open to this), what skills from them could you use now?

any skills...
- - C++ programming skills for coding
- - 'normal user' skills for testing, bug reporting, and asking for new
features
- - writting skills for documentation, tutorials... and translate them
to other languages
- - communication skills to demonstrate Protux to others

| 16) What advice do you have for those who are interested in
| developing applications that address the creation of music/the
| manipulating of sound, regardless of platform?

The application shall not limit creativity, nor impose a way of thinking

| 17) If there's anything else you'd like to comment on that you
| think I missed :-), feel free to add it here.


/Martin

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBYq9CENZb8plGFLQRAi7iAJ9AMjGJYPa/G9WTgJNkyimvSZjn4gCeKL04
mslOGcTUBpsfwPUIEuhz0so=
=ting
-----END PGP SIGNATURE-----