Csound Csound-dev Csound-tekno Search About

Re: [Cs-dev] Csound5 MIDI changes - some testing needed

Date2005-02-21 21:19
From"Art Hunkins"
SubjectRe: [Cs-dev] Csound5 MIDI changes - some testing needed
Istvan et al,

Yes, that is what I'm asking for.

In a larger context, what I'm asking for is an example of this: let's try to
make, from the *user's* standpoint, CS5 work as similar to CS4 as possible.
(-M0 corresponds/defaults to the first MIDI *input* device on MyCsound4
(Lazzarini) and GBS8 (Ramsdell) and the comparable flag in CsoundAV.)

It may well be because of the lack of MIDI out in CS4 that the flag -M0
always returns the first MIDI input device. IMO -M0 should correspond to the
first MIDI input device in CS5 as well.

Frankly, I'd like -M to bring up a window of MIDI input device choices,
and -o dac to bring up a window of audio output devices - just like CsoundAV
does - but this may be asking for too much. However, it's *very user
friendly* - and this is what we need to aim for.

I expect Dr. B would back me on this "user friendly/intuitive" priority.

Art Hunkins

----- Original Message -----
From: "Istvan Varga" 
To: 
Sent: Monday, February 21, 2005 3:25 PM
Subject: Re: [Cs-dev] Csound5 MIDI changes - some testing needed


> Art Hunkins wrote:
>
> > I hope this fixes the -M0 problem, for which CS5 used to interpret as
MIDI
> > *output* rather than the first input device. So, now does -M0 "default"
to
> > the first MIDI input device?
>
> -M0 is interpreted as the first PortMIDI device, which may be input or
> output depending on your system. With some effort it may be changed to
> skip numbers of devices of the wrong type, although there are also more
> important issues to deal with right now.
> What you are asking for is mapping device numbers as shown below:
>
> INPUT
>     1: EMU10K1 MPU-401 (UART) (ALSA)     => -M 0
>     7: VirMIDI 1-0 (ALSA)                => -M 1
>     9: VirMIDI 1-1 (ALSA)                => -M 2
>    11: VirMIDI 1-2 (ALSA)                => -M 3
>    13: VirMIDI 1-3 (ALSA)                => -M 4
>
> OUTPUT
>     0: EMU10K1 MPU-401 (UART) (ALSA)     => -Q 0
>     2: Emu10k1 Port 0 (ALSA)             => -Q 1
>     3: Emu10k1 Port 1 (ALSA)             => -Q 2
>     4: Emu10k1 Port 2 (ALSA)             => -Q 3
>     5: Emu10k1 Port 3 (ALSA)             => -Q 4
>     6: VirMIDI 1-0 (ALSA)                => -Q 5
>     8: VirMIDI 1-1 (ALSA)                => -Q 6
>    10: VirMIDI 1-2 (ALSA)                => -Q 7
>    12: VirMIDI 1-3 (ALSA)                => -Q 8
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-02-21 21:25
From"Richard Boulanger"
SubjectRe: [Cs-dev] Csound5 MIDI changes - some testing needed
Art,

As regards clear and intuitive user interface, I am right with you there
Art.  

I have been working with csound5 now a bit.  Phew....  This is not for
beginners at all...  If you have been doing your composing with WinSound,
CsoundAV, SuperMills, or MacCsoound - you can forget it.

It might be possible for one to make the first step if there were a simple
set of test/demo orchestras and command-lines that would cover all the
basics with Csound5.  In essence, a folder filled with  presets/demos/tests
that - once installed, anyone could fire off this or that command line and
get to run.

I would leave it to the Csound5 developers to tell us what orchestras would
comprise this test set, and what would they need to test?

Real-time
MIDI
Write to File
Plugin opcodes
UDOs
Include files
Multi-Channel Output
Real-Time Audio IN
InterApplication Communication
Python Driven Orcs
Changing buffer sizes
Analysis and Other Utilities
JACK
FTLK

Thus, all these (and any/many others that you Csound5 developers would come
up with) should be included with Csound5 distributions as the
"starter-testor pak" - and the included set of sample command-line files
should be easy for the beginner/testor to run with when testing and modify
by substituting their own .orc/.sco/.csd when composing.

-Dr.B.

on 2/21/05 4:19 PM, Art Hunkins at abhunkin@uncg.edu wrote:

> Istvan et al,
> 
> Yes, that is what I'm asking for.
> 
> In a larger context, what I'm asking for is an example of this: let's try to
> make, from the *user's* standpoint, CS5 work as similar to CS4 as possible.
> (-M0 corresponds/defaults to the first MIDI *input* device on MyCsound4
> (Lazzarini) and GBS8 (Ramsdell) and the comparable flag in CsoundAV.)
> 
> It may well be because of the lack of MIDI out in CS4 that the flag -M0
> always returns the first MIDI input device. IMO -M0 should correspond to the
> first MIDI input device in CS5 as well.
> 
> Frankly, I'd like -M to bring up a window of MIDI input device choices,
> and -o dac to bring up a window of audio output devices - just like CsoundAV
> does - but this may be asking for too much. However, it's *very user
> friendly* - and this is what we need to aim for.
> 
> I expect Dr. B would back me on this "user friendly/intuitive" priority.
> 
> Art Hunkins
> 
> ----- Original Message -----
> From: "Istvan Varga" 
> To: 
> Sent: Monday, February 21, 2005 3:25 PM
> Subject: Re: [Cs-dev] Csound5 MIDI changes - some testing needed
> 
> 
>> Art Hunkins wrote:
>> 
>>> I hope this fixes the -M0 problem, for which CS5 used to interpret as
> MIDI
>>> *output* rather than the first input device. So, now does -M0 "default"
> to
>>> the first MIDI input device?
>> 
>> -M0 is interpreted as the first PortMIDI device, which may be input or
>> output depending on your system. With some effort it may be changed to
>> skip numbers of devices of the wrong type, although there are also more
>> important issues to deal with right now.
>> What you are asking for is mapping device numbers as shown below:
>> 
>> INPUT
>>     1: EMU10K1 MPU-401 (UART) (ALSA)     => -M 0
>>     7: VirMIDI 1-0 (ALSA)                => -M 1
>>     9: VirMIDI 1-1 (ALSA)                => -M 2
>>    11: VirMIDI 1-2 (ALSA)                => -M 3
>>    13: VirMIDI 1-3 (ALSA)                => -M 4
>> 
>> OUTPUT
>>     0: EMU10K1 MPU-401 (UART) (ALSA)     => -Q 0
>>     2: Emu10k1 Port 0 (ALSA)             => -Q 1
>>     3: Emu10k1 Port 1 (ALSA)             => -Q 2
>>     4: Emu10k1 Port 2 (ALSA)             => -Q 3
>>     5: Emu10k1 Port 3 (ALSA)             => -Q 4
>>     6: VirMIDI 1-0 (ALSA)                => -Q 5
>>     8: VirMIDI 1-1 (ALSA)                => -Q 6
>>    10: VirMIDI 1-2 (ALSA)                => -Q 7
>>    12: VirMIDI 1-3 (ALSA)                => -Q 8
>> 
>> 
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

_______________________________________________________________________
 +  Dr. Richard Boulanger, Professor
 +  Music Synthesis Department, Berklee College of Music
 +  1140 Boylston Street  - Boston, MA  02215-3693
 +  Office Phone: (617) 747-2485   Office Fax: (617) 747-2564
 +  eMail: rboulanger@csounds.com  or  rboulanger@berklee.edu
 +  WebPage: http://csounds.com/boulanger/
________________________________________________________________________
 +  Almost Everything Csound @ http://csounds.com/
 +  The Csound Catalog with Audio @ http://csounds.com/catalog/
 +  The Csound Book @ http://csounds.com/book/
 +  The Csound Magazine @ http://csounds.com/ezine/
 +  CsoundForums @ http://csounds.com/phpBB2/
________________________________________________________________________



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net