Dmedia

Bug #678024
Comment #4

Comment 4 for bug 678024

Revision history for this message

Jason Gerard DeRose (jderose) wrote on 2010-11-28:

I wanted to clarify that this design bug is about the *import* process (importing newly captured files from CD/SD cards), not *migration* (importing an existing library into dmedia). These are quite different use cases because you will probably only perform a *migration* once, and it merits a lot of options and confirmation from the user at each step of the way. On the other hand, *imports* are that error-prone repetitive tasks that the pro user will do over and over again... the best UX is truly for them to occur with no user intervention at all.

I also wanted to provide a real life example to hopefully convince people that the low-volume casual use-case and the high-volume pro use case are quite different, merit a different UX.

Again, Tara (~frmdrt) provides my real-world use case. She shoots weddings in the photo-journalistic style (basically tries to capture candid moments, does more than just posed shots). In order to get enough good candids, you need to shoot an incredible amount of photos. For the last wedding she shot, it was her plus two assistant photographers (Jeff and I actually). And during the ceremony I shot video. By the time it was all done, there were 5 memory cards (2 x 16GB, 3 x 32GB) which were almost all full. There were over 4,000 RAW photos and around 60 1080p video clips.

A week of full on HDSLR movie or TV production will easily produce several *terabytes* of video. Can you image the poor schmuck that has to feed all those cards into a workstation over and over again? This is why we need an import process that requires no user intervention, is fool proof.

This is also a really cool opportunity for the freedesktop... no one currently has a good workflow for the pro file import process. We're not playing catch up here, we're setting the standard.

Making the UX right for importing multiple cards simultaneously is also important, a big opportunity. It's not just about trying to get the imports completed faster... more important is to interrupt said poor schmuck fewer times. Throw 4 cards into the card readers, do something else. Notice that *all* cards have completed, yank them out, throw 4 more cards into the readers.

I wanted to clarify that this design bug is about the *import* process (importing newly captured files from CD/SD cards), not *migration* (importing an existing library into dmedia).  These are quite different use cases because you will probably only perform a *migration* once, and it merits a lot of options and confirmation from the user at each step of the way.  On the other hand, *imports* are that error-prone repetitive tasks that the pro user will do over and over again... the best UX is truly for them to occur with no user intervention at all.

I also wanted to provide a real life example to hopefully convince people that the low-volume casual use-case and the high-volume pro use case are quite different, merit a different UX.

Again, Tara (~frmdrt) provides my real-world use case.  She shoots weddings in the photo-journalistic style (basically tries to capture candid moments, does more than just posed shots).  In order to get enough good candids, you need to shoot an incredible amount of photos.  For the last wedding she shot, it was her plus two assistant photographers (Jeff and I actually).  And during the ceremony I shot video.  By the time it was all done, there were 5 memory cards (2 x 16GB, 3 x 32GB) which were almost all full.  There were over 4,000 RAW photos and around 60 1080p video clips.

A week of full on HDSLR movie or TV production will easily produce several *terabytes* of video.  Can you image the poor schmuck that has to feed all those cards into a workstation over and over again?  This is why we need an import process that requires no user intervention, is fool proof.

This is also a really cool opportunity for the freedesktop... no one currently has a good workflow for the pro file import process.  We're not playing catch up here, we're setting the standard.

Making the UX right for importing multiple cards simultaneously is also important, a big opportunity.  It's not just about trying to get the imports completed faster... more important is to interrupt said poor schmuck fewer times.  Throw 4 cards into the card readers, do something else.  Notice that *all* cards have completed, yank them out, throw 4 more cards into the readers.