pythonsound-devel Mailing List for The Python Sound Project (Page 2)
Status: Beta
Brought to you by:
mupuxeddu
Menu
▾
▴
pythonsound-devel — Generic list for developers
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(53) |
Nov
(7) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Paul W. <sli...@ya...> - 2001-10-23 01:59:33
|
A number of minor fixes made: omde/rhythm.py: - spelling fixes... rythm -> rhythm INSTALL: added note about SCALA and SHARC databases, since omde won't install without them. setup.py: Changed pathnames to use os.path.join for platform independence omde/chaos.py: Bug fixed: changed omde.function.make_function to omde.functional.make_function omde/functional.py: Bugs fixed: Freezer() had __init__ defined twice - the second one should be __call__(). Docstrings: many used generator when they meant function. -- paul winkler home: http://www.slinkp.com music: http://www.reacharms.com calendars: http://www.calendargalaxy.com |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-21 00:20:28
|
On Sat, 20 Oct 2001, Paul Winkler wrote: > Hi Maurizio, > > I can't seem to check in some little fixes. Haven't used cvs except > for checkout before... What am I missing? > > [pw@roaddog omde]$ cvs -z3 -d:pserver:sl...@cv...:/cvsroot/pythonsound login > (Logging in to sl...@cv...) > CVS password: > [pw@roaddog omde]$ cvs commit -m "Spelling corrections: rythm -> rhythm" omde/rhythm.py cvs [server aborted]: "commit" requires write access to the repository You need to use SSH. export CVS_RSH=ssh export CVS...@cv...:/cvsroot/pythonsound See the "Developer CVS Access via SSH" section here: http://sourceforge.net/cvs/?group_id=15938 and this docs if you need more info about SSH http://sourceforge.net/docman/display_doc.php?docid=761&group_id=1 http://sourceforge.net/docman/display_doc.php?docid=6841&group_id=1 Hope this helps, Maurizio Umberto Puxeddu. |
|
From: Paul W. <sli...@ya...> - 2001-10-20 22:32:48
|
Hi Maurizio, I can't seem to check in some little fixes. Haven't used cvs except for checkout before... What am I missing? [pw@roaddog omde]$ cvs -z3 -d:pserver:sl...@cv...:/cvsroot/pythonsound login (Logging in to sl...@cv...) CVS password: [pw@roaddog omde]$ cvs commit -m "Spelling corrections: rythm -> rhythm" omde/rhythm.py cvs [server aborted]: "commit" requires write access to the repository -- paul winkler home: http://www.slinkp.com music: http://www.reacharms.com calendars: http://www.calendargalaxy.com |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-20 00:16:50
|
Hello. Since the same generators could be used not only in pmask but in other context (for example Aggregate.timewarp() method), they are now part of OMDE. There are now two kind of "generator" base classes: Function and Generator. Function are function of time, they are evaluated at a specific time f(t0) Generator are objects that simply return something each time you call them. There is a way to convert a Generator to a Function and to freeze a Function into a Generator. I introduced the Converter subclass of Generator to integrate the code by Erasmus. There is no more a pmask package but only a omde.pmask module. Maurizio Umberto Puxeddu. |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-19 23:57:47
|
I dropped happydoc and adopted pydoc since this is the standard docstring processing tool from Python 2.1 on. The resulting reference documentation is available here: http://pythonsound.sourceforge.net/reference/omde.html It's linked from the http://pythonsound.sourceforge.net/ home page. Maurizio Umberto Puxeddu. |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-19 23:48:51
|
I fixed a bug in makeScalaDB utility (it used to put full pathname of the .scm file on my machine instead of scale name) and I had to rebuild the scales files. I also completed the omde.spectrum module and makeSharcDB. I'm trying to get in contact with G.Sandell and have the permission to include the SHARC database in the OMDE/pmask tarballs. You can download both databases using the downloadDB script in utility/ cd utility ./downloadDB ../omde Maurizio Umberto Puxeddu. |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-19 02:08:46
|
Hello. I committed lots of changes to the repository. Tomorrow I'll post a report. You will prefer delete your tree and checkout omde from scratch. Sorry but I'm tired. Regards, Maurizio Umberto Puxeddu. |
|
From: Paul W. <sli...@ya...> - 2001-10-11 17:18:13
|
On Thu, Oct 11, 2001 at 02:20:21PM +0200, Maurizio Umberto Puxeddu wrote: > I agree. I turned self.*0 in self._* etc and self.cached_* in > self._cached_*. Sounds good. > I added slinkp to the team. > You can still send me patches if you feel more comfortable. Also when > doing large scale changes it is better to send me a patch at the moment. > For small bugs fixes and doctest you can directly commit them to the > repository. OK. For anything large, I will want to check with you anyway. > Why do you like > > a = 1; b = 2 > > instead of > > a, b = 1, 2 > > ? It's an unnecessary optimization. Feel free to ignore it. Got the idea from a comp.lang.py post: http://groups.google.com/groups?q=fastest+group:comp.lang.python&hl=en&as_qdr=m&rnum=2&selm=2261322.7AAxBmiTta%40lunix.schabi.de Looking at the timings in that post again, there's not enough speed difference (maybe 10%) to warrant it, unless we actually reach a point where such tiny improvements are worthwhile. I should follow my own advice and not optimize until it's clearly necessary. -- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-11 12:23:08
|
On Wed, 10 Oct 2001, Paul Winkler wrote: > I'd consider making cached_onset and its friends semi-private, e.g. > self._cached_onset. The Aggregate's namespace is getting pretty > crowded, and those are attributes that the user should probably not > touch directly. I agree. I turned self.*0 in self._* etc and self.cached_* in self._cached_*. > > > - I assume flatten() is supposed to do the same thing as unwind()? > > > > It makes the Aggregate flat and returns nothing. > > Aha, so it's like an in-place unwind(). Done. I added it when committing your patch. > login name: slinkp I added slinkp to the team. You can still send me patches if you feel more comfortable. Also when doing large scale changes it is better to send me a patch at the moment. For small bugs fixes and doctest you can directly commit them to the repository. Why do you like a = 1; b = 2 instead of a, b = 1, 2 ? If you really don't like multiple assignments, let's use a = 1 b = 2 ok? Thank you. Maurizio Umberto Puxeddu. |
|
From: Paul W. <sli...@ya...> - 2001-10-11 02:58:52
|
On Wed, Oct 10, 2001 at 10:59:10PM +0200, Maurizio Umberto Puxeddu wrote: > > - changed Aggregate to cache end time; it caches onset and duration, > > so it seemed consistent to do the same with end. > Well, I don't know... I mean, it's just adding complexity. Anyway I > commited it. Not a big deal - all this cache stuff is just an optimization anyway, and it's still early to be doing that. I'd consider making cached_onset and its friends semi-private, e.g. self._cached_onset. The Aggregate's namespace is getting pretty crowded, and those are attributes that the user should probably not touch directly. > > - I assume flatten() is supposed to do the same thing as unwind()? > > It makes the Aggregate flat and returns nothing. Aha, so it's like an in-place unwind(). Done. > Do you have a SourceForge account? Now that you mention it, I do - I'd forgotten about it! user ID: 38329 login name: slinkp Guess I'll have to get more familiar with CVS. It's silly to be emailing patches like this. -- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-10 21:02:02
|
On Wed, 10 Oct 2001, Paul Winkler wrote: > Hi Maurizio, > > Attached are more doctests and bugfixes against current CVS. > (Wed Oct 10 19:04:17 UTC 2001) Thank you very much. I commited almost everything. > - changed Aggregate to cache end time; it caches onset and duration, > so it seemed consistent to do the same with end. Well, I don't know... I mean, it's just adding complexity. Anyway I commited it. > - I assume flatten() is supposed to do the same thing as unwind()? It makes the Aggregate flat and returns nothing. Do you have a SourceForge account? Maurizio Umberto Puxeddu. |
|
From: Paul W. <sli...@ya...> - 2001-10-10 19:06:52
|
Hi Maurizio, Attached are more doctests and bugfixes against current CVS. (Wed Oct 10 19:04:17 UTC 2001) Notes: - updated everything, including doctests, to use foo.onset() and foo.duration() as methods instead of attributes. - Changed several ArgumentError (which is undefined) to ValueError - Changed disjoint() to not lengthen durations if they were already short enough. - Aggregate.duration() was calling Aggregate.move_absolute_forward() which was broken - it doesn't work to just inherit this from Event. So I added Aggregate.move_absolute_forward(). In my interpretation, this should scale the durations of all sub-events by the same ratio, and adjust their onset times relative to onset of the Aggregate. See the test examples for an idea of what this does. - TO DO: look at other move_ methods for Aggregate and see if they work. - changed Aggregate to cache end time; it caches onset and duration, so it seemed consistent to do the same with end. - fixed Aggregate.extend (various errors) - still haven't tested serialize(). - Aggregate.unwind: changed "unwinded_list" to "unwound" ... isn't English fun? :-/ - I assume flatten() is supposed to do the same thing as unwind()? - changed sort_by_attr to work with new onset0 and duration0 attributes (but not visible to the user). We should be able to sort by end() as well, but I haven't looked at that yet so it raises an error now. -- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-10 18:12:49
|
On Tue, 9 Oct 2001, Paul Winkler wrote: > Are PseudoEvent and MetaEvent the same thing? Yes. I'll use one of them or another less sci-fi term, if I find one. Maurizio Umberto Puxeddu. |
|
From: Paul W. <sli...@ya...> - 2001-10-09 21:08:54
|
On Tue, Oct 09, 2001 at 10:52:13PM +0200, um...@ti... wrote: > Think of using PseudoEvents or MetaEvents. "PseudoEvent" or > "MetaEvents" are buzzwords. In fact their are just parametrized > factories of events or aggregates. They are built with a > configuration, can be manipulated in the standard ways Events, when > they are actually converted they generate the real events and return > them. They will be probably subclasses Event but have additional > properties like "brightness" or > "being-more-dense-at-the-start-less-dense-at-the-end" or "position" > and so on and so forth. I like this concept very much. Are PseudoEvent and MetaEvent the same thing? > for each object contained and recursively: > ask: "Do you have this property/method?" > if yes, call/change > > This is not implemented but I have to do this in order get it working. OK, I see what you're aiming at. That's even better than polymorphism! I was worried that the end user, trying to write an omde script, would have to do lots of by-hand "try... except" or other conditional tests. It looks like you're considering a framework whereby Aggregates take care of that for you. I like it. -- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com |
|
From: <um...@ti...> - 2001-10-09 20:52:19
|
Think of using PseudoEvents or MetaEvents. "PseudoEvent" or "MetaEvents" are buzzwords. In fact their are just parametrized factories of events or aggregates. They are built with a configuration, can be manipulated in the standard ways Events, when they are actually converted they generate the real events and return them. They will be probably subclasses Event but have additional properties like "brightness" or "being-more-dense-at-the-start-less-dense-at-the-end" or "position" and so on and so forth. Now I would like to have an aggregate (containing also some of these PseudoEvents) and perform a global operation, let's say "make it brighter". Since in the aggregate there will be also normal Events and Aggregates and PseudoEvent that have no "brightness" property, the only way to do this is for each object contained and recursively: ask: "Do you have this property/method?" if yes, call/change This is not implemented but I have to do this in order get it working. That said you'll see that the problem below is just a special case. > Paul Winkler <sli...@ya...> wrote > On Tue, Oct 09, 2001 at 08:20:14PM +0200, Maurizio Umberto Puxeddu wrote: > > On Tue, 9 Oct 2001, Paul Winkler wrote: > > > > > On Tue, Oct 09, 2001 at 07:02:40PM +0200, Maurizio Umberto Puxeddu wrote: > > You use move*() methods to move things around. Such methods do not > > depend on or change the duration of the event so they would go in the Spot > > interface and you would be still able to move F around. > > Moving an aggregate would move all moveable contained objects. > > And what does stretching an Aggregate do? It can't just stretch all > sub-objects - some of them might not be stretchable. Can I stretch you? Yes: I stretch. No: continue. No problems for the user. In fact once this will be in place, I won't need the attachment thing anymore. Maurizio Umberto Puxeddu. |
|
From: Paul W. <sli...@ya...> - 2001-10-09 18:33:33
|
On Tue, Oct 09, 2001 at 08:20:14PM +0200, Maurizio Umberto Puxeddu wrote: > On Tue, 9 Oct 2001, Paul Winkler wrote: > > > On Tue, Oct 09, 2001 at 07:02:40PM +0200, Maurizio Umberto Puxeddu wrote: > You use move*() methods to move things around. Such methods do not > depend on or change the duration of the event so they would go in the Spot > interface and you would be still able to move F around. > Moving an aggregate would move all moveable contained objects. And what does stretching an Aggregate do? It can't just stretch all sub-objects - some of them might not be stretchable. That's why I think F should provide stretch methods. It's simpler. Then you can stop thinking about whether an object is stretchable or not, and whether or not to put it in the "attachments". They all become the same and you can put them all in the same place. Simpler for the user. > On the other side stretching a function table doesn't make sense so it > will not have such stretch*() methods. Doesn't it sound good? No. :) The fact that a function table has no duration is just a detail. -- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com |
|
From: Paul W. <sli...@ya...> - 2001-10-09 18:25:21
|
On Tue, Oct 09, 2001 at 08:00:50PM +0200, Maurizio Umberto Puxeddu wrote: > On Tue, 9 Oct 2001, Paul Winkler wrote: > > > If you like. But why is it necessary for the programmer to remember > > that this method "has to do some work"? He/she is only interested in > > the return value. > > If you know that a call is potentially going to consume much time, > you can think of caching the values instead of calling it > twice. Nothing more. OK, I see your point. > Probably the best way should be caching onset min, onset max and end > max values instead of caching onset and duration, isn't it? I think I'll > do this. This is starting to sound rather like pysco. :) Especially since Aggregate now subclasses Event. In pysco, I didn't provide methods like those you have - I just had attributes, and required that time-modifying methods must update the relevant attributes. This meant that accessing the values is always fast, but modifying an Aggregate might be slow. pysco.Event had two attributes: endbeat (this is duration, which is actually a better name) last_at (this corresponds to calculate_min_max_onset()[1]) For non-Aggregates, last_at was just 0. I think omde is well on the way to being "like pysco but better"! -- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-09 18:23:06
|
On Tue, 9 Oct 2001, Paul Winkler wrote: > On Tue, Oct 09, 2001 at 07:02:40PM +0200, Maurizio Umberto Puxeddu wrote: > > Probably we should have a base class for Event, say Spot or so, which has > > an onset but not a duration nor stretch methods. Event should be a Spot > > with a duration. F should derive (indirectly) from Spot and not from > > Event. > > But then you can't treat instances of F and I polymorphically. And if > it has no stretch methods, how can we move F instances around? IMHO it > would be nice if F had the Event interface. You use move*() methods to move things around. Such methods do not depend on or change the duration of the event so they would go in the Spot interface and you would be still able to move F around. Moving an aggregate would move all moveable contained objects. On the other side stretching a function table doesn't make sense so it will not have such stretch*() methods. Doesn't it sound good? > Are you worried about F having the misleading attribute "duration" > which actually stores its size? That could be fixed by overloading the > __init__ and __str__ methods. There are no problems with csound scores. I'm using Sample tables right now, for example (as attachment of course). But all the code related to Csound scores is bad placed now. I have to take some time and think of it. Maurizio Umberto Puxeddu. |
|
From: Paul W. <sli...@ya...> - 2001-10-09 18:11:32
|
On Tue, Oct 09, 2001 at 07:02:40PM +0200, Maurizio Umberto Puxeddu wrote: > > I don't remember if I already posted something about this subject. I don't think so. > Probably we should have a base class for Event, say Spot or so, which has > an onset but not a duration nor stretch methods. Event should be a Spot > with a duration. F should derive (indirectly) from Spot and not from > Event. But then you can't treat instances of F and I polymorphically. And if it has no stretch methods, how can we move F instances around? IMHO it would be nice if F had the Event interface. Are you worried about F having the misleading attribute "duration" which actually stores its size? That could be fixed by overloading the __init__ and __str__ methods. -- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-09 18:03:35
|
On Tue, 9 Oct 2001, Paul Winkler wrote: > If you like. But why is it necessary for the programmer to remember > that this method "has to do some work"? He/she is only interested in > the return value. If you know that a call is potentially going to consume much time, you can think of caching the values instead of calling it twice. Nothing more. Probably the best way should be caching onset min, onset max and end max values instead of caching onset and duration, isn't it? I think I'll do this. > > > BUG FIXED: calculate_onset_min_max always returned None as minimum. > > > > > > BUG FIXED: calculate_begin_end always returned None as the start. > > > > Did you checked it? > > min(None, everything) is always everything. It's like None is infinite and > > this is the reason to use max2(). > > $ python > Python 2.1 (#5, Oct 8 2001, 00:32:31) > [GCC 2.96 20000731 (Red Hat Linux 7.0)] on linux2 > Type "copyright", "credits" or "license" for more information. > >>> min (None, 1) > >>> print min (None, 1) > None Python 2.0 (#2, May 22 2001, 11:42:51) [GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-81)] on linux2 Type "copyright", "credits" or "license" for more information. >>> min(None, 1) 1 >>> Ok. I defined min2 in omde.utility. Should be fixed in the CVS. Maurizio Umberto Puxeddu. |
|
From: Paul W. <sli...@ya...> - 2001-10-09 17:26:38
|
On Tue, Oct 09, 2001 at 06:35:41PM +0200, Maurizio Umberto Puxeddu wrote: > > BUG FIXED: F.end() added, to always return F.onset instead of F.duration > > (which is actually not duration but table length). > > Using F and I polymorphically would not have worked. > There was I reason for not to add the end() method... but I don't remember > what... If you remember, I'd be curious to hear. I can't think of any problems with F.end(). > The problem of the "duration" of tables was known to me. This is the > reason the attach() method and related code. But it's a temporary > workaround. Aha, I didn't make the connection. I was wondering what those were for! > > SUGGESTION: a shorter name for calculate_onset_min_max, et al, > > would be get_onset_min_max. > > calculate_ was there to remeber that it is not at accessor method but it > has to do some work. Could we use calc_ as a compromise? If you like. But why is it necessary for the programmer to remember that this method "has to do some work"? He/she is only interested in the return value. > > BUG FIXED: calculate_onset_min_max always returned None as minimum. > > > > BUG FIXED: calculate_begin_end always returned None as the start. > > Did you checked it? > min(None, everything) is always everything. It's like None is infinite and > this is the reason to use max2(). $ python Python 2.1 (#5, Oct 8 2001, 00:32:31) [GCC 2.96 20000731 (Red Hat Linux 7.0)] on linux2 Type "copyright", "credits" or "license" for more information. >>> min (None, 1) >>> print min (None, 1) None -- ................ paul winkler ................ custom calendars: http://www.calendargalaxy.com A member of ARMS: http://www.reacharms.com home page: http://www.slinkp.com |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-09 17:05:29
|
I don't remember if I already posted something about this subject. Probably we should have a base class for Event, say Spot or so, which has an onset but not a duration nor stretch methods. Event should be a Spot with a duration. F should derive (indirectly) from Spot and not from Event. Maurizio Umberto Puxeddu. |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-09 16:57:08
|
Hello. I finally commited your contributions and several other changes. I am not able to do a proper test and I'm sure I've broken something somewhere. The most important news is that Aggregate is now a subclass of Event and duration(), onset() end end() are methods. Aggragates's onset and duration are computed and cached. This probably has some side-effect that I currently don't see... I started to write basic tutorials in the doc/guide directory using docbook. There still are several rough hacks here and there. Regards, Maurizio Umberto Puxeddu. |
|
From: Maurizio U. P. <um...@ti...> - 2001-10-09 16:38:28
|
On Sat, 6 Oct 2001, Paul Winkler wrote: > I'm still exploring omde/score.py, which seems to be the area that > largely overlaps my pysco ideas. I thought as long as I'm trying > things out to see what they do, I might as well save my test cases and > add a doctest hook to the module. In the process, I found a few things > that I'm pretty sure are bugs and took the liberty of fixing them. Thank you very much: you do work that I planned to do plus things that I hadn't noticed. > The attached diff is against cvs of today, Oct 6, 19:50 UTC. > > Notes on changes: > > - General modifications: > * Added many tests to docstrings. > * Added _test() to run doctest on the docstrings. > > - Event: > CHANGED: Changed all spellings of "strech" to "stretch". > FIXED BUG: stretch_absolute_backward used 'alfa' should be 'time' > FIXED BUG: stretch_relative_backward used 'alfa', should be 'alpha' > FIXED INCONSISTENCY: stretch_relative_backward was always returning floats; > other methods return ints if given int arguments. Should be consistent. > > - F: > BUG FIXED: but maybe it was a feature.... but if F(number=None), > it's free to choose a number that was already specified by the user. > I changed it to keep track of all used numbers and choose the lowest > unused number. > > BUG FIXED: F.end() added, to always return F.onset instead of F.duration > (which is actually not duration but table length). > Using F and I polymorphically would not have worked. There was I reason for not to add the end() method... but I don't remember what... The problem of the "duration" of tables was known to me. This is the reason the attach() method and related code. But it's a temporary workaround. See below. > - Aggregate: > BUG FIXED: removed first definition of load() ... it was defined twice > and the first looked broken. > > ADDED: append() which adds one object to the list. > We have extend(), why not continue the list metaphor? > > BUG FIXED: extend() had the wrong order of arguments to isinstance() > > CHANGED: saveAs to raise a proper TypeError if wrong argument given > > CHANGED: deepcopy() wasn't returning anything. > > BUG FIXED: clone() was missing, though some other methods use it. > I assume it's the same as deepcopy. One name should be used throughout. > > SUGGESTION: a shorter name for calculate_onset_min_max, et al, > would be get_onset_min_max. calculate_ was there to remeber that it is not at accessor method but it has to do some work. Could we use calc_ as a compromise? > BUG FIXED: calculate_onset_min_max always returned None as minimum. > > BUG FIXED: calculate_begin_end always returned None as the start. Did you checked it? min(None, everything) is always everything. It's like None is infinite and this is the reason to use max2(). > BUG FIXED: calculate_onset_min_max, et al. will now work with > classes that derive from both Event and Aggregate. Ok. The only problems is that I made a lot of changes on that file too today and moved ScoreEvent, I, F etc in omde.csound. BTW, I find some problems putting *all* conversion to csound numeric score notation out of the omde.score module. Maurizio Umberto Puxeddu. |
|
From: Patrick K. <pk...@ny...> - 2001-10-08 16:28:08
|
IM A CSOUND BEGINNER!!! I open csound 4.15 for MAC. I want to pvanal a file. When trying to analyze it, the dnoiser opens - I DONT WNAT THAT!!!! The same happens when I try to render an instrument under csound - HIT RENDER AND THE DNOISER OPENS - I DONT WANT THAT EITHER!!! I tried to trash the dnoiser - But then csound doesn't wnat to render at all! What shall I do? HELP! Patrick |
