David Battistella
Forum Replies Created
-
I have a 4210. The thing is a tank. It is fast and it is Raid 3. So far I have had to replace three drives in the unit it is still under warranty.
The good news is that I have not had any data loss in that time. The bad news is that a new recent management decision has now prevented them from doing “cross shipment”
This is a giant pain in the but for people like us who can not afford to be down at all.
Back when things were HUGE and not CIPRICO, there was a policy to report a down drive. They then take a credit card imprint and ship you a new drive. This, of course allowed you to work away and wait for your drive. When it arrived you could install it and then run a reconstruct (all the while still working on with the unit) and put the bad drive back in the box and ship it back to CIPRICO.
The system had changed. You now how to ship them your drive and if you want a drive back quickly you have to pay for it on your own ticket, otherwise it’s a few days.
A formatted HUGE 4210 is about 2.9TB of safe storage. Backing that up is no easy task. and if you are ever down (even if you have not lost data) it hurts.
I think the new policy will affect my decision when I am looking for more storage. This is my second HUGE product, but with the CIPRICO changes (and frankly, dunce like decisions about changing cross shipping policies with existing customers) I am may to have to look to another manufacturer. SAS raid 6 looks interesting for sure.
I must say that Lance and Gerry and others I have dealt with at HUGE are really helpful and second to none, but sometimes management doesn’t respond the way the front liners do.
The drive is great, but when you drop that kind of change you really need to pick a company that is going to stick to the plan that you bought into, rather than evoke new polices to loyal legacy customers.
My two cents.
David
For what it is worth, HUGE are very sticky about the drives that they put into their arrays. I suspect that within about 18 months we will be seeing a lot of failure reporting on there forums of “less expensive” esata solutions. I can assure you that HUGE does put the drive through a very rigourous check and they fail many drives that end up in your firewire enclosures. Data is not to be messed with, it’s your whole business.
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella -
GOP (group of Pictures)
Convert to a Panasonic DVCPRO codec for best most consistent results.
David
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella -
Will,
M2V is a long GOP format. This means that the video is represented in I and P frames. each frame is not assigned one timecode frame. What happens is and I frame gets drawn and then several P frames are drawn to “look” like the I frame.
In DV, for example, this does not exist. There is one frame represented for each timecode number.
David
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella -
Yes
Capture the material at a smaller frame size and data rate. This is how they get the multiple angles looking so smooth in all the demo’s.
Figure out the data rate of your drive array and then divide that by the angles.
This is a math problem. DV id 3.8 mb.sec. Can you ask a hard drive to seek on twenty different parts of the drive simultaneously and then push about 100mb/sec.
I’m not surprised it’s dropping frames.
David
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella -
Why would you edit an m2v file. Can’t you extract a real format from that camera?
David
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella -
Shoot HD at 720. You can always extract 24 frames from that. THe data rates are low enough to edit with FW 800 drives on a macbook pro.
david
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella -
300 dpi is overkill and you are asking FCP to work harder than it needs to.
You are seeing a proxy of a file that needs to be rendered. You probably see a dark green bar in the timeline and this means you need a render.
I suggest you leave the file at 72 DPI and make the canvas much bigger than it has to be. You will save yourself headaches and a lot of render time.
David
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella -
What color is the graphic?
Does it happen on playback?
What typeface are you using?
all of these will factor.
David
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella -
I’ll just add that Final Cut Pro has a purchased installed user base of about 1 million customers now. That means more people will develop for it and you have more knowledge to draw on when learning the program.
David
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella -
I can confirm the same problem inteh same codec but on a Dual G5, 2.7 machine, I think it’s the way QT and FCP talk to each other.
David
Peace and Love 🙂
Read my Blog
https://blogs.creativecow.net/DavidBattistella