![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: KeyFrame Data | |
photonal Member |
![]() ![]() ![]()
I would like to import KeyFrame data into Kyma and apply it as a controller. The attached file contains example data which consists of the Frame Number together with an associated value. Does anyone have suggestions as to how this might be achieved? For example: i) import the Key Frame data into Kyma for use in the Timeline [This message has been edited by photonal (edited 08 January 2013).] IP: Logged | |
SSC Administrator |
![]() ![]() ![]() One approach might be to take a SoundToGlobalController and feed it to a MIDIVoice with the script option checked. Use the script to read your text file and use it to set the time and value of a continuous controller. If you put this MIDIVoice into a Timeline, your generated control should show up as one of the parameters and then you could record it in the Timeline. Or simply use the generated controller in your Sound directly. IP: Logged | |
photonal Member |
![]() ![]() ![]()
A solution was hacked together based on the 'Distance->time, angle->pan, energy->amplitude, angle->frequency' sound from '01 Sonification Sound Examples' The KeyFrame data file was reduced to just the Frame and corresponding value (see AVO-Voc-Edit.txt) as the file needed a little tidying up before it would be imported; most importantly was removing spaces at the end of each line and the very final line needed to be removed as this kept giving 'Unknown char' errors. KeyFrames.kym was the initial sound built to test the import and map the data to the SoundToGlobalController sound as suggested. Next this was placed into a Timeline (see KeyFrames.ktl.zip) and the generated data was recorded - which worked a treat! Thanks for that. The BPMRandoMiniLoop was then controlled by slaving its BPM to ValueDisplay (from KeyFrames II) which had been promoted to a master controller. Although it's not working 100% I'm not sure why but the generated key frame data kicks in late. The FrameNumberDisplay parameter control of KeyFrames II in the Timeline jumps from 0 to 799 at 00:00:31:29. Any idea why this is happening? [This message has been edited by photonal (edited 13 January 2013).] 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.