|
|
GT Lines (Composition by gtoledo3)
This is an upload of a test application ( which used Quartz Builder ) that draws groups of lines. There is a bit of play with the controls (available via the menu bar, or command-I). Y-scrolling the trackpad in the automatic mode is going to control distance of lines from each other. In the non-scroll mode, the Y-scroll will work the same, while the X-scroll will move the line scene. It's a bit of a stab at some of the line group art stuff that I tend to see in t.v ads. Change log: 1.0-Original. 1.1-re-upload with a different opening default setting, slightly changed function on manual x-scroll. |
Thanks for sharing. Unfortunately that's crashing for me on launch (no window appears)
Interesting. It is working for me on SL or Leopard, on Nvidia or Intel.
Thanks for letting me know. I'm going to test it some more, and try another build. I'm not sure exactly why it would do that. That message about colorspace in the error is kind of interesting, and miffs me a bit.
Do you mind me asking what kind of system you're using (gpu...obvious what software you're using, and I tested it on that build), or if you've enabled any system settings in the option preferences in QC that are non-standard?
Thanks for letting me know.
edit- yeah, I'm miffed. I'm testing now on two different systems, two different OS's and all is well. I do see something I didn't quite intend, but not a biggie, just that I left the backing transparent.
Can you do me a favor, and see if anything gets printed in the Console when it crashes? something like "retrying with alternative colorspace." ? If so, please let me know as soon as possible -- there are a small number of machines that trigger that, and I have no idea why, and no idea how to work around it.
Works fine for me. Very nice, too :)
a|x
Thanks for saying that Chris... my first instinct was to write to ask if he could do that, but I got sidetracked in re-downloading what I put on the website, and re-checking on both machines.
Console messages would really be great, and maybe even a system profile. Feel free to send them to cwright, or me, whichever strikes your fancy.
Thanks tb, on both counts! I'm looking forward to my next version for sure.
I opened it up on my white macbook... man that thing has a hard time with high iteration counts. It was kind of sad. Next go round, I'll probably set my default amount of GL Lines lower, and let the thickness of the quads cover it up, and have it open in an audio reactive mode.
My personal like on this is the offset of the lines... it gives that fun cyber graffiti look. I was a little skeptical about getting this look, but really happy that what I imagined did work. I programmed the main part of this one away from the computer by just daydreaming about it a bit, that's for sure.
Also, those that use Y and X two finger scrolling should be rewarded by some interactivity... Y scroll always changes difference between lines, and in manual mode, X scrolling works to shift the entire scene, so that you can draw something, then push it off screen.
Last night, in one of my newer working versions with some savage tweaks and appropriate extra little png's, I was able to get things looking like I was drawing landscape on the fly.
Thanks GT
Very nice and lots of different looks, always like that. Couldn't fathom the Queue value setting, is it active?
Works on PPC G5 with Nvidia FX5200. Fewer lines doesn't seem to speed it up much for higher-res 'drawing' of curves eg. loop-the-loop in my old box though. Wondering how much faster it views as an app than in QC editor?
Like how the GT-graf app icon is wrapped in alpha when app-switching in Finder too. That's a first (in my book).
The queue is definitely active. The thing that probably weirds you out about the queue is that it doesn't go back "down" from whatever value it is raised to. I haven't decided exactly if I want to have people be able to flush all of the values or if I want to line to contract from the front or back if length is changed after the queue is set.
I'm actually a bit surprised that the javascript queue doesn't contract by default, because it seems like it should. The queue is stock apple sample code... you can check it out in the mouse ribbon example in SL. It is slightly tweaked to be a bit different (the vertex creator part, and the thickness... at least I believe I wound up with the slightly thinner line version), but the queue is undisturbed.
What kind of performance do you get? Does it look smooth, or is it "jerky"? This is just the kind of thing that gets extremely variable, so I'm curious, especially from someone using PPC. I mean, I get around 30~60fps on some intense settings. Then I opened up on my white Macbook, and it was a little less impressive. Iterator/queue heavy stuff can get really taxing.
It views faster as an app than in the QC editor, 100% sure. That's one of the big plusses of Quartz Builder. The QC app is a boondoggle for performance. Just grab the Editor window while you're Viewing something, and see what I mean. Aside from that, there are many other small performance tweaks that make something compiled in Quartz Builder tend to run better and faster (notwithstanding the mystery crash described earlier in this thread... which I would really like to get cleared up).
By alpha, you mean alpha black? Interesting. Let me know...
works great for me. really good performance actually very impressed, with performance. changing the queue doesn't seem to slow it down any.
Cool, thanks Dust.
Hi Chris or anyone else interested in this. I'm getting the same problem although with a different app (built with quartz builder 1.4)
*** Terminating app due to uncaught exception 'NSGenericException', reason: '-[QCRenderer initWithCGLContext:pixelFormat:colorSpace:patch:]: Argument "colorSpace" does not verify "(CGColorSpaceGetModel(colorSpace) == kCGColorSpaceModelRGB) && (CGColorSpaceGetType(colorSpace) != kCGColorSpaceDeviceRGB)"'
It works fine on my 2010 macbook pro (nvidia 330m) but crashes 80% of the time on 2 different 2010 mac mini's (nvidia 320m)
I also get the "retrying with alternative colorspace." message you mention in the console (see below for more detail)
Does anyone have any more insight into this - is it machine specific or specifically related to quartz builder? ie if I rebuild the composition into my own custom app without using quartz builder will this still happen or will it happen on these machines no matter what?
Cheers James
Chris replied to this on the apple dev list - the solution is to change the color profile in the display preferences
I'm glad this was figured out - you're not the first person that's replied about this happening.