Re: [linux-audio-dev] why is no-one responding

2003-02-12 Thread janne halttunen
On 13 Feb 2003 01:38:13 +1100
Son of Zev [EMAIL PROTECTED] wrote:

 However I have been involved in the ardour lists for over 2 years. I
 have spent much time reading about potential problems and responded to
 all those that have had the courtesy to respond. I have also learnt and
 spent much time investigating problems that have nothing to do with the
 production of music.. simply to try and help developers iron out
 problems.. 

Pretty much everyone into linux audio at this point does that. 


 If you look back into archives a couple of years back alot of
 development into inclusion of MIDI sync was added to some softwares
 (especially MusE) to accomodate users like myself who depend on this
 sync to make software compatible with real studios. 

 BUT. In the last few weeks I have spent much time into trying to
 configure and compile ardour (the potentially greatest audio recording
 software available to us)

Heh, I've been up to the same task.  It seems to depend on fairly recent development 
tools, and upgrading to them all can mess things up.  But slowly working towards it.


 but all my responses after I sent an opinion
 to the string ahem concerning Steinberg having produced (but not
 released) versions of their commercial softwares under our much loved
 platform, have been completely ignored.. except this one.. 
 
 My responses have not been ignorant nor lacking in information. As I
 mentioned I have spent much time learning about the Linux platform and
 contributing when I can ... 

Well, position yourself with a working ardour, and then think how much time you would 
spend on helping others, when all that time you could be making music :)


 My annoyance is when it was asked of me to provdie more information and
 I did .. no response came.. then when I tried to resolve it myself and
 no further response came that's when I could only put 2  2 together and
 see that a response I made to the string ahem could have been related 

Sometimes more information does ring a bell to someone, sometimes it doesn't.  That's 
pretty much about it from my point of view.  There are many bits in cyberspace.


janne

(or is there? ;)


 cheers
 
 Allan 



Re: [linux-audio-dev] Additional LADSPA hints

2003-01-16 Thread janne halttunen
On Wed, 15 Jan 2003 18:13:35 +
Steve Harris [EMAIL PROTECTED] wrote:

 AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
 by a high time res. slider or control data, but shouldn't be connected to
 the next audio signal by default. I can't think of any simple examples off
 hand, but combined with MOMENTARY it could be used for sample accurate
 tempo tapping.
 
 My comments: I really like MOMENTARY and RANDOMISABLE. AUDIO_RATE_CONTROL
 could be useful, but might be painful for hosts to implement. I dont have
 any particular use for it right now.

Not to mention that AUDIO_RATE_CONTROL would completely useless in JACK?  
You'd have a buffer-full of samples and apply frequency shift to them, which would 
change the length of that buffer, which you couldn't give to JACK unless you do some 
rebuffering.

Correct me if I'm wrong.  We have similar issue with ecasound's Pitch Shifter operator 
in connection with JACK.


janne



Re: [linux-audio-dev] Additional LADSPA hints

2003-01-16 Thread janne halttunen
On Thu, 16 Jan 2003 13:58:58 +
Steve Harris [EMAIL PROTECTED] wrote:

 On Thu, Jan 16, 2003 at 02:38:53PM +0200, janne halttunen wrote:
  On Wed, 15 Jan 2003 18:13:35 +
  Steve Harris [EMAIL PROTECTED] wrote:
  
   AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
   by a high time res. slider or control data, but shouldn't be connected to
   the next audio signal by default. I can't think of any simple examples off
   hand, but combined with MOMENTARY it could be used for sample accurate
   tempo tapping.
  
  Not to mention that AUDIO_RATE_CONTROL would completely useless in JACK?  
 
 No, I dont think so. An audio rate control is just one that has a value
 per sample, instead of a value per block. Its usful for things like FM
 frequency which can be changed very quickly. Hey, I just thought of a use
 for it ;)

But how can it be used for tempo tapping then?


janne



Re: [linux-audio-dev] Additional LADSPA hints

2003-01-16 Thread janne halttunen
On Thu, 16 Jan 2003 16:35:37 +
Steve Harris [EMAIL PROTECTED] wrote:

 On Thu, Jan 16, 2003 at 05:31:56PM +0200, janne halttunen wrote:
   No, I dont think so. An audio rate control is just one that has a value
   per sample, instead of a value per block. Its usful for things like FM
   frequency which can be changed very quickly. Hey, I just thought of a use
   for it ;)
  
  But how can it be used for tempo tapping then?
 
 Tempo tapping is a way of determining the tempo of the musicians music,
 you tap the button in time to the music and the software then uses that to
 sync delays and similar effects. It doesn't do any time stetching.

Ah, allright.  Neat. :)


janne



Re: [linux-audio-dev] Tk Ecasound 0.6.0 Released!

2002-10-08 Thread janne halttunen

On Wed, 02 Oct 2002 17:36:56 -0300
Luis Pablo Gasparotto [EMAIL PROTECTED] wrote:

 Tk Ecasound 0.6.0 was released!

This is starting to look really good!  Add individual starting positions for tracks 
(using ewf) and I am sold. :)

I noticed that the autodetected external audio editor is the one in .ecasoundrc.. 
Perhaps it could be set from within the program?


janne



Re: [linux-audio-dev] Tk Ecasound 0.6.0 Released!

2002-10-08 Thread janne halttunen

On Tue, 8 Oct 2002 11:08:29 +0300
janne halttunen [EMAIL PROTECTED] wrote:

 On Wed, 02 Oct 2002 17:36:56 -0300
 Luis Pablo Gasparotto [EMAIL PROTECTED] wrote:
 
  Tk Ecasound 0.6.0 was released!

 I noticed that the autodetected external audio editor is the one in .ecasoundrc.. 
Perhaps it could be set from within the program?

Ah, it was in the Options allright.


janne



Re: [linux-audio-dev] testing LADSPA plugins

2002-09-12 Thread janne halttunen

On Thu, 12 Sep 2002 17:52:39 +0100
Steve Harris [EMAIL PROTECTED] wrote:

 On Thu, Sep 12, 2002 at 04:36:43 +0100, Nathaniel Virgo wrote:
  I was wondering if anyone has any ideas on the best way to test/debug some 
  LADSPA plugins that I've written (using the cmt framework).  
 
 I'l gladly help though, I've been meaning to write a test harness
 plugin host for months. 

There is pre-alpha Python host project at:

http://python-ladspa.sourceforge.net/

if anyone's into such thing.


janne
___
linux-audio-dev mailing list
[EMAIL PROTECTED]
http://music.columbia.edu/mailman/listinfo/linux-audio-dev



Re: [linux-audio-dev] analysis/resynthesis environment: python?

2002-08-20 Thread janne halttunen

On Fri, 16 Aug 2002 16:48:17 +0200
Kasper Souren [EMAIL PROTECTED] wrote:

 On Friday 09 August 2002 00:39, Andrew W. Schmeder wrote:
  However these days I recommend Python with Numeric/Scientific/SciPy
 
 What do you use to play and load sound?

Well, there is module in standard lib to read and write wavs, called wave.

http://www.python.org/doc/current/lib/module-wave.html

To play them, I have used a module called linuxaudiodev.  It's bit strange since there 
is no mention of it in any documentation, but it has been bundled with python for some 
time now, for what I know.  Interface is similar to module sunaudiodev.

http://www.python.org/doc/current/lib/module-sunaudiodev.html

The linuxaudiodev module seems bit buggy, but is fine for basic operation.

 Maybe it's nice to use libsndfile for soundfile stuff. I did 
 it before for someone who programs in Pascal.

If you come up with bindings for libsndfile, I'd be very interested.


 For playing sound I was thinking about the pyeca thingy, but it's just an 
 interface to ecasound, and to play a sound you first need to write it to a 
 file.

What's wrong with writing straight to alsa or oss device?


janne



Re: ECA homepage. Re: [linux-audio-dev] App intercomunication issues, some views. GSOUND ????

2002-08-02 Thread janne halttunen

On Fri, 2 Aug 2002 14:11:03 +0200 (MET DST)
Kjetil S. Matheussen [EMAIL PROTECTED] wrote:

 Hi, I've been on the www.eca.cx homepage many times. But each time
 I get so confused. How about a redisign. For example to put a
 menu on the left like this:
 
 -overview (the heteca page)
 -ecasound
   -main
   -features
(...)

Umm, 'heteca' is my rather dated frontend to ecasound and it currently doesn't even 
have a webpage.  The source is available, though the program itself is pretty unusable 
for reallife purposes. :(

I'm thinking of rewriting this thing on gtk2 someday. :)


janne