Help: altering permissions of every audio file of Audio Folder

[Alécio Costa]

Hi,

Today I faced a very strange situation: I received 2 DVDr-s and as I copied them to my internal sata drives on a MAC Pro with 10.6.8, no matter if I manually changed permissions of every folder, the interior content ( tons of pt audio diles) continued with the read only permission.

I never had any problem opening drives, dvdr-s and cdr-s.

I imagine there shall be a shortcut for globally fixing this but I just don´t know it.
I also have no idea why the original owner did this. Seems he had some trouble with this "new" client of mine.

Any guiding light on this?


Thanks and Nice weekend!

[suicune]

When you have the parent session folder info open in the finder, unlock the permissions, entered your admin password and change them to read & write, then on the bottom left-hand corner there's a little settings button. Click on it and there's an option 'Apply to enclosed items'. Click that and it'll warn you it's not undoable, hit ok and it should sort all the files out.

[JFreak]

Or, you can use this command in Terminal app:

sudo chmod -R ugo+rw *

Execute this in your root session folder to give each and every user in the system read and write privileges.

Not so elegant regarding data security, but if you're the only user that has access to your workstation then who cares.

[Alécio Costa]

thanks, guys!

At GS a folk also informed this|:

Hi Alécio, try this:

- Open Terminal
- type "cd " (including the space) and then drag the affected Audio Files folder onto the terminal window. Then press Enter

- type "ls -l" and press Enter

This will display the permissions of all (visible) files in the folder.

To modify permissions of all files in the folder, type:

"sudo chmod a+r *.wav" to add read permissions to all (users, groups, others), for all wav files in the folder, or
"sudo chmod a+w *.wav" to add write ..., or
"sudo chmod a+x *.wav" to add execute ...

Run "ls -l" again to confirm ...

Use "chmod u+r *" to add read permissions to users only, g for groups, o for others (for example).

[groundcontrol]

http://www.ohanaware.com/permissionsreset/

This little app can be handy at times.

[JFreak]

Originally Posted by Alécio Costa

At GS a folk also informed this...

Yes, the guy suggested the same thing than my one line command UNIX is pretty nice because you can combine many things into one command.

To be clear; let me state the obvious: this would be wrong approach to almost anything, as it is a potential security risk. But if you know what you're doing and nobody else uses your workstation, it is just fine.

Now the better way would be actually changing the ownership of the files, so your user really owns them. That command would be CHOWN and used like this:

- open terminal and change directory to your project folder
- issue this command: sudo chown -R yourusername:yourusergroup *

It means that the command changes ownership of all files in that folder and its subfolders to whatever username and usergroup you want them to be assigned.

If there are multiple users that require access to the same files, this might get trickier than the CHMOD trick, but this is the proper (and secure) way to do it. If you only have one user that uses Protools, do this instead of the chmod. And even if you had more users, they would most likely belong to same usergroup which means you can chmodby the user group and not let everyone have full control.

Okay, let me end this nerding session now, let's make some music ;D

[Alécio Costa]

Hi, Jfreak
I am the only user at this machine.
I will try now the stuff you guys informed me.

Frankly, I don´t know why did the previous guy did this to such files.

[Alécio Costa]

ops
Now It seems to be doing fine!
Thanks

[Alécio Costa]

it is fine!