Quantcast

changes in global orchestra are not processed

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

changes in global orchestra are not processed

zappfinger
When I change ftgen parameters in my 'global orchestra' (for the instrument), they are not taken over.
Even after a recompile, I still get the same sound, waveform and table length in the display.

BTW, why are there multiple tabs 'global orchestra' and 'global score'? (In the instrument editor and the tabs above that. They seem to have a different function.

Richard
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: changes in global orchestra are not processed

bwong

> BTW, why are there multiple tabs 'global orchestra' and 'global score'? (In
> the instrument editor and the tabs above that. They seem to have a different
> function.
>
> Richard

The global tabs for the instrument are associated and saved with the instrument, so that you can (usually) have a completely encapsulated blue instrument with all the variables and tables required. All the data in the instrument global tabs get saved in the instrument library if you save the instrument there. This is very useful and should be used whenever possible, since it makes adding those instruments to songs a simple drag and drop process.
The other global tabs are for the song itself, since there are situations where it is still desirable to have global variables defined outside of the instruments. For example I have an instrument which uses an UDO, which in turn requires a function table. That function table must be defined in the global orchestra of the song not the instrument because the UDO is a separate code entity from the instrument.
Brian    
------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and publish
your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: changes in global orchestra are not processed

bwong
In reply to this post by zappfinger

Just so you know, all the global orchestra and global score of the song and instruments get combined together in the respective global orchestra and global score sections of the csd file that blue generates. You can generate the csd to screen or file and check them over for errors, such as duplicate global variable names.
BW

----------------------------------------

> Date: Mon, 28 Mar 2011 15:43:24 -0700
> From: [hidden email]
> To: [hidden email]
> Subject: [Bluemusic-users] changes in global orchestra are not processed
>
> When I change ftgen parameters in my 'global orchestra' (for the instrument),
> they are not taken over.
> Even after a recompile, I still get the same sound, waveform and table
> length in the display.
>
> BTW, why are there multiple tabs 'global orchestra' and 'global score'? (In
> the instrument editor and the tabs above that. They seem to have a different
> function.
>
> Richard
     
------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Bluemusic-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/bluemusic-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: changes in global orchestra are not processed

zappfinger
Thanks Brian for the explanation.

BTW, the problem I mentioned here went away by restarting Blue, so it was just a glitch.

Richard
Loading...