My first runs of 5.2b6 were quirkier than I'd like. Loading up a previously created set, moving from one scene to the other, scene launch quantize was off on the initial launch of the scene, as if a wait occurred for something to be read from disk right at scene play. After it was launched once, subsequent launches were smooth.
Another thing I've wondered about is if and where any temp files are written, and how to ensure temp files are cleared up properly if they are written (is it just the 'temporary sound files' that you are prompted to delete, or something else?).
My issues have been mostly minor with all the upgrades, but seem most likely to occur when moving from one version to the other. Is there some official way to ensure "fresh" prefs?
Q for Abes, Some 5.2b6 observations...
Q for Abes, Some 5.2b6 observations...
UTENZIL a tool... of the muse.
Ok, cool, "recording folder", thx. (Things have worked well, so I've just never worried about it--hoffman2k wrote:The location of the temp folder (recording folder) can be found in the prefs.
I don't know what you mean with fresh prefs. But when 5.2 is released. It wont copy the preferences from the betas. It'll copy those from the previous Live version.
).Now, I've noticed this, that the beta does not use my old prefs. I'm asking about 'fresh prefs' because some problems I (and others too) had when going from release to release were cleared up when deleting the prefs and letting the app regenerate them.
UTENZIL a tool... of the muse.