garageCube

bratch · by **bratch** » Sat Dec 17, 2005 4:12 pm

please please, we need 2.5 for Xmas !!!

Stim · by **Stim** » Mon Dec 19, 2005 4:26 am

Oh yeah. That would be sweet. Major show in early January.

yves@garagecube · by **yves@garagecube** » Mon Dec 19, 2005 6:42 pm

As I wrote before we target the end of the year. This was the target, but it will be more likely for january.

Unfortunately it took quiet a bit of time to get a PCIE G5 with extra PCIE 3D cards for finalizing the multi-projection development.

The good news is that the extra time allowed me to integrate CoreVideo/CoreImage in the engine. I'm sure everybody will be pretty happy about that.

Stim · by **Stim** » Tue Dec 20, 2005 1:45 am

Oh man, I'm dying for this tool.

January 5 - Las Vegas. I can only hope...

Jesper Fryd · by **Jesper Fryd** » Fri Dec 23, 2005 8:25 pm

The good news is that the extra time allowed me to integrate CoreVideo/CoreImage in the engine. I'm sure everybody will be pretty happy about that.

Neat!
But what does that mean, specifically?

studioc · by **studioc** » Sat Dec 24, 2005 2:24 pm

I think what they are talking about is that many of the effects/video manipulations are embedded in the OS. In this way, if these effects already reside in the OS, and effects are used, that will result in a speed bump for us. The technicalities I am not sure of. But I believe that Tiger will roar with core image, etc.

vjfj · by **vjfj** » Mon Dec 26, 2005 1:44 pm

CoreImage means extremely clear and fast graphics output for mac users! anyone with tiger who has had the chance to try out arkaos VJ "HW" version will know what i mean. it just rocks. that M8 2.5 will have it makes my day

and if i may add in, my wish would be to have audio analysis to assign a frequency to each effect/layer. and to have more transitions, like chromakey and lumakey, or slides and wipes...

yves@garagecube · by **yves@garagecube** » Wed Dec 28, 2005 3:29 pm

More information regarding CoreImage can be found here:

http://www.apple.com/macosx/features/coreimage/

It is important to note that CoreImage requires a modern GPU or it will fall back to its software render (->very slow).

Yves.

shaze · by **shaze** » Thu Dec 29, 2005 10:40 pm

One question :
there will be 2 version of 2.5, one with coreimage/corevideo support and one without ?

My GPU don't support CoreImage/CoreVideo and I'm afraid it will be very slow on my mac.
What is your opinion on this ?

Thanks
Olivier

Akira · by **Akira** » Fri Dec 30, 2005 9:45 am

Nice time for me to buy one of those new supported iBook G4s then ;D

yves@garagecube · by **yves@garagecube** » Sat Dec 31, 2005 5:53 pm

One question :
there will be 2 version of 2.5, one with coreimage/corevideo support and one without ?

My GPU don't support CoreImage/CoreVideo and I'm afraid it will be very slow on my mac.

There will be an option in the preferences to switch from the software engine to the CI engine. In other words, the old engine will continue to be supported.

Yves.

chromafresh · by **chromafresh** » Thu Jan 19, 2006 10:01 pm

Is it just me or does this topic just keep telling me that its been updated, when it hasn't.... I keep coming back and seeing the orange icon and thinking "oh! maybe theres an announcement" then once again reading Yves old post about toggling the Core Image... very strange

*sigh* ah well.

moonbase · by **moonbase** » Thu Jan 19, 2006 10:10 pm

Not just you, I get that too.
Reckon the forum-engine-software whatever is getting overexcited about the
next version too and keeps posting the orange flag up on this topic - strange!!!

stuart · by **stuart** » Fri Jan 20, 2006 9:24 pm

Yves,

will you be able to tell us which machines/GPUs will benefit from coreimage and which machines should use the original engine?

yves@garagecube · by **yves@garagecube** » Mon Jan 30, 2006 11:18 pm

Actually it's kind of black magic to know which cards supports or does not support CI.

You can find a partial list on the Apple web site, here:

http://www.apple.com/macosx/features/coreimage/

It seems that some other cards are supported. Also I think (but I might be wrong) that some effects may be supported by some cards (depending of the complexity of the shader) while some others not. When the cards do not support CI, it falls down to altivec optimized code which is bad (but not as bad as non-vectorized CPU code).

It seems that the best is to give a try on your machine. there are several freewares out there that allow you to test CI filters.

Yves.

garageCube

Who is online