![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: Timeline VCS problem |
Bill Meadows Member |
![]() ![]() ![]() I tried to use a Timeline from last year (pre KymaX) and had some problems. Many VCS controls were missing. I think this is related to the problem reported by Garth Paine. In all cases, a Gain module was "downstream" from the missing controls. However, the effect was somewhat random - i.e.- not all "upstream" controls were missing. For instance, in one case, two SampleClouds go to a Mixer and then to a Gain. Controls for one SampleCloud are missing, the other one is o.k. This was working perfectly when I last used it (pre KymaX), and I changed nothing before compiling. IP: Logged |
SSC Administrator |
![]() ![]() ![]() Try editing the Sound and playing both SampleClouds on their own. Then close the editor and save the changes back to the timeline. (VCS layers exist only for Sounds that have been played independently of the entire patch.) IP: Logged |
Bill Meadows Member |
![]() ![]() ![]() I tried your suggestion, but it didn't hep. I have now uncovered a really bizarre behavior. I started with a new Timeline, and pasted a Sound into it. This Sound uses SpectrumInRAM to resynth a file - it has no audio input, so the track uses no audio input. I made several parameters Live and compiled it. So far, so good, the Timeline VCS looks correct (the controls show up). However, if I assign an audio input the that track and recompile - the VCS controls disappear! If I set it back to "no audio input" and recompile - all the VCS controls return. I tried another Sound which uses no audio inputs (made with MultiSample) and it does the same thing! (While writing this, I have discovered that if I use a new MultiSample prototype, it does *not* do this. The Sounds I am using are copied from a Timeline I created last year in Kyma5.xx - they worked fine then. They are also o.k. when compiled individually.) Any help would be appreciated - this Timeline was a live performance piece that I want to repeat. (I have now repeated this behavior with the "Drone" prototype - drop it in a Timeline and compare the VCS when the track input changes from none to 1.) [This message has been edited by Bill Meadows (edited 21 March 2004).] IP: Logged |
SSC Administrator |
![]() ![]() ![]() Note that in Kyma X, the behavior of track inputs is slightly different from that in Kyma.5: A track input is substituted for the *replaceable input* of all Sounds on that track. From your description, it sounds to me as if the replaceable input on your Sound may not be where you think it is in the signal flow graph. The replaceable input is indicated by a cyan halo around the Sound's name. To set a replaceable input, select the module that *should* be the replaceable input, then use the Action menu to set the replaceable input. Is this what happened in your Timeline? IP: Logged |
Bill Meadows Member |
![]() ![]() ![]() Yes! That corrects the VCS problem! Thanks. Now, if you can figure out the other issue (the Timeline I emailed) I think I'll be good to go! IP: Logged |
SSC Administrator |
![]() ![]() ![]() That one had the same problem. The replaceableInput was not where you thought it was and the track input was replacing too much of the Sound. 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.