Aperture 3 default file permissions for referenced images

Hi,
This might be a bit more an OS X question than an Aperture question, but perhaps asking this here might help other people with similar case.
Is there a way to change the default file permissions Aperture 3 sets for image files imported from a digital camera?
My wife and I both import photos from our camera to a directory hierarchy under /Users/Shared/Photos/, and we both have our own Aperture libraries which reference the masters from that location.
However, when one of us imports photos from the camera, the permissions for the image files are set as 600 and the permissions need to be changed into 660 (for example) or otherwise the images are not readable for the other. (In the shell umask shows 0022 by default, but as I start the Aperture from the dock, changing the umask in the shell doesn't help)
Message was edited by: AJH75

Similar Messages

How to set default file permissions for applicatio...

I have the nokia n86 and was wondering if there was any way of setting the file permissions of a program via the phone. To put it in context, i downloaded a program that edits photos but everytime i try to load a picture from my phone it asks me (for every single folder in my phone, not just the photo ones) if the program can open it. I can be there clicking yes all day as i there is a lot of folders and subfolders on the phone. I know sony ericssons had an option where you could select the programs permissions to always ask or never ask but i cant seem to find a similar option on the nokia.
Does anyone have any ideas?

Same issue here. Everything I put on the drive is set to Read-only for the group.

Loupe Offline for Referenced Images?

In the Aperture 3 documentation, we get this...
Even though the masters are offline, you can browse, search, and assign metadata to preview images. You can even use the Loupe to zoom in on preview images, because they are high-quality JPEG files.
And in Aperture 2, this was correct. Now that I have finally gotten around to upgrading to Aperture 3, I find this functionality is broken. The loupe is displayed as "offline" for referenced images and refuses to magnify my previews (though I can zoom in on them just fine).
This is a big problem, because i rely on the loupe for sorting images, and don't always have my master images available.
Is there a way to restore the loupe for viewing previews like Aperture 2?

In the Aperture 3 documentation, we get this...
Even though the masters are offline, you can browse, search, and assign metadata to preview images. You can even use the Loupe to zoom in on preview images, because they are high-quality JPEG files.
And in Aperture 2, this was correct. Now that I have finally gotten around to upgrading to Aperture 3, I find this functionality is broken. The loupe is displayed as "offline" for referenced images and refuses to magnify my previews (though I can zoom in on them just fine).
This is a big problem, because i rely on the loupe for sorting images, and don't always have my master images available.
Is there a way to restore the loupe for viewing previews like Aperture 2?

How do I change the default file format for saving files in Preview

I often take screen clips and save them as files to my desktop, then upload them to my website or include them in emails. The default file format for Preview seems to be TIFF, but I'd prefer jpg. How do I convince Preview to use jpg as the default file format?
TIA,
Thad

I should have been a little clearer...
If I'm emailing a screen-clip, I can just paste it right into the email, but I post on a lot of discussion boards and it's often nice to be able to include a screen shot in those. My preferred way to do that is to post the clip at my personal website and then put a link in the post. It gives me the ability to delete the image whenever I want (a plus for any security freak) and it works on every discussion board I know. Some boards allow attachments, some don't. Plus I don't want to have to remember different d/b file attachment procedures. Anyway, when I make a screen-clip, I need to temporarily save it (usually to my desktop), then ftp it to my website. I use Preview to do that. It's simple. But I'd like it to default to .jpg instead of .png or .tiff. (FWIW, I just tried it and the default was .png, but I swear I did something similar earlier that defaulted to .tiff when I first tried to save the newly-created file).

How do I reset the default file association for .bat files on Windows 8.1?

Windows 8.1 allows the user to change the file association for .bat files. I made the mistake of using this facility to change the default file association for .bat files to Notepad++. Now when I attempt to run a .bat file, the script for the .bat
comes up in Notepad++, instead of its being run as an executable file! All my .bat files are now useless. I tried finding a way to change this back to the original executable setting, including deleting Notepad++ from my system, but nothing
has worked.
There are discussions that I found on the Internet about this problem, and the solutions to which I was led have not worked either. Most of the solutions apply to Windows 7 or Vista, but not to Windows 8. There are a few solutions that purport to apply to Windows
8 and 8.1, but they do not work for me.
(Disconcertingly, some of the solutions presented for the problem that apply to Vista or Windows 7 and are dated as early as 2009, so this problem has apparently been around for some time, but Microsoft still keeps .bat files on the Control Panel facility that
enables the change to be made. I cannot see why, but there it remains.)
Can someone please help me change this file association back to the original setting for Windows 8.1? Remember, most if now all the links that address this issue are focused on Windows 7. I need an answer that has been tried and proven to apply to Windows 8.1.
Nothing I have tried works.

Hi,
For the issue, we can restore Default File Extension Type Associations through adding the registry entries.
1. Download the .reg file from the following link.
http://www.eightforums.com/attachments/tutorials/8025d1345781188-default-file-associations-restore-windows-8-bat.reg
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
2. Save the .reg file to your desktop.
3. Double click on the downloaded .reg file to Merge it.
4. If prompted, click on Run, Yes (UAC), Yes, and OK to approve the merge.
5. Sign out and in, or restart the computer to apply.
6. If you are logged in as a standard user and this still does not help, then have the administrator also merge the needed .reg file for the listed file extension or protocol below while logged into their administrator account.
Hope this helps.
Regards,
Kelvin hsu
TechNet Community Support

Can I change the default 'File Type' for PL/SQL Source File to '*.prc' ?

Want to change the 'default' extension for PL/SQL source to '*.prc'
When navigating 'File' / 'Save As', and selecting the 'File Type' list box,
The default 'File Type' for PL/SQL Source File is '*.pls'.
Can I change the default 'File Type' for PL/SQL Source File to '*.prc' ?
I have followed , 'Tools', 'Preferences' , 'File Types' and added '.prc' as 'Sql Script' file type, because (PL/SQL Source) is not present in the list.

You can certainly overwrite the 'Save As' extension as you are saving the file. I have added an ER for more control over this functionality.
sue

What is the default file format for saving in MS Office 2013? Is it still the transitional OOXML or the ISO/IEC 29500 strict format?

As I have read, MS Office 2013 is able to read and write the ISO/IEC 29500 strict (standardized Office Open XML) file format. MS Office 2010 was only able to read the strict format and MS Office 2007 could neither read nor write the strict format. The
.docx, .xlsx and .pptx saved by Office 2007 and 2010 were only complying to the OOXML transitional, as far as I understood.
My main question is what the default file format for saving in MS Office 2013 actually is? Is it still the transitional OOXML or the ISO/IEC 29500 strict format?
In case, MS Office still saves in the transitional standard by default, is it possible to set the strict standard in the settings? Is this recommended (I assume that OOXML strict is the future) to do this?
Thanks.

Yes, the Transitional is still the default file format for saving in Office 2013, and we can modify this setting in Word Options, Save:
As Alex Brown covers in his
blog post, "Transitional is intended to preserve the fidelity of existing binary documents being migrated to ISO/IEC 29500, and includes many legacy features for compatibility with existing documents. Strict is a subset of Transitional that does not
include legacy features – this makes it theoretically easier for a new implementer to support (since it has a smaller technical footprint, so to speak), but also makes it less able to preserve the fidelity of existing documents."
Max Meng
TechNet Community Support

How to set default file type for Open dialog

Dear my friends,
I am using "At selection-screen ON VALUE-REQUEST FOR filepath" to display open dialog and i want to set default file type for open dialog = *.txt.
Thank your times !

Hello,
U can make use of this code:
AT SELECTION-SCREEN ON VALUE-REQUEST FOR SP_FILE.
PERFORM SAVE_DIALOG CHANGING SP_FILE G_F_RC.
FORM SAVE_DIALOG CHANGING PO_FILE PO_RC.
DATA: L_VA_BOXTITLE     TYPE STRING,
        L_VA_DEFAULTFILE TYPE STRING,
        L_VA_DEFAULTNAME TYPE STRING,
        L_VA_DEFAULTPATH TYPE STRING,
        L_VA_DEFAULTFULL TYPE STRING,
        L_VA_FILTERTEXT   TYPE STRING,
        L_VA_CODE         TYPE I.
CLEAR: PO_RC, G_F_CONF.
L_VA_BOXTITLE   = TEXT-B01.
L_VA_FILTERTEXT = TEXT-B02.
IF PO_FILE IS INITIAL.
    CLEAR L_VA_DEFAULTFILE.
ELSE.
    L_VA_DEFAULTFILE = PO_FILE.
ENDIF.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_SAVE_DIALOG
    EXPORTING
      WINDOW_TITLE            = L_VA_BOXTITLE
      DEFAULT_EXTENSION       = 'TXT'
      DEFAULT_FILE_NAME       = L_VA_DEFAULTFILE
      FILE_FILTER             = L_VA_FILTERTEXT
      INITIAL_DIRECTORY       = 'C:SAPWorkdir'
    CHANGING
      FILENAME                = L_VA_DEFAULTNAME
      PATH                    = L_VA_DEFAULTPATH
      FULLPATH                = L_VA_DEFAULTFULL
      USER_ACTION             = L_VA_CODE
    EXCEPTIONS
      CNTL_ERROR              = 1
      ERROR_NO_GUI            = 2
      OTHERS                  = 3.
IF SY-SUBRC <> 0.
    PERFORM CHECK_ERRORTYPE(Z48M_MATDATA_UP) CHANGING SY-MSGTY.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
               WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    CLEAR PO_FILE.
    EXIT.
ENDIF.
IF L_VA_CODE NE 0.
    MESSAGE S818(3F) WITH TEXT-011.
    CLEAR: PO_FILE, PO_RC.
    EXIT.
ELSE.
    WRITE L_VA_DEFAULTFULL TO PO_FILE.
    G_F_CONF = G_C_XFELD.
ENDIF.
ENDFORM.                    " save_dialog
If useful reward.
Vasanth

Default File Type for New Forms - How to change?

Hi,
How can I change propperty: Default File Type for New Forms?
It is enabled! Do I have to be Administrator to change it? I have SAP ALL..
SFP -> Layout -> Tools --> Options -> Document Handling
tnx, Adibo.

There is no authorisation required for changing the file type. You are saying its enabled, then you can change it.
Edited by: Nikhil Poojari on Aug 28, 2009 6:50 AM

:-) How can we change the default file path for Bank file ( dmee ) ?

Hi All,
We encounter a problem.
Electronic bank file ( created after a F110 run ) are created, in an automatic way to the DIR_TEMP directory. ( On the SAP server )
How can we change the default file path for Bank files ( dmee ) ?
We'd like to specify another path.
Thx for your help.
Erwan

Hello,
Make sure that you have created the directory in transaction code AL11 with the help of basis consultants.
You can link your PC directory to the application server.
You can maintain the path whether your file needs to get saved in OBPM4 against your DMEE structure example GB_BACS etc.
If you do not maintain any path in OBPM4, then the file gets saved to temporary directory. If you give the directory path name in OBPM4, then the file gets saved to that directory with numbers 0001, 0002, 0003 etc till it reaches 9999 and reset from the beginning.
If you give the path as well as file name as ABCD, then the file gets generated to that directory folder with ABCD0001, ABCD0002, ABCD0003 etc. till it reaches ABCD9999 and reset from the beginning.
Hope this solves your problem.
Regards,
Ravi

Aperture cannot locate newly imported referenced images

My friend and I both use Aperture (3.4.3) on OSX 10.7.5.
She recently started having an issue when importing photos as referenced, with images stored on her external hard drive.
After importing, on all images she gets the red slash thru the 'referenced master' badge, indicating that Aperture cannot locate the master images. Aperture also refuses to reconnect with the master images. It's worth noting that all other images in her library are correctly "referenced" to the same external hard drive. The issue is with newly imported images.
The only solution thus far is for her to import as managed, then relocate original out to the external hard drive.
She has both repaired and rebuilt her Aperture library with no change.
She has run Disk Utility on both her external hard drive and her internal hard drive which contains her Aperture library. No errors were found.
Has anyone seen anything like this? Suggestions are welcome!

Have you verified file permissions on the external drive? To avoid permissions problems on an external disk, I just enable "Ignore Ownership" for the entire volume using the Get Info command for it. I do this only for non-boot data only volumes where Aperture libraries are stored. (Actually you can't do it for boot volumes anyway)
You'd think doing the Aperture repair commands would fix this but maybe it only fixes Managed libraries and the referenced files need to be done by the Finder.

Managing backup systems for referenced image masters

The manual says:
+Aperture doesn’t back up the masters of referenced images located outside the Aperture library. *You must maintain your own backup system of referenced image masters.* Aperture does back up the versions, previews, and metadata information associated with referenced images, but not the masters themselves.+ (my bolding)
So, somehow, I ended up with some images (older, it seems) in the vault but other images (newer) as referenced. An incomplete back up to the vault. I understand how I can move those referenced to the Vault but:
1) is there a fast way to find and select all the referenced masters for this move? Like a menu item or a button in a dialog box that says "Find and move all referenced Masters to the vault"? Simple eh?
2) why does Apple not allow you to keep referenced Masters out of the vault but a copy of the Master backed up in it? When it goes to reinstall (hopefully never!), it can just reinstall the whole vault in Aperture - if need be. I could live with this especially if it makes backing up all my Masters easy and recovering all of them assured.
3) Since #2 is not possible for now - how do people back up referenced files and why do you do referenced over Vaulted or a combination of the two (which is what I have but, not knowing I was doing this)? I would like to be able to look at images on my MacBook Pro but really keep the bulk of the images and editing on a MacPro.
4) when I imported iPhoto to Aperture, did they all come in as vault Masters or referenced?

Joseph Coates wrote:
...when I imported iPhoto to Aperture, did they all come in as vault Masters or referenced?
Images are imported according to settings you select. Probably you initially imported using a Managed-Images Library. To import by Reference from within Aperture, import images from the hard drive folder into Aperture selecting "Store files in their current location."
...how do people back up referenced files
Using any normal data backup method. I like to simply manually Finder-copy to external hard drives.
and why do you do referenced over Vaulted or a combination of the two (which is what I have but, not knowing I was doing this)?
Actually the correct syntax is Referenced over Managed. Vault refers to one type of backup routine that does include Managed Masters.
The primary problem with using a Managed-Masters Library instead of a Referenced-Masters Library is that for almost all modern digital photogs using Aperture their quantity of image files will grow quickly, rapidly taking more and more space on a single internal hard drive if Managed-Masters keeps all image files on a single internal hard drive.
Hard drives slow as they fill, so unless a multi-drive SATA/eSATA array is used a Managed-Library drive will sooner or later lose performance. Use of Referenced-Masters allows the Library to forever stay small enough not to overfill a single drive.
Personally I consider separate backup of Masters outside Aperture's Vault protocol a benefit, not a negative.
Using a Managed-Masters Library works even for for laptop/iMac owners if completed Projects with Masters are constantly purged from Aperture but that is inappropriate workflow for most photogs, and the benefits of using a Managed-Masters workflow are minimal.
I would like to be able to look at images on my MacBook Pro but really keep the bulk of the images and editing on a MacPro.
Although various user workarounds exist, the issue of synching your laptop Library with your desktop Library has not (yet) been addressed by Apple. IMO Apple's failure (still) to address this key issue is a travesty; Apple's single-user Filemaker has had that capability since the 1980's.
I suggest going to "Provide Aperture Feedback" under the Aperture menu and requesting that Apple provide single-user synch capabilities for two Libraries (such as the laptop/desktop setups that you and I both have). Note that it is important to specify single-user, two-Libraries, because multi-user scenarios are entirely different solutions that - unlike single user solutions - are usually very complex and expensive.
-Allen Wicks

Can i use an old iPhoto library for referenced images?

I upgraded to Mavericks today (from Snow Leopard) and want to find a way to continue to view + edit images from my old iPhoto library.
My version of iPhoto is 8.1.2, and is 390GB. I have also been using Aperture for some time, and now have 3.5.1. The Aperture library is 71GB of Managed Images.
I have several backups of the iPhoto library of external disks. Can I set things up so that the images can be accessed by Aperture as Referenced Images'?
And if so, will the iPhoto structure (events, folders etc) be retained?

It's achieveable, but somewhat of a hack, and the best you'll get is something close to your event structure, but not albums.
I'd really recommend lêonie's approach above.
However, if you really want to play...:
There are two main problems to solve.
1) The files are inside the iPhoto library bundle which is not selectable from the import panel.
2) You'll have a combination of master, non-destructive edits, and previews. I no longer have an 8.1 library to check so I can't decribe the structure). You'll need to decide if you want to bring in originals and edits (where available).
You'll need to have a look around the iPhoto library structure; navigate to it in finder, right-click the library and choose 'Show package contents'.
Explore this until you are happy you know where the images are stored (orginals and edited copies), these are the images you can access directly.
To make them accessible for import in Aperture, drag any folders your are interested in (eg: originals, masters, previews, etc) to your finder favourites sidebar. This doesn't move them anywhere, it just gives you shortcuts to those folders that reside inside the iPhoto library bundle.
In Aperture, use 'Import->Folders as Projects' from the file menu. Here you can specify that the images stay in their original location (imported as referenced) and you can use the shortcut on your finder sidebar (created above) to navigate into the iPhoto library to pick up the images.
You can try the different options for the stucture of the import ('Folders and Projects' or 'Projects and Albums'). 'Folders and Projects' will probably work best as it will give something approximating your import history which may match your event structure, but the project names will likely not match the event names.
Once you've got them in Aperture, youll probably need to tidy up the structure, but in Aperture you can move and change projects as much as you want withouth affecting anything in the old iPhoto Library. The things that can impact the iPhoto Library are deleting or relocating any of the masters.
As I say, it's a bit of a hack, and in the long run you will probably be better off by just importing the library and relocating the masters. This will keep your event and album structure and be much cleaner, but it will give you an additional copy of the images, which I suspect is what you are trying to avoid.
Also, if you get future problems with your images, you'll have to explain all the above or people may have trouble helping you!
Andy

How do I set the default file path for the Place command?

I keep my graphics files for each document in a particular folder. Every time I open an existing InDesign document and place a new image I have to browse back to that location - even though all of the previous images in that document came from the same folder. InDesign does not remember the file path that was used previously in the document. This is very annoying.
IS THERE A WAY TO SET THE DEFAULT FILE PATH, OR LOCATION, FOR IMAGE FILES?
I have looked through the preferences, searched the forums and internet, but I have not found any reference to setting default paths. Is there a setting like the one in MS Word called "File Locations" on the Options toolbox?
Thank you.

Since you're working in ID on Windows, you can take advantage of a neat trick in Windows. Copy the file path out of the File Explorer address bar and paste it directly into the Place filename field. That will jump you directly to the desired volume. For example, let's say I want to place a graphic located at X:\PS Jobs\May PS\709672bp\Working Source Files\Links. I copy that entire path from the File Explorer address bar, go to InDesign, select File|Place, and press Control + V to paste that path into the filename field. I press the Open button and Shazam! I'm there instantly, without a bunch of navigation.
You can do the same thing in the File|Save As and File|Export fields. Let's say you want export a PDF file from InDesign to the volume X:\PS Jobs\May PS\709672bp\Working PDF Files. First copy the desired file path from the File Explorer window. In InDesign, select File|Export, click anywhere in the filename field, and press the Home key to move the insertion point to the front of the filename. Press Control + V to paste that path in front of the filename, then add the backslash character (\). The filename will now look like this: X:\PS Jobs\May PS\709672bp\Working PDF Files\Filename.pdf. Press the Save button to bring up the Export Adobe PDF window. Select your desired PDF preset, press the Export button, and the PDF file will magically appear in the desired volume.
This sounds really complicated, but it's not. In practice, it only takes a few seconds. I probably save an hour's worth of needless navigation every day with this technique.

How to change default file permissions so others can write to file

We have 15 people sharing files on a network. If we open a file on the network, work on it, and save it, it is readable and writeable for everybody. But if we drag the file off the network, work on it on our own hard drive, and save it, and THEN drag it back to the network, it is read-only for everybody. Documents made on our own hard drives are, by default, read-only for others.
This is a real time waster for us!
This means that every time we make a document on our own hard drives, we have to remember to go to the extra trouble to change it's permissions before we put it on our network. Please, is there some way to change the default settings, so that if I, say, save a Word doc on my hard drive and then move it to the network, it is readable and writeable by everybody without me having to change it's permissions?

Sounds like you are not using ACLs. When you double click your share point in Server.app, how many entries do you have in the Permissions window? If you have only 3 then you are not using ACLs which explains why your permissions are not inheriting. POSIX permissions, the base three of owner, group, and everyone, do not inherit. You need to add at least one more permission entry to the table. This is called an ACE (access control entry). Together, you are building an ACL (access control list). Try not to use users. Always add groups if possible as it is easier to manage and never requires propagation of the permissions.
R-
Apple Consulting Network
Apple Professional Services
Author "Mavericks Server – Foundation Services" :: Exclusively available in Apple's iBooks Store

Aperture 3 default file permissions for referenced images

Similar Messages

Maybe you are looking for