Mozy and Restore

	Mozy and Restore On a scale of personal data disasters from 1 to 10, what would you rate a simultaneous double disk failure of your RAID 1 group and a more or less complete corruption of your Time Machine backup images? Pretty high…
On a scale of personal data disasters from 1 to 10, what would you rate a simultaneous double disk failure of your RAID 1 group and a more or less complete corruption of your Time Machine backup images? Pretty high I would guess. Let’s call it a 8.5. The only real way it gets worse is if you simultaneously lose root. Fortunately, I have Mozy. (I also have a sparse bundle of backup data that I can open and read, but I can’t copy files from it without getting error messages. I welcome any thoughts any of you might have on that one!) Before I initiated a restore with Mozy I did a quick google around to see what sort of restore speeds I could expect. To my surprise, the first few responses google returned didn’t leave me with much optimism. However, not only did I not have much optimism, I also didn’t have much choice. So I gritted my teeth and got down to it. The good news (and really the only good news of the day) is that Mozy is happily restoring my data at pretty reasonable speeds: peaking at over 2.0 MB/s over my ISP connection, and averaging somewhere around 1.0 MB/s. And it was ridiculously easy to browse the data that I wanted to restore, pick a destination, and just restore. I was at about 35 GB restored when I left for work this morning, with no hiccups, burps, or other forms of nastiness from Mozy. It is just working, and working well. Which is really the whole point. Mozy, not just for backup, but restore too!
Update your feed preferences

URL: http://emcfeeds.emc.com/rsrc/link/_/mozy_and_restore__396517867?f=84f8d580-01de-11de-22d1-00001a1a9134

Intel Clear Video™ and H.264/AVC

 

As I mentioned in my last blog post, I&aposve been working on getting H.264/AVC acceleration enabled.  This project was started by a post by one of the community members:

http://software.intel.com/en-us/forums/developing-software-for-visual-computing/topic/60703/page/1/

 

Over the last month, "casimier666" and I have been adding the acceleration code to Media Player Classic – Home Cinema.  Its been quite an education for me, and I owe much thanks to him for his help throughout the process.    I am happy to say that as of today, the player can now use the Intel Clear Video™ hardware to offload the processing to the hardware!

 

The code has been checked into sourceforge here: http://mpc-hc.svn.sourceforge.net/viewvc/mpc-hc/trunk/.

While it can play most clips we through at it – there are still a few that it can not.  Video clips with multiple slices per frame still have some corruption, but we are working on it and will update the code base when its fixed.   

 

I wanted to let you all know what the next steps are for this project.  I am currently writing a whitepaper that goes over the unique aspects of the DXVA2 interface on the G45.  It will contain some sample code and a bit of tutorial information on how DXVA2 works.  If you have suggestions on what should be in the paper, please drop me a note.

 

The following is a preview of the information in the paper:

 

  – Intel Clear Video™ for the G45 supports VLD mode acceleration for H.264/AVC content via the following GUID:

        DXVADDI_Intel_ModeH264_E: {604F8E68-4951-4c54-88FE-ABD25C15B3D6} 

 

While there are additional modes of acceleration available,  we are not going to focus on them.  VLD mode is an end-to-end  acceleration path that yields the best performance – and it’s the easiest to enable. 

 

One of the key enabling items for the G45 is when dealing with slices in the content.    The G45 chipset requires that the host send down the slice data in the DXVA_Slice_H264_Long structure, and does not support the DXVA_Slice_H264_Short version.   

 

The DXVA_Slice_H264_Long structure is where "casimier666" and I spent the most time working to get correct.  This mode of operation requires the host application to keep track of the reference pictures in the decoded picture buffer, and then send the correct references so that the hardware will decode the picture.  The host controls the management of the list, with short and long term pictures being added/removed via commands in the bit stream itself.     I don’t have much experience with the short structure – but I bet its easier then the long version!

 

Another challenge with the DXVA_Slice_H264_Long structure is the management of the offsets into the slice data.  The long version requires that each slice pass the "SliceBytesInBuffer", and the "BitOffSetToSliceData".  These offsets can be calculated as the bitstream gets parsed.  There&aposs a few special rules that the host must be aware of when setting the offsets.  I&aposll go over more of those in the whitepaper.

 

This project has been a great example of the community members and us at Intel working together to do something great.  If you would like to contribute to this effort, download the code and check it out!

I&aposll make sure to update everyone when the paper is done, and the code is 100%.

Thanks for Reading!

Eric

URL: http://feedproxy.google.com/~r/IntelBlogs/~3/vW7KvrdoQW0/

White House CTO Takes Leave of Absence

Although not implicated in a federal probe involving graft and corruption in his former office with the District of Columbia, new White House Chief Technology Officer Vivek Kundra takes a leave of absence only a week after accepting the position.
– After just one week on the job, President Obama’s new chief technology officer, Vivek Kundra, has taken a leave of absence in the wake of a federal graft and corruption investigation at the District of Columbia’s office of the chief information officer. Kundra, who served as DC’s Chief Informa…

URL: http://www.eweek.com/c/a/IT-Management/White-House-CTO-Takes-Leave-of-Absence-519393/?kc=rss