![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: debugger |
sm Member |
![]() ![]() ![]() is there any way to safe data (incomming, generated or similar) to a file? (in order to have a history of events, ....) this would make debugging easy. ->michael IP: Logged |
SSC Administrator |
![]() ![]() ![]() What kind of incoming data did you have in mind? MIDI? text? audio? IP: Logged |
sm Member |
![]() ![]() ![]() yes, midi, audio and also data which is generatet by kyma. e.g. the output of peak & envelope followers, oscillators... i thought on something like: "route this data to the debugger window/file" what is your way of debugging kyma sounds? IP: Logged |
SSC Administrator |
![]() ![]() ![]() For visualizing the signal, I sometimes drop an Oscilloscope Sound just to the right of the signal I want to monitor. To see a readout of numbers, I use a SoundToGlobalController (See the Global Controllers category of the Prototype strip). This turns either a Sound or a !HotParameter into a "fader" that shows up on the VCS so you can monitor the numerical output. IP: Logged |
sm Member |
![]() ![]() ![]() yes. but what i would apreciate most would be to have the possibbility to write this data to a file. this would give us also a history. which is very helpfull, in fact necessery, for tracking fast changing data. i often cannot move my eyes fast enough to keep track of 3 faders..... it is also very sad, that the midi-monitor is not a window in itself. michael IP: Logged |
sm Member |
![]() ![]() ![]() about using the "oscilloscope" on my G3 400 MHz PB this works so slow that i can make no connection between what i hear and what i see (wysiwyg?!) are there any settings i did wrong. IP: Logged |
SSC Administrator |
![]() ![]() ![]() The oscilloscope display will be faster at thousands of colors. If you want a record of incoming MIDI, you could record it in the timeline. IP: Logged |
sm Member |
![]() ![]() ![]() hm, tried also in tousands of colors without a significant gain in drawing speed.also some buttons in kyma are no more recognizeable. i didnīt try to record midi in the timeline yet. but is it possible to visualize the keyDown events. i guess they are off per default? IP: Logged |
dennis Member |
![]() ![]() ![]() Here's what I use: 1) Probably SoundToGlobalController the most. Typically, I look at "raw" values but sometimes I lightly process the data, especially with countTriggers to make it easier to see. You can fuss with the VCS a lot to change the presentation but I usually avoid that since it's only temporary debugging info anyway. 2) When I need to look at a signal generated at the sampling rate, I insert a DiskRecorder and capture the signal to the hard drive. Then I look at it later with some program like CoolEdit. This is especially handy when you're looking at how two signals are synchronized; I record them in stereo. You can trigger or gate DiskRecorder so it's easy to capture just what you want. 3) Occassionally, I'll use the Full Waveform menu item but its view is rather simple and limited. With CoolEdit et al you can zoom in and slice and dice. More than anything, what helps me is careful thought and progressive, incremental implementation. (Can SymSound make this a menu item for me, please? Hope this helps. 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.