![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: 6.42 |
HectorBenard Member |
![]() ![]() ![]() It's great to see another nice update from SSC. Good job guys! Being able to use more than one set of microsounds at a time is a feature that many people have wanted for a while, and it's great that it is now possible to do this. The random triggers expressions are also a nice addition. In the past I often found myself having to come up with more complicated ways to achieve this kind of behavior, and having simple standard capytalk expressions to do it will be very useful. As a suggestion, and even though it's easy to see what each expression does, I think it would be very helpful to have a quick reference sheet for these capytalk expressions (and some of the other recent ones), for completeness sake, and also because sometimes it's easy to forget exactly what some of them do, or even that they are available. This is especially true when working under pressure and with limited time for a given project. Thanks, and keep up the good work! Best, Hector IP: Logged |
HectorBenard Member |
![]() ![]() ![]() While on the subject of capytalk expressions and long-desired features, I thought I'd mention another little thing that I'd love to see in a future update: I think it would be extremely useful if ramp: and fullRamp: (or expressions that could be equivalent to them, like a "ramp2:" ) had an extra argument that would allow you to determine the value the expression should return before the ramp gets triggered, as opposed to it always being 1. I often come across situations where this feature would make my life a lot easier, and this would allow you to use ramp as a simple linear envelope in many situations (without having to use an extra Sound), for example to gradually increase the value of a parameter from x to y at any given moment by just triggering the ramp. Perhaps even an additional argument could be included to indicate the value the expression should return after the ramp concludes. Cheers, Hector IP: Logged |
SSC Administrator |
![]() ![]() ![]() Thanks, Hector. I neglected to mention that I've been working on a CapyTalk addendum here: http://www.symbolicsound.com/cgi-bin/bin/view/Learn/KymaManual . If you notice anything missing, please let us know (or edit that page). Thanks! (coincidentally, I had been considering the possibility of optional arguments to ramp: for initialValue and restingValue) [This message has been edited by SSC (edited 02 March 2007).] IP: Logged |
HectorBenard Member |
![]() ![]() ![]() Ah, That's great! Thanks!
quote: I guess great minds do think alike! H [This message has been edited by HectorBenard (edited 02 March 2007).] IP: Logged |
photonal Member |
![]() ![]() ![]() "You can now load several user microsounds at the same time. Give each user microsound class file a different name and then put all of them into a folder. Select Choose user microsounds... from the File menu; Kyma will ask you to locate one of the files in the folder of files you wish to load and use." Thanks for this new feature - Only I get an error message when I try it I locate the microsound as requested, the first is loaded but fails trying to load a second within the same folder. Should the microsounds have specific names? I have for example, User Microsound Classes 1.asy, User Microsound Classes 2.asy IP: Logged |
SSC Administrator |
![]() ![]() ![]() It is possible that the combination of microsound files is too long to fit into memory (about 4400 words is available). Microsound authors should probably take a look at their code and remove any duplicate or unused modules in order to optimize the length of the files. (In the next update, we have added an error message to catch this case and give some feedback as to how long the combined microsounds files are). IP: Logged |
jesges Member |
![]() ![]() ![]() quote: Maybe the expression "sampleFileNamesInSameFolder". Sorry for no edit the wiki but sometimes I find a bit complex... and now it's a table IP: Logged |
All times are CT (US) | next newest topic | next oldest topic |
![]() ![]() |
This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.