12:50 a.m.
I have plugged a digital camera into my usb port and mounted it using
the popup displayed from the auto detect via konqueror (this annoys me
as well). When konqueror is launched it displays the contents via
Camera:/ which is okay, but subsequently I can't find any entries under
/run that represent the camera. I assumed there would be a mount point
under /run like there is for a usb flash disk. Given that there appears
to not be a mount point under /run, where is it mounted in Fedora 20, so
that I can point dolphin (which is what should be launched from the
'Open with File Manager' prompt, not Konqueror) at the mount point
rather than having to manually type Camera:/ into the address bar.
regards,
Steve
5:01 p.m.
On 10/25/2014 01:31 PM, poma wrote:
On 25.10.2014 03:19, poma wrote:
> On 25.10.2014 02:09, poma wrote:
>> On 25.10.2014 01:31, Stephen Morris wrote:
>>> On 10/25/2014 01:09 AM, poma wrote:
>>>> On 24.10.2014 07:50, Stephen Morris wrote:
>>>>> I have plugged a digital camera into my usb port and mounted it
using
>>>>> the popup displayed from the auto detect via konqueror (this annoys
me
>>>>> as well). When konqueror is launched it displays the contents via
>>>>> Camera:/ which is okay, but subsequently I can't find any entries
under
>>>>> /run that represent the camera. I assumed there would be a mount
point
>>>>> under /run like there is for a usb flash disk. Given that there
appears
>>>>> to not be a mount point under /run, where is it mounted in Fedora 20,
so
>>>>> that I can point dolphin (which is what should be launched from the
>>>>> 'Open with File Manager' prompt, not Konqueror) at the mount
point
>>>>> rather than having to manually type Camera:/ into the address bar.
>>>> ptp != usb_storage
>>>>
>>>> http://en.wikipedia.org/wiki/Picture_Transfer_Protocol
>>>> http://www.gphoto.org/proj/libgphoto2/
>>>>
>>>> modinfo -d usb_storage
>>>> USB Mass Storage driver for Linux
>>>>
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/dri...
>>>>
>>>>
>>>> poma
>>>>
>>> Thankyou for the links. I looked at those links which gave me a lot more
>>> information that I didn't know about. Unfortunately the documentation on
>>> libphoto2 seems to potentially be self conflicting. The list of cameras
>>> that libphoto2 supports seems to have my Nikon D3100 listed, but the
>>> list of cameras and how they are supported under Unix does not appear to
>>> list my camera.
>>> Following Cameron's email I checked the mount list which seems to
>>> indicate there is no mount point, which also coincides with the
>>> available device interface in the system tray not being able to unmount
>>> the camera before disconnection.
>>> Also now that I have changed to application preference order in the
>>> properties of the folder displayed by dolphin, whenever I select 'Open
>>> with File Manager' at device detection time the process correctly
>>> launched dolphin to display the contents, whereas yesterday when
>>> konqueror was the default application, manually pointing dolphin at
>>> Camera:/ would not display the contents of the camera because dolphin
>>> was trying to treat the camera as a usb device and couldn't acquire the
>>> usb. The only issue with dolphin is it doesn't display the folder name
>>> where the images are stored on the camera as the same name that the
>>> camera says it is, dolphin seems to be putting its own prefix on the
>>> folder name.
>>> Also dolphin seems to be starting at a higher point in the directory
>>> tree for its displays than where Windows starts.
>>> DigiKam now seems be displaying the files on the camera now as well,
>>> whereas yesterday it couldn't either, although digiKam doesn't
>>> understand the raw format files that I am taking with the camera. I
>>> could use jpeg images but that is not as good for image manipulation and
>>> corrections as raw is. I can process these files using the raw interface
>>> to Photoshop Elements and Elements itself, albeit under windows, so not
>>> being able to access these under Linux is not that big a deal to me,
>>> other than the fact that I have to use Windows.
>>>
>>> regards,
>>> Steve
>>>
>> Does the Nikon D3100 supports USB mass storage mode?
>> http://goo.gl/7bGFuh
>>
>
> In this respect manual(D3100_EN.pdf) is questionable
>
http://www.nikonusa.com/en/Nikon-Products/Product/dslr-cameras/D3100.html...
>
> Therefore you can try this *if* the device supports both - PictBridge(PTP) & USB
storage, and they collide:
>
> /etc/modprobe.d/usb_storage-quirks-Nikon_D3100.conf
> # Nikon D3100
> #
> # lsusb
> # ID 04b0:0130 Nikon Corp. Coolpix 4600 (ptp)
> # ID 04b0:0427 Nikon Corp.
> # modinfo -p usb_storage
> # ...
> # quirks:supplemental list of device IDs and their quirks (string)
> #
> # 1.
> options usb_storage quirks=04b0:0130:i
> #
> # 2.
> # options usb_storage quirks=04b0:0427:i
> #
> # 3.
> # options usb_storage quirks=04b0:0130:i,04b0:0427:i
> #
> # *uncomment* only *one* of the three *options* that you'll *use* as the first
case!
>
>
> Ref.
> - https://www.kernel.org/doc/Documentation/kernel-parameters.txt
> ..
> usb-storage.quirks=
> [UMS] A list of quirks entries to supplement or
> override the built-in unusual_devs list. List
> entries are separated by commas. Each entry has
> the form VID:PID:Flags where VID and PID are Vendor
> and Product ID values (4-digit hex numbers) and
> Flags is a set of characters, each corresponding
> to a common usb-storage quirk flag as follows:
> ...
> i = IGNORE_DEVICE (don't bind to this
> device);
> ...
> Example: quirks=0419:aaf5:rl,0421:0433:rc
>
> - https://www.kernel.org/doc/Documentation/usb/hotplug.txt
>
> - USB: add Nikon D300 camera to unusual_devs
>
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/d...
>
>
BTW
- Nikon D3100 specifications
http://www.dpreview.com/reviews/nikond3100/page2.asp
...
Connectivity • USB 2.0 (Hi-Speed)
• Mass storage / PTP selectable
- Digikam support Nikon D3100
http://thread.gmane.org/gmane.comp.kde.digikam.user/14517
Xfce
- USB storage
$ thunar /run/media/user/</dev/disk/by-uuid/>/
- MTP (Media Transfer Protocol)
$ thunar mtp://[usb:<bus>,<devnum>]/
- PTP (Picture Transfer Protocol)
$ thunar gphoto2://[usb:<bus>,<devnum>]/
Good luck with reading and playing with the device. :)
poma
Ref.
Mailing list
https://www.digikam.org/contact?q=support#mailinglists
Thanks for all the info
Poma, there is some very useful information in
those links. Even though the links say the camera is switchable between
the 2 modes I'm not sure whether it is manually switchable. The manual
and camera itself don't have any details on how to do it. It seems as
though it may be automatically switchable depending on the access
mechanism. Under linux it seems to be accessed via PTP but under Windows
(I'll need to double check this) it seems to be accessed in USB Mass
Storage mode as it seems to be mounted as a USB device. I was able to
remove files from the SD card on the camera using dolphin and digiKam
was able to access the files directly by auto navigating down to the
appropriate directory, but GIMP was unable to touch the camera at all.
regards,
Steve
4:19 p.m.
On 02.11.2014 20:58, Stephen Morris wrote:
On 10/31/2014 11:47 AM, poma wrote:
> On 30.10.2014 21:58, Stephen Morris wrote:
>> On 10/29/2014 01:15 PM, poma wrote:
>>> On 28.10.2014 21:27, Stephen Morris wrote:
>>>> On 10/28/2014 06:58 AM, poma wrote:
>>>>> On 27.10.2014 20:40, Stephen Morris wrote:
>>>>>> On 10/27/2014 12:13 PM, poma wrote:
>>>>>>> On 27.10.2014 00:53, Ed Greshko wrote:
>>>>>>>> On 10/27/14 07:48, poma wrote:
>>>>>>>>> You might try to contact the author
>>>>>>>>> http://www.cybercom.net/~dcoffin/dcraw/
>>>>>>>> The first few sentences on that site would seem to answer
all the questions....
>>>>>>>>
>>>>>>>> "....My software is for processing those images
*after* downloading them."
>>>>>>>>
>>>>>>> Touché.
>>>>>>>
>>>>>>>
>>>>>>> poma
>>>>>> I'll probably contact the author as well. It fine to only
support
>>>>>> processing after downloading, but it should still display the
contents
>>>>>> of the files so that you can decide what to download to process.
>>>>>>
>>>>>> regards,
>>>>>> Steve
>>>>>>
>>>>> Great, never underestimate the social moment.
>>>>>
>>>>>
>>>>> poma
>>>>>
>>>> I've checked Rawtherapee and Darktable for their functionality.
>>>> Rawtherapee appears to not support importing photos from any source that
>>>> is not mounted, whereas Darktable will import photos from any detected
>>>> device and displays the contents of the photos on the camera when
>>>> prompting for which photos should be imported from the camera, which
>>>> presumably means that Darktable is not using dcraw the access the
>>>> camera, it is doing it itself.
>>>>
>>>
http://www.darktable.org/2012/10/whats-involved-with-adding-support-for-n...
>>> RAW format support
>>> darktable uses two libraries to read RAW files. Most common RAW formats
are read via the RawSpeed library (by Klaus Post), more esoteric RAW formats not supported
by RawSpeed are read via LibRaw (which in turn is based on Dave Coffin's dcraw).
>> I've looked at the cameras.xml file linked to in the above web page and
>> it lists the D3100 which I assume means RawSpeed has support for my
>> camera, which would explain why Rawtable provides an on camera image
>> preview when importing the files.
>>> BTW did you check with the Rawstudio
>>> http://rawstudio.org
>> I haven't looked at this application as yet, mainly because until now I
>> didn't know it existed.
>>> Perhaps the only real issue with the Nikon D3100 is the lack of USB Mass
Storage mode.
>> Its not so much the lack of a USB Mass storage mode, its the lack of the
>> ability to preview the contents of the images on camera when I want to
>> copy the files to my network storage for processing in Photoshop
>> Elements, and, with some of them to produce a photo print. I only want
>> to copy the files I am going to keep, so I want the ability to view the
>> images, delete the ones I don't want to keep, then mass extract the
>> remaining files to my NAS. Hence for me the ability to mass preview the
>> images on camera is paramount, and any application that is used to
>> process the files needs to have the ability to do some rudimentary
>> correction to the raw file and save those corrections in a separate
>> "correction" file (the way the raw interface in the Photoshop
>> applications do) so that the actual raw file is left unchanged, so that
>> at the "corrections" file can be deleted at any time to back out the
>> changes without impacting the original raw file.
>>
>> regards,
>> Steve
>>
> In your case is just perhaps crucial.
> Shall we start a thread again? :)
> ptp != usb_storage
It probably should be, we have probably moved away from the original
reason for raising this thread.
I think what this has moved to is that it seems that under Linux there
seems to be a requirement to take digital photos in Raw+JPG mode in
order for processes to be able to do what I want.
regards,
Steve
Next time you get the other camera in your hands, you 'll know what the functionality
should be supported.
Hurray
7:47 p.m.
On 30.10.2014 21:58, Stephen Morris wrote:
On 10/29/2014 01:15 PM, poma wrote:
> On 28.10.2014 21:27, Stephen Morris wrote:
>> On 10/28/2014 06:58 AM, poma wrote:
>>> On 27.10.2014 20:40, Stephen Morris wrote:
>>>> On 10/27/2014 12:13 PM, poma wrote:
>>>>> On 27.10.2014 00:53, Ed Greshko wrote:
>>>>>> On 10/27/14 07:48, poma wrote:
>>>>>>> You might try to contact the author
>>>>>>> http://www.cybercom.net/~dcoffin/dcraw/
>>>>>> The first few sentences on that site would seem to answer all the
questions....
>>>>>>
>>>>>> "....My software is for processing those images *after*
downloading them."
>>>>>>
>>>>> Touché.
>>>>>
>>>>>
>>>>> poma
>>>> I'll probably contact the author as well. It fine to only support
>>>> processing after downloading, but it should still display the contents
>>>> of the files so that you can decide what to download to process.
>>>>
>>>> regards,
>>>> Steve
>>>>
>>> Great, never underestimate the social moment.
>>>
>>>
>>> poma
>>>
>> I've checked Rawtherapee and Darktable for their functionality.
>> Rawtherapee appears to not support importing photos from any source that
>> is not mounted, whereas Darktable will import photos from any detected
>> device and displays the contents of the photos on the camera when
>> prompting for which photos should be imported from the camera, which
>> presumably means that Darktable is not using dcraw the access the
>> camera, it is doing it itself.
>>
> http://www.darktable.org/2012/10/whats-involved-with-adding-support-for-n...
> RAW format support
> darktable uses two libraries to read RAW files. Most common RAW formats are read
via the RawSpeed library (by Klaus Post), more esoteric RAW formats not supported by
RawSpeed are read via LibRaw (which in turn is based on Dave Coffin's dcraw).
I've looked at the cameras.xml file linked to in the above web page and
it lists the D3100 which I assume means RawSpeed has support for my
camera, which would explain why Rawtable provides an on camera image
preview when importing the files.
>
> BTW did you check with the Rawstudio
> http://rawstudio.org
I haven't looked at this application as yet, mainly because until now I
didn't know it existed.
>
> Perhaps the only real issue with the Nikon D3100 is the lack of USB Mass Storage
mode.
Its not so much the lack of a USB Mass storage mode, its the lack of the
ability to preview the contents of the images on camera when I want to
copy the files to my network storage for processing in Photoshop
Elements, and, with some of them to produce a photo print. I only want
to copy the files I am going to keep, so I want the ability to view the
images, delete the ones I don't want to keep, then mass extract the
remaining files to my NAS. Hence for me the ability to mass preview the
images on camera is paramount, and any application that is used to
process the files needs to have the ability to do some rudimentary
correction to the raw file and save those corrections in a separate
"correction" file (the way the raw interface in the Photoshop
applications do) so that the actual raw file is left unchanged, so that
at the "corrections" file can be deleted at any time to back out the
changes without impacting the original raw file.
regards,
Steve
In your case is just perhaps crucial.
Shall we start a thread again? :)
ptp != usb_storage
poma
9:15 p.m.
On 28.10.2014 21:27, Stephen Morris wrote:
On 10/28/2014 06:58 AM, poma wrote:
> On 27.10.2014 20:40, Stephen Morris wrote:
>> On 10/27/2014 12:13 PM, poma wrote:
>>> On 27.10.2014 00:53, Ed Greshko wrote:
>>>> On 10/27/14 07:48, poma wrote:
>>>>> You might try to contact the author
>>>>> http://www.cybercom.net/~dcoffin/dcraw/
>>>> The first few sentences on that site would seem to answer all the
questions....
>>>>
>>>> "....My software is for processing those images *after* downloading
them."
>>>>
>>> Touché.
>>>
>>>
>>> poma
>> I'll probably contact the author as well. It fine to only support
>> processing after downloading, but it should still display the contents
>> of the files so that you can decide what to download to process.
>>
>> regards,
>> Steve
>>
> Great, never underestimate the social moment.
>
>
> poma
>
I've checked Rawtherapee and Darktable for their functionality.
Rawtherapee appears to not support importing photos from any source that
is not mounted, whereas Darktable will import photos from any detected
device and displays the contents of the photos on the camera when
prompting for which photos should be imported from the camera, which
presumably means that Darktable is not using dcraw the access the
camera, it is doing it itself.
http://www.darktable.org/2012/10/whats-involved-with-adding-support-for-n...
RAW format support
darktable uses two libraries to read RAW files. Most common RAW formats are read via the
RawSpeed library (by Klaus Post), more esoteric RAW formats not supported by RawSpeed are
read via LibRaw (which in turn is based on Dave Coffin's dcraw).
BTW did you check with the Rawstudio
http://rawstudio.org
Perhaps the only real issue with the Nikon D3100 is the lack of USB Mass Storage mode.
3:27 p.m.
On 10/28/2014 06:58 AM, poma wrote:
On 27.10.2014 20:40, Stephen Morris wrote:
> On 10/27/2014 12:13 PM, poma wrote:
>> On 27.10.2014 00:53, Ed Greshko wrote:
>>> On 10/27/14 07:48, poma wrote:
>>>> You might try to contact the author
>>>> http://www.cybercom.net/~dcoffin/dcraw/
>>> The first few sentences on that site would seem to answer all the
questions....
>>>
>>> "....My software is for processing those images *after* downloading
them."
>>>
>> Touché.
>>
>>
>> poma
> I'll probably contact the author as well. It fine to only support
> processing after downloading, but it should still display the contents
> of the files so that you can decide what to download to process.
>
> regards,
> Steve
>
Great, never underestimate the social moment.
poma
I've checked Rawtherapee and Darktable for their functionality.
Rawtherapee appears to not support importing photos from any source that
is not mounted, whereas Darktable will import photos from any detected
device and displays the contents of the photos on the camera when
prompting for which photos should be imported from the camera, which
presumably means that Darktable is not using dcraw the access the
camera, it is doing it itself.
regards,
Steve
2:58 p.m.
On 27.10.2014 20:40, Stephen Morris wrote:
On 10/27/2014 12:13 PM, poma wrote:
> On 27.10.2014 00:53, Ed Greshko wrote:
>> On 10/27/14 07:48, poma wrote:
>>> You might try to contact the author
>>> http://www.cybercom.net/~dcoffin/dcraw/
>> The first few sentences on that site would seem to answer all the questions....
>>
>> "....My software is for processing those images *after* downloading
them."
>>
> Touché.
>
>
> poma
I'll probably contact the author as well. It fine to only support
processing after downloading, but it should still display the contents
of the files so that you can decide what to download to process.
regards,
Steve
Great, never underestimate the social moment.
poma
6:26 p.m.
On 26.10.2014 00:10, Stephen Morris wrote:
On 10/25/2014 12:14 PM, Ed Greshko wrote:
> On 10/25/14 07:31, Stephen Morris wrote:
>> DigiKam now seems be displaying the files on the camera now as well, whereas
yesterday it couldn't either, although digiKam doesn't understand the raw format
files that I am taking with the camera. I could use jpeg images but that is not as good
for image manipulation and corrections as raw is.
> You may be bumping up against an issue with DigiKam and image previews.
>
> I have this issue with a Cannon. When I hook up the camera a "preview"
window pops up the photos taken in RAW format do not display in the preview. However,
once they are downloaded and placed in the library they display and can be worked with
just fine. This is with LibRaw-0.15.4-1.fc20 installed.
>
When you say the photos don't display in the preview, do you mean it
doesn't see the files at all, or can't show the contents?
I assumed the reason it shows a default image for the files rather than
the contents was because the raw format on my Nikon is proprietary and
libraw hasn't been updated to support the format. The same issue was
present with the raw interface in Photoshop/Photoshop Elements, it had
to be updated to support the camera before it could manipulate the files
in the NEF format that the D3100 takes.
I've tried accessing the camera with GIMP, but it can't even see it. I
haven't tried RAWTHERAPEE or DARKTABLE yet, but I know those two can
process the NEF files when they are on a hard disk.
regards,
Steve
- LibRaw 0.11.2
http://www.libraw.org/node/416
New dcraw 9.05 imported, new cameras supported:
...
Nikon: D3100, D7000, P7000,
- LibRaw / Changelog.txt
https://github.com/LibRaw/LibRaw/blob/master/Changelog.txt#L738
...
* Imported 0.11(2) version changes:
+ dcraw 9.05 (1.439) imported, many new cameras supported:
...
Nikon: D3100, D7000, P7000,
- LibRaw 0.11.2 Released
2. Imported dcraw 9.05 (1.439), support for many cameras added:
...
Nikon: D3100, D7000, P7000
poma
6:53 p.m.
On 10/27/14 07:48, poma wrote:
You might try to contact the author
http://www.cybercom.net/~dcoffin/dcraw/
The first few sentences on that site would seem to answer all the questions....
"....My software is for processing those images *after* downloading them."
--
If you can't laugh at yourself, others will gladly oblige.
5:17 p.m.
On 10/26/14 06:10, Stephen Morris wrote:
On 10/25/2014 12:14 PM, Ed Greshko wrote:
> On 10/25/14 07:31, Stephen Morris wrote:
>> DigiKam now seems be displaying the files on the camera now as well, whereas
yesterday it couldn't either, although digiKam doesn't understand the raw format
files that I am taking with the camera. I could use jpeg images but that is not as good
for image manipulation and corrections as raw is.
> You may be bumping up against an issue with DigiKam and image previews.
>
> I have this issue with a Cannon. When I hook up the camera a "preview"
window pops up the photos taken in RAW format do not display in the preview. However,
once they are downloaded and placed in the library they display and can be worked with
just fine. This is with LibRaw-0.15.4-1.fc20 installed.
>
When you say the photos don't display in the preview, do you mean it doesn't see
the files at all, or can't show the contents?
It shows the existence of the files with a "default icon" but not the image
itself.
I assumed the reason it shows a default image for the files rather
than the contents was because the raw format on my Nikon is proprietary and libraw
hasn't been updated to support the format. The same issue was present with the raw
interface in Photoshop/Photoshop Elements, it had to be updated to support the camera
before it could manipulate the files in the NEF format that the D3100 takes.
In digikam, if you go to "Help--->Supported Raw Cameras" you'll see your
camera is listed.
I've tried accessing the camera with GIMP, but it can't even
see it. I haven't tried RAWTHERAPEE or DARKTABLE yet, but I know those two can process
the NEF files when they are on a hard disk.
And that appears to be the same for digikam. Once you move the files to the
system's disk you can view and work with them.
--
If you can't laugh at yourself, others will gladly oblige.
5:10 p.m.
On 10/25/2014 12:14 PM, Ed Greshko wrote:
On 10/25/14 07:31, Stephen Morris wrote:
> DigiKam now seems be displaying the files on the camera now as well, whereas
yesterday it couldn't either, although digiKam doesn't understand the raw format
files that I am taking with the camera. I could use jpeg images but that is not as good
for image manipulation and corrections as raw is.
You may be bumping up against an issue with DigiKam and image previews.
I have this issue with a Cannon. When I hook up the camera a "preview" window
pops up the photos taken in RAW format do not display in the preview. However, once they
are downloaded and placed in the library they display and can be worked with just fine.
This is with LibRaw-0.15.4-1.fc20 installed.
When you say the photos don't display in the preview, do you mean it
doesn't see the files at all, or can't show the contents?
I assumed the reason it shows a default image for the files rather than
the contents was because the raw format on my Nikon is proprietary and
libraw hasn't been updated to support the format. The same issue was
present with the raw interface in Photoshop/Photoshop Elements, it had
to be updated to support the camera before it could manipulate the files
in the NEF format that the D3100 takes.
I've tried accessing the camera with GIMP, but it can't even see it. I
haven't tried RAWTHERAPEE or DARKTABLE yet, but I know those two can
process the NEF files when they are on a hard disk.
regards,
Steve
6:48 p.m.
On 26.10.2014 23:11, Stephen Morris wrote:
On 10/26/2014 10:26 AM, poma wrote:
> On 26.10.2014 00:10, Stephen Morris wrote:
>> On 10/25/2014 12:14 PM, Ed Greshko wrote:
>>> On 10/25/14 07:31, Stephen Morris wrote:
>>>> DigiKam now seems be displaying the files on the camera now as well,
whereas yesterday it couldn't either, although digiKam doesn't understand the raw
format files that I am taking with the camera. I could use jpeg images but that is not as
good for image manipulation and corrections as raw is.
>>> You may be bumping up against an issue with DigiKam and image previews.
>>>
>>> I have this issue with a Cannon. When I hook up the camera a
"preview" window pops up the photos taken in RAW format do not display in the
preview. However, once they are downloaded and placed in the library they display and can
be worked with just fine. This is with LibRaw-0.15.4-1.fc20 installed.
>>>
>> When you say the photos don't display in the preview, do you mean it
>> doesn't see the files at all, or can't show the contents?
>> I assumed the reason it shows a default image for the files rather than
>> the contents was because the raw format on my Nikon is proprietary and
>> libraw hasn't been updated to support the format. The same issue was
>> present with the raw interface in Photoshop/Photoshop Elements, it had
>> to be updated to support the camera before it could manipulate the files
>> in the NEF format that the D3100 takes.
>> I've tried accessing the camera with GIMP, but it can't even see it. I
>> haven't tried RAWTHERAPEE or DARKTABLE yet, but I know those two can
>> process the NEF files when they are on a hard disk.
>>
>> regards,
>> Steve
>>
> - LibRaw 0.11.2
> http://www.libraw.org/node/416
> New dcraw 9.05 imported, new cameras supported:
> ...
> Nikon: D3100, D7000, P7000,
>
> - LibRaw / Changelog.txt
> https://github.com/LibRaw/LibRaw/blob/master/Changelog.txt#L738
> ...
> * Imported 0.11(2) version changes:
> + dcraw 9.05 (1.439) imported, many new cameras supported:
> ...
> Nikon: D3100, D7000, P7000,
>
> - LibRaw 0.11.2 Released
> 2. Imported dcraw 9.05 (1.439), support for many cameras added:
> ...
> Nikon: D3100, D7000, P7000
>
>
> poma
Looking at those links there isn't any detail on what support has been
provided. Given that digiKam and dolphin don't display the contents of
the images when they are on the camera but do when they are on the hard
disk, does that mean that support hasn't been properly implemented in
dcraw? I would have expected the support to provide the ability to
display the contents of the images in the camera when being previewed so
that one could make the decision about which images to move off the
camera sdcard.
regards,
Steve
You might try to contact the author
http://www.cybercom.net/~dcoffin/dcraw/
poma
5:11 p.m.
On 10/26/2014 10:26 AM, poma wrote:
On 26.10.2014 00:10, Stephen Morris wrote:
> On 10/25/2014 12:14 PM, Ed Greshko wrote:
>> On 10/25/14 07:31, Stephen Morris wrote:
>>> DigiKam now seems be displaying the files on the camera now as well, whereas
yesterday it couldn't either, although digiKam doesn't understand the raw format
files that I am taking with the camera. I could use jpeg images but that is not as good
for image manipulation and corrections as raw is.
>> You may be bumping up against an issue with DigiKam and image previews.
> >> I have this issue with a Cannon. When I hook up the
camera a "preview" window pops up the photos taken in RAW format do not display
in the preview. However, once they are downloaded and placed in the library they display
and can be worked with just fine. This is with LibRaw-0.15.4-1.fc20 installed.
> > When you say the photos don't display in the preview,
do you mean it
> doesn't see the files at all, or can't show the contents?
> I assumed the reason it shows a default image for the files rather than
> the contents was because the raw format on my Nikon is proprietary and
> libraw hasn't been updated to support the format. The same issue was
> present with the raw interface in Photoshop/Photoshop Elements, it had
> to be updated to support the camera before it could manipulate the files
> in the NEF format that the D3100 takes.
> I've tried accessing the camera with GIMP, but it can't even see it. I
> haven't tried RAWTHERAPEE or DARKTABLE yet, but I know those two can
> process the NEF files when they are on a hard disk.
> regards,
> Steve
- LibRaw 0.11.2
http://www.libraw.org/node/416
New dcraw 9.05 imported, new cameras supported:
...
Nikon: D3100, D7000, P7000,
- LibRaw / Changelog.txt
https://github.com/LibRaw/LibRaw/blob/master/Changelog.txt#L738
...
* Imported 0.11(2) version changes:
+ dcraw 9.05 (1.439) imported, many new cameras supported:
...
Nikon: D3100, D7000, P7000,
- LibRaw 0.11.2 Released
2. Imported dcraw 9.05 (1.439), support for many cameras added:
...
Nikon: D3100, D7000, P7000
poma
Looking at those links there isn't any detail on what support has been
provided. Given that digiKam and dolphin don't display the contents of
the images when they are on the camera but do when they are on the hard
disk, does that mean that support hasn't been properly implemented in
dcraw? I would have expected the support to provide the ability to
display the contents of the images in the camera when being previewed so
that one could make the decision about which images to move off the
camera sdcard.
regards,
Steve
5:04 p.m.
On 10/26/2014 09:17 AM, Ed Greshko wrote:
On 10/26/14 06:10, Stephen Morris wrote:
> On 10/25/2014 12:14 PM, Ed Greshko wrote:
>> On 10/25/14 07:31, Stephen Morris wrote:
>>> DigiKam now seems be displaying the files on the camera now as well, whereas
yesterday it couldn't either, although digiKam doesn't understand the raw format
files that I am taking with the camera. I could use jpeg images but that is not as good
for image manipulation and corrections as raw is.
>> You may be bumping up against an issue with DigiKam and image previews.
>>
>> I have this issue with a Cannon. When I hook up the camera a "preview"
window pops up the photos taken in RAW format do not display in the preview. However,
once they are downloaded and placed in the library they display and can be worked with
just fine. This is with LibRaw-0.15.4-1.fc20 installed.
>>
> When you say the photos don't display in the preview, do you mean it doesn't
see the files at all, or can't show the contents?
It shows the existence of the files with a "default icon" but not the image
itself.
> I assumed the reason it shows a default image for the files rather than the contents
was because the raw format on my Nikon is proprietary and libraw hasn't been updated
to support the format. The same issue was present with the raw interface in
Photoshop/Photoshop Elements, it had to be updated to support the camera before it could
manipulate the files in the NEF format that the D3100 takes.
In digikam, if you go to "Help--->Supported Raw Cameras" you'll see
your camera is listed.
> I've tried accessing the camera with GIMP, but it can't even see it. I
haven't tried RAWTHERAPEE or DARKTABLE yet, but I know those two can process the NEF
files when they are on a hard disk.
>
And that appears to be the same for digikam. Once you move the files to the system's
disk you can view and work with them.
This might be because the camera is being
accessed in PTP mode. I
thought I saw in one of the links that Poma supplied that PTP access
doesn't allow the contents of the images to be modified.
regards,
Steve
8:14 p.m.
On 10/25/14 07:31, Stephen Morris wrote:
DigiKam now seems be displaying the files on the camera now as well,
whereas yesterday it couldn't either, although digiKam doesn't understand the raw
format files that I am taking with the camera. I could use jpeg images but that is not as
good for image manipulation and corrections as raw is.
You may be bumping up against an issue with DigiKam and image previews.
I have this issue with a Cannon. When I hook up the camera a "preview" window
pops up the photos taken in RAW format do not display in the preview. However, once they
are downloaded and placed in the library they display and can be worked with just fine.
This is with LibRaw-0.15.4-1.fc20 installed.
--
If you can't laugh at yourself, others will gladly oblige.
6:33 p.m.
On 25.10.2014 00:24, Cameron Simpson wrote:
On 24Oct2014 16:09, poma <pomidorabelisima(a)gmail.com> wrote:
> On 24.10.2014 07:50, Stephen Morris wrote:
>> I have plugged a digital camera into my usb port and mounted it using
>> the popup displayed from the auto detect via konqueror (this annoys me
>> as well). When konqueror is launched it displays the contents via
>> Camera:/ which is okay, but subsequently I can't find any entries under
>> /run that represent the camera. I assumed there would be a mount point
>> under /run like there is for a usb flash disk. Given that there appears
>> to not be a mount point under /run, where is it mounted in Fedora 20, so
>> that I can point dolphin (which is what should be launched from the
>> 'Open with File Manager' prompt, not Konqueror) at the mount point
>> rather than having to manually type Camera:/ into the address bar.
>
> ptp != usb_storage
>
> http://en.wikipedia.org/wiki/Picture_Transfer_Protocol
> http://www.gphoto.org/proj/libgphoto2/
>
> modinfo -d usb_storage
> USB Mass Storage driver for Linux
>
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/dri...
Oh, and in terms of diagnostics. Instead of poking around where you think the
mount point should be, just run "mount". If it is not listed anywhere,
there's
no mount point.
Reading what is on those links will give you an answer.
BTW, a digicam vendor, the full name of the product model are?
The link to the full specs?
poma
5:24 p.m.
On 24Oct2014 16:09, poma <pomidorabelisima(a)gmail.com> wrote:
On 24.10.2014 07:50, Stephen Morris wrote:
> I have plugged a digital camera into my usb port and mounted it using
> the popup displayed from the auto detect via konqueror (this annoys me
> as well). When konqueror is launched it displays the contents via
> Camera:/ which is okay, but subsequently I can't find any entries under
> /run that represent the camera. I assumed there would be a mount point
> under /run like there is for a usb flash disk. Given that there appears
> to not be a mount point under /run, where is it mounted in Fedora 20, so
> that I can point dolphin (which is what should be launched from the
> 'Open with File Manager' prompt, not Konqueror) at the mount point
> rather than having to manually type Camera:/ into the address bar.
ptp != usb_storage
http://en.wikipedia.org/wiki/Picture_Transfer_Protocol
http://www.gphoto.org/proj/libgphoto2/
modinfo -d usb_storage
USB Mass Storage driver for Linux
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/dri...
Oh, and in terms of diagnostics. Instead of poking around where you think the
mount point should be, just run "mount". If it is not listed anywhere,
there's
no mount point.
Cheers,
Cameron Simpson <cs(a)zip.com.au>
The mark must be robust enough to survive MP3 transmission over the Internet,
but remain inaudible when played on the yet to be launched DVD-Audio players.
- the SDMI audio watermarkers literally ask for the impossible, since all
audio compressors aim to pass _only_ human perceptible data
http://www.newscientist.com/news/news.jsp?id=ns224836
9:09 a.m.
On 24.10.2014 07:50, Stephen Morris wrote:
I have plugged a digital camera into my usb port and mounted it using
the popup displayed from the auto detect via konqueror (this annoys me
as well). When konqueror is launched it displays the contents via
Camera:/ which is okay, but subsequently I can't find any entries under
/run that represent the camera. I assumed there would be a mount point
under /run like there is for a usb flash disk. Given that there appears
to not be a mount point under /run, where is it mounted in Fedora 20, so
that I can point dolphin (which is what should be launched from the
'Open with File Manager' prompt, not Konqueror) at the mount point
rather than having to manually type Camera:/ into the address bar.
ptp != usb_storage
http://en.wikipedia.org/wiki/Picture_Transfer_Protocol
http://www.gphoto.org/proj/libgphoto2/
modinfo -d usb_storage
USB Mass Storage driver for Linux
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/dri...
poma
9:31 p.m.
On 25.10.2014 03:19, poma wrote:
On 25.10.2014 02:09, poma wrote:
> On 25.10.2014 01:31, Stephen Morris wrote:
>> On 10/25/2014 01:09 AM, poma wrote:
>>> On 24.10.2014 07:50, Stephen Morris wrote:
>>>> I have plugged a digital camera into my usb port and mounted it using
>>>> the popup displayed from the auto detect via konqueror (this annoys me
>>>> as well). When konqueror is launched it displays the contents via
>>>> Camera:/ which is okay, but subsequently I can't find any entries
under
>>>> /run that represent the camera. I assumed there would be a mount point
>>>> under /run like there is for a usb flash disk. Given that there appears
>>>> to not be a mount point under /run, where is it mounted in Fedora 20, so
>>>> that I can point dolphin (which is what should be launched from the
>>>> 'Open with File Manager' prompt, not Konqueror) at the mount
point
>>>> rather than having to manually type Camera:/ into the address bar.
>>> ptp != usb_storage
>>>
>>> http://en.wikipedia.org/wiki/Picture_Transfer_Protocol
>>> http://www.gphoto.org/proj/libgphoto2/
>>>
>>> modinfo -d usb_storage
>>> USB Mass Storage driver for Linux
>>>
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/dri...
>>>
>>>
>>> poma
>>>
>> Thankyou for the links. I looked at those links which gave me a lot more
>> information that I didn't know about. Unfortunately the documentation on
>> libphoto2 seems to potentially be self conflicting. The list of cameras
>> that libphoto2 supports seems to have my Nikon D3100 listed, but the
>> list of cameras and how they are supported under Unix does not appear to
>> list my camera.
>> Following Cameron's email I checked the mount list which seems to
>> indicate there is no mount point, which also coincides with the
>> available device interface in the system tray not being able to unmount
>> the camera before disconnection.
>> Also now that I have changed to application preference order in the
>> properties of the folder displayed by dolphin, whenever I select 'Open
>> with File Manager' at device detection time the process correctly
>> launched dolphin to display the contents, whereas yesterday when
>> konqueror was the default application, manually pointing dolphin at
>> Camera:/ would not display the contents of the camera because dolphin
>> was trying to treat the camera as a usb device and couldn't acquire the
>> usb. The only issue with dolphin is it doesn't display the folder name
>> where the images are stored on the camera as the same name that the
>> camera says it is, dolphin seems to be putting its own prefix on the
>> folder name.
>> Also dolphin seems to be starting at a higher point in the directory
>> tree for its displays than where Windows starts.
>> DigiKam now seems be displaying the files on the camera now as well,
>> whereas yesterday it couldn't either, although digiKam doesn't
>> understand the raw format files that I am taking with the camera. I
>> could use jpeg images but that is not as good for image manipulation and
>> corrections as raw is. I can process these files using the raw interface
>> to Photoshop Elements and Elements itself, albeit under windows, so not
>> being able to access these under Linux is not that big a deal to me,
>> other than the fact that I have to use Windows.
>>
>> regards,
>> Steve
>>
>
> Does the Nikon D3100 supports USB mass storage mode?
> http://goo.gl/7bGFuh
>
In this respect manual(D3100_EN.pdf) is questionable
http://www.nikonusa.com/en/Nikon-Products/Product/dslr-cameras/D3100.html...
Therefore you can try this *if* the device supports both - PictBridge(PTP) & USB
storage, and they collide:
/etc/modprobe.d/usb_storage-quirks-Nikon_D3100.conf
# Nikon D3100
#
# lsusb
# ID 04b0:0130 Nikon Corp. Coolpix 4600 (ptp)
# ID 04b0:0427 Nikon Corp.
# modinfo -p usb_storage
# ...
# quirks:supplemental list of device IDs and their quirks (string)
#
# 1.
options usb_storage quirks=04b0:0130:i
#
# 2.
# options usb_storage quirks=04b0:0427:i
#
# 3.
# options usb_storage quirks=04b0:0130:i,04b0:0427:i
#
# *uncomment* only *one* of the three *options* that you'll *use* as the first case!
Ref.
- https://www.kernel.org/doc/Documentation/kernel-parameters.txt
..
usb-storage.quirks=
[UMS] A list of quirks entries to supplement or
override the built-in unusual_devs list. List
entries are separated by commas. Each entry has
the form VID:PID:Flags where VID and PID are Vendor
and Product ID values (4-digit hex numbers) and
Flags is a set of characters, each corresponding
to a common usb-storage quirk flag as follows:
...
i = IGNORE_DEVICE (don't bind to this
device);
...
Example: quirks=0419:aaf5:rl,0421:0433:rc
- https://www.kernel.org/doc/Documentation/usb/hotplug.txt
- USB: add Nikon D300 camera to unusual_devs
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/d...
BTW
- Nikon D3100 specifications
http://www.dpreview.com/reviews/nikond3100/page2.asp
...
Connectivity • USB 2.0 (Hi-Speed)
• Mass storage / PTP selectable
- Digikam support Nikon D3100
http://thread.gmane.org/gmane.comp.kde.digikam.user/14517
Xfce
- USB storage
$ thunar /run/media/user/</dev/disk/by-uuid/>/
- MTP (Media Transfer Protocol)
$ thunar mtp://[usb:<bus>,<devnum>]/
- PTP (Picture Transfer Protocol)
$ thunar gphoto2://[usb:<bus>,<devnum>]/
Good luck with reading and playing with the device. :)
poma
Ref.
Mailing list
https://www.digikam.org/contact?q=support#mailinglists
1:58 p.m.
On 10/31/2014 11:47 AM, poma wrote:
On 30.10.2014 21:58, Stephen Morris wrote:
> On 10/29/2014 01:15 PM, poma wrote:
>> On 28.10.2014 21:27, Stephen Morris wrote:
>>> On 10/28/2014 06:58 AM, poma wrote:
>>>> On 27.10.2014 20:40, Stephen Morris wrote:
>>>>> On 10/27/2014 12:13 PM, poma wrote:
>>>>>> On 27.10.2014 00:53, Ed Greshko wrote:
>>>>>>> On 10/27/14 07:48, poma wrote:
>>>>>>>> You might try to contact the author
>>>>>>>> http://www.cybercom.net/~dcoffin/dcraw/
>>>>>>> The first few sentences on that site would seem to answer all
the questions....
>>>>>>>
>>>>>>> "....My software is for processing those images *after*
downloading them."
>>>>>>>
>>>>>> Touché.
>>>>>>
>>>>>>
>>>>>> poma
>>>>> I'll probably contact the author as well. It fine to only
support
>>>>> processing after downloading, but it should still display the
contents
>>>>> of the files so that you can decide what to download to process.
>>>>>
>>>>> regards,
>>>>> Steve
>>>>>
>>>> Great, never underestimate the social moment.
>>>>
>>>>
>>>> poma
>>>>
>>> I've checked Rawtherapee and Darktable for their functionality.
>>> Rawtherapee appears to not support importing photos from any source that
>>> is not mounted, whereas Darktable will import photos from any detected
>>> device and displays the contents of the photos on the camera when
>>> prompting for which photos should be imported from the camera, which
>>> presumably means that Darktable is not using dcraw the access the
>>> camera, it is doing it itself.
>>>
>>
http://www.darktable.org/2012/10/whats-involved-with-adding-support-for-n...
>> RAW format support
>> darktable uses two libraries to read RAW files. Most common RAW formats are
read via the RawSpeed library (by Klaus Post), more esoteric RAW formats not supported by
RawSpeed are read via LibRaw (which in turn is based on Dave Coffin's dcraw).
> I've looked at the cameras.xml file linked to in the above web page and
> it lists the D3100 which I assume means RawSpeed has support for my
> camera, which would explain why Rawtable provides an on camera image
> preview when importing the files.
>> BTW did you check with the Rawstudio
>> http://rawstudio.org
> I haven't looked at this application as yet, mainly because until now I
> didn't know it existed.
>> Perhaps the only real issue with the Nikon D3100 is the lack of USB Mass Storage
mode.
> Its not so much the lack of a USB Mass storage mode, its the lack of the
> ability to preview the contents of the images on camera when I want to
> copy the files to my network storage for processing in Photoshop
> Elements, and, with some of them to produce a photo print. I only want
> to copy the files I am going to keep, so I want the ability to view the
> images, delete the ones I don't want to keep, then mass extract the
> remaining files to my NAS. Hence for me the ability to mass preview the
> images on camera is paramount, and any application that is used to
> process the files needs to have the ability to do some rudimentary
> correction to the raw file and save those corrections in a separate
> "correction" file (the way the raw interface in the Photoshop
> applications do) so that the actual raw file is left unchanged, so that
> at the "corrections" file can be deleted at any time to back out the
> changes without impacting the original raw file.
>
> regards,
> Steve
>
In your case is just perhaps crucial.
Shall we start a thread again? :)
ptp != usb_storage
It probably should be, we have probably moved away from the original
reason for raising this thread.
I think what this has moved to is that it seems that under Linux there
seems to be a requirement to take digital photos in Raw+JPG mode in
order for processes to be able to do what I want.
regards,
Steve
poma
3:58 p.m.
On 10/29/2014 01:15 PM, poma wrote:
On 28.10.2014 21:27, Stephen Morris wrote:
> On 10/28/2014 06:58 AM, poma wrote:
>> On 27.10.2014 20:40, Stephen Morris wrote:
>>> On 10/27/2014 12:13 PM, poma wrote:
>>>> On 27.10.2014 00:53, Ed Greshko wrote:
>>>>> On 10/27/14 07:48, poma wrote:
>>>>>> You might try to contact the author
>>>>>> http://www.cybercom.net/~dcoffin/dcraw/
>>>>> The first few sentences on that site would seem to answer all the
questions....
>>>>>
>>>>> "....My software is for processing those images *after*
downloading them."
>>>>>
>>>> Touché.
>>>>
>>>>
>>>> poma
>>> I'll probably contact the author as well. It fine to only support
>>> processing after downloading, but it should still display the contents
>>> of the files so that you can decide what to download to process.
>>>
>>> regards,
>>> Steve
>>>
>> Great, never underestimate the social moment.
>>
>>
>> poma
>>
> I've checked Rawtherapee and Darktable for their functionality.
> Rawtherapee appears to not support importing photos from any source that
> is not mounted, whereas Darktable will import photos from any detected
> device and displays the contents of the photos on the camera when
> prompting for which photos should be imported from the camera, which
> presumably means that Darktable is not using dcraw the access the
> camera, it is doing it itself.
>
http://www.darktable.org/2012/10/whats-involved-with-adding-support-for-n...
RAW format support
darktable uses two libraries to read RAW files. Most common RAW formats are read via
the RawSpeed library (by Klaus Post), more esoteric RAW formats not supported by RawSpeed
are read via LibRaw (which in turn is based on Dave Coffin's dcraw).
I've looked at the cameras.xml file linked to in the above web page and
it lists the D3100 which I assume means RawSpeed has support for my
camera, which would explain why Rawtable provides an on camera image
preview when importing the files.
BTW did you check with the Rawstudio
http://rawstudio.org
I haven't looked at this application as yet, mainly because until now I
didn't know it existed.
Perhaps the only real issue with the Nikon D3100 is the lack of USB Mass Storage mode.
Its not so much the lack of a USB Mass storage mode, its the lack of the
ability to preview the contents of the images on camera when I want to
copy the files to my network storage for processing in Photoshop
Elements, and, with some of them to produce a photo print. I only want
to copy the files I am going to keep, so I want the ability to view the
images, delete the ones I don't want to keep, then mass extract the
remaining files to my NAS. Hence for me the ability to mass preview the
images on camera is paramount, and any application that is used to
process the files needs to have the ability to do some rudimentary
correction to the raw file and save those corrections in a separate
"correction" file (the way the raw interface in the Photoshop
applications do) so that the actual raw file is left unchanged, so that
at the "corrections" file can be deleted at any time to back out the
changes without impacting the original raw file.
regards,
Steve
6:20 p.m.
On 26.10.2014 00:01, Stephen Morris wrote:
On 10/25/2014 01:31 PM, poma wrote:
> On 25.10.2014 03:19, poma wrote:
>> On 25.10.2014 02:09, poma wrote:
>>> On 25.10.2014 01:31, Stephen Morris wrote:
>>>> On 10/25/2014 01:09 AM, poma wrote:
>>>>> On 24.10.2014 07:50, Stephen Morris wrote:
>>>>>> I have plugged a digital camera into my usb port and mounted it
using
>>>>>> the popup displayed from the auto detect via konqueror (this
annoys me
>>>>>> as well). When konqueror is launched it displays the contents
via
>>>>>> Camera:/ which is okay, but subsequently I can't find any
entries under
>>>>>> /run that represent the camera. I assumed there would be a mount
point
>>>>>> under /run like there is for a usb flash disk. Given that there
appears
>>>>>> to not be a mount point under /run, where is it mounted in Fedora
20, so
>>>>>> that I can point dolphin (which is what should be launched from
the
>>>>>> 'Open with File Manager' prompt, not Konqueror) at the
mount point
>>>>>> rather than having to manually type Camera:/ into the address
bar.
>>>>> ptp != usb_storage
>>>>>
>>>>> http://en.wikipedia.org/wiki/Picture_Transfer_Protocol
>>>>> http://www.gphoto.org/proj/libgphoto2/
>>>>>
>>>>> modinfo -d usb_storage
>>>>> USB Mass Storage driver for Linux
>>>>>
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/dri...
>>>>>
>>>>>
>>>>> poma
>>>>>
>>>> Thankyou for the links. I looked at those links which gave me a lot more
>>>> information that I didn't know about. Unfortunately the documentation
on
>>>> libphoto2 seems to potentially be self conflicting. The list of cameras
>>>> that libphoto2 supports seems to have my Nikon D3100 listed, but the
>>>> list of cameras and how they are supported under Unix does not appear to
>>>> list my camera.
>>>> Following Cameron's email I checked the mount list which seems to
>>>> indicate there is no mount point, which also coincides with the
>>>> available device interface in the system tray not being able to unmount
>>>> the camera before disconnection.
>>>> Also now that I have changed to application preference order in the
>>>> properties of the folder displayed by dolphin, whenever I select
'Open
>>>> with File Manager' at device detection time the process correctly
>>>> launched dolphin to display the contents, whereas yesterday when
>>>> konqueror was the default application, manually pointing dolphin at
>>>> Camera:/ would not display the contents of the camera because dolphin
>>>> was trying to treat the camera as a usb device and couldn't acquire
the
>>>> usb. The only issue with dolphin is it doesn't display the folder
name
>>>> where the images are stored on the camera as the same name that the
>>>> camera says it is, dolphin seems to be putting its own prefix on the
>>>> folder name.
>>>> Also dolphin seems to be starting at a higher point in the directory
>>>> tree for its displays than where Windows starts.
>>>> DigiKam now seems be displaying the files on the camera now as well,
>>>> whereas yesterday it couldn't either, although digiKam doesn't
>>>> understand the raw format files that I am taking with the camera. I
>>>> could use jpeg images but that is not as good for image manipulation and
>>>> corrections as raw is. I can process these files using the raw interface
>>>> to Photoshop Elements and Elements itself, albeit under windows, so not
>>>> being able to access these under Linux is not that big a deal to me,
>>>> other than the fact that I have to use Windows.
>>>>
>>>> regards,
>>>> Steve
>>>>
>>> Does the Nikon D3100 supports USB mass storage mode?
>>> http://goo.gl/7bGFuh
>>>
>>
>> In this respect manual(D3100_EN.pdf) is questionable
>>
http://www.nikonusa.com/en/Nikon-Products/Product/dslr-cameras/D3100.html...
>>
>> Therefore you can try this *if* the device supports both - PictBridge(PTP) &
USB storage, and they collide:
>>
>> /etc/modprobe.d/usb_storage-quirks-Nikon_D3100.conf
>> # Nikon D3100
>> #
>> # lsusb
>> # ID 04b0:0130 Nikon Corp. Coolpix 4600 (ptp)
>> # ID 04b0:0427 Nikon Corp.
>> # modinfo -p usb_storage
>> # ...
>> # quirks:supplemental list of device IDs and their quirks (string)
>> #
>> # 1.
>> options usb_storage quirks=04b0:0130:i
>> #
>> # 2.
>> # options usb_storage quirks=04b0:0427:i
>> #
>> # 3.
>> # options usb_storage quirks=04b0:0130:i,04b0:0427:i
>> #
>> # *uncomment* only *one* of the three *options* that you'll *use* as the
first case!
>>
>>
>> Ref.
>> - https://www.kernel.org/doc/Documentation/kernel-parameters.txt
>> ..
>> usb-storage.quirks=
>> [UMS] A list of quirks entries to supplement or
>> override the built-in unusual_devs list. List
>> entries are separated by commas. Each entry has
>> the form VID:PID:Flags where VID and PID are Vendor
>> and Product ID values (4-digit hex numbers) and
>> Flags is a set of characters, each corresponding
>> to a common usb-storage quirk flag as follows:
>> ...
>> i = IGNORE_DEVICE (don't bind to this
>> device);
>> ...
>> Example: quirks=0419:aaf5:rl,0421:0433:rc
>>
>> - https://www.kernel.org/doc/Documentation/usb/hotplug.txt
>>
>> - USB: add Nikon D300 camera to unusual_devs
>>
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/d...
>>
>>
> BTW
> - Nikon D3100 specifications
> http://www.dpreview.com/reviews/nikond3100/page2.asp
> ...
> Connectivity • USB 2.0 (Hi-Speed)
> • Mass storage / PTP selectable
>
> - Digikam support Nikon D3100
> http://thread.gmane.org/gmane.comp.kde.digikam.user/14517
>
> Xfce
> - USB storage
> $ thunar /run/media/user/</dev/disk/by-uuid/>/
>
> - MTP (Media Transfer Protocol)
> $ thunar mtp://[usb:<bus>,<devnum>]/
>
> - PTP (Picture Transfer Protocol)
> $ thunar gphoto2://[usb:<bus>,<devnum>]/
>
>
>
> Good luck with reading and playing with the device. :)
>
>
> poma
>
>
> Ref.
> Mailing list
> https://www.digikam.org/contact?q=support#mailinglists
Thanks for all the info Poma, there is some very useful information in
those links. Even though the links say the camera is switchable between
the 2 modes I'm not sure whether it is manually switchable. The manual
and camera itself don't have any details on how to do it. It seems as
though it may be automatically switchable depending on the access
mechanism. Under linux it seems to be accessed via PTP but under Windows
(I'll need to double check this) it seems to be accessed in USB Mass
Storage mode as it seems to be mounted as a USB device. I was able to
remove files from the SD card on the camera using dolphin and digiKam
was able to access the files directly by auto navigating down to the
appropriate directory, but GIMP was unable to touch the camera at all.
regards,
Steve
Yeah this is one possibility, to change the operating modes via apps, like the mechanism
used by USB_ModeSwitch.
USB_ModeSwitch - Handling Mode-Switching USB Devices on Linux
Introduction
http://www.draisberghof.de/usb_modeswitch/#intro
poma
8:13 p.m.
On 27.10.2014 00:53, Ed Greshko wrote:
On 10/27/14 07:48, poma wrote:
> You might try to contact the author
> http://www.cybercom.net/~dcoffin/dcraw/
The first few sentences on that site would seem to answer all the questions....
"....My software is for processing those images *after* downloading them."
Touché.
poma
2:40 p.m.
On 10/27/2014 12:13 PM, poma wrote:
On 27.10.2014 00:53, Ed Greshko wrote:
> On 10/27/14 07:48, poma wrote:
>> You might try to contact the author
>> http://www.cybercom.net/~dcoffin/dcraw/
> The first few sentences on that site would seem to answer all the questions....
> "....My software is for processing those images
*after* downloading them."
Touché.
poma
I'll probably contact the author as well. It fine to only support
processing after downloading, but it should still display the contents
of the files so that you can decide what to download to process.
regards,
Steve
8:19 p.m.
On 25.10.2014 02:09, poma wrote:
On 25.10.2014 01:31, Stephen Morris wrote:
> On 10/25/2014 01:09 AM, poma wrote:
>> On 24.10.2014 07:50, Stephen Morris wrote:
>>> I have plugged a digital camera into my usb port and mounted it using
>>> the popup displayed from the auto detect via konqueror (this annoys me
>>> as well). When konqueror is launched it displays the contents via
>>> Camera:/ which is okay, but subsequently I can't find any entries under
>>> /run that represent the camera. I assumed there would be a mount point
>>> under /run like there is for a usb flash disk. Given that there appears
>>> to not be a mount point under /run, where is it mounted in Fedora 20, so
>>> that I can point dolphin (which is what should be launched from the
>>> 'Open with File Manager' prompt, not Konqueror) at the mount point
>>> rather than having to manually type Camera:/ into the address bar.
>> ptp != usb_storage
>>
>> http://en.wikipedia.org/wiki/Picture_Transfer_Protocol
>> http://www.gphoto.org/proj/libgphoto2/
>>
>> modinfo -d usb_storage
>> USB Mass Storage driver for Linux
>>
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/dri...
>>
>>
>> poma
>>
> Thankyou for the links. I looked at those links which gave me a lot more
> information that I didn't know about. Unfortunately the documentation on
> libphoto2 seems to potentially be self conflicting. The list of cameras
> that libphoto2 supports seems to have my Nikon D3100 listed, but the
> list of cameras and how they are supported under Unix does not appear to
> list my camera.
> Following Cameron's email I checked the mount list which seems to
> indicate there is no mount point, which also coincides with the
> available device interface in the system tray not being able to unmount
> the camera before disconnection.
> Also now that I have changed to application preference order in the
> properties of the folder displayed by dolphin, whenever I select 'Open
> with File Manager' at device detection time the process correctly
> launched dolphin to display the contents, whereas yesterday when
> konqueror was the default application, manually pointing dolphin at
> Camera:/ would not display the contents of the camera because dolphin
> was trying to treat the camera as a usb device and couldn't acquire the
> usb. The only issue with dolphin is it doesn't display the folder name
> where the images are stored on the camera as the same name that the
> camera says it is, dolphin seems to be putting its own prefix on the
> folder name.
> Also dolphin seems to be starting at a higher point in the directory
> tree for its displays than where Windows starts.
> DigiKam now seems be displaying the files on the camera now as well,
> whereas yesterday it couldn't either, although digiKam doesn't
> understand the raw format files that I am taking with the camera. I
> could use jpeg images but that is not as good for image manipulation and
> corrections as raw is. I can process these files using the raw interface
> to Photoshop Elements and Elements itself, albeit under windows, so not
> being able to access these under Linux is not that big a deal to me,
> other than the fact that I have to use Windows.
>
> regards,
> Steve
>
Does the Nikon D3100 supports USB mass storage mode?
http://goo.gl/7bGFuh
In this respect manual(D3100_EN.pdf) is questionable
http://www.nikonusa.com/en/Nikon-Products/Product/dslr-cameras/D3100.html...
Therefore you can try this *if* the device supports both - PictBridge(PTP) & USB
storage, and they collide:
/etc/modprobe.d/usb_storage-quirks-Nikon_D3100.conf
# Nikon D3100
#
# lsusb
# ID 04b0:0130 Nikon Corp. Coolpix 4600 (ptp)
# ID 04b0:0427 Nikon Corp.
# modinfo -p usb_storage
# ...
# quirks:supplemental list of device IDs and their quirks (string)
#
# 1.
options usb_storage quirks=04b0:0130:i
#
# 2.
# options usb_storage quirks=04b0:0427:i
#
# 3.
# options usb_storage quirks=04b0:0130:i,04b0:0427:i
#
# *uncomment* only *one* of the three *options* that you'll *use* as the first case!
Ref.
- https://www.kernel.org/doc/Documentation/kernel-parameters.txt
..
usb-storage.quirks=
[UMS] A list of quirks entries to supplement or
override the built-in unusual_devs list. List
entries are separated by commas. Each entry has
the form VID:PID:Flags where VID and PID are Vendor
and Product ID values (4-digit hex numbers) and
Flags is a set of characters, each corresponding
to a common usb-storage quirk flag as follows:
...
i = IGNORE_DEVICE (don't bind to this
device);
...
Example: quirks=0419:aaf5:rl,0421:0433:rc
- https://www.kernel.org/doc/Documentation/usb/hotplug.txt
- USB: add Nikon D300 camera to unusual_devs
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/d...
poma
7:09 p.m.
On 25.10.2014 01:31, Stephen Morris wrote:
On 10/25/2014 01:09 AM, poma wrote:
> On 24.10.2014 07:50, Stephen Morris wrote:
>> I have plugged a digital camera into my usb port and mounted it using
>> the popup displayed from the auto detect via konqueror (this annoys me
>> as well). When konqueror is launched it displays the contents via
>> Camera:/ which is okay, but subsequently I can't find any entries under
>> /run that represent the camera. I assumed there would be a mount point
>> under /run like there is for a usb flash disk. Given that there appears
>> to not be a mount point under /run, where is it mounted in Fedora 20, so
>> that I can point dolphin (which is what should be launched from the
>> 'Open with File Manager' prompt, not Konqueror) at the mount point
>> rather than having to manually type Camera:/ into the address bar.
> ptp != usb_storage
>
> http://en.wikipedia.org/wiki/Picture_Transfer_Protocol
> http://www.gphoto.org/proj/libgphoto2/
>
> modinfo -d usb_storage
> USB Mass Storage driver for Linux
>
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/dri...
>
>
> poma
>
Thankyou for the links. I looked at those links which gave me a lot more
information that I didn't know about. Unfortunately the documentation on
libphoto2 seems to potentially be self conflicting. The list of cameras
that libphoto2 supports seems to have my Nikon D3100 listed, but the
list of cameras and how they are supported under Unix does not appear to
list my camera.
Following Cameron's email I checked the mount list which seems to
indicate there is no mount point, which also coincides with the
available device interface in the system tray not being able to unmount
the camera before disconnection.
Also now that I have changed to application preference order in the
properties of the folder displayed by dolphin, whenever I select 'Open
with File Manager' at device detection time the process correctly
launched dolphin to display the contents, whereas yesterday when
konqueror was the default application, manually pointing dolphin at
Camera:/ would not display the contents of the camera because dolphin
was trying to treat the camera as a usb device and couldn't acquire the
usb. The only issue with dolphin is it doesn't display the folder name
where the images are stored on the camera as the same name that the
camera says it is, dolphin seems to be putting its own prefix on the
folder name.
Also dolphin seems to be starting at a higher point in the directory
tree for its displays than where Windows starts.
DigiKam now seems be displaying the files on the camera now as well,
whereas yesterday it couldn't either, although digiKam doesn't
understand the raw format files that I am taking with the camera. I
could use jpeg images but that is not as good for image manipulation and
corrections as raw is. I can process these files using the raw interface
to Photoshop Elements and Elements itself, albeit under windows, so not
being able to access these under Linux is not that big a deal to me,
other than the fact that I have to use Windows.
regards,
Steve
Does the Nikon D3100 supports USB mass storage mode?
http://goo.gl/7bGFuh
poma
6:31 p.m.
On 10/25/2014 01:09 AM, poma wrote:
On 24.10.2014 07:50, Stephen Morris wrote:
> I have plugged a digital camera into my usb port and mounted it using
> the popup displayed from the auto detect via konqueror (this annoys me
> as well). When konqueror is launched it displays the contents via
> Camera:/ which is okay, but subsequently I can't find any entries under
> /run that represent the camera. I assumed there would be a mount point
> under /run like there is for a usb flash disk. Given that there appears
> to not be a mount point under /run, where is it mounted in Fedora 20, so
> that I can point dolphin (which is what should be launched from the
> 'Open with File Manager' prompt, not Konqueror) at the mount point
> rather than having to manually type Camera:/ into the address bar.
ptp != usb_storage
http://en.wikipedia.org/wiki/Picture_Transfer_Protocol
http://www.gphoto.org/proj/libgphoto2/
modinfo -d usb_storage
USB Mass Storage driver for Linux
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/dri...
poma
Thankyou for the links. I looked at those links which gave me a lot more
information that I didn't know about. Unfortunately the documentation on
libphoto2 seems to potentially be self conflicting. The list of cameras
that libphoto2 supports seems to have my Nikon D3100 listed, but the
list of cameras and how they are supported under Unix does not appear to
list my camera.
Following Cameron's email I checked the mount list which seems to
indicate there is no mount point, which also coincides with the
available device interface in the system tray not being able to unmount
the camera before disconnection.
Also now that I have changed to application preference order in the
properties of the folder displayed by dolphin, whenever I select 'Open
with File Manager' at device detection time the process correctly
launched dolphin to display the contents, whereas yesterday when
konqueror was the default application, manually pointing dolphin at
Camera:/ would not display the contents of the camera because dolphin
was trying to treat the camera as a usb device and couldn't acquire the
usb. The only issue with dolphin is it doesn't display the folder name
where the images are stored on the camera as the same name that the
camera says it is, dolphin seems to be putting its own prefix on the
folder name.
Also dolphin seems to be starting at a higher point in the directory
tree for its displays than where Windows starts.
DigiKam now seems be displaying the files on the camera now as well,
whereas yesterday it couldn't either, although digiKam doesn't
understand the raw format files that I am taking with the camera. I
could use jpeg images but that is not as good for image manipulation and
corrections as raw is. I can process these files using the raw interface
to Photoshop Elements and Elements itself, albeit under windows, so not
being able to access these under Linux is not that big a deal to me,
other than the fact that I have to use Windows.
regards,
Steve
3461
days inactive
3470
days old
26 comments
4 participants
participants (4)
-
Cameron Simpson -
Ed Greshko -
poma -
Stephen Morris