![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: PenTilt range, etc. |
HectorBenard Member |
![]() ![]() ![]() I've noticed that whenever a parameter is controlled by PenTilt (x, y or radius), the full range of the fader can never be covered. When the range of the fader is from 0 to 2 (PenTiltX and PenTiltY) the fader only goes from about -0.6667 up to 0.6667. If the range of the fader is changed in the VCS editor, the values are scaled, but the full range is still never covered by the fader. Something similar happens with PenTiltRaduis, where the fader only moves from 0 to about 1.6. Shouldn't the mapping be adjusted so that the full range of the faders can be controlled with PenTilt? On a separate subject, there seems to be something wrong with oscilloscope display and spectrum display. First I noticed it at home but thought it was probably just my old laptop. But I used a sound with an oscilloscope display at school today and realized that it also happened there, and when I tried other sounds (including oscilloscope form the info menu) nothing seemed to work. The dislays just appear frozen and they never update. Also the problems with the DSP status window seem to still be happening. The DSP status only works for a while, but when Kyma has been runing for a couple of hours it stops working completely. Even when you close the window and reopen it from the menu, or when you click on the sampling rate (as suggested in the tweaky), the window remains frozen until you quit Kyma and launch it again. I've experienced this at home and at school as well. Have you come across these problems? By the way, the problem I was has having with the pen controlling the cursor even when it was supposed to control only the sound (which I mentioned in the forum last week) just went away on its own. When I tried it a couple of days later everything worked fine, but I have no idea what was causing the problem or what fixed it, since I had tried everything (including restarting the computer several times) and nothing seemed to work before. Cheers. IP: Logged |
HectorBenard Member |
![]() ![]() ![]() Nobody has anything to say about the range of PenTilt? It's very hard to use it successfully if mapping some fader to a tilt parameter doesn't allow you to cover the full range of that fader. Am I the only one having this problem? IP: Logged |
SSC Administrator |
![]() ![]() ![]() Yes, the problem with PenTilt is that when you tilt the pen 90 degrees the tip can no longer maintain contact with the surface. The tilt value is actually correct, but since the pen has lost contact with the surface, it is no longer transmitting the tilt. One possibility might be to use only 0-45 degrees of the tilt so you would be sure to get the full range. (Or perhaps 0-60 degrees would give you more range yet still be assured of not lifting the pen tip). IP: Logged |
HectorBenard Member |
![]() ![]() ![]() Thanks for your suggestion. For all practical purposes though, only the values that can actually be transmitted should be taken into consideration, right? I can always scale the values in my sound so that I will have the range that I need while using only the available values of tilt, but it really seems like a roundabout way of doing it. Currently there seems to be no way to access the bottom and top of a given fader through the tilt parameters, so if I want to assign a fader to be controlled with tilt I can't do it from the vcs and have to go into the sound and re-scale it in the parameter field. Shouldn't the mapping be adjusted so that the values that tilt can transmit cover the full range of the fader it is assigned to? 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.