I asked about this a while back but got no response, does that mean no 
one is working on multi port midi for csound5?

I consider this to be one of csounds main weaknesses for real time work. 
I realize it is also a problem because any solution introduces backwards 
compatibility nightmares. If nothing else is being done, I propose the 
following solution, which I think would be a good addition nontheless.

We add an opcode, midiinrouter or somesuch. It acts like midi in with 
two differences, obviously multi ports, but also have it possible for it 
to empty the entire midiin queue and dispatch all events, *within one 
kpass*. This is the one horrible thing about midiin for realtime work 
with low kcycles. I'm envisioning being able to have a midi router 
instrument that simply empties the whole queue and then makes event 
calls to send the data to other instruments, thus having any midi events 
currently in the queue in one kpass all synced up. This would actually 
*improve* midi event synchronization at the expense of max one kpass 
latency instead of the opposite. Other instruments have only to act as 
if an event call of the right amp is a midi off or act like a turn off 
call is a note off.

Thoughts? If no one else is interested I will try looking into the 
opcode myself, though it may take me a while as I am quite busy with 
some other ( bread and butter ) coding right now. And I would like input 
by better csounders to do it right.

Thanks
Iain



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I would rather like to have a feature freeze now, that is, assuming
there are other people (not just me) who want an actual release of
Csound 5 to happen in a finite and preferably not very long time,
rather than staying indefinitely in this ever-beta status.
So, would it be possible to temporarily stop adding new opcodes,
frontends and other new features so that we can finally have a
release ?

Iain Duncan wrote:

> I asked about this a while back but got no response, does that mean no 
> one is working on multi port midi for csound5?
> 
> I consider this to be one of csounds main weaknesses for real time work. 
> I realize it is also a problem because any solution introduces backwards 
> compatibility nightmares. If nothing else is being done, I propose the 
> following solution, which I think would be a good addition nontheless.
> 
> We add an opcode, midiinrouter or somesuch. It acts like midi in with 
> two differences, obviously multi ports, but also have it possible for it 
> to empty the entire midiin queue and dispatch all events, *within one 
> kpass*. This is the one horrible thing about midiin for realtime work 
> with low kcycles. I'm envisioning being able to have a midi router 
> instrument that simply empties the whole queue and then makes event 
> calls to send the data to other instruments, thus having any midi events 
> currently in the queue in one kpass all synced up. This would actually 
> *improve* midi event synchronization at the expense of max one kpass 
> latency instead of the opposite. Other instruments have only to act as 
> if an event call of the right amp is a midi off or act like a turn off 
> call is a note off.


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Istvan Varga wrote:
> I would rather like to have a feature freeze now, that is, assuming
> there are other people (not just me) who want an actual release of
> Csound 5 to happen in a finite and preferably not very long time,
> rather than staying indefinitely in this ever-beta status.
> So, would it be possible to temporarily stop adding new opcodes,
> frontends and other new features so that we can finally have a
> release ?

Sure, I can respect that. I will be happy to play with my ideas on my 
own and let others help with the brainstorming if interested, but avoid 
any additions that will delay a release. As I don't do anything that 
goes in a release, me tinkering with this should have no effect one way 
or another. I think something as important as multi device midi i/o 
should be done properly too, so not rushing that is a good plan. I will 
say however, that it is one of the weaknesses that gets me funny looks 
when I try to get others to try csound, and I remember years ago it was 
on the to do list for csound5, I guess it fell off somehow.

Iain



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hear, hear!  Let us have a release of 5.0 in days or weeks.  Certainly
this year.  I would like to see concentration on installers.

My interest tends to Csound as a stand-alone, and by installer is
aimed at that on Linux and Mac.
==John ffitch


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Steven Yi wrote:

> In terms of time table, installers seem like the most pressing thing
> on everyone's minds, as the rest of the above seem in very good shape
> (bravo all of you! ^_^).  Just to get some kind of timeline out for
> consideration, would a rough schedule of getting installers done in a
> week,

Actually, the installers are a major problem, and it is not likely
that this issue is going to be solved in a week or even in any
predictable amount of time. It would be possible to have installers
for Windows and OS X in 1-2 weeks if anyone would actually work on
it - but that is not the case (the situation is particularly bad
with respect to the Mac platforms). Linux is a different issue: we
already have scripts for generating packages, but due to the lack of
binary compatibility and different directory structure, a separate
package should be generated for every commonly used distribution
and release, and there is just no one who would actually do that
tedious task. Thus, the standard means of installing on Linux still
remains compiling from sources.


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Nov 19, 2005, at 7:08 AM, Istvan Varga wrote:

> Actually, the installers are a major problem, and it is not likely
> that this issue is going to be solved in a week or even in any
> predictable amount of time. It would be possible to have installers
> for Windows and OS X in 1-2 weeks if anyone would actually work on
> it - but that is not the case (the situation is particularly bad
> with respect to the Mac platforms).

I have created a preliminary installer package for Macintosh OS 10.  
(Tested on OS 10.3.9)

It can be found here

http://www.csounds.com/akbari/Csound5beta-inst1.dmg.bz2

It contains

On Nov 19, 2005, at 5:17 AM, jpff@codemist.co.uk wrote:

> Binaries:
>          
> brkpt,cs,csb64enc,cscore,csound,cvanal,dnoise,envext,extract,extractor,
>          
> het_export,het_import,hetro,linseg,lpanal,lpc_export,lpc_import,makecsd 
> ,
>         mixer,pvanal,pvlook,scale,scot,scsort,sdif2ad,srconv,tabdes
>
> Opcodes+Modules: (all lib*.so files)
>
> Libraries:
>         libcsound, liblo, libportaudio, libsndfile
>
> Manual in HTML:

+ A custom set of example csd files and example .csoundrc file.

This package was compiled with GCC 3.x at both single and double  
precision. In the compressed disk image, there are two packages, one is  
Csound and the other is dependencies. I used the following convention  
in the install targets

Csound5.pkg

(../ = /csound5 by default but is relocatable)

../bin - 32bit float binaries
../bin64 - 64bit double precision binaries
../examples - a custom Csound test suite of example files that != the  
canonical examples folder
../lib - all opcodes at single precision
../lib64 - all opcodes at double precision
../manual - manual compiled from CVS

Csound5-Deps.pkg

libcscore.a
libfltk_forms.1.1.dylib
libfltk_forms.a
libfltk_forms.dylib
libfltk_gl.1.1.dylib
libfltk_gl.a
libfltk_gl.dylib
libfltk_images.1.1.dylib
libfltk_images.a
libfltk_images.dylib
libfltk_jpeg.a
libfltk_png.a
libfltk.1.1.dylib
libfltk.a
libfltk.dylib
libjpeg.62.0.0.dylib
libjpeg.62.dylib
libjpeg.a
libjpeg.dylib
libjpeg.la
liblo.0.4.0.dylib
liblo.0.5.0.dylib
liblo.0.dylib
liblo.dylib
liblo.la
libpmidi.dylib
libpng.3.1.2.8.dylib
libpng.3.dylib
libpng.a
libpng.dylib
libpng12.0.1.2.8.dylib
libpng12.0.dylib
libpng12.a
libpng12.dylib
libportaudio.a
libportaudio.dylib
libportaudio.dylib.0.0.19
libportmidi.a
librtpa.dylib
libsndfile.1.0.11.dylib
libsndfile.1.dylib
libsndfile.a
libsndfile.dylib
libsndfile.la
libtiff.3.7.2.dylib
libtiff.3.dylib
libtiff.a
libtiff.dylib
libtiff.la

all files were compiled from today's (Nov 19, 2005) CVS sources. The  
main difference is that this build includes the python opcodes, FLTK,  
and OSC (and their required libraries).


-David



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net