|
 Kyma Forum
 Kyma Support
 Kyma save error
|
| next newest topic | next oldest topic |
| Author | Topic: Kyma save error |
|
Bill Meadows Member |
posted 16 September 2000 17:38
 
This has happened a couple of times now - I create a new Sound in the Sound Editor, and when I try to use command-S to save, I get this error message: Error: The message #isFilteredBy:, sent to a KMacFilename('Viking:'), an instance of class KMacFilename, was not understood. The strange thing is that if I click the "close" box in the corner of the window, I get a dialog-box prompt to save the file, and it works fine with no error. Any ideas? Also, it seems like sometimes when I do command-S, it closes the window (which is annoying), and sometimes it doesn't. Bill IP: Logged |
|
SSC Administrator |
posted 16 September 2000 20:37
Will look into it and see if we can fix it before we upload the new update (later this weekend). It seems to be something to do with the Sound Browser... IP: Logged |
|
dennis Member |
posted 18 September 2000 09:53
Bill Meadows wrote: "Also, it seems like sometimes when I do command-S, it closes the window (which is annoying), and sometimes it doesn't." I've had this happen, too, but I can't reliably reproduce it. E.g., if I open a Sound file containing Sounds A and B, then a Sound Editor on A and B, modify A and B, then close the active window, Kyma closes the inactive Sound Editor window when saving the active Editor. So maybe, when Kyma closes the active window, it's confusing which window is active? IP: Logged |
|
David McClain Member |
posted 19 September 2000 10:59
I just had a situation occur, where after much fiddling around with a timeline and then saving it and exiting Kyma, the file cannot be reloaded due to some Smalltalk class being "nil" not responding to "#scale:duration:". The file is encoded in a semi-binary form and so efforts to edit it with EMACS were like fumbling around in the dark. No great loss... just fooling around on this one. But for the future, it seems I should always work on a copy of a known working file so I can have a backup. Had the file been encoded as Smalltalk source, it would have been fixable. Better yet, why not have the loader simply issue an error message, punt on the unknown situations, and continue loading the file. At least then it could be patched up again and not totally lost. - DM IP: Logged |
|
dennis Member |
posted 15 December 2000 09:52
Bill Meadows wrote: "Also, it seems like sometimes when I do command-S, it closes the window (which is annoying), and sometimes it doesn't." Earlier, I wrote: "I've had this happen, too, but I can't reliably reproduce it. I think it has something to do with Kyma mistakenly believing that a different window is active." Now, I think I've got a reproducible case! If I compile/load/start, then adjust the VCS (e.g. change positions of faders, etc), when I pick "Save" in the Sound Editor, Kyma unexpectedly closes the Editor window. So it seems that modifying the VCS causes the Sound Editor window to close the next time you pick "Save". I'm using the latest Kyma release under Win95. Does this help? IP: Logged |
|
SSC Administrator |
posted 15 December 2000 09:57
Thanks Dennis, that does help us. IP: Logged |
I think it has something to do with Kyma mistakenly believing that a different window is active. All times are CT (US) | next newest topic | next oldest topic |
  |
|
Contact Us | Symbolic Sound Home
This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.
Ultimate Bulletin Board 5.45c