[linux-audio-dev] Re: [linux-audio-user] NI Traktor

2003-06-12 Thread Allan Klinbail
On Thu, 2003-06-12 at 17:13, Frank Barknecht wrote:
 Hallo,
 Robert Jonsson hat gesagt: // Robert Jonsson wrote:
 
  This is a first for audio applications.


I've seen Microsoft adds (paid ones) on SourceForge. so this doesn't
surprise me too much... There are alot of OSX apps appearing so it
doesn't surprise me that they are doing this. However.. I too am not
sure if I like commercial software appearing there, at the same time it
does mean that they are taking notice of the community and seeing Open
Source users as being a potential market.  



  
  Native Instruments Traktor just appeared on Freshmeat!  :)
  
  I guess some people are starting to take notice of the OSS community. Though 
  it isn't OSS in itself and not available for Linux (OS X, + a few marginal 
  os:es).
  But the most interesting thing was that they used Freshmeat as a marketing 
  channel.
 
 There goes the neighborhood... 
 
 I'm not sure if I like it, that freshmeat now includes non-free
 commercial software only available on non-free commercial OSes
 
 ciao
-- 
Allan Klinbail [EMAIL PROTECTED]



Re: [linux-audio-dev] libakai

2003-06-12 Thread Allan Klinbail
Hey There

Does this mean I can read and listen to my MPC200xl .snd files?

What about editing, which software can read it?

cheers

Allan 



On Thu, 2003-06-12 at 22:28, Christian Schoenebeck wrote:
 Hi!
 
 I have ported Sebastien Metrot's libakai to Linux some couple of weeks ago. 
 Until it will be in CVS one day you can get it from:
 
   http://stud.fh-heilbronn.de/~cschoene/projects/libakai/
 
 I added some code to the demo application to extract samples from a Akai disc 
 yesterday, so you can now actually not only see but also hear what's on a 
 disc.
 
 You will notice that there's still a small bug, I will fix it ASAP, but I 
 won't complain if someone else will look for it ;)
 
 Best regards.
 Christian
-- 
Allan Klinbail [EMAIL PROTECTED]



Re: [linux-audio-dev] Re: [linux-audio-user] Re: New LADSPA Hints -clarification of definitions

2003-03-02 Thread Allan Klinbail
Hi All

Can I clarify a few definitions here based on real hardware usage.   
  
   I think there was one more too, but I can't think what it was...
  
  I remember one about sidechains or something. I don't know what a sidechain is,
  though, I just recall seeing it somewhere :)
 
 I dont think that one is practical.

A sidechain is  a send/return insert for a single device.. e.g. if you
don't have mutiband compressors (but had three standard compressors) 
but wanted to compress specific frequencies you would plug an eq rack
into your sidecahin in/out plug of your compressor..then the signal
output of the compressor is what would be compressed. Say by boosting
the bass frequencies, the bass frequencies would be compressed more than
the rest of the signal.  ..  A simpler example would be wanting to
distort a signal before compressing it. The distortion unit would be
plugged into the sidechain. I suggest going to a hardware manufacturers
site, say DBX and downloading a pdf of a compressor manual and
investigating the block diagram. 

 The reason for using a sidechain (in the hardware world)  as opposed to
plugging everything inline.. is simplification of patching and
minimising the number of cables being used.  

In software there would be no reason other than aestethics to include a
sidechain as it is possible to plug modules into each other in series
without getting ground noise from excessive amounts of cabling. So Steve
you are correct it isn't really useful.  

 For example the distinction between the control output of an envelope
 follower and the gain reduction output of a compressor, the follower is
 inteded to drive eg. a filters cutoff, wheres the gain reduction is just
 inteded to be viewed by the user as a clue as to what is going on.

Correct about control output. However gain reduction on a compressor
actually controls the output level or gain from the unit, it is not
simply for the user as a clue as to what is going on.. Often when
compressing the resultant output may be larger than desired... When
compressing a signal,  input level is often boosted to get more of an
effect from the compressor (usually this is controlled with the input
gain on the desk) which is why the output level would often be very
high.. gain reduction is a way of counteracting this.

Here is a simplified diagram of a system using desk inserts for inline
compression within one channel of an analogue mixing desk. 


0 ---0--0  --- 0 --0  BUS  
 input   input   compressor   eq  level fader  
 gain   via section
   insert 

So using an insert means the input gain effects the input to the
compressor and not directly to the desk channel. Without gain reduction
the compressor is likely to send a signal that is is either hot (too
high and hence distorting within the channel) or in some cases too low,
making it impossible to give it effective signal level within the entire
mix. This would be useful in a software compressor as well.

As basic audio engineering tells us, the signal must be high enough to
be clear of the ground noise and low enough not to distort within the
mix. 

I hope this helps.. 

cheers

Allan 




Re: [linux-audio-dev] MIDI Clock and ALSA seq

2003-02-17 Thread Allan Klinbail
Not being a coder so you can all shout me down in flames if you like if
my response is misguided .. 

 Thanks, but I really wanted someting with dynamic timing. Does this queue
 tie me to a particular BPM? All I wanted was to be able to put the tick
 out every 24th of the buffer.

Isn't the pulse of MIDI clock defined by the BPM, that's how all
instruments synced to MIDI clock work... I'm a little confused as to how
they would otherwise as BPM is the defining feature of MIDI clock

SMPTE/MTC is another thing though, it is timed in frames and maybe that
is what you need here??? 

You should be able to alter the tempo in real time and  MIDI clock send
those changes through the system so that all machines can see that
change i.e.  my delay unit with MIDI controlled delay times only
looks at the BPM, nothing else. Also think of 2 drum machines synced
together... when one slows down the other must do exactly the same. 

I hope this is useful... but it probably isn't 

cheers

Allan 


 
 - Steve






Re: [linux-audio-dev] MIDI Clock and ALSA seq

2003-02-17 Thread Allan Klinbail
Cool 

So I was right... I didn't know what I was talking about.. 

thanks for the reply though.. 

Allan 


On Tue, 2003-02-18 at 00:43, Steve Harris wrote:
 On Mon, Feb 17, 2003 at 11:52:56 +1100, Allan Klinbail wrote:
  Not being a coder so you can all shout me down in flames if you like if
  my response is misguided .. 
  
   Thanks, but I really wanted someting with dynamic timing. Does this queue
   tie me to a particular BPM? All I wanted was to be able to put the tick
   out every 24th of the buffer.
  
  Isn't the pulse of MIDI clock defined by the BPM, that's how all
  instruments synced to MIDI clock work... I'm a little confused as to how
  they would otherwise as BPM is the defining feature of MIDI clock
 
 Not AFAIK. MIDI clock is just synced to bars and the receiving unit has to
 lock onto the pulses.
 
 I have a delay box that I wanted to sync to the software, its expecting 24
 MIDI clock pulses per bar and will sync to that. I dont know if midi clock
 explictly states the BPM, but I know this particular box will track
 variably timed clock pulses in any case.
 
 As it happens I just fudged it by programming the tempo manually and
 sticking to one tempo. It worked ok :) but it isn't really what I wanted.
  
  You should be able to alter the tempo in real time and  MIDI clock send
  those changes through the system so that all machines can see that
  change i.e.  my delay unit with MIDI controlled delay times only
  looks at the BPM, nothing else. Also think of 2 drum machines synced
  together... when one slows down the other must do exactly the same. 
 
 Yes, but I wanted to be able to track dynamic tempos, and I dont what to
 have to build a new queue for every bar. Also I wanted the beggining of
 the bar to line up with the beggining of the sample loop, which requires
 the pulse timing to be controlled by the player.
 
 It could be that I just misunderstood the code Takashi sent out though.
 
 - Steve








[linux-audio-dev] why is no-one responding are you all just a bunch of *^%^%^wits???

2003-02-12 Thread Allan Klinbail
Hi Guys 

This is quite a disturbing message.. 

nearly 2 weeks ago Paul Davis marked one of my messages as something
seriously wrong going on .. when libraries were compiling as dynamic
not static... 

since then I have responded with full outputs of what is happening. 

In response I sent full output of what was going on .. tried to sort it
out by myself and sent further results.. 

Okay some of it was too big to get to the list immediately pending list
moderator acceptance.. and then some of it just purely didn't get
responded to.

I have done everything I have asked of me from the list, including
Paul's responses ..and also taken my own initiatives following lack of
response and still have recieved no response. 

Sure I am not a coder just a potential professional user.. but that
really shouldn't be an issue... 

Okay some individuals responded to some of my initial questions, and
thankyou to the two of them.. however noone has responded to further
enquiries, after acting on the responses I did get.. 

Is it because I feigned mild support to Steinberg having (while
unreleased) versions of their software for Linux?? Or is it because I'm
obviously not  a coder?? Is it simply because I used the wrong subject
line?

This disgusts me as about 2 years ago when I said I was going to give up
on Linux to the LAD lists a massive response came about saying I should
keep going and my opinions (not even problems relating to software
directly) were valued and necessary. Now when I have real problems
compiling something, contained with as much information I could forward
were included it seems it is irrelevant and no-one seems willing to
respond at all (let alone Paul) .. Other compile and/or configure
problems have been responded too earlier than mine (at all really as my
last few posts have not received any reply)   even though I acted upon
all requests made of me.

I am active in all lists that I am involved in with any replies that I
may have a potential answer to and have been promoting this OS and in
particular the potential of Ardour to many fellow professionals in the
industry. I also have rad and learnt as much as I could to give
qualitative feedback to any problems I incur.

All I seek is the ability to use open source software in preference to
rip-off commercial apps. Yes, I admit there is potential for both to
exist on this platform and would use some commerical apps to aide in
crossover but that is not the point of this (ardour-dev) list. 

It would seem only the MusE list responds to anything I send, and only a
few particular individuals at that. 

Aside from being upset, it appears to me that you guys are all a bunch
of hypocrites.. Asking for further information, and clarification but
never actually responding, while I do everything that I can possibly
thing\k of in aiding you answer my questions.. yet continue to be
ignored... It does not seem to be a coincidence that all response ended 
after my response to the string ahem. 

So I've wasted 2+ years of my life and countless dollars continuing down
this path.

Yes this is an emotional response as it seems like my friends advised me
I should have just bought a Mac ,, inferior latency aside.. at least the
support groups there (even those non-funded as this list) genuinely
help. 

My only problem is , where do I go from here?? This really saddens me as
I thought this (Linux)  was the future. It seems it is only a future for
the GPL elite. 


extremely pissed off

Allan Klinbail  



 

  









Re: [linux-audio-dev] why is no-one responding are you all just abunch of *^%^%^ wits???]

2003-02-12 Thread Allan Klinbail
-Forwarded Message-

From: Son of Zev [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Alsa-dev 


Thanks Vincent.

Your reply is appreciated. 

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.. Credit goes to some who have especially Takashi Iwai, Robert
Jonsson, Tommi Ilmonen and a few others. 

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

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 

cheers

Allan 



On Thu, 2003-02-13 at 00:50, Vincent Touquet wrote:
 I'm not a real coder either (so one might argue I shouldn't be on
 linux-audio-dev, but I'm just interested in the discussions), so I think
 I understand the root cause of your grief.
 
 I think if (if) the Ardour developers are _expecting_ quality feedback
 from normal users (not just programmers) at this stage, they should
 provide tarballs of the stable CVS snapshots they want to be tested.
 
 But maybe they want to wait for 1.0 before letting endusers test it?
 In that case, maybe you tried to use it too early in its development ?
 I think they honestly appreciate your effort to participate, there
 should be no doubt about that, but maybe Ardour is still changing too
 rapidly for you to be able to track it.
 
 I think only the developers of Ardour can clear out this question.
 
 best regards,
 Vincent





[linux-audio-dev] mutiband compressor plugin?

2002-09-01 Thread Allan Klinbail

Hi All

Does anyone know of a multiband compressor plugin suitable for
mastering? 

Or is anyone interested in building one.. ? 

cheers

Allan 
-- 
Linux: Because a PC is a terrible thing to waste.
(By [EMAIL PROTECTED], Mark Komarinski)

-- 
Linux: Because a PC is a terrible thing to waste.
(By [EMAIL PROTECTED], Mark Komarinski)





Re: [linux-audio-dev] USB Souncards

2002-01-19 Thread Allan Klinbail

Hi

This is more of a general comment 

I'd try and steer away from USB audio... 
Reports in magazines like Sound on Sound and Audio Technology (an
Australian publication) don't rate any USB audio devices highly .. due
to the low bandwidth and shared nature of the USB protocol. i.e. the
FOstex USB Midi/audio desk (sorry can't remember the model) can't handle
full spec MIDI and all audio processes at one time... 

When using laptops it is highly recommended to use a firewire hard disk
as your recording media as the latency of the hard drive on even the
best laptops is unacceptable under any OS (especially when multitracking
even just on output).

From reading the alsa-user-ML archives I have seen various reports.
Basically ALSA has not written support for USB audio specifically as
yet, however some people have had some luck in getting these devices to
work. 

I would recommend posting a question to the alsa-user mailing list
[EMAIL PROTECTED] (you need to be a member) to see how easily
it has been done, and with which devices.. if this is your only option.

My strongest reccomendation would be either to wait till there is a
firewire audio device, with it's information released so that someone
can write a driver specific to it. (i.e. not the MOTU or other devices
currently out there). With any luck maybe the mLan spec will be
available to open source developers at some stage and an mLan
(firewire) device would be the strongest suggestion, especially with
future  studio expansion in mind. 

Allan


On Fri, 2002-01-18 at 14:15, Brad Bowman wrote:
 I was planning to get a new sound card to use now
 with my current fragile laptop and future whizz-bang
 desktop.  As they only have USB in common I thought
 that might be best although hints in the earlier
 usb audio thread have worried me.  If I'm paying
 a premium price for poor performance then I might
 just wait until I'm in a position to get a nice
 desktop.
 
 So, in short, what are the issues with USB sound cards
 under Linux?  In particular, does it effect latency and
 realtime reliability?
 
 Thanks,
 
 Brad