Batch import via daisy chained card reader
I used to be able to batch import multiple cards into earlier versions of C1Pro, now if I start one card importing, put in another, it just tries to get me to reimport the first cards files again, I see no way of choosing the second card, even if I direct the import window to the new card, it still shows me the first images on the first card. If I ignore this, and select IMPORT, it just imports duplicates from the first card.
In older versions, as soon as another card was detected, a NEW import window appeared so it was then possible to choose the new card and import at the same time. This now no longer works, so I have five very expensive FW800 Lexar Pro card readers and can only use one of them.
A fix for this would be mighty welcome.
In older versions, as soon as another card was detected, a NEW import window appeared so it was then possible to choose the new card and import at the same time. This now no longer works, so I have five very expensive FW800 Lexar Pro card readers and can only use one of them.
A fix for this would be mighty welcome.
0
-
Good idea. I suggest you make a feature request in a support case to get it within Phase One into the proper channels. This is a user forum and users can fix this. 0 -
I'll do exactly that Paul, thanks for the suggestion.
Now, where exactly can I create a support case for this issue? I've looked everywhere and keep getting blind alleyed, or blinded alleys, or whatever!
cheers0 -
[quote="John16" wrote:
I'll do exactly that Paul, thanks for the suggestion.
Now, where exactly can I create a support case for this issue? I've looked everywhere and keep getting blind alleyed, or blinded alleys, or whatever!
cheers
Go to http://xchange.phaseone.com/Content/Support.aspx
Contact Support. Skip the question about registered product.0 -
done, thanks again.
So, what's the chances of a software upgrade based solely on my feature request (actually feature re-instatement).
Consumer power, dontcha just love it?0 -
John,
We can't seem to replicate the issue. If others can provide more info we may be able to identify the cause of this error for you.0 -
I have a case open on it. We are working through it, looks like un-named cards could be the culprit 0
Post ist für Kommentare geschlossen.
Kommentare
6 Kommentare