Kineme Core Suggestions

toneburst's picture

Just a couple of little things that might be worth considering for a future release:

Would it be possible to have the option of aligning selected objects centrally, as well as aligning along their left or right edges? Also, it would be good to be able to set the grid distance used when auto-aligning objects in some kind of preference (I like to place things very close together, to save screen-space).

a|x

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

ayalacortes's picture
Kinemecore feature?

I use two displays with my computer to test two simultaneously running compositions (one on each screen) using the network broadcasting patch. Using a Macbook Pro both compositions will open one on each screen as I left them before quitting QC. It seems not all systems remember the position of the viewer/editors. A new Macmini 2Gb doesn't remember the position of the viewer/editor windows on the second screen so every time I start QC I have to rearrange them. Would it be possible to attach each composition to each screen so they open on their "own" screen?

may be something like a "Force remember viewer/editor positions" option?

Why would this be useful? Will be great to start QC running both (or more) compositions in full screen mode on each screen.... for instance.

dust's picture
Re: Kineme Core Suggestions

i to have wondered why they don't have an alignment or even snap to grid in QC. i mean im not complaining i like the grid it reminds me of graph paper which seems fitting for doing node based graph foundation things but why not be able to change the grid size and align etc.. im going to try and load up kineme core again. it was working beautiful in qc 4 until i tried to slim titles and then i got all these back trace errors. eventually after trashing the preferences i was able to get it back to normal.

is anybody else having issues with kineme core in qc 4. i know chris said to not use it but it worked fine for me for some time. i have got the latest version. i would like to be able to see through my editor again but now i can't get rid of back trace errors. is there some folder that holds QC cache or something i can delete and try all over agian. i have all ready trashed the preferences both qc and kcore but for some reason when i ever i add the plugin again i get back trace errors or NSwindow error.

gtoledo3's picture
Re: Kinemecore feature?

(no comment on whether it is possible as a QC hack, but it will work if you build an app with Quartz Builder... or rather, it's a feature to be able to setup a default screen for your fullscreen window to populate. If you don't have a bunch of controls going on, it's fairly cool.)

gtoledo3's picture
Re: Kineme Core Suggestions

Use the most recent version. This should be ok.

Don't use slim title bars - these don't work in SL, but are still in the Core because they historically worked. Really, the only thing that you should need to do to restore if you enabled them would be to uncheck them, close QC, and then re-open.

If you run the new version of the KCore, and keep getting backtrace errors, take note to see if it's a specific scenario, like inter-composition communication. I would bet that the NSWindow error in this scenario is related to using KCore + OSC. Note when the backtrace happens... exactly what steps precede it, and if repeating those steps be changing variables (like different comps, opening template on startup vs. blank vs. another composition).

Also, note if you've enabled any non-standard settings in QC, and try to regress.

ayalacortes's picture
Re: Kinemecore feature?

(thanks for the tip. Indeed... QuartzBuilder does the trick in full screen for both compositions each one in their own display and I'm using it "live" on stage in one public exhibition. But... got some trouble trying to tell the computer which App should stay in the main Display and which one in the Display 1. Plus which one stays in front receiving signal. May be a "Display 0" or "Main display" option is missing in QuartzBuilder to be able to use the main display in full screen as well. Therefore I thought opening the compositions directly in QC could do the job.)

cwright's picture
Re: Kinemecore feature?

this is possible, but you should file a feature request with apple first -- they got some amount of position/size saving going on already, so it makes more sense for them to finish/fix that than have us do it.

cwright's picture
Re: Kinemecore feature?

The main display is Display 1 -- a second display is Display 2. We considered starting at 0 (computers do, after all), but then decided it would look strange.

If you're running more than 1 composition in QC, you're really going to suffer, performance-wise. QC is single-threaded, so every composition will run on the same thread (CPU). QuartzBuilder Apps are multithreaded, so they'll use more than 1 CPU (though they only load 1 composition, currently, so that's not too much of a win -- event handling and UI stuff is the main thread, all rendering is the second thread).

ayalacortes's picture
Re: Kineme Core Suggestions

Actually you just solved my day long fight starting QC without crashing it. I have deleted all including Xcode from the command line and was still getting the back trace errors after re-installing the whole thing. I did everything except deleting the preferences. Now I did and now with fresh preferences I don't get the back trace error, the blank patch windows, etc. The reason I was using Kinemecore was to open two compositions in full screen. I didn't realise the mess started when clicking the other options in Kcore. I was even moving back to QC3 to use Kcore as it was working perfectly before. Just posted in the QC list mi wishes to move back to QC3... anyway. The command i found in the installation instructions of Xcode was this: sudo /Developer/Library/uninstall-devtools --mode=xcodedir

Will be nice to have Kienemecore running back in QC4

Thanks for the tip!

cwright's picture
Re: Kineme Core Suggestions

also, after all that info gathering, please please please provide it to the developers (us) -- it's next to impossible to debug an issue that we're not experiencing, based only on a description that it generates a backtrace.

gtoledo3's picture
Re: Kineme Core Suggestions

Oh yeah, the MOST important part!