Yes, MacIntels are relatively new on the market, and, yes, most programs that run on pre-Intel Mac boxes also run on MacIntels, but what you're failing to acknowledge is that most Mac software on the market was developed before MacIntels existed; therefore, that software was originally written for PPC and UPDATED to universal when MacIntels became available.
If software companies wanted to keep their programs relevant, they HAD to update for MacIntels or be left in the dust, whereas RED is a new arrival on the market and does not pre-date MacIntels.
What kind of sense does it make for a forward-looking company with limited time/resources to make their wares backward compatible to a configuration that is rapidly becoming outdated?
Answer: It doesn't.
Have you ever programmed? High performance stuff? It's not just a switch you flick on. There's tons of hand written assembly code (low level cpu stuff) and platform specific optimizations in it. It takes months and months to do.
The PowerPC platform just isn't the future. Looking at that combined with the time / resources (and thus money needed) with none of the major platforms going in that direction why would we build for it? Do you also want us to support your G4 because you still have one for your render "farm"?
Which other 4K camera can you buy for this money with this level of support? All our software tools are FREE OF CHARGE.
Finally, we've stated again and again that we are looking into supporting other apps. These platforms are the ones that perform well and we are comfortable with so that's what we started out with.
Had we started out supporting everything under the sun you wouldn't have had ANY post tools AT ALL for the next couple of years. You have to start SOMEWHERE.
We have pledged to do the best we can. We stated from the beginning that we'd be in constant development and everyone's along for the right. Don't mistaken this for a finished fully polished product. This is in development and in beta.
If this is not how you like to work then I kindly suggest you look somewhere else.
Sorry to pile on as well Evolve but the G5 chip was behind the tech curve before it was released. While Apple was doing their dog and pony show to convince you that it was "whip fast", they were busy negotiating with Intel on an exit strategy.
And it may be a few years since I wrote any code but when you are doing low level coding, I suspect that the processor architecture is still where the last erg of performance comes from and we need every bit we can get.
If they tried to support old architecture then it wouldn't be anywhere near ready for us to beta test nor would it be anywhere hear realtime at any reasonable resolution.
The Red team has accomplished another great step and it is because they didn't support an old, slow processor.
Even if it hurts us a little in the wallet it is for our own good.
Evolve, when it was first announced that there would be no support for PPC I was disappointed because I have a very fast G5 (Quad). But I understood the position they were taking then and now that I have played with Redcine on an Intel (Macbook Pro 2.4ghz) I can see why they went in the direction they did. My Macbook is doing okay with settings at 1/4 high but I'm already thirsty for more power. I'll be going for one of the next generation Mac Pros when they come out. Red was quite upfront from the beginning that these are professional tools, and despite the low cost of the camera, some of the other tools are expensive when you add them all up.
Ok I've played with it for only about 30 minutes during lunch but:
It does run on Windows XP 64bit (despite the "Windows XP 32 SP2 Only" Warning.)
Debayering 4k REDCode felt SLOW. About 5-12 seconds per frame (Render times seemed to fluxuate wildly.) I had some heavy 1080p comps today that were rendering considerably faster. If that's what we should expect for REDCode RAW I would strongly advise using REDCode RGB if it's considerably faster or else evaluate your other options.
I would like to be able to zoom using the scroll wheel.
Pressing R/G/B for shuffling channels would be nice while in the viewport.
Histogram took forever to update about the same amount of time as it took to debayer the frame in addition.
C*/FFI style pan/zoom buttons for tablet users would be nice. (For those who don't know what that is: A "Pan" Button and a "Zoom" Button. Which when pushed act like the middle mouse button and Al+middle mouse button for tablet users.
When zooming it would be nice to get a context box pop up to let you know what zoom level you're at. Say have it come in bold up in a corner and then fade out.
Proxy levels work very well.
I was dissapointed there were no 'quick export' options. Aka. a drop down in the export tab to just say "SD" "720p" Or what have you. Scaling and repositioning is great for final shots but it would be nice to just batch out a hundred shots to SD proxies for the offline edit and worry about cropping and polishing later once you know if they'll even be used.
What's with the Slate font? IMO it's a bit too cute for a slate.
Still crashy but its recovery/autobackup worked very well every time.
I think I found a bug on Dual monitor systems where the ?hot box? On the screen divide won't go away when the mouse leaves.
No render glitches at all.
Nvidia 8800 GTX
4GB of RAM
Windows Xp Pro 64bit Edition
I've run Linux x86 Shake and Dual G5 Shake side by side and there was no comparison the G5s were pure garbage compared to an x86 system more than 12 months older. You got "squeezed" alright... it was when you invested in the powerPC architecture.
But, this also uses Quicktime for the scaling, which is much, much slower than doing the scaling first in the GPU in REDCINE.
LA, CA, USA
|« Previous Thread | Next Thread »|