Bob Gundu
Well-known member
- Joined
- Mar 17, 2011
- Messages
- 10,238
- Reaction score
- 3
- Points
- 38
- Location
- Toronto, ON Canada
- Website
- www.10fh.com
This is how RED is figuring out the upgrade program:
Last edited:
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
his is how RED is figuring out the upgrade program:
Sony make their announcements
Red responds competively and agressively with new prices...
curious where you came up with this "fact"... or "theory" ??
Jim Jannard said:ASICs that weren't fast enough for EPIC… just became a gold mine for Scarlet.
"An obscene amount of profit" are pretty strong words. Even so, don’t expect epic’s price to fall close to the current scarlet price. In relation to the BT scarlet, Jim said the new price of epic would beThat means we can continue to charge the same for an EPIC (and now make an obscene amount of profit) or lower the price.
I would take that to mean at least 2 times the BT Scarlet price which puts Epic at least $14k. Originally epic was supposed to cost $28k, so that seems kind of low.a significantly higher investment.
This makes me wonder if something close to the original R1 price would be reasonable. It would also be good to keep in mind that they still have to putanyone who doesn't own an EPIC will after Nov. 1st.
Thus it seems like under $18k would be unlikely. There still needs to be some room for Scarlet in the mix. Originally epic was slated for a price of $28k, so considering all of the statements made by RED it seems safe to assume that the price will be at or less then that.all those 18,000 parts into such a small package.
Dragon has actually gotten more expensive to make because we needed to respin the ASIC to go along with the recent improvements of the sensor...
and later Jarred clarified,across the lineup...
Heh heh heh.... Jim didn't mean across everything we make. Just Camera Brains.
I can tell you right now Scarlet, as it sits , cannot handle the Dragon.
But as it sits, neither can the Epic.
One way or another we will make sure Scarlet customers have a pathway to the Dragon.
It is a complicated problem, but a good problem to have.
Red does not HAVE to do anything. I am with Terry Verhaar, Anyone reading negativity into this really isnt paying attention or had no business buying a camera in the first place. Am I a genius for selling BOTH my EPIC X last January when I saw Scarlet killing the rental market? I look like it now... but that killed me to do.
I PAID A $10,000 PREMIUM to jump the line on EPiC-X in 2010. then Red came out with the EPIC_M... and sold 1000 cameras ahead of me. did Red screw me? Hell no.
Am I stoked about the price cut as I literally have been building my $50K cart? hell YES! Timing is everything...![]()
Secondly. I hope SHawn Nelson is Guess is RIGHT !! But no way Epic X with TI PL Mount and SSD Module is under $20K. That would be awesome though and Id buy 2.
Red ONE MX rented so fast I made doubled my investment. Epic rented so slow I sold them as soon as Scarlet was announced. I bought a Scarlet and HATED it and sold that too.
I wish Scarlet would die an ignobale death. The RED ONE is by far a superior camera and value and I hope to hell Terry is right in that Scarlet NEVER gets the Dragon sensor. EPIC is and should be EPIC!
Ha ha ha, he should of posted that last week. On another note, why do some people think there will be no upgrade path for Scarlet to Dragon? Wouldn't this render the Scarlet obsolete?
I guess I meant more in the lines of whether or not there were any hints that may have led someone to think that the Scarlet would not have a path to Dragon, last word I read was yes but pricing was not fixed, did I miss something?No - it would just make Scarlet not upgradeable to Dragon. Doesn't make it "not upgradeable."
Yes - and, to me, implicitly that still begs the question of whether there is only THE Dragon or multiple Dragons.
This is how RED is figuring out the upgrade program:
I derived mine with an Algorithm. It doesn't mean my algorithm was correct though![]()