|
|
leopard-snowleopard i have a really big problem. i made a really important composition a year ago but in qc3 ,leopard. Now iam trying open with SL and i cant. I tried to go in with property list editor and clean some dangerous patches, but no result. Still QC quits. Any idea? thanks, d.
|
If you got any crash logs or error messages please let us know.
Open in Leopard , if you can, explode your macros, I'd be mostly looking for iterators, especially nested iterators and also for any GLSL shader patches.
I'd try rebuilding the code from text, rather than patch, in the case of CI kernels, scripts and shaders.
Process of elimination.
Eventually works.
To all intents , the composition should have auto updated as needed, but what can you do when the general rules go awry?
Going in with property list editor and cleaning stuff could wind up being really frustrating and fruitless, especially if you're messing around with patches that have incoming and outgoing connections. You're more likely to do damage than letting QC do it's thing.
What does the exception window say when you try to open it, with the original file?
Doh
Most obvious trick - try , if you haven't already, to open QC and the comp in 32 bit mode in SL, see if that doesn't work out for you.
also try not auto run the patch when you load it. you can set "only show editor" in the prefs.
i have no good solution, just working solution.
leopard installed on old MBP
patch is running (5fps), i dont know where is the problem but i will try...
thanks for all the ideas.
Are you using replicate in time patch anywhere? That one got broken, and now causes poor frame rates, and no replications.
try copying the leopard version of qc 2 to your snow leopard disk, then open the file with qc 2 on snow leopard. if everything looks good then save it and open it with qc 3 ?
LOL. Pretty good advice I guess, except it would be a matter of copying QC 3 or 3.1 to the SL drive / partition. :-). QC 2 was Tiger [10.4.x].
Haha.... Qc in tiger wow yeah that was before my time. I ment copy the leopard version to your snow leard computer. Just the qc app. Dont install leopard Xcode on your snow leopard computer that will probably not work to well.
I can remember using both versions of qc for a bit when snow leopard came out so it may help. Also maybe it could be an issue with using an old leopard plugin In Snow leopard. If I remember correctly kineme gl tools cased some black screen weirdness when sow leopard came out. So defiantly make sure you have snow leopard versions of kineme core and gl tools etc...
If your not using anything specifically snow leopard like mesh and open cl stuff then you should be able to run a leopard patch in snow leopard. it might just be a case of refactoring your code into a snow leopard patch via copy paste. When ever I can not open an old patch In a new system and it doesn't work usually copying it or rebuilding it in the new system works. if that doesn't work then re installing snow leopard fresh should clear up the issues. I don't know what machine you have and what version of th sl your using but 10.6.2 update broke every thing qc for me. 10.6.8 should work though ??
It's not really good advice; the app will load the same qc framework. It won't really solve any sl specific problems at all.
i made it, step by step copying all the macro patches, because:
I found one bad macro patch (with glsl shader), another one (kineme 3d) and a third one (old CVtools). I cleaned this macros and one with wii and one with osc and voila still not working:)
thats totally my fault, i started to use SL really late, but now i will do the same with lion... because before gigs i cannot change the operation system and start to kill my mind.
complaining ended here______
It sounds like two of the problems are just plugin problems, not necessarily SL. K3D changed alot and screwed up translations, rotations, scale, and loading on some stuff (yay). CVTools release lopped out some patches that used to be present in the beta OpenCV patch. Old versions of the patches could be used instead of more recent ones.
The fact you're having a GLSL problem between Leopard and SL is interesting, because I remember some fixes, but no breakage. If it's anything to do with Particle Tools (like pt stuffed inside of a GLSL environment, or PT inside of an RII in certain scenario), it's possible that is problematic.
It's definitely worth testing on not only the OS, but the exact machine that you have to run something on when it comes to this stuff.
You may wish to booth QC in 32 bit mode by doing a "get info" on the app. That will keep stuff as close to what you've been used to as possible (but won't fix a lot... it will just help you load some older plugins that haven't been compiled for 64 bit).
good or bad advice take it for what its worth. i'm not the only person that did this when snow leopard came out.
http://kineme.net/Discussion/General/RunningQC3.xSnowLeopard
the good thing is that snow leopard issues got sorted out pretty quickly so if your having a problem with a plugin or what ever theres probably a new one for you.
i can remember some conversations about linking in old qc frameworks that did solve some problems with various updates of sl. don't remember the particular thread at the moment
It's not worth much. I'm not trying to thump you or anything, just add some clarity to an otherwise mind numbing analysis. Loading the old QC app in a new OS loads the new framework. If the problem is with patches not loading, it's likely because of plugins or patches not being the same, and/or changed in the framework, not the QC editor app.
To be nitpicky, also, it was not QC2 in Leopard it was QC3, and if one has multiple partitions, you can just open it up while it's located on another partition, and it's the same as copying it onto the partition you're booted in, there's no need to copy it.
What do you mean "linking in old QC frameworks"? That's an entirely different matter from using an old QC app. I remember exactly 0 problems being solved by opening up the old QC app in SL.
Again, I'm not trying to correct you in particular, I just have a preference for users not to have really fundamentally flawed ideas about what's going on or poor problem solving methodology based on myth.