Aperture 3 and flickr title

Good morning and ..... happy new year.
I use Aperture 3 and I sync my flickr album with it, but there is a think I don't like: the title in flickr is the version name of the photo. Is there a way to set caption to be the flickr name?
Thank in advance.
http://davidecherubino.tel

I'd love an answer to this, as well.
Using Aperture's primary competitor, the Title of the image in the IPTC data mapped directly to Flickr's title, and the Caption to Flickr's caption. I can't tell what the disconnect is with Flickr-Aperture, but I'd like to know.
Anyone?

Similar Messages

  • Guidance on Aperture and Flickr Integration

    Can anyone point me to anything that advises on the correct way to use the synchronisation feature. I just can't get this to work consistently; my Flickr folder in Aperture does not match the set in Flickr.
    As seen on Flickr, I routinely get duplication whilst other photos go missing. I only get duplication in the Aperture album.
    I'm on the verge of giving up on it, which isn't a big deal, but this kind of flakiness does make me doubt the solidity of the application in general. I'd much rather think that I've just misunderstood something.

    i had a set in Flickr that is where i place 1 photo a day for all 365 days this year. i have been using my iPhone 4 to upload photos to Flickr, but i had synced this set to Aperture. today i used my regular camera and edited the photo in Aperture and dragged it to the Flickr set (in Aperture). when i went to Flickr, the new photo was there, but 3 previous photos were now listed as being newer than the photo i just added. my 3 previous photos that had 10 - 20 views had been removed and replaced with the same photo without the tags, without the titles, without the views, and without correct date for when the photos were taken. i had to spend a lot of time in Flickr trying to correct things and guessing the dates taken. not fun. and i really don't like losing the view count as i take great pride in that.
    i was pretty excited to upgrade to Aperture, but version 3.0 is disappointing if it's going to screw up my hard work.

  • Aperture and Flickr Export Problems - Missing Files

    I have a MacPro, Aperture 3, and Flickr Pro account. I was planning on using Flickr as an online storage/back-up option for lower-res files. However, whenever I try to upload a project to Flickr files always seem to drop off.
    For example, if I export a project with 446 files in it, when it gets to Flickr it'll say I only have 403 images. Likewise if I try a smaller project (e.g., 426 -> 404).
    Has this happened to anyone else? Any ideas what is the cause of this problem?
    Also, any way to remove that 500 upload limit per project to Flickr? Flickr itself does not limit the number of photos you can store in a set.
    Thanks!

    Maybe it's related to this bug?
    http://discussions.apple.com/thread.jspa?threadID=2354356

  • Aperture and Flickr sync

    I sync nearly every project in Aperture with Flickr. Now I would like to check which photos I have synced and which not, but I can not find the richt selection in Aperture. Can anybody help me?

    Having exactly the same problem. My guess is that Aperture sync is broken. The Flickr App behaves exactly the same and can't sort out the right date stamp. In my experience Aperture only sometimes messes up the tags and names, but always the time stamp, even after several resyncs.

  • Aperture and Flickr

    I asked this question before, but I think I was not specific enough.
    When you publish i.e. a project to Flickr a set is created in Flickr and that set is also shown in the Aperture Library. When you look at the metadat of a photo, you can she under "sharing" that it is published to Flickr, so it looks like that this information is stored in the metadata.
    What I would like to do is a search in my whole aperture library for photos that are (or are not) published to Flickr, but I cannot find the specific field in the search criteria. Is this missing, or am I overlooking something?

    Maybe it's related to this bug?
    http://discussions.apple.com/thread.jspa?threadID=2354356

  • Facebook and Flickr with Aperture on Macbook Pro

    I have set up both a Facebook and Flickr account in Aperture.  They work great and like how easy they are to use.  I do have a problem though.
    After using my Macbook, I close the screen and leave it.  When I come back and open the screen, sometimes Aperture gives me an error that says:
    There was a problem connecting to Facebook.
    The operation couldn’t be completed. (OSStatus error -1.)
    After clearing the message it comes back in an endless loop.  Am I doing something wrong?  Should I exit Aperture before closing the screen evertime?  How can I clear this error without killing the application?
    Thanks.
    Mike T4

    This is not much help, but I don't think it's an infinitely loop. I suspect the number of times you get the message is related to the number of flickr sets you have in Aperture. If you are patient, and click the OK button enough times, it will go away.
    I really don't like force quitting - especially Aperture. I have always been able to "outlast" Aperture by clicking the OK button enough times.

  • Aperture 3 and Flickr sync problems

    Hi!
    I started using Aperture 3 recently and made the mistake of authorizing Aperture to sync with Flickr.  I hate it!  Now I want to deauthorize it somehow but don't know where or how?  I've read horror stories that all of my Flickr photos will be deleted from Flickr if I deauthorize, but none of my Flickr photos were uploaded from Aperture, they were already in Flickr and were automatically synced to Aperture once I authorized it.  Now that I realize I've made a mistake I want to get out, but how?
    TIA!
    Debbie

    I have been using the sync feature between my Aperture library and Facebook and Flickr for 6 months and I finally gave up on it yesterday.
    As an example of what I usually go through, I uploaded 159 photos to my flickr account this past weekend, then added some captions/descriptions/tags etc. on flickr (was that a mistake?). Then Aperture promptly undid some my work at the next synchonization... I don't want photos on my stream named DSC_6788.jpg, etc.  Thing is, Aperture undoes some of what I do on Flickr but not all.  There's no rhyme, reason, or pattern to it.  If I use Aperture to add tags (by entering keywords in the right field), even those partially disappear after the next sync.
    Another maddening thing is that it makes the filename the caption on Facebook albums.  I/e/. if, on Facebook, I added a desctiptive caption on a picture such as "Mommy and Daddy making out under the Eiffel Tower" (totally a made up example), then next time a synch happens, the caption would be "DSC_8646.jpg."  Gee, thanks for the help, Aperture.
    For 6 months I have lived in fear of opening up Aperture.  Will the sync mess up what I've published online?
    There should be option to not have Aperture override what you do on flickr (and Facebook).  I am a strong believer in the "Publish and Forget" model for places like Flickr and Facebook, not the sync model.
    For now, it's back to export to a folder and upload via the uploader.

  • HT4906 Both my iPhoto, Aperture and OX is update still having problem asking me to update my iPhoto.

    Both my iPhoto, Aperture and OX is update still having problem asking me to update my iPhoto.

    Make a temporary, backup copy (select the library and type Command+D) if you don't already have a currnet backup of the library and  apply the two fixes below in order as needed:
    Fix #1
    Launch iPhoto with the Command+Option keys held down and rebuild the library.
    Since only one option can be run at a time start with Option #1, followed by #3 and then #4 as needed.
    Fix #2
    Using iPhoto Library Manager  to Rebuild Your iPhoto Library
    Download iPhoto Library Manager and launch.
    Click on the Add Library button, navigate to your Home/Pictures folder and select your iPhoto Library folder.
    Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File ➙ Rebuild Library menu option
    In the next  window name the new library and select the location you want it to be placed.
    Click on the Create button.
    Note: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.
    OT

  • IPhoto and Flickr - disappearing photos and involuntary syncing

    After control-clicking on Check Now in one of my Flickr albums, within iPhoto of course, all of the pictures in the album disappeared, leaving only the name of the album in the list of Flickr albums in iPhoto.
    The set made from that album is still present on the Flickr website (so far), even after navigating away from the page and coming back. I have no idea what is going on.
    I assumed that Check Now would sync any changes I made to photos in that Flickr set back to the same photos on iPhoto.
    I am worried that Flickr is now going to delete all of those photos entirely from iPhoto (as well as from the Flickr site). That would be a big problem. It hasn't done that so far, but who knows? I understand that the syncing between iPhoto and Flickr is two way - i.e. true syncing.
    When your changes in Flickr sync back to iPhoto, does Flickr change your original in iPhoto (or whatever is serving as your original for Flickr's purposes - that is, the most recently modified version in iPhoto), or is there a separate version created just for uploading to Flickr, that is stored in the Flickr album on iPhoto, and that is the only version that is changed by Flickr when it is syncing back (to iPhoto)? I hope it is the latter. If not, many of us may be in for a surprise.
    Should I delete the empty Flickr album from iPhoto, which should have the effect of deleting that set and its photos from the Flickr website, and start all over? This was a big, long upload, which is why I am hesitating.
    I just started using Flickr yesterday and have had some trouble with it - for example, I've deleted albums/sets and re-uploaded them, for various reasons. Perhaps I've confused the poor thing.
    I have Flickr Pro, if that makes a difference.
    Confused.
    Thanks in advance.

    Barb2008 wrote:
    After control-clicking on Check Now in one of my Flickr albums, within iPhoto of course, all of the pictures in the album disappeared, leaving only the name of the album in the list of Flickr albums in iPhoto.
    Hi,
    The Flickr tool in iPhoto is both pretty neat and pretty frustrating. While I think it is a good start, it still needs work. I probably can not answer most of your questions, but I can clarify a few and offer my own experiences...
    The set made from that album is still present on the Flickr website (so far), even after navigating away from the page and coming back. I have no idea what is going on.
    That is weird. So the Flickr set in iPhoto cleared itself but the actual set on Flickr is still intact, right? Have you tried restarting your computer, going to disk utility and repairing disk permissions on your start up drive, then restarting iPhoto?
    If that doesn't clear it up, you might try rebuilding the iPhoto library by closing iPhoto then restarting while holding down the Option key. Then try some of the rebuild options and see where that gets you.
    I assumed that Check Now would sync any changes I made to photos in that Flickr set back to the same photos on iPhoto.
    The syncing is two ways, but the Flickr sync back to iPhoto is more limited. For example, if you add keywords in Flickr those keywords will be synced back to iPhoto. However if you add a photo from your flickr account into that album, Flickr will send a small version thumbnail back to iPhoto, not the original photo.
    But yes, to answer your question, all syncing between iPhoto and Flickr is more or less a two way sync.
    I am worried that Flickr is now going to delete all of those photos entirely from iPhoto (as well as from the Flickr site). That would be a big problem. It hasn't done that so far, but who knows? I understand that the syncing between iPhoto and Flickr is two way - i.e. true syncing.
    First off, Flickr can never remove anything from your iPhoto library. Perhaps a photo might be removed from a flickr album in your iPhoto, but the photo will still exist in your library. So you can not lose anything from your library using Flickr.
    Second, if the Flickr album in your iPhoto is empty but the photos are still in the album in Flickr, then they will not be removed later. The sync tends to be a real time event where if you remove photos from an iPhoto Flickr album, iPhoto then begins to remove them from Flickr as well.
    My own experience is that sometimes things happen like you experienced, where the iPhoto Flickr album gets "disconnected" from the on-line Flickr album. At this point there is no longer a connection and one doesn't effect the other. I have not found a way to relink the two which is one of the weak points of the new iPhoto Flickr syncing.
    As a side note, a nice feature would be a menu item to actually do that, disconnect iPhoto from an on-line album, as it would be nice to be able to upload an album, then disconnect it so no further changes are made to Flickr regardless of what happens to the iPhoto album. Basically a "do not update" setting.
    When your changes in Flickr sync back to iPhoto, does Flickr change your original in iPhoto (or whatever is serving as your original for Flickr's purposes - that is, the most recently modified version in iPhoto), or is there a separate version created just for uploading to Flickr, that is stored in the Flickr album on iPhoto, and that is the only version that is changed by Flickr when it is syncing back (to iPhoto)? I hope it is the latter. If not, many of us may be in for a surprise.
    To the best of my knowledge, Flickr does not sync back actual changes to the photo itself. It will sync back things like album name changes, title changes, keyword additions, and stuff like that. However I have never actually tried publishing an album to Flick then editing a photo in that album in Flickr to see what it does. I should try that to see. Generally, if I have used iPhoto to publish photos to Flickr, then I use iPhoto to make any edits to the photo, not Flickr.
    Should I delete the empty Flickr album from iPhoto, which should have the effect of deleting that set and its photos from the Flickr website, and start all over? This was a big, long upload, which is why I am hesitating.
    As I mentioned above, if the album in iPhoto is empty but everything is still intact on Flickr, then likely the album in iPhoto was "disconnected" (link lost) from the Flickr album. When you go into that album in iPhoto, does it still show a Flickr link in the upper left? If so, what happens when you click that link? Does it take you to the album?
    I just started using Flickr yesterday and have had some trouble with it - for example, I've deleted albums/sets and re-uploaded them, for various reasons. Perhaps I've confused the poor thing.
    Flickr is pretty good. It is the iPhoto to Flickr interface and syncing that is a bit weak. It sounds like your issues are with iPhoto's syncing with Flickr than with anything to do with Flickr itself.
    I myself use a number of tools with Flickr and I find iPhoto doesn't offer many choices on how it works with Flickr. Actually it doesn't really offer any choices, you get one method of interaction and that is it. So for many tasks I use other tools to get photos onto Flickr.
    That said, if you have a full album/event you want to put on Flickr, the iPhoto interface is very handy for publishing a set on Flickr with keywords, map data, etc. and allows you to edit photos later and have those updates automatically go to Flickr as well. But with that comes some problems like being able to edit a photo in iPhoto for a different purpose, perhaps forgetting you added it to a Flickr album since you are accessing the photo elsewhere in iPhoto than that Flickr set, and then having those edits updated to Flickr without you realizing or intending.
    Barb2008 wrote:
    More info about my question - there is an emanating wave or broadcast signal icon beside each Flickr album name in the iPhoto source menu. It looks a bit like the Airport signal icon along the top bar of the computer screen. When you click on it, the sync symbol appears and goes round and round for awhile. So that is how you manually sync Flickr albums and sets I guess.
    Yes, even if you just click on the set to look at it in iPhoto, you will usually see the little "broadcast" icon indicate it is checking the set against the Flickr set. Usually you see one of several icons. The little broadcast icon like the airport signal simply indicates that the set is synced to a Flickr set but is currently idle. When you click that icon or the set, the icon changes to a circle. A couple of swirling arrows in the circle indicates it is checking online. If there are updates then the circle goes blank and you start to see an advancing pie piece indicating how much of the sync is complete. If the circle just sits there blank for a long time, then the sync has stalled or not working.
    One album has the symbol, and two don't. These are the two I had trouble with today (deleting and re-uploading, etc.)
    The album that has the symbol also has a link at the top of the photos to the page on Flickr containing that photo set.
    The two albums that don't have the symbol do not display a link to the appropriate Flickr page. The corresponding sets are both visible on Flickr, however, as I said.
    Perhaps I should start all over?
    Ah, ok that answers the question I asked above. Sounds like the two albums somehow got de-linked from Flickr. Both sets show up on the left side under the Flickr listings?
    If that is the case, you have a couple of options.
    One is if you are satisfied with the set as it appears over in Flickr and don't really have a need to keep a live link between the two (Flickr and iPhoto) you can probably delete those sets from our of iPhoto's "Flickr" albums and your Flickr sets will stay.
    On the other hand, if you wish to keep a live link to the two albums so you can continue to edit or update the album, keywords, photos, etc. then you probably want to redo those two.
    Unfortunately as I said above, I don't know how to get an album to RE-link back to Flickr once that link has been broken and where it has happened to me I either have removed the set from iPhoto, removed the set and all photos from Flickr (using the Flickr web site tools), then recreating the set in iPhoto and clicking the Flickr upload button again to recreate the whole thing. Or I leave the set on Flickr and continue to work with it directly at Flickr using other tools to add additional photos and doing all my edits on the set or the photos from the Flickr website itself.
    Regards,
    Patrick

  • Aperture and FlickrExport quits unexpectedly

    I have been uploading photos from Aperture to Flickr for many months with the FliclrExport plugin with no problem. Today as the first photo is halfway up Aperture quits! No message saying it quit unexpectedly or anything.
    I have installed all the latest updates and even upgraded to Aperture 2.1 and still it crashes.
    Any Ideas?

    Have you uploaded the FlikrExport plugin? If you're upgraded Aperture, you may need to upgrade the plugin as well.

  • I have been storing my Aperture and IMovie Libraries on an external hard drive that recently died.  Fortunately I've been using Time Machine to back up to a 2nd external drive.  How do I restore my libraries to a new external hard drive?

    I have been storing my Aperture and IMovie Libraries on an external hard drive that recently died.  Fortunately I've been using Time Machine to back up to a 2nd external drive.  How do I restore my libraries to a new external hard drive?

    This is a tricky one.
    Open up Time Machine and go back to a date using the timeline on the right side of the window when you know the drive was working and was backing up as part of Time Machine backups.
    Click on the name of your Mac under the Devices heading on the left side of the window in Time Machine, and if things are working correctly you will see Macintosh HD (or whatever you have named it) and the name of the external hard drive that was backing up in the past.
    Right-Click on the name of the external hard drive and then click on "Restore (name of drive) to....."  You may be asked for your adminstrator password at this point.
    It might be easier to restore the drive contents to your desktop if you have room on your Mac, and then copy things over to the new external drive where you want to store the Aperture and iMovie Libraries.
    Once the libraries have been moved over the new external hard drive, you will likely need to "point" Aperture and iMovie to the location of the libraries on the new external hard drive.

  • Vicious MPD widget not displaying the artist and song title

    EDIT: This thread can be closed now. It turns out Clementine doesn't support mpd and I'm now running ncmpcpp and the widget shows the artist and song title.
    I have trouble getting the mpd widget running in awesome wm, it will only display "N/A - N/A". I've read the wiki and done a lot of googling but I can't figure out what I'm missing.
    Here's my rc.lua
    -- Standard awesome library
    local gears = require("gears")
    local awful = require("awful")
    awful.rules = require("awful.rules")
    require("awful.autofocus")
    -- Widget and layout library
    local wibox = require("wibox")
    local vicious = require("vicious")
    -- Theme handling library
    local beautiful = require("beautiful")
    -- Notification library
    local naughty = require("naughty")
    local menubar = require("menubar")
    -- {{{ Error handling
    -- Check if awesome encountered an error during startup and fell back to
    -- another config (This code will only ever execute for the fallback config)
    if awesome.startup_errors then
    naughty.notify({ preset = naughty.config.presets.critical,
    title = "Oops, there were errors during startup!",
    text = awesome.startup_errors })
    end
    -- Handle runtime errors after startup
    do
    local in_error = false
    awesome.connect_signal("debug::error", function (err)
    -- Make sure we don't go into an endless error loop
    if in_error then return end
    in_error = true
    naughty.notify({ preset = naughty.config.presets.critical,
    title = "Oops, an error happened!",
    text = err })
    in_error = false
    end)
    end
    -- {{{ Variable definitions
    -- Themes define colours, icons, and wallpapers
    beautiful.init("/usr/share/awesome/themes/zenburn/theme.lua")
    -- This is used later as the default terminal and editor to run.
    terminal = "tilda"
    editor = "gedit"
    -- os.getenv("EDITOR") or
    editor_cmd = terminal .. " -e " .. editor
    -- Default modkey.
    -- Usually, Mod4 is the key with a logo between Control and Alt.
    -- If you do not like this or do not have such a key,
    -- I suggest you to remap Mod4 to another key using xmodmap or other tools.
    -- However, you can use another modifier like Mod1, but it may interact with others.
    modkey = "Mod4"
    -- Table of layouts to cover with awful.layout.inc, order matters.
    local layouts =
    awful.layout.suit.floating,
    awful.layout.suit.tile,
    awful.layout.suit.tile.left,
    awful.layout.suit.tile.bottom,
    awful.layout.suit.tile.top,
    awful.layout.suit.fair,
    awful.layout.suit.fair.horizontal,
    awful.layout.suit.spiral,
    awful.layout.suit.spiral.dwindle,
    awful.layout.suit.max,
    awful.layout.suit.max.fullscreen,
    awful.layout.suit.magnifier
    -- {{{ Wallpaper
    if beautiful.wallpaper then
    for s = 1, screen.count() do
    gears.wallpaper.maximized(beautiful.wallpaper, s, true)
    end
    end
    -- {{{ Tags
    -- Define a tag table which will hold all screen tags.
    tags = {}
    for s = 1, screen.count() do
    -- Each screen has its own tag table.
    tags[s] = awful.tag({"term", "www", "mp3", "skype", "office", "dev", "misc" }, s)
    end
    -- {{{ Menu
    -- Create a laucher widget and a main menu
    myawesomemenu = {
    { "manual", terminal .. " -e man awesome" },
    { "edit config", editor_cmd .. " " .. awesome.conffile },
    { "reboot", "gksudo reboot" },
    { "restart", awesome.restart },
    { "quit", awesome.quit }
    mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
    { "open terminal", terminal }
    mylauncher = awful.widget.launcher({ image = beautiful.awesome_icon,
    menu = mymainmenu })
    -- Menubar configuration
    menubar.utils.terminal = terminal -- Set the terminal for applications that require it
    -- Initialize widget
    mpdwidget = wibox.widget.textbox()
    -- Register widget
    vicious.register(mpdwidget, vicious.widgets.mpd,
    function (mpdwidget, args)
    if args["{state}"] == "Stop" then
    return " - "
    else
    return args["{Artist}"]..' - '.. args["{Title}"]
    end
    end, 10)
    -- {{{ Wibox
    -- Create a textclock widget
    mytextclock = awful.widget.textclock()
    -- Create a wibox for each screen and add it
    mywibox = {}
    mypromptbox = {}
    mylayoutbox = {}
    mytaglist = {}
    mytaglist.buttons = awful.util.table.join(
    awful.button({ }, 1, awful.tag.viewonly),
    awful.button({ modkey }, 1, awful.client.movetotag),
    awful.button({ }, 3, awful.tag.viewtoggle),
    awful.button({ modkey }, 3, awful.client.toggletag),
    awful.button({ }, 4, function(t) awful.tag.viewnext(awful.tag.getscreen(t)) end),
    awful.button({ }, 5, function(t) awful.tag.viewprev(awful.tag.getscreen(t)) end)
    mytasklist = {}
    mytasklist.buttons = awful.util.table.join(
    awful.button({ }, 1, function (c)
    if c == client.focus then
    c.minimized = true
    else
    -- Without this, the following
    -- :isvisible() makes no sense
    c.minimized = false
    if not c:isvisible() then
    awful.tag.viewonly(c:tags()[1])
    end
    -- This will also un-minimize
    -- the client, if needed
    client.focus = c
    c:raise()
    end
    end),
    awful.button({ }, 3, function ()
    if instance then
    instance:hide()
    instance = nil
    else
    instance = awful.menu.clients({ width=250 })
    end
    end),
    awful.button({ }, 4, function ()
    awful.client.focus.byidx(1)
    if client.focus then client.focus:raise() end
    end),
    awful.button({ }, 5, function ()
    awful.client.focus.byidx(-1)
    if client.focus then client.focus:raise() end
    end))
    for s = 1, screen.count() do
    -- Create a promptbox for each screen
    mypromptbox[s] = awful.widget.prompt()
    -- Create an imagebox widget which will contains an icon indicating which layout we're using.
    -- We need one layoutbox per screen.
    mylayoutbox[s] = awful.widget.layoutbox(s)
    mylayoutbox[s]:buttons(awful.util.table.join(
    awful.button({ }, 1, function () awful.layout.inc(layouts, 1) end),
    awful.button({ }, 3, function () awful.layout.inc(layouts, -1) end),
    awful.button({ }, 4, function () awful.layout.inc(layouts, 1) end),
    awful.button({ }, 5, function () awful.layout.inc(layouts, -1) end)))
    -- Create a taglist widget
    mytaglist[s] = awful.widget.taglist(s, awful.widget.taglist.filter.all, mytaglist.buttons)
    -- Create a tasklist widget
    mytasklist[s] = awful.widget.tasklist(s, awful.widget.tasklist.filter.currenttags, mytasklist.buttons)
    -- Create the wibox
    mywibox[s] = awful.wibox({ position = "top", screen = s })
    -- Widgets that are aligned to the left
    local left_layout = wibox.layout.fixed.horizontal()
    left_layout:add(mylauncher)
    left_layout:add(mytaglist[s])
    left_layout:add(mypromptbox[s])
    -- Widgets that are aligned to the right
    local right_layout = wibox.layout.fixed.horizontal()
    right_layout:add(mpdwidget)
    if s == 1 then right_layout:add(wibox.widget.systray()) end
    right_layout:add(mytextclock)
    right_layout:add(mylayoutbox[s])
    -- Now bring it all together (with the tasklist in the middle)
    local layout = wibox.layout.align.horizontal()
    layout:set_left(left_layout)
    layout:set_middle(mytasklist[s])
    layout:set_right(right_layout)
    mywibox[s]:set_widget(layout)
    end
    -- {{{ Mouse bindings
    root.buttons(awful.util.table.join(
    awful.button({ }, 3, function () mymainmenu:toggle() end),
    awful.button({ }, 4, awful.tag.viewnext),
    awful.button({ }, 5, awful.tag.viewprev)
    -- {{{ Key bindings
    globalkeys = awful.util.table.join(
    awful.key({ modkey, }, "Left", awful.tag.viewprev ),
    awful.key({ modkey, }, "Right", awful.tag.viewnext ),
    awful.key({ modkey, }, "Escape", awful.tag.history.restore),
    awful.key({ modkey, }, "j",
    function ()
    awful.client.focus.byidx( 1)
    if client.focus then client.focus:raise() end
    end),
    awful.key({ modkey, }, "k",
    function ()
    awful.client.focus.byidx(-1)
    if client.focus then client.focus:raise() end
    end),
    awful.key({ modkey, }, "w", function () mymainmenu:show() end),
    -- Layout manipulation
    awful.key({ modkey, "Shift" }, "j", function () awful.client.swap.byidx( 1) end),
    awful.key({ modkey, "Shift" }, "k", function () awful.client.swap.byidx( -1) end),
    awful.key({ modkey, "Control" }, "j", function () awful.screen.focus_relative( 1) end),
    awful.key({ modkey, "Control" }, "k", function () awful.screen.focus_relative(-1) end),
    awful.key({ modkey, }, "u", awful.client.urgent.jumpto),
    awful.key({ modkey, }, "Tab",
    function ()
    awful.client.focus.history.previous()
    if client.focus then
    client.focus:raise()
    end
    end),
    -- Standard program
    awful.key({ modkey, }, "Return", function () awful.util.spawn(terminal) end),
    awful.key({ modkey, "Control" }, "r", awesome.restart),
    awful.key({ modkey, "Shift" }, "q", awesome.quit),
    awful.key({ modkey, }, "l", function () awful.tag.incmwfact( 0.05) end),
    awful.key({ modkey, }, "h", function () awful.tag.incmwfact(-0.05) end),
    awful.key({ modkey, "Shift" }, "h", function () awful.tag.incnmaster( 1) end),
    awful.key({ modkey, "Shift" }, "l", function () awful.tag.incnmaster(-1) end),
    awful.key({ modkey, "Control" }, "h", function () awful.tag.incncol( 1) end),
    awful.key({ modkey, "Control" }, "l", function () awful.tag.incncol(-1) end),
    awful.key({ modkey, }, "space", function () awful.layout.inc(layouts, 1) end),
    awful.key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
    awful.key({ modkey, "Control" }, "n", awful.client.restore),
    -- Prompt
    awful.key({ modkey }, "r", function () mypromptbox[mouse.screen]:run() end),
    awful.key({ modkey }, "x",
    function ()
    awful.prompt.run({ prompt = "Run Lua code: " },
    mypromptbox[mouse.screen].widget,
    awful.util.eval, nil,
    awful.util.getdir("cache") .. "/history_eval")
    end),
    -- Menubar
    awful.key({ modkey }, "p", function() menubar.show() end)
    clientkeys = awful.util.table.join(
    awful.key({ modkey, }, "f", function (c) c.fullscreen = not c.fullscreen end),
    awful.key({ modkey, "Shift" }, "c", function (c) c:kill() end),
    awful.key({ modkey, "Control" }, "space", awful.client.floating.toggle ),
    awful.key({ modkey, "Control" }, "Return", function (c) c:swap(awful.client.getmaster()) end),
    awful.key({ modkey, }, "o", awful.client.movetoscreen ),
    awful.key({ modkey, }, "t", function (c) c.ontop = not c.ontop end),
    awful.key({ modkey, }, "n",
    function (c)
    -- The client currently has the input focus, so it cannot be
    -- minimized, since minimized clients can't have the focus.
    c.minimized = true
    end),
    awful.key({ modkey, }, "m",
    function (c)
    c.maximized_horizontal = not c.maximized_horizontal
    c.maximized_vertical = not c.maximized_vertical
    end)
    -- Bind all key numbers to tags.
    -- Be careful: we use keycodes to make it works on any keyboard layout.
    -- This should map on the top row of your keyboard, usually 1 to 9.
    for i = 1, 9 do
    globalkeys = awful.util.table.join(globalkeys,
    awful.key({ modkey }, "#" .. i + 9,
    function ()
    local screen = mouse.screen
    local tag = awful.tag.gettags(screen)[i]
    if tag then
    awful.tag.viewonly(tag)
    end
    end),
    awful.key({ modkey, "Control" }, "#" .. i + 9,
    function ()
    local screen = mouse.screen
    local tag = awful.tag.gettags(screen)[i]
    if tag then
    awful.tag.viewtoggle(tag)
    end
    end),
    awful.key({ modkey, "Shift" }, "#" .. i + 9,
    function ()
    if client.focus then
    local tag = awful.tag.gettags(client.focus.screen)[i]
    if tag then
    awful.client.movetotag(tag)
    end
    end
    end),
    awful.key({ modkey, "Control", "Shift" }, "#" .. i + 9,
    function ()
    if client.focus then
    local tag = awful.tag.gettags(client.focus.screen)[i]
    if tag then
    awful.client.toggletag(tag)
    end
    end
    end))
    end
    clientbuttons = awful.util.table.join(
    awful.button({ }, 1, function (c) client.focus = c; c:raise() end),
    awful.button({ modkey }, 1, awful.mouse.client.move),
    awful.button({ modkey }, 3, awful.mouse.client.resize))
    -- Set keys
    root.keys(globalkeys)
    -- {{{ Rules
    awful.rules.rules = {
    -- All clients will match this rule.
    { rule = { },
    properties = { border_width = beautiful.border_width,
    border_color = beautiful.border_normal,
    focus = awful.client.focus.filter,
    keys = clientkeys,
    buttons = clientbuttons } },
    { rule = { class = "MPlayer" },
    properties = { floating = true } },
    { rule = { class = "pinentry" },
    properties = { floating = true } },
    { rule = { class = "gimp" },
    properties = { floating = true } },
    -- Set Firefox to always map on tags number 2 of screen 1.
    { rule = { class = "Firefox" },
    properties = { tag = tags[2] } },
    -- {{{ Signals
    -- Signal function to execute when a new client appears.
    client.connect_signal("manage", function (c, startup)
    -- Enable sloppy focus
    c:connect_signal("mouse::enter", function(c)
    if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
    and awful.client.focus.filter(c) then
    client.focus = c
    end
    end)
    if not startup then
    -- Set the windows at the slave,
    -- i.e. put it at the end of others instead of setting it master.
    -- awful.client.setslave(c)
    -- Put windows in a smart way, only if they does not set an initial position.
    if not c.size_hints.user_position and not c.size_hints.program_position then
    awful.placement.no_overlap(c)
    awful.placement.no_offscreen(c)
    end
    end
    local titlebars_enabled = false
    if titlebars_enabled and (c.type == "normal" or c.type == "dialog") then
    -- buttons for the titlebar
    local buttons = awful.util.table.join(
    awful.button({ }, 1, function()
    client.focus = c
    c:raise()
    awful.mouse.client.move(c)
    end),
    awful.button({ }, 3, function()
    client.focus = c
    c:raise()
    awful.mouse.client.resize(c)
    end)
    -- Widgets that are aligned to the left
    local left_layout = wibox.layout.fixed.horizontal()
    left_layout:add(awful.titlebar.widget.iconwidget(c))
    left_layout:buttons(buttons)
    -- Widgets that are aligned to the right
    local right_layout = wibox.layout.fixed.horizontal()
    right_layout:add(awful.titlebar.widget.floatingbutton(c))
    right_layout:add(awful.titlebar.widget.maximizedbutton(c))
    right_layout:add(awful.titlebar.widget.stickybutton(c))
    right_layout:add(awful.titlebar.widget.ontopbutton(c))
    right_layout:add(awful.titlebar.widget.closebutton(c))
    -- The title goes in the middle
    local middle_layout = wibox.layout.flex.horizontal()
    local title = awful.titlebar.widget.titlewidget(c)
    title:set_align("center")
    middle_layout:add(title)
    middle_layout:buttons(buttons)
    -- Now bring it all together
    local layout = wibox.layout.align.horizontal()
    layout:set_left(left_layout)
    layout:set_right(right_layout)
    layout:set_middle(middle_layout)
    awful.titlebar(c):set_widget(layout)
    end
    end)
    client.connect_signal("focus", function(c) c.border_color = beautiful.border_focus end)
    client.connect_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
    function run_once(prg,arg_string,pname,screen)
    if not prg then
    do return nil end
    end
    if not pname then
    pname = prg
    end
    if not arg_string then
    awful.util.spawn_with_shell("pgrep -f -u $USER -x '" .. pname .. "' || (" .. prg .. ")",screen)
    else
    awful.util.spawn_with_shell("pgrep -f -u $USER -x '" .. pname .. " ".. arg_string .."' || (" .. prg .. " " .. arg_string .. ")",screen)
    end
    end
    awful.util.spawn_with_shell("setxkbmap -layout se")
    run_once("tilda",nil,nil,"term")
    run_once("firefox &",nil,nil,"www")
    run_once("clementine ",nil,nil,"mp3")
    run_once("skype ",nil,nil,"skype")
    run_once("dropboxd &",nil,nil,nil)
    run_once("keepassx ",nil,nil,"www")
    run_once("volumeicon &",nil,nil,nil)
    awesome.font = "DejaVuSansCondensed 12"
    Here's my mpd.lua:
    -- Licensed under the GNU General Public License v2
    -- * (c) 2010, Adrian C. <[email protected]>
    -- {{{ Grab environment
    local tonumber = tonumber
    local io = { popen = io.popen }
    local setmetatable = setmetatable
    local string = { gmatch = string.gmatch }
    local helpers = require("vicious.helpers")
    -- Mpd: provides Music Player Daemon information
    -- vicious.widgets.mpd
    local mpd = {}
    -- {{{ MPD widget type
    local function worker(format, warg)
    local mpd_state = {
    ["{volume}"] = 0,
    ["{state}"] = "N/A",
    ["{Artist}"] = "N/A",
    ["{Title}"] = "N/A",
    ["{Album}"] = "N/A",
    ["{Genre}"] = "N/A",
    --["{Name}"] = "N/A",
    --["{file}"] = "N/A",
    -- Fallback to MPD defaults
    local pass = warg and (warg.password or warg[1]) or "\"\""
    local host = warg and (warg.host or warg[2]) or "127.0.0.1"
    local port = warg and (warg.port or warg[3]) or "6600"
    -- Construct MPD client options
    local mpdh = "telnet://"..host..":"..port
    local echo = "echo 'password "..pass.."\nstatus\ncurrentsong\nclose'"
    -- Get data from MPD server
    local f = io.popen(echo.." | curl --connect-timeout 1 -fsm 3 "..mpdh)
    for line in f:lines() do
    for k, v in string.gmatch(line, "([%w]+):[%s](.*)$") do
    if k == "volume" then mpd_state["{"..k.."}"] = v and tonumber(v)
    elseif k == "state" then mpd_state["{"..k.."}"] = helpers.capitalize(v)
    elseif k == "Artist" then mpd_state["{"..k.."}"] = helpers.escape(v)
    elseif k == "Title" then mpd_state["{"..k.."}"] = helpers.escape(v)
    elseif k == "Album" then mpd_state["{"..k.."}"] = helpers.escape(v)
    elseif k == "Genre" then mpd_state["{"..k.."}"] = helpers.escape(v)
    --elseif k == "Name" then mpd_state["{"..k.."}"] = helpers.escape(v)
    --elseif k == "file" then mpd_state["{"..k.."}"] = helpers.escape(v)
    end
    end
    end
    f:close()
    return mpd_state
    end
    return setmetatable(mpd, { __call = function(_, ...) return worker(...) end })
    I'm using Clementine to play the music if that makes a difference.
    Last edited by DisposableHero (2013-11-25 01:12:01)

    Hi,
    If the songs were purchased from itunes, I suggest that you delete the tracks from your itunes library and move to trash (providing you live in a country that permits redownloading). See http://support.apple.com/kb/PH12283.
    Jim

  • New to Apple and Aperture-I am surprised at the lack of integration between Aperture and applications as iMovie.

    Aperture slideshow is terrible in terms of entering any text on a photo.  It appears that you have to export the photos from Aperture to the desktop to import the photos to iMovie to be able to add quite good text to individual photos. While I am new to the Apple system (I am quite knowledgable in Windows), I am surprised that iMovie cannot import an Album or a Project from Aperture.  It does not appears possible to to copy and paste from Aperture to the project created in iMovie without exporting to the desktop.  This seems like a step backwards.
    Since I come from Windows I will be importing most of my photos into Lightroom3 and doing  most of my work.  Yet, there are features in Aperture that I like and will probably use both for the time being.  I am using Aperture 3 and iLife11.  New Macbook Pro

    I read the manuals and watched the tutorials on the Apple web site as well as F1 in Aperture and never saw a reference to using Windows menu to list photos in iMovie.  I check this and it does seem to work.  however, you must admit that the procedure for adding text on a photo is limited as compare to iMovie.  Maybe, it is because I want to add text to a photo for posting on Mobileme or other photo posting sites so friends can view the photos in a slideshow or one by one.
    I assume that you can answer this question. Since I was exporting photos to the desktop so I could import them in iMovie, if I delete the folder on the desktop will they disappear form the project in iMovie?  Since I do not like a lot of folders on the desktop can I move them to the Pictures folder and not loose the project links in iMovie?

  • Did up date for 10.7.4 to 10.7.5 and update for Aperture and now  Aperture doesn't open.  How do I fix?

    Did up date for 10.7.4 to 10.7.5 and update for Aperture and now  Aperture doesn't open.  How do I fix?

    I heard dump the app and reinstall?  How do I go about that?

  • If I install a trial version of Aperture and don't like it, will I be able to still use my photo library in iPhoto?

    I'm evaluating both Aperture and Adobe's Lightroom to decide which one meets my needs for the best price (got a deal on Lightroom 3 for $120 and I know Aperture 3 is $79 in the Mac App Store).
    I have a few questions:
    I currently use iPhoto '11 (9.1.3) and have Photoshop CS4, so I have tools for importing DSLR shots and making pro-type changes in Camera Raw, while also having iPhoto to organize my photo library and syncing Events and Albums with my iPhone and iPad.
    I like that I would be able to maintain my iPhoto library data for Faces and Places in Aperture, but am concerned that when the iPhoto library is "upgraded" for Aperture, and I decide I don't really need that program, the upgraded library won't work with iPhoto anymore.
    Will I still be able to use iPhoto to access and organize my library, or will it be forever converted for use with Aperture?
    I'm considering Lightroom because I have been disappointed with the number of bugs showing up in recent iPhoto releases. I'm a bit weary of buying another photo management software product from Apple. iPhoto '11 crashed my old iMac very frequently (I wound up upgrading to a new iMac due to this and I was expecting to run out of hard drive space in a year or two anyway).
    Recently, iPhoto bugs make Events show up multiple times in iTunes when syncing for iPhone and iPad.
    If iPhoto management is this unstable, I would like to consider choosing a new method of organizing and syncing to iOS devices and abandoning the iPhoto library method.
    Will I find a better user experience with Aperture, or does it also use the single file library and suffer the same struggles iPhoto users have been seeing lately?

    I like that I would be able to maintain my iPhoto library data for Faces and Places in Aperture, but am concerned that when the iPhoto library is "upgraded" for Aperture, and I decide I don't really need that program, the upgraded library won't work with iPhoto anymore.
    The iPhoto library isn't changed in any way by Aperture. Aperture will import the Library and you can choose to copy the files to the Aperture Library or reference them within iPhoto. As long as you don't delete files from the iPhoto Library via Aperture (which you could do if you choose to Reference) there is no impact on iPhoto
    Will I still be able to use iPhoto to access and organize my library, or will it be forever converted for use with Aperture?
    They are completely different libraries.
    Recently, iPhoto bugs make Events show up multiple times in iTunes when syncing for iPhone and iPad.
    Fixed in the 9.1.3 update.
    Will I find a better user experience with Aperture, or does it also use the single file library and suffer the same struggles iPhoto users have been seeing lately?
    Like iphoto, Aperture can use the "single file library" or it can use a Referenced Library (just like iphoto can). Note that using a Referenced Library offers not a whit more in terms of features or capabilities. It's file storage plain and simple. Nothing more.
    No you won't see the "same struggles iPhoto users have been seeing..." because Aperture is an entirely different allication.
    But you my see Aperture or Lightroom struggles
    Regards
    TD

Maybe you are looking for