First time here? Check out the FAQ!
x

Custom Prototypes - sometimes loads sometimes doesn't

+1 vote
972 views
Hi

As above, sometimes the custom prototypes strip loads when I open Kyma, sometimes it reverts to just prototypes.  What am I doing wrong?

thanks

Geoff
asked May 27, 2019 in Using Kyma by ghood (Master) (3,020 points)
When you quit Kyma, do you leave your custom prototypes window open? (Maybe the difference is that you sometimes close the prototypes window before quitting Kyma?)
Always open. I never close it manually.
Does it seem to happen just after you update to a new version of Kyma 7?
It seems to happen randomly and not just upon new version installation.
any update on what might be causing this? Seems to have got worse with latest version. It drives me nuts having to load my custom prototypes every time I open Kyma :)   Thanks
The most likely culprit is that, under some circumstances, your Kyma Preferences are not saved. That's why we asked if it happened just after updating to a new version. I know it's hard to trace back to what happened just before you started up (or if there is anything different about the way you shut down the night before), but if you notice any kind of correlation that would be a big help toward tracking this down. Thanks!
Thanks SSC.  I've been trying to spot a pattern but can't find a sucessful one.  If I open Kyma, open custom prototypes then close Kyma upon re-starting it does load up again.  However, upon restart of Kyma next time (e.g. after computer re-start) then it defaults back to regular prototypes.  At first I thought it was something to do with shutting down the pacarana prompt as part of Kyma close but exploring seems it's not this.  It's very bizarre though.  Just to be clear, for everyone else, it should load my custom prototypes every time I re-start Kyma right (except perhaps after a new version installation as you mention)? Does this work for everyone else?
It seems that the first time I load Kyma after switching on my computer it doesn't load custom prototypes (CP).  If then open the CP, close Kyma and re-start my CP do open.  

What's really odd is if I start my computer, open Kyma, don't load my CP (which haven't loaded by default), then close and re-open Kyma they load anyway.  

Can you think what may be causing this @ssc?
That does work for me. Kyma does appear to load my CPs every time it starts.
Geoff, when you quit Kyma, are you being prompted to save some open, edited files?
Yes, although frequently I don't save if I haven't changed anything or I've simply opened a few things to experiment etc. I've certainly not made edits to the custom prototypes.
Thanks
Are you ever clicking Cancel in this situation? It is possible that this might cause the problem you are seeing.
No, not.clicking cancel. Just no to saving (when I dont need to)

1 Answer

0 votes

I don't know if this is happening to you but something that catches me out quite often is the "Enable" drop down on the File Open dialog. 

To include Custom Prototypes in your Prototypes strip you have to open the file with "Custom Prototype" in the Enable drop down. 

 

So far so good. But the open dialog remembers the last setting of the Enable drop down (which probably makes sense for other file types but I think not for Custom Prototype). So next time I go to open a .KYM file, if I don't remember to change the Enable back to "Any openable file" (which I rarely do), kyma will open the .KYM file as a Custom Prototype set and get rid of mine. 

answered Jul 17, 2019 by alan-jackson (Virtuoso) (15,840 points)
edited Jul 17, 2019 by alan-jackson
Thanks Alan, yes I was already using that to open custom prototype strip.
Yes of course. Were you setting Enable back to "Any openable file" next time you open a .kym file? That's the bit that catches me out.
I very rarely open kym files that way. I use the sound browser instead...unless you're saying that you need to set that back anyway to get Kyma to reopen my custom prototypes upon start? Which would seem a little odd...
Ah ok. You're quite right you don't need to set that back if you're using the Browser. It's probably something else then.
...