Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Thanks Apple...

what about having a cheaper mac for editing and a PC for renders

or edit on a Mac, and have a number of inexpensive commodity hardware boxes running as a cluster to render... that way you can easily scale up your computing power to decrease rendering time by adding additional machines to the network...
 
We are so funny!

We are so funny!

Jim and the crew make it possible for us to save something like a few hundred thousand dollars on a camera body, the hardware makers send us boxes that are twice as fast every few seasons, and we just want more....
 
Ralph, for you it may be an option save a few hundred thousand, I never had that option in the first place. Jim is creating tools for me as an independent film maker that I never would have access to.

I'm just looking for solutions that meet the same new price brackets he now markets to
 
But that wouldn't be Avid qualified so that's not going to work.

"Price/performance-wise, comparing Apple to PC is like comparing Sony to RED".
That is ridiculous. I guess it depends on your definition of performance.
The Apple solution costs more, but its consistent and works.

My non-Avid qualified PC has had 0 crashes in the past 6 months. Seriously.

I've done about 20-30 large, paying, FCP jobs, using about 8-9 FCP systems. Always had crashes, gamma & render inconsistencies. Not a big problem (except when it screws up the online for a Lexus promo you're finishing on a Quantel at $$$/hour) but a minor irritation to be sure.

Anyway, just saying... it'd be awesome for a RED render farm. And you'd have cash left over to buy a used copy of Avid ;) Just need redrushes for PC, please... or some way to create .RLX looks on PC for use with MetaFuze.

Bruce Allen
www.boacinema.com
 
Don't forgot HD's Apple solutions have had such a long history with Avid too!!!
 
I just got my new mac pro 2.93 and it's twice as fast as my previous machine 2.66 running compressor! Looking good folks!! Now where's FCP3?
 
Jim and the crew make it possible for us to save something like a few hundred thousand dollars on a camera body,
the hardware makers send us boxes that are twice as fast every few seasons, and we just want more....

Yep....not sure why we always ask for more either. Oh wait use I do!!!

It's so I don't have this!!
View attachment 11208
"...A new wing was built to house Illiac IV It took one month to disassemble the unit from our testbed in Paoli, which had 100 tons of air conditioning built into it.
The computer totalled 53' in length, and took 11 40' vans to house it, weighing 99 tons. One truck alone had only power supplies in it. Illiac IV had a total of 11,739 pc boards......."

Ah progress!!
Dave,
 
My non-Avid qualified PC has had 0 crashes in the past 6 months. Seriously.

I've done about 20-30 large, paying, FCP jobs, using about 8-9 FCP systems. Always had crashes, gamma & render inconsistencies. Not a big problem (except when it screws up the online for a Lexus promo you're finishing on a Quantel at $$$/hour) but a minor irritation to be sure.

Anyway, just saying... it'd be awesome for a RED render farm. And you'd have cash left over to buy a used copy of Avid ;) Just need redrushes for PC, please... or some way to create .RLX looks on PC for use with MetaFuze.

Bruce Allen
www.boacinema.com

redrushes for pc would be great.
we use i7 PCs for almost 2 months now.
adobe installed everywhere.

our current workflow is adobe-speedgrade-combustion

if you would know a way how cs4 can export dnxhd it would be good to know.
 
It's beginning to seem pretty obvious to me that the render farm is something that absolutely must be done to keep pace with the enormous files that the Red cameras will be producing. I double-dog-dare you to render anything from that monster 6 x 17cm sensor using an off-the-shelf workstation and meet any deadlines.

That said, I am imagining a rack of commodity linux boxes all connected to your workstation via gibabit ethernet and possibly eSATA as well. Your workstation can delegate a huge rendering job to the various machines by simply chopping up the source file and handing pieces off to the various machines which would devour it like hungry sharks. Adding 8 extra cores to the task might be as easy as popping in one of these --a nehalem equivalent of which is no doubt due shortly.

AMD also offers good price/performance. You can get comparable clock speeds to the Intel chips for half the price. Or you can get a full 16-core AMD monster, something like this:
4 x AMD Opteron 8380 2.5GHz 75w CPU
Tyan 4-socket mobo
32 GB of G-Skill RAM
6 x Western Digital Caviar 640GB Drives in RAID 0 config.
550 Power Supply, 4u rackmount case
approx $6700 including tax and shipping. Compare to a 8-core Mac with RAID card, 4 drives, and 32GB for $12,100.

This is very different from a mac but would probably offer similar performance. I'd love to try and benchmark one. Some notable differences:
* AMD box has 4 processors and 16 full cores.
* Mac box has 2 processors and 8 cores but each is hyperthreaded...results in 16 threads under optimum circumstances
* Mac has slightly higher clock speed, 2.66Ghz vs. 2.5Ghz
* Mac memory runs faster (1066 vs. 667). However, the chip-to-memory bandwidth advantage of the Mac may be mitigated by fact that it has half as many CPU sockets. The existence of 4 separate sockets in the AMD box means that you have twice as many sockets per thread.
* AMD machine has 6 drives to Mac's 4. Also room for 3 more internal drives with 9 internal drive slots.
* AMD has no optical drive and inferior video card but it wouldn't be running as a desktop machine. For optical drive, add $25.
* AHEM - $6000 price difference

Heck you could install windows on it but by using linux, you might gain several advantages:
1) no mac tax
2) no windows tax
3) no need to port software to windows if software can run on linux*

*Given that OSX is really BSD Unix, I would imagine that these rendering algorithms already exist in a code format that is quite ready for export to a linux box.

Does that sound ridiculous? Seems to me all that remains is the development of a bit of network code and a bit of code to let your workstation break the job out to the various machines. If done right, this render farm approach could support really amazing scalability. Just plug in another machine.
 
It's beginning to seem pretty obvious to me that the render farm is something that absolutely must be done to keep pace with the enormous files that the Red cameras will be producing. I double-dog-dare you to render anything from that monster 6 x 17cm sensor using an off-the-shelf workstation and meet any deadlines.

That said, I am imagining a rack of commodity linux boxes all connected to your workstation via gibabit ethernet and possibly eSATA as well. Your workstation can delegate a huge rendering job to the various machines by simply chopping up the source file and handing pieces off to the various machines which would devour it like hungry sharks. Adding 8 extra cores to the task might be as easy as popping in one of these --a nehalem equivalent of which is no doubt due shortly.

AMD also offers good price/performance. You can get comparable clock speeds to the Intel chips for half the price. Or you can get a full 16-core AMD monster, something like this:
4 x AMD Opteron 8380 2.5GHz 75w CPU[/url]
Tyan 4-socket mobo
32 GB of G-Skill RAM
6 x Western Digital Caviar 640GB Drives in RAID 0 config.
550 Power Supply, 4u rackmount case
approx $6700 including tax and shipping. Compare to a 8-core Mac with RAID card, 4 drives, and 32GB for $12,100.

This is very different from a mac but would probably offer similar performance. I'd love to try and benchmark one. Some notable differences:
* AMD box has 4 processors and 16 full cores.
* Max box has 2 processors and 8 cores but each is hyperthreaded...results in 16 threads under optimum circumstances
* Mac has slightly higher clock speed, 2.66Ghz vs. 2.5Ghz
* Mac memory runs faster (1066 vs. 667). However, the chip-to-memory bandwidth advantage of the Mac may be mitigated by fact that it has half as many CPU sockets. The existence of 4 separate sockets in the AMD box means that you have twice as many sockets per thread.
* AMD machine has 6 drives to Mac's 4. Also room for 3 more internal drives with 9 internal drive slots.
* AMD has no optical drive and inferior video card but it wouldn't be running as a desktop machine. For optical drive, add $25.
* AHEM - $6000 price difference

By using commodity x86 machines, you gain several advantages:
1) no mac tax
2) no windows tax
3) no need to port software to windows if software can run on linux*

*Given that OSX is really BSD Unix, I would imagine that these rendering algorithms already exist in a code format that is quite ready for export to a linux box.

Does that sound ridiculous? Seems to me all that remains is the development of a bit of network code and a bit of code to let your workstation break the job out to the various machines. If done right, this render farm approach could support really amazing scalability. Just plug in another machine.

No its not ridiculous. Its ridiculous that Apple never managed to exploit the future of render farms, by making xgrid more common and pumping out tonnes of cheap mac minis...
 
Very much agree with what's said but don't want to skate too close to the PC/Mac debate.

However, the thing that does bug me about multiple systems is the network I/O as Gigabit ethernet in reality only gives 40-50MB/sec transfer between machines (Vista64).
Whilst were talking about being able to have these cheap machines, I'd love to hear of an equally cheap way of networking them (and not necessarily for render farm)
1. Cheap fibre? (oxymorom)
2. Can esata do host to host?
3. Other...???

Dave
 
what about the new xeon 8 core native...with the possibility of using 4 sockets.so it is 4*8-core*2 threads( in perfect case)....so it could be 64 threads
along with DDR3 1600Mhz memory and using the new seagat 7200.12 in raid 0plus SSD drives i think it would be the perfect match

Jim

i know about the conection between apple and Red but is it possible to have, in the future,all the tools that we use in mac in a windows based platform? i love MAC OSX but the price paid for a MAC in terms of hardware when compared with other platform is just to big

thanks

Joao tiago@ Planar
Portugal
 
I started thinking about the whole gigabit ethernet as I/O bottleneck and I think you are right. The theoretical limit is only 125MB/sec and in reality is probably less. On the bright side, a Mac Pro has dual GB ethernet connectors so that potentially doubles bandwidth.

I looked back at the Tyan mobo and it lacks eSata.

USB, firewire, and eSATA are all two-way connectors. If you can write a driver to get your PC to talk to a hard drive or thumb drive, you can write a driver to have it talk to another PC. They just need a protocol. It would require a bit of coding.
 
screw the recession... I'm investing.

now if we can just get the rest of the country to adopt this mantra (as I am)

the recession will end... as they all do, with restored consumer confidence.

there is another post on here with an excellent argument on buying the 2.26 and NOT wasting money on the 2.93 FYI.
 
redrushes for pc would be great.


if you would know a way how cs4 can export dnxhd it would be good to know.

Go to the Avid website and download the Avid Codecs. This will give you DNxHD as a Quicktime export codec option.
 
Here is USB for pc to pc file transfer. Here is an awesome tutorial about connecting two PCs via firewire.
 
there is another post on here with an excellent argument on buying the 2.26 and NOT wasting money on the 2.93 FYI.

Figure it's cheaper than getting a Pablo/Storage.

Been doing some testing in REDrushes v3.60 on Mac Pro 8 core 2.93 transcoding to Apple ProRes 422 (HQ). Getting only 3 cores to max out... transcoding is way slower than using Compressor/Qmaster. Perhaps I'm doing something wrong. With Qmaster all 16 cores were max out and the same job was done in 2 minutes 15 seconds. With REDrushes 8 minutes 10 seconds.

Render: Cores per Clip set to Auto. Changed to 8... still get the same performance.

Update: So for a single clip Qmaster is faster but for multiple clips Qmaster/REDrushes are the same speed? I'm beginning to understand the fine differentiations and extra added benefits of REDrushes now.
 
NM...
 
Back
Top