Reasons for using the Import Module?

User avatar
G8DHE
Posts: 242
Joined: 21 Aug 17 13:58

Reasons for using the Import Module?

Post by G8DHE » 03 May 20 13:11

"Not using PSU's Import Module? Wow, any reason why not?"

It just doesn't do anything that isn't already handled or isn't amenable to automation. My cards and cameras are recognised when they connect using USBDLM (https://www.uwe-sieber.de/usbdlm_e.html) which fires off batch routines that move the files to the right part of my file structures, add in additional files where needed for later web activity, or transfers race result spreadsheets and text files as needed. Ejects the device/card when it has verified that all files have been successfully moved. If I'm remote on the Laptop then they stay local to the Laptop, if the Laptop is on the local network then they are transferred direct to the Server.

All my images have GPS data in the EXIF direct from the cameras, so no need to handle separate GPX/KML etc. files to GeoTag. You can't rely on Google location info as you move around a site to remain consistent, it will hop around the nearest road names or not have any useful reference point other than a Town name at best. As I do a lot of watersports, I'm sometimes on a RIB in the middle of a river or estuary Google usually returns "Europe", so Reverse lookup isn't much help!

A lot of my labelling is tied up with event activities, specific race starts, turns, finishes etc. that can't be easily grouped without looking at the image and image time and my own commentary captured using a headcam and image timings for things like Podium prize givings etc.

The other major activity is labelling individuals within an image, again not something that can be done at import time, I tend to now use TagThatPhoto running on the laptop when out and about, and also on the main workstation, but this takes place in background when driving home or overnight ready for next day etc.

Would be interested how others use the features and facilities, especially now when we all have time to think about about our processes and workflows!

Below is a typical set of race Event structures I use, expanded to show all the levels.
Image
Geoff Mather (G8DHE)

User avatar
G8DHE
Posts: 242
Joined: 21 Aug 17 13:58

Re: A couple of suggestions

Post by G8DHE » 03 May 20 14:28

Yes happy for it to be moved, I think having a forum for discussing workflow would be a great asset to be honest.
Geoff Mather (G8DHE)

Mke
Posts: 520
Joined: 15 Jun 14 15:39

Re: A couple of suggestions

Post by Mke » 04 May 20 14:39

Hert wrote:
03 May 20 11:09
Not using PSU's Import Module? Wow, any reason why not?
I rarely use it either; it's just not normally the 1st thing in my workflow.

johnlill
Posts: 37
Joined: 03 Mar 06 16:01

Re: A couple of suggestions

Post by johnlill » 04 May 20 17:55

Hert wrote:
03 May 20 11:09
Not using PSU's Import Module? Wow, any reason why not? It should offer every possible feature needed to ingest, it's fast, and it's integrated.

BTW; also check your mouse settings in the OS
I do use the import module for the reasons you mention. It's no big deal about automatically starting the import wizard when a card is inserted and ejecting when done (although I would like that!), but adding a search bar to add labels to all images in an import (rather than navigating the tree) would be helpful. I'll post a suggestion on mantis.

I did check my mouse settings in the OS. It doesn't matter what I set them at, PSU still scrolls way too many lines with each notch of the wheel as shown in the video.

andrew.heard
Posts: 171
Joined: 16 Jun 10 0:36

Re: A couple of suggestions

Post by andrew.heard » 04 May 20 23:26

Hert wrote:
03 May 20 11:09
Not using PSU's Import Module?
I stopped using it long ago because it often crashed. Maybe it works now but I've never gone back to investigate. I found it more reliable to right click on a folder in the LHS Folder panel & Verify the folder from there. Because my (Windows) structure is (essentially) <decade>\<year>\<month>, my import workflow is simply a matter of copying new files into the current <month> folder using Windows Explorer, then occasionally from PSu I right+click+Verify that folder to import the latest files. It's quick & efficient.

Hert
Posts: 6417
Joined: 13 Sep 03 7:24

Re: A couple of suggestions

Post by Hert » 05 May 20 8:49

The copy process, how you describe it, would be faster with Photo Supreme than using Windows explorer to copy files. This because Photo Supreme will do that multi threaded. And at the same time PSU can create the folder structure and name your files.
But if your current workflow with manual import works, then it works :)
This is a User-to-User forum which means that users post questions here for other users.
Feature requests, change suggestions, or bugs can be logged in the ticketing system

fbungarz
Posts: 1594
Joined: 08 Dec 06 5:03
Location: Arizona, USA

Re: A couple of suggestions

Post by fbungarz » 06 May 20 19:39

Not using PSU's Import Module? Wow, any reason why not? It should offer every possible feature needed to ingest, it's fast, and it's integrated.
Hert - I am using the import module of course!
But I am not using it "straight from the memory card"...
I typically shoot so many duplicates of lichens at slightly different settings (playing with the aperture for best depth-of-field) that I prefer sorting out the keepers first and do the ratings in FastPictureViewer - copying only the ones I want for the import from the card to my harddisk - and then starting the import in PSu.

I agree that PSu's import is extremely powerful, but just purely for culling images it is simply to slow, the thumbs from a big memory card popping up ever so slowly and quickly glancing through full views, rate and make the keepers is simply not efficient for me in comparison with FastPictureViewer.

Sorry for the misunderstanding. Of course everyone does things a bit differently and I can understand if there is a request for an option to automatically start the importer upon insert and eject the card when it is done - if this remains an option, i.e., can also be disabled...

Cheers,
Frank

fbungarz
Posts: 1594
Joined: 08 Dec 06 5:03
Location: Arizona, USA

Re: Reasons for using the Import Module?

Post by fbungarz » 06 May 20 19:49

I should have posted this here:

Hert - I am using the import module of course!
But I am not using it "straight from the memory card"...
I typically shoot so many duplicates of lichens at slightly different settings (playing with the aperture for best depth-of-field) that I prefer sorting out the keepers first and do the ratings in FastPictureViewer - copying only the ones I want for the import from the card to my harddisk - and then starting the import in PSu.

I agree that PSu's import is extremely powerful, but just purely for culling images it is simply to slow, the thumbs from a big memory card popping up ever so slowly and quickly glancing through full views, rate and make the keepers is simply not efficient for me in comparison with FastPictureViewer.

Sorry for the misunderstanding. Of course everyone does things a bit differently and I can understand if there is a request for an option to automatically start the importer upon insert and eject the card when it is done - if this remains an option, i.e., can also be disabled...

Cheers,
Frank

oversampling
Posts: 41
Joined: 13 Aug 15 17:39

Re: A couple of suggestions

Post by oversampling » 06 May 20 22:01

I, for one, always use PSU import function and find it very valuable (only wish it remembered the location I imported from in the last round)

gcurrie
Posts: 34
Joined: 02 May 10 2:55

Re: Reasons for using the Import Module?

Post by gcurrie » 13 May 20 7:42

Yes I use the import module and have specific profiles as well for moving files from PC desktops to a file server (PostgreSQL version).
After many versions where it was seemed less than reliable, it appears to be solid as of 5.x.

Our workflow spends significant time on PCs doing ruthless culling, precise naming and RAW processing.
This is all done so we can import the cleanest 'collection' into the PSU photo library (GIGO).

After import, we create selected versions with further processing. Then the fun begins.
Gordon Currie
Photo Supreme 5.4 PostgreSQL on Windows Server Essentials 2016

snowman1
Posts: 273
Joined: 01 Jan 07 3:13
Location: UK

Re: Reasons for using the Import Module?

Post by snowman1 » 13 May 20 12:44

I also use the importer - it provides important functions for me like making safety copies, naming to my standards, putting in folders to my preferences, and initial labelling (which assists me later on in processing). And it means I do all this in one step, which is very convenient. It's a very good tool, and one that's an essential feature to PSU IMO.

However I do wish this bug https://mantis.idimager.com/view.php?id=3213, this bug https://mantis.idimager.com/view.php?id=3091 and this feature request https://mantis.idimager.com/view.php?id=3090 would get implemented :-( They are all longstanding. Hert?!
Snowman1
http://www.flickr.com/photos/snowman-1/
--------------------------------------

snowman1
Posts: 273
Joined: 01 Jan 07 3:13
Location: UK

Re: Reasons for using the Import Module?

Post by snowman1 » 13 May 20 12:47

Our workflow spends significant time on PCs doing ruthless culling, precise naming and RAW processing.
This is all done so we can import the cleanest 'collection' into the PSU photo library (GIGO).
Gordon, so - to clarify - you do all this before importing? What tools do you use for this if you don't mind me asking?
Snowman1
http://www.flickr.com/photos/snowman-1/
--------------------------------------

jstartin
Posts: 410
Joined: 23 Aug 06 13:47
Location: UK

Re: Reasons for using the Import Module?

Post by jstartin » 13 May 20 21:53

As a hobbyist photographer (without the constraints of huge numbers, rapid culling, getting stuff out to clients, etc) I always use the import module. It provides every facility I can think of (and more!) and is both convenient and reliable. A rock solid way of being consistent with no fuss.
Jim (Photo Supreme: AMD Quad-Core A8-5500 Accelerated Processor 3.2 GHz; internal AMD Radeon™ HD7560D; 4GB DDR3 SDRAM; Win10x64)

HaraldE
Posts: 254
Joined: 29 Apr 07 22:30
Location: Bålsta, Sweden

Re: Reasons for using the Import Module?

Post by HaraldE » 27 Aug 20 23:17

Me using Import almost everytime I have some new photos in Mobile or Camera. This will do some nice housekeeping like updating proper metadate. Also very fond of the fact that PSU remembers what was imported last time and only grabs the new photos.

Regards, Harald

HCS
Posts: 155
Joined: 19 Feb 14 22:08

Re: Reasons for using the Import Module?

Post by HCS » 12 Oct 20 9:42

I copy my files to a drop zone first, a dedicated folder to receive the files from card.

Then i run the PSU importer, it takes care of renaming according to my rules and moving to a dated folder in the dropzone to indicate successful processing. I also attach labels depending on date of import (i want to retain that beyond what PSU offers) and sometimes content based.

In PSU, i take care of further labeling the files and moving them to the archive folder structure.

Post Reply