James Harkins | 1 Feb 2004 04:27
Picon
Favicon

Environment.pop - debug calls

Just discovered some spurious debug calls in Meta_Environment-pop. I 
have removed them and committed the revision.

H. James
____________________________________

H. James Harkins /// dewdrop_world
http://www.duke.edu/~jharkins

"If attacked by a lion, thrust your arm down his throat.
This takes some practice."  -- Cyril Connolly
Fredrik Olofsson | 2 Feb 2004 03:02

some helpfile typos to fix

for anyone with 5min. to spare...

Document helpfile:
.new method - wrong order of text, title

FunctionDef help:
"literals"
obsolet.  perhaps add a short note on selectors?  what are those 
anyway?  all objects inside of a function?

Streams-Patterns-Events6help:

"/* CRASHES THE LANG"
no it doesn't.

"// BUGGY - SOMEHOW DISABLES PATTERNS IF ONE OF THESE IS NOT 0.0"
seems to work now too.

"( // BUGGY - THIS ONE SOMEHOW DISABLES PATTERNS"
works as far as i can see.

   #|
      fredrikolofsson.com     klippav.org
   |#
James McCartney | 2 Feb 2004 05:22
Picon

Re: some helpfile typos to fix


selectors contains names of methods called in this method.

On Feb 1, 2004, at 6:02 PM, Fredrik Olofsson wrote:

> obsolet.  perhaps add a short note on selectors?  what are those 
> anyway?  all objects inside of a function?
>
--
james mccartney
http://www.audiosynth.com
Dave Watson | 2 Feb 2004 18:50

Re: some helpfile typos to fix

I committed most of these changes.  All of them except for the one to
the FunctionDef help file.

If anyone else has a little time the help file for DetectSilence is also
incorrect.

--Fredrik Olofsson <f@...> [040201 18:11]:
> for anyone with 5min. to spare...
> 
> Document helpfile:
> .new method - wrong order of text, title
> 
> Streams-Patterns-Events6help:
> 
> "/* CRASHES THE LANG"
> no it doesn't.
> 
> "// BUGGY - SOMEHOW DISABLES PATTERNS IF ONE OF THESE IS NOT 0.0"
> seems to work now too.
> 
> "( // BUGGY - THIS ONE SOMEHOW DISABLES PATTERNS"
> works as far as i can see.
Kasper Souren | 2 Feb 2004 19:36
Picon
Favicon

Re: [linux] sc3 ebuild

ian esten wrote:
> for all the gentoo users out there.
> i believe gentoo have recently changed their policy and now cvs ebuilds
> can't be part of the portage tree. so, to use this ebuild:

Thanks! It works okay here. But I wonder what happens with the 
plugins. `qpkg -l supercollider-cvs|grep plugins` shows me 
there are none installed by the ebuild.

That it still works here is probably due to the 
/usr/local/lib/SuperCollider/plugins that come from the hand 
compiled cvs.

 > src_compile() {
 > 	./linux/bootstrap
 >
 > 	local myconf
 > 	local myarch
 >
 > 	myarch=`get-flag -march`
 > 	myconf="--with-audio-api=jack"
 >
 > 	cd $S
 >
 > 	econf ${myconf} || die "configure failed"
 > 	emake || die "parallel make failed"
 > }
 >
 > src_install() {
 > 	einstall || die "make install failed"
(Continue reading)

Scott Wilson | 2 Feb 2004 22:37

Re: some helpfile typos to fix


On Monday, February 2, 2004, at 12:50  PM, Dave Watson wrote:

> I committed most of these changes.  All of them except for the one to
> the FunctionDef help file.

Committed.

>
> If anyone else has a little time the help file for DetectSilence is 
> also
> incorrect.
>
I'll do this, but:

I assume amp is the threshold beneath which in must fall and time is 
the amount of time it must remain there before doneAction is evaluated. 
Can someone confirm this?

Also, is DetectSilence limited to the doneActions listed in the class 
file or will it work with all the ones available to EnvGen? I assume 
the comments in the class file are just out of date, correct?

S.
Julian Rohrhuber | 3 Feb 2004 01:02
Picon
Favicon

/n_release

wouldn't it be a good idea to have an osc message?
it could have the following behaviour:

if (the node is a synth) {
	if (it has a gate arg) {
		 set this arg to zero
	} else { free the node }
} else { free the node }  // or do the above recursively, don't know.

this would avoid a bit of logic in sclang, as we wouldn't have to
care about how the synth releases itself.

the argument sent with it could be the release time if it has a gate.

moreover (maybe), the doneActions could use this instead of \free,
which would make it softer in sound.
--

-- 

.
James McCartney | 3 Feb 2004 01:19
Picon

Re: /n_release


On Feb 2, 2004, at 4:02 PM, Julian Rohrhuber wrote:

> wouldn't it be a good idea to have an osc message?
> it could have the following behaviour:
>
> if (the node is a synth) {
> 	if (it has a gate arg) {
> 		 set this arg to zero
> 	} else { free the node }
> } else { free the node }  // or do the above recursively, don't know.
>
> this would avoid a bit of logic in sclang, as we wouldn't have to
> care about how the synth releases itself.

I don't think this is correct. Under some conditions it will create 
more logic not less.
Currently if a sound has a percussive envelope and you send it a gate 
off message then there is no harm done, nothing happens and the sound 
will still fade out and end by itself. If this message were implemented 
as above then you had better be careful not to send an n_release 
message to a percussive sound or it will cut off the decay too doon.

> the argument sent with it could be the release time if it has a gate.

then that would be like voice stealing. It means that the controlling 
function needs to know how long the decay for the note should be. That 
should be a function of the envelope.

> moreover (maybe), the doneActions could use this instead of \free,
(Continue reading)

James McCartney | 3 Feb 2004 03:10
Picon

Re: /n_release


On Feb 2, 2004, at 4:19 PM, James McCartney wrote:

> or it will cut off the decay too doon.

too soon.
andi | 3 Feb 2004 11:58
Picon

libsndfile static linking

hi,

i have troubles linking libsndfile from the xcode project. anybody any 
hints? other than that, i switched to panther, so binary snapshots 
should continue to be released regularly when this problem is solved.

andi

Gmane