[openbeos-midi] Re: Everybody Ready

  • From: Kevin Kuo <shaggyafterjack@xxxxxxxxx>
  • To: openbeos-midi@xxxxxxxxxxxxx
  • Date: Mon, 15 Apr 2002 20:48:41 -0700 (PDT)


Way to get the ball moving!

well, I don't have midi hardware I think (using an Intel 810 mobo with celeron
500).  As far as midi knowledge is concerned, I know as much or as little as
the  next general purpose (lol) programmer you are going to come across -- very
little.  But, learning is always cool with me.

so let me list this out:
  BSamples -- if it has something to do with sound sampling
  BMidiSynth -- at least knowing what the hell it is

2)~200 MB/day
3)celeron 500 running linux with i810 (embedded sound, and video);
  p3 500 notebook
  neither has midi AFAIK
5)I'll buy Be compliant midi keyboards, devices, etc if necessary, so I can
work on some hardware level stuff.

In my experience, it has been easier to get structures that fill the role first
and then build the class methods that use them.  For rapid development and
experimentation we can use python to get a feel of what data structures we need
and what kind of methods.  Once we have a good feeling, we can start
translating that over to C++

Also, does anyone have the BeOS API then?  And how do I get a version of BeOS
R5 running on my computer?


--- Paul Stadler <paul_stadler@xxxxxxxxxxx> wrote:
> All,
> I'm anxious to get this thing going, and you probably are too.  The first 
> thing I'd like to do is come up with a development plan.  Since the API is 
> already layed out for us, there's not much surface level design needed, but 
> we can discuss guts a little bit if you like.  We don't need to be perfectly 
> clear on this but instead just need to get everyone moving in the same 
> direction.
> Simply enough, we'll need to just run through and implement each class.  
> What I need to know from everyone is:
> 1) What your interest is (as far as which class).
> 2) What your bandwidth is.
> 3) What your hardware configuration is. (important for BMidiPort, and the 
> synth)
> 4) What your experience with MIDI is.
> 5) How willing you are to stray from (1).
> Hopefully, we'll be able to find a good allocation for everyone such that 
> this thing can be implemented rapidly and with quality.
> The order that I have in mind for the classes is something like this:
> 1) BMidi
> 2) BMidiText (so we can see what's going on)
> 3) BMidiStore (no hardware required here... just files)
> 4) BMidiPort (need hardware for this)
> 5) BSynth
> 6) BMidiSynth
> 7) BMidiSynthFile
> 8) BSamples
> [A test app probably should be in there somewhere.]
> The order above is one that satisfies some of the dependencies among 
> classes.  Personally, I believe in stubbing out the entire structure before 
> filling in the classes.  I don't know what methodology you are used to, so 
> please chip in your feedback there as well.  Please let me know what your 
> thoughts are on this.  Please don't hesitate to criticize and/or contribute.
> Cheers,
> Paul
> _________________________________________________________________
> Send and receive Hotmail on your mobile device: http://mobile.msn.com

Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax

Other related posts: