Hi all,
I've released pd 0.35 test 9 on the usual,
http://crca.ucsd.edu/~msp/software.html
... most of the big problems in test 8 are fixed, but some little ones remain.
For Windows users, the default is now not even to try to open midi input, but you can still override this with "-midiin 1" flag (put this in a shortcut for easiest use.) If you have MIDI input open and you close Pd's "command prompt" window, you can hose Windows!!! I'm going to have to try to contact Microsoft to get some advice how to deal with this one... that's why the default is now not to open MIDI input.
cheers Miller
Hi Miller,
is the Windows readsf~ and writesf~ stuff in this or do I still need to patch it? ( can't remember all the details off hand but I sent and email a week or so ago).
cheers
mark
-----Original Message----- From: Miller Puckette [mailto:mpuckett@man104-1.ucsd.edu] Sent: 13 February 2002 17:29 To: pd-list@iem.kug.ac.at Subject: [PD] pd 0.25 test 9
Hi all,
I've released pd 0.35 test 9 on the usual,
http://crca.ucsd.edu/~msp/software.html
... most of the big problems in test 8 are fixed, but some little ones remain.
For Windows users, the default is now not even to try to open midi input, but you can still override this with "-midiin 1" flag (put this in a shortcut for easiest use.) If you have MIDI input open and you close Pd's "command prompt" window, you can hose Windows!!! I'm going to have to try to contact Microsoft to get some advice how to deal with this one... that's why the default is now not to open MIDI input.
cheers Miller
It's not there... I'll look at this, it probably won't break anything if I put this in and I don't see any licensing problems.
cheers Miller
On Wed, Feb 13, 2002 at 06:24:44PM -0000, mark wrote:
Hi Miller,
is the Windows readsf~ and writesf~ stuff in this or do I still need to patch it? ( can't remember all the details off hand but I sent and email a week or so ago).
cheers
mark
-----Original Message----- From: Miller Puckette [mailto:mpuckett@man104-1.ucsd.edu] Sent: 13 February 2002 17:29 To: pd-list@iem.kug.ac.at Subject: [PD] pd 0.25 test 9
Hi all,
I've released pd 0.35 test 9 on the usual,
http://crca.ucsd.edu/~msp/software.html
... most of the big problems in test 8 are fixed, but some little ones remain.
For Windows users, the default is now not even to try to open midi input, but you can still override this with "-midiin 1" flag (put this in a shortcut for easiest use.) If you have MIDI input open and you close Pd's "command prompt" window, you can hose Windows!!! I'm going to have to try to contact Microsoft to get some advice how to deal with this one... that's why the default is now not to open MIDI input.
cheers Miller
hi,
[f]expr[~] does not compile in linux, looking for m_pd.h in
LINUXINCLUDE = -I/usr/local/include
while LINUXINCLUDE = -I../../src is much more likely a place to find it.
Krzysztof
Oops... will fix for test 10 (tonight?)
cheers Miller
On Fri, Feb 15, 2002 at 10:39:17AM +0100, Krzysztof Czaja wrote:
hi,
[f]expr[~] does not compile in linux, looking for m_pd.h in
LINUXINCLUDE = -I/usr/local/include
while LINUXINCLUDE = -I../../src is much more likely a place to find it.
Krzysztof
hi Miller,
probably two of the little ones:
All the regular arrays -- unless they have beed created in an older Pd version, or converted manually -- are flipped _on display_, i.e. they have Y-bounds reverted, while those in [table]s are not.
If an array is created in a new graph, glist_addglist() gets
Y to:' == -1,
Y from:' == 1, and all the pixel coordinates
equal 0. This means the graph is not reflipped, because
``if (py2 < py1)'' condition does not hold. Tables differ,
because although glist_addglist() is passed the same Y-bound
values, py2 == 50, py1 == 350, and the graph is reflipped.
(Sorry if I am missing something obvious, but I still cannot come to terms with array flipping.)
Also [table]'s window is still unnamed, due to lacking x/y atoms in a canvas_new() call (you will find a patch against test8 in my `$0-array' posting from 03 Feb 2002).
Krzysztof
Miller Puckette wrote: ...
... most of the big problems in test 8 are fixed, but some little ones remain.
Miller Puckette hat gesagt: // Miller Puckette wrote:
For Windows users, the default is now not even to try to open midi input, but you can still override this with "-midiin 1" flag
I found a problem with midiin under linux, I think. I use two midi in devices normally, one for the keyboard and one for sequencer, and I start with "-midiindev 2,23". With test9, I could not get midi input from /dev/midi22 anymore unless I select only one to use, i.e. "-midiindev 23" works.
__ __
Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______
/ __// __ /__/ __// // __ \ / / __ \ ___\
/ / / ____/ / / / // ____// /\ \ ___\____ \
/_/ /_____/ /_/ /_//_____// / \ \_____\_____
/_/ _\
Oops!
in s_main.c, line 59, change
int sys_midiindevlist[1] = {0}; int sys_midioutdevlist[1] = {DEFMIDIOUTDEV};
to
int sys_midiindevlist[MAXMIDIINDEV] = {0}; int sys_midioutdevlist[MAXMIDIOUTDEV] = {DEFMIDIOUTDEV};
duh... Thanks for flagging it.
Miller
On Sun, Feb 17, 2002 at 05:15:21PM +0100, Frank Barknecht wrote:
Miller Puckette hat gesagt: // Miller Puckette wrote:
For Windows users, the default is now not even to try to open midi input, but you can still override this with "-midiin 1" flag
I found a problem with midiin under linux, I think. I use two midi in devices normally, one for the keyboard and one for sequencer, and I start with "-midiindev 2,23". With test9, I could not get midi input from /dev/midi22 anymore unless I select only one to use, i.e. "-midiindev 23" works.
Ciao,
__ __
Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______ / __// __ /__/ __// // __ \ / / __ \ ___\ / / / ____/ / / / // ____// /\ \ ___\____ \ /_/ /_____/ /_/ /_//_____// / \ \_____\_____
/_/ _\