Network Servers and 4.6
Has anyone else had problems accessing files on a network server since moving from an early version of V4?
I had been running 4.0 for a while and accessing my archive of raw files across the network. Works fine but obviously not as fast as a local drive. I changed to 4.6 today and all my raw files are tagged with the view-only icon. I can preview them, see all my crops and tuning, but cant process them or adjust the tunings.
This happened to once before with a version of 3.7 but went away with an upgrade.
Am running a linux server with samba to deliver the files across a PC network. Nothing fancy. I tested dragging a folder off the network drive and onto a local disk, that avoids the problem (although is not any kind of solution).
- e
I had been running 4.0 for a while and accessing my archive of raw files across the network. Works fine but obviously not as fast as a local drive. I changed to 4.6 today and all my raw files are tagged with the view-only icon. I can preview them, see all my crops and tuning, but cant process them or adjust the tunings.
This happened to once before with a version of 3.7 but went away with an upgrade.
Am running a linux server with samba to deliver the files across a PC network. Nothing fancy. I tested dragging a folder off the network drive and onto a local disk, that avoids the problem (although is not any kind of solution).
- e
0
-
Happens to me too, images on a network share are read-only in 4.6.1. 0 -
A great program is getting worse and worse. No per-channel curves adjustment, now no ability to edit the files via networks. This sucks! 0 -
I have tried this with Windows 2000 server, Windows 2003, Mac OS 10.5.6 Server.
And NetGear ReadyNAS
Client both Windows XP and Mac OS 10.5.6 with out any issues.
Only thing I have noticed, which I am investigating is folder listing which acts strange with a NAS and Mac OS 10.5.6 connected over AFP.
Could anyone provide more information in regards to Linux kernel version, Samba version, authentication method? SMB protocol is of course a given.... but client OS might be of interest.
(Per channel adjustment is in the pipeline)0 -
My samba server: ludde@sauron:~$ cat /etc/debian_version
lenny/sid
ludde@sauron:~$ uname -a
Linux sauron 2.6.27.8 #1 SMP Sat Dec 6 23:08:13 CET 2008 x86_64 GNU/Linux
ludde@sauron:~$ /usr/sbin/smbd -V
Version 3.2.5
smb.conf:
security = user
The client machine is Windows XP running in VMWare:
Microsoft Windows XP Professional
5.1.2600 Service Pack 3 Build 2600
Capture One version 4.6.10 -
Hi,
I'm having this problem too, did anyone work out a way to get Capture One to allow editing on Samba drives?
My details:
fastsrv:~# uname -a
Linux fastsrv 2.6.18-6-686 #1 SMP Fri Dec 12 16:48:28 UTC 2008 i686 GNU/Linux
fastsrv:~# smbd -V
Version 3.0.24
fastsrv:~#
Windows Visa Enterprise 64
Thanks!
Anthony0 -
I use a ReadyNAS X6 network server and only have CIFS protocol enabled. on my pc and laptop I'm using windows vista business edition. even if i map the shared folder, i still get a view only option for my RAW files ☹️ 0 -
Hi,
I have the same problem, too.
I'm using OSX Server 10.4.11 (I know it's old) as the server, 64bit vista PC as a client. Sharing is done via OSX's SMB.
Nikon's Capture NX 2 and Adobe Lightroom 2 can work properly with this configuration (on exact same files), but Capture ONE 4.6.3 shows these as "read-only"
I've also tested Buffalo's LinkStation NAS, but got the same result...
Love the app, but unusable till this problem is fixed... ☹️0 -
Hey, I have kinda solved this...
On the server side, I changed the share point's default permission from 744 to 777. This has solved the "read-only" problem.
744 should have worked fine as I was accessing the share as the owner. Also, other apps were working properly under 744 privileges.
I have no idea why Capture One needs 777, but hope someone can nail down the issue! 😊0 -
Though I did not run tests (yet), I suspected a permission problem as Satoru discovered. Hopefully this helps the Linux/Samba users as well (Mac OS X is a Samba running on FreeBSD). 0 -
[quote="Paul_E" wrote:
Though I did not run tests (yet), I suspected a permission problem as Satoru discovered. Hopefully this helps the Linux/Samba users as well (Mac OS X is a Samba running on FreeBSD).
I would rather hope that this helps PhaseOne find the root cause and fix the problem 😊
- as Satoru points out, it should not be required to make your files worldwritable to get CO1 working.
I've seen problems similar to the ones described here on my FreeBSD/netatalk server, and a brief test indicates that changing permissions also yields better results in this scenario - though I haven't tested enough to be able to conclude that It Works (tm).
/Niels Chr.
BTW, my problem is described in Case-ID 43831 if anyones interested (Ulf? 😊0 -
Hello
A fix for this is not implemented in Capture One 4.7 but it is being looked at, I have been able to reproduce this both with NAS (stand alone, not AD or OD sync) and with Linux (same apply with user right sync)0 -
Hello,
I've just started using a Netgear ReadyNAS Duo and found I cannot move files from one folder to another within C1 (v4.7 LE), nor can I delete files using the delete function within C1. I get a Network Error (from Vista) askng me to check that the network drive is connected. I can move files, and delete files from within Windows Explorer without any problem. Is my problem related to that described above? I'm using Vista Home Premium with all updates applied. I have no problems editing or processing the raw files on the network drive from C1, so I clearly have access, but I can't move or delete them from within C1.
Duncan0 -
I have found a work-around. I made the directories containing images writable by anybody and I am able to process the images.
chmod go+w DIRECTORY0 -
To all ReadyNas users who are in User security mode and can only access images on share in view-only mode, try this: go to the share listing and click on the CIFS properties of the share that have the images (In my case, my share has default access disabled and the write-enabled user is me). Click in Advance Options,and make sure that the Share folder owner is admin, not your username. In case it is, change it to admin, check the box "Set ownership and permission for existing files and folders in this share to the above settings...blah blah blah" and then click Apply. Worked for me. Thanks to Ludvig2 for opening my eyes 🤓
P.S.-Unfortunately, this only works with files already on the share. If you copy new pictures, you'll have to do the operation again.0 -
Has anyone worked a fix for this?
I'm on Windows XP pro
C-1 4.8.1
And I can not edit files on the network.0 -
Windows SMB w/ NAS and Mac OS AFP w/ NAS should now be solved with 4.8.2
For Windows user, please map drives.0 -
Didn't worked for me. I've mapped the shared folder, but only the files who were already there before the "set ownership" process explained earlier could be edited. The newer files have the read only icon (shared on Readynas X6). But he can create the preview files. 0 -
Anyone else that can chip in regarding the ReadyNAS?
I have just tested this transferring files from Mac OS 10.5.7 (SMB) to a Ubuntu 9.04 Linux machine and then mapped the Linux shared folder on a Windows XP SP3 with CO 4.8.2, no problem.
Makes sure that the folder has both read and write access and the files does not have read only property.0 -
[quote="Ulf" wrote:
Anyone else that can chip in regarding the ReadyNAS?
I have just tested this transferring files from Mac OS 10.5.7 (SMB) to a Ubuntu 9.04 Linux machine and then mapped the Linux shared folder on a Windows XP SP3 with CO 4.8.2, no problem.
Makes sure that the folder has both read and write access and the files does not have read only property.
As long as the read/write permissions are set up on the share then I have no problem moving/editing files on my ReadyNAS Duo from any of my Vista machines on the network.
It is important to note though, that if you logon to Vista with user name "Fred" (for example), and have user name "Fred" with read/write access on the NAS, the NAS user "Fred" permissions may differ from the Vista user "Fred". Just because both users have the same name does not mean they are treated the same in Vista. the NAS user and the Vista user will have different permissions as default. You need to edit the NAS user "Fred" to have the correct read/write permissions in Vista.0 -
Thanks for input Duncan, I am sure this will be helpful for anyone that owns a ReadyNAS 0 -
Hi guys, thanks for the tips, but didn't helped. I was on the verge of giving up, when i took a peek on the CIFS share options of the shared folder and found an option named "Automatically set permissions on new files and folders", which used to set any files/folders rights that are saved there to "Ready/Write". And it worked! Of course i've had to delete and recreate the files again. Thanks Duncan22 for the light, Ulf for the patience, and everyone else for collaborating. Now i have to figure out how to get the readynas to work with offline files on my vista laptop, but that's another forum 😄
Thanks a lot!0
Post ist für Kommentare geschlossen.
Kommentare
21 Kommentare