Csound API - What version of Csound do you use?
|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
 |
Csound API - What version of Csound do you use?
by Steven Yi
::
Rate this Message:
Hi All,
I'm currently working on blue using the API for rendering. Right now, I have it working fine with the API, but there's some complications. Because the csnd.jar is built with the same namespace whether it is built with double or float, I can only really compile against one or the other. I personally use the double version of Csound due to its better accuracy in computation and sound quality that I have in some cases found to be noticeably better. The way I think things are going to work out now is that it will be required to have the double version of the csnd.jar if you are going to compile blue. If you have csound installed, I think this should not be a big issue as most likely the csnd.jar should come with csound. If you are building csound yourself, you may need to get csound to build the csnd.jar too, which would require the JDK (Java Developer Kit) installed instead of just the JRE. This should be fine because if you're compiling blue, you're already using the JDK, so most likely will need just to configure Sconstruct when building Csound. At the moment, to use the API when running blue, you'd have to enable it in the Program Options, plus it'd also have to be available. I'm thinking that eventually, blue's installer can be modified to look for the API jar and do any configuration necessary at installation time, so the user can use the API version of running blue. As a fall back, if the configuration doesn't work, then the user would be able to just use the commandline version as always. So this is most a heads up for users who compile blue that you will now need the doubles version of csnd.jar to build. You shouldn't need it to run though, so if just want it for building, I can send you a copy of the csnd.jar which I think will be alright for building. To note: After I get this sort of initial build and runtime stuff done, I already have the API version of the CSDRunner working pretty much just like the commandline version. I will be looking at the ability to change widget values for BSB instruments in realtime next, which I hope won't take much time as I think the coding is pretty straightforward. Users will have to be aware that for BSB instruments, when it goes to create the CSD, if the API is enabled, the code will soon generate differently. Instead of outputting gk variables if the widget is set to allowAutomation, it will change to be k variables and using chnget to get the value from the host. The difference should not affect anyone's code who is using the BSB widgets correctly. For those widgets that do not allow automation, even when API is in use, it will generate just as a static numeric constant. This means that if you're expecting to be able to modify the value in real-time it won't work. You'll have code with it expecting a k-rate variable. Most of you using BSB already know this, so this is just a reminder. Thanks and please feel free to voice any concerns! steven ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Bluemusic-users mailing list Bluemusic-users@... https://lists.sourceforge.net/lists/listinfo/bluemusic-users |
|
|
Re: Csound API - What version of Csound do you use?
by Dave Seidel
::
Rate this Message:
I always use the double version, even when I do real-time stuff, so from
my point of view your plan sounds great, Steven. - Dave Steven Yi wrote: > Hi All, > > I'm currently working on blue using the API for rendering. Right now, > I have it working fine with the API, but there's some complications. > Because the csnd.jar is built with the same namespace whether it is > built with double or float, I can only really compile against one or > the other. I personally use the double version of Csound due to its > better accuracy in computation and sound quality that I have in some > cases found to be noticeably better. > > The way I think things are going to work out now is that it will be > required to have the double version of the csnd.jar if you are going > to compile blue. If you have csound installed, I think this should > not be a big issue as most likely the csnd.jar should come with > csound. If you are building csound yourself, you may need to get > csound to build the csnd.jar too, which would require the JDK (Java > Developer Kit) installed instead of just the JRE. This should be fine > because if you're compiling blue, you're already using the JDK, so > most likely will need just to configure Sconstruct when building > Csound. > > At the moment, to use the API when running blue, you'd have to enable > it in the Program Options, plus it'd also have to be available. I'm > thinking that eventually, blue's installer can be modified to look for > the API jar and do any configuration necessary at installation time, > so the user can use the API version of running blue. As a fall back, > if the configuration doesn't work, then the user would be able to just > use the commandline version as always. > > So this is most a heads up for users who compile blue that you will > now need the doubles version of csnd.jar to build. You shouldn't need > it to run though, so if just want it for building, I can send you a > copy of the csnd.jar which I think will be alright for building. > > To note: After I get this sort of initial build and runtime stuff > done, I already have the API version of the CSDRunner working pretty > much just like the commandline version. I will be looking at the > ability to change widget values for BSB instruments in realtime next, > which I hope won't take much time as I think the coding is pretty > straightforward. Users will have to be aware that for BSB > instruments, when it goes to create the CSD, if the API is enabled, > the code will soon generate differently. Instead of outputting gk > variables if the widget is set to allowAutomation, it will change to > be k variables and using chnget to get the value from the host. The > difference should not affect anyone's code who is using the BSB > widgets correctly. For those widgets that do not allow automation, > even when API is in use, it will generate just as a static numeric > constant. This means that if you're expecting to be able to modify > the value in real-time it won't work. You'll have code with it > expecting a k-rate variable. Most of you using BSB already know this, > so this is just a reminder. > > Thanks and please feel free to voice any concerns! > steven > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Bluemusic-users mailing list > Bluemusic-users@... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > > ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Bluemusic-users mailing list Bluemusic-users@... https://lists.sourceforge.net/lists/listinfo/bluemusic-users |
|
|
|
| Free Forum Powered by Nabble | Forum Help |