ye sir.... copy to disk and start editing is the only way that makes sense.

On Sun, Jan 3, 2021 at 10:46 AM Jean-Luc CECCOLI
<[email protected]> wrote:
>
> > Message du 02/01/21 19:30
> > De : "Tom Whale"
> > A : [email protected]
> > Copie à :
> > Objet : Re: [darktable-user] Importing from camera
> >
> > On 02.01.2021 at 18:47 Jean-Luc CECCOLI wrote:
> >
> > > I wonder why on earth do some people absolutely want to import right from 
> > > the camera.
> > > It is far slower and less safe than doing it by reading the card from a 
> > > card reader.
> > > Safe : if the card falls on to the ground, it will not be the same as if 
> > > it were the camera.
> > > Slower : I admit this is based upon my own observations with Nikon
> > > 1 v1, D700 and D4s conneted either via usb2 or usb3.
> > > Plus, if I do not mistake, this just does import the pictures into
> > > the database, so they will not be available anymore after unplugging the 
> > > camera.
> > > I think, together with others on this list, that the best is to
> > > copy the files from the card to the disk, and then import them.
> > > There are many tools that allow organizing while copying, most of
> > > them have been listed in previous posts.
> >
> > But you cannot import directly from SD-card. When doing this, the
> > photos remain on the SD-Card and the sidecar-files are written on the
> > SD-card. Sorry but this is a no-go.
> > The only practicable way is to copy the photos on the harddisk.
>
> Yes, indeed.
> And this is why I use /import/ through the 5 first lines, describing what I 
> think to be a database related operation (line 6), and then suggest to /copy/ 
> the files to the disk as the most sensible thing to do.
>
> Rgrds,
>
> J.-Luc
> ____________________________________________________________________________
> darktable user mailing list
> to unsubscribe send a mail to [email protected]
>


-- 
:-)~MIKE~(-:
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to