Flickr plugin video limits incorrect

The flickr plugin which came with Lightroom 5 still enforces Flickr's video limit of 2 videos per month.  Flickr did away with that limitation back in May, according to Flickr support.  The result is normally some of my videos do not upload.   I'm not sure if Adobe supplies the plugin, or it's by a third party author, or I would contact them.
The free Flickr account video limits are 1GB in size and 3 minutes in length.

I hope Adobe corrects this problem with the 5.2 update.  Essentially the Flickr plugin is useless if you want to upload videos in addition to photos.  I was really looking forward to managing my Flickr photos (and videos) with LR5.  Bummer.
I posted a problem report with Adobe describing the problem.

Similar Messages

  • Flickr plugin does not "replace" when uploading after elimination of Flickr Pro accounts

    When uploading an image to flickr it has been possible for Pro accounts to re-upload a photo and replace an existing upload. This "replace" functionality keeps intact any comments, ratings, "favorites" etc that the photo has accumulated on the Flickr website since the original image was uploaded. The Lightroom Flickr plugin (authored by Adobe) has always correctly limited this "replace" functionality to Pro accounts (flickr did not allow the API call for non-pro accounts).
    With the recent flickr policy change eliminating Pro accounts, flickr has enabled the replacement functionality for all users. However, the Lightroom flickr plugin still performs a check for a Pro account and does not attempt to replace a previously uploaded image if a user has a non-pro account (which is now all accounts that were not grandfathered in as Pro). The plugin currently uses the older behavior of first deleting the image and then uploading a new image, thus losing all comments, history, views, bookmarks etc that the old image has accumulated.
    There is another non-adobe flickr plugin, and the author of that plugin stated on his web site that simply using the old Pro "replace" API call now works for normal flickr accounts.
    I recognize that this flickr policy change happened recently, but I'd like to be sure that Adobe is aware of this change so that the next point release of Lightroom will include a change to the built-in flicker plugin to remove the check for Pro accounts and allow all users to replace photos. I used this feature a lot when I was a pro subscriber, and I think all flickr users of Lightroom would appreciate this change. It is still possible for all users to replace an image on Flickr by exporting to a jpg from Lightroom and then uploading the replacement through the web site, but enabling the plugin would obviously be better for customers.

    I worked with Gokul from Adobe support, and we eventually stumbled into the solution.
    The system clock was wrong! 
    Based on something Friedl says on the blog for his Flickr plugin, the Flickr authentication APIs will fail if the system clock is wrong.  His plugin helpfully points out that the clock is wrong when you install it.  It also reports the error that he gets from the Flickr APIs: HTTP 401 (not authorized).  Unfortunately, Lightroom's builtin Flickr publishing plugin doesn't report any error, and it just fails silently.
    In my case, Windows appeared to be displaying the correct time, but the time zone was incorrect, and my system time was actually 3 hours ahead.  I reset the clock and timezone and restarted Lightroom.  Now, the builtin Flickr publish plugin is working again.

  • Flickr plugin issue corrected in LR 5.2 RC

    I just installed Lightroom 5.2 RC, and confirmed that the bug related to video upload limits has been corrected.  I've reported this issue in several forums.  The issue occurred because the Flickr  plugin enforced a 2 movie per month upload limit.  However, Flickr lifted that limitation back in May.  The current video limits are less than 3 minutes in length, and no greater than 1 GB in size.  I just uploaded an event which contained 5 videos.  Fantastic!
    Thank you for fixing this Adobe!

    It doesn't appear that either of the two profiles you listed are specifically for the newer Nikkor 18-35mm 'G' lens. You can use the Adobe Lens Profile Downloader to install the available 1.0 crop factor profiles. One is listed as a 'D' lens, which is clearly not what you want. The other two don't specify which  lens was used. Try the two below and see if the Vignetting and Distortion corrections appear correct with one of them. Since this lens was introduced a little over six months ago my guess is that none of the Adobe or Download lens profiles are for the 'G' lens, which is substantially improved over the 'D' lens. You may be able to use them by reducing the "default" Distortion and Vignetteing settings from 100. You'll need to check the results over the zoom range for distortion and aperature range for vignetting. Keep in mind that full 100% correction of vignetting and distortion is usually not desireable with a super wideangle zoom, which can make the image look "unnatural."

  • Lightroom 4.1: Publishing Service Flickr plugin; Using HTML in Caption field

    All,
    After hours of troubleshooting I have narrowed down a problem with an error message I’m getting when I try to export from Lightroom 4.1 using the Flickr Publishing service. The error msg is:
    Can't update this collection
    Could not contact the Flickr web service. Please check your Internet connection
    I have narrowed down the problem to my attempt to add basic HTML tags to the Caption (Description) Field of the Meta Data. This has worked perfectly well in all versions of Lightroom 3.6 and below (I didn’t try this type of export using Lightroom 4.0). I have also noticed that a simple page break, such as below, will also throw the same error:
    “Lorem ipsum @evansante.com dolor sit amet, consectetuer
    adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat veniam, quis nostrud exerci t”
    Flickr will recognize URL in simple text and format them properly so:
    “Lorem ipsum http://www.myurl.com dolor sit amet, consectetuer “
    Will work.
    Does anyone know of a work around that will allow including page breaks or HTML??? Thanks in advance - CES

    This bug, in a related way, has been noted by several users some time ago …
    http://forums.adobe.com/thread/999503?tstart=30
    and was reported as a bug a month ago during the release candidate period …
    http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_1_rc2_a_cr_or_lf_n_the_m iddle_of_a_caption_causes_failure_to_connect_to_flickr  
    Although the above mentioned bug is raised specifically in relation to “Breaks” in the caption text I believe it may be symptomatic of either generically poor XML information encoding by LR when talking to Flickr or poor / incorrect use of Flickr Api’s which cannot cope with trivial complexity in the caption field.
    – in either case it needs fixing with some priority in my opinion, but possibly the philosophy of the on-going Flickr plugin support needs fixing too.  
    The LR Flickr publishing service has not been maintained very well in my opinion even when fixes may sometimes be trivial.     Perhaps Adobe would do well to employ or contract with JF for such plugins in future.    I use the excellent SmugMug plugin as the yardstick by which I measure the Flickr plugin.
    A fix should also be treated as priority because the LR error message takes aim at the reliability of your internet connection which may cause some to erroneously try to chase down non-existent problems with a perfectly good infra-structure or OS / Firewall configuration – that is seriously bad advice for a caption related LR bug and has scope to seriously compound the problem for the user!  
    Adobe, you have a responsibility to fix this before people mess with their reliable setups.
    Sorry, I am not aware of any work rounds to your problem with this and suspect it may be a windows only problem (please confirm if not).   
    Although not entirely exactly as per your problem (I believe it is generically the same) you may wish to add your vote to the above mentioned problem report or raise a new one.

  • Why do i need three? - Google Talk Plugin, Google talk plugin video renderer and Google talk plugin video accelerator?

    When I check my plugins, the following three, very closely related (in my mind) plugins are listed, and the "Renderer" still shows "Research" when checking to see if it is Up-To-Date. It seems to me I don't need all three. I tried removing the Renderer (yes, I know how to do that safely), but Google seems to continue to reinstall it (with one or both of the other two...?)...I'll ask this on a Google Forum too, since it's their product, but wondered if anyone has any insight. I obsess about plugins that need "Research" - Thanks!
    Google Talk Plugin Video Accelerator version:0.1.44.24
    Google Talk Plugin Version 3.15.2.12038
    Google Talk Plugin Video Renderer Version 3.15.2.12038

    Went to Google Talk Help and found advice to remove the "googletalkplugin_port file on [my] computer."
    http://support.google.com/chat/bin/static.py?hl=en&page=known_issues.cs ... and click "Voice and video plug-in unrecognized" under "Currently Known Issues"....
    Now, the only Google Talk plugin I have in Firefox is
    Google Talk Plugin Video Renderer
    Version 3.15.2.12038
    ...but it does indeed remain "Unrecognized" by Mozilla/Firefox...

  • Flickr plugin broken

    As with the Facebook plugin, and discussion here: http://forums.adobe.com/message/4854227  the flickr plugin (and anything that writes to the temporary area) are broken on Windows 7, at least since the latest Windows update.  The plugin crashes because it can't write temporary files to the drive.  I am running Lightroom 4.2  and Flickr Plugin 4.2.0.850741.  Instead I installed Jeffry Friedl's Flickr plugin as a workaround, which does not have this issue (http://regex.info/blog/lightroom-goodies/facebook).
    Adobe, please look at this!

    Also, I used Microsoft's Process Monitor to track which files were written when I published a 1-photo collection to Flickr:
    These are exactly the directories and files you'd expect, which suggests something very curious on your configuration.  A screenshot of the error message might produce more clues.

  • Disable Jeffrey Friedl's Flickr Plugin before installing LR3

    If you're using Jeffrey Friedl's Flickr plugin in LR2, save yourself some grief and disable it before installing LR3. If you don't, LR3 won't start up properly and it will give you a very misleading message that it can't open your converted LR2 catalog. It makes you think that something went wrong converting the LR2 catalog, but it really didn't. I finally figured this out by deleting my converted LR2 catalog, then starting LR3 and telling it to create a new catalog instead of converting my LR2 catalog. It did this, and then gave me the true error message that the flickr plugin was not compatible with LR3 and it automatically disabled it. At this point, I was able to select my LR2 catalog to open (from within LR3) and it went through the conversion process again and successfully opened the catalog. Jeffrey currently only has a beta version of his LR3 compatible flickr plugin. You can find it on his blog.http://regex.info/blog/2010-06-08/1539

    kirbinster, sounds like you might also have other issues with your installation. I didn't have the issue with the help files. So, I'm not sure. You might try uninstalling LR3 and starting over, assuming you still have your LR2 catalog intact. Before you re-install, go into the plugin manager in LR2 and disable the Flickr plugin.

  • MXF encoding creates illegal brightess / luma ranges, despite the video limiter. TV Station rejects MXF encoded files

    Her is a simple setup producing the problem:
    Created a HD Bars and Tone.
    Created an Adjustmentlayer placed it above the bars and added a Video Limiter.
    Video Limiter:     set the Signal Min to 0 %
                             set the Signal Max to 100 %
    The YC-Waveform shows: the Values of the chroma and luminace are properly clipped. The ranges are between 0.3 and 1.0 V
    Render a MXF file with the Preset MZD OP1a -> XDCAM HD 50 PAL and reimport it to premiere (ohter preset create similar problems)
    Check the rendered Sequnce in the YC-Waveform.
    The YC-Waveform shows: In the chroma there is one spike going up to aproxemitly 1.14 (Between the last bar and the bar before it)
    and one spike is going down to a value of aprocimatly 0.26. In the Luma there are also to spike but far less pronounced.
    On the other hand, if I render an uncompressed quicktime and reimport, all the values are fine.
    The TV Station rejects the MXF files.
    THX in advance for your insight and help.
    YC-Waveform before encoding:
    YC-Wavform after encoding and reimport into premiere:
    The Spikes are hard to see, so I marked tehm with the circels.

  • Broadcast Safe or Video Limiter?

    I've testet Broadcast Safe Filter today.
    Compared with Broacast Safe Filter in Final Cut the result in Premiere CC looks a litte bit strange when there are to many highlights in the picture - so you can't use it. Final Cut always did a good job with the same pictures. What's the difference between this two programms and this special filter?
    Using Video Limiter seems to make a good Job with same Settings (110% luminace level). Is there any difference to know?

    Shooternz has seen some weird behavior with the filter as well.  For me it's always worked quite well and fairly invisibly.

  • Lightroom 5.7 - Flickr plugin fails to upload some photos,"Some export operations were not performed."

    There are 5 specific images which the plugin refuses to upload. Rebooting, restarting, nothing helps.
    Is there a solution or work-around?

    Sporadic uploading problems have long been reported with the built-in Flickr plugin.  You might try this third-party Flickr plugin.  The author has an excellent reputation and actively maintains his plugins (in contrast to Adobe); in fact, the author designed the plugin publishing architecture for Adobe.

  • How do I remove the flickr plugin in lightroom 3

    I'm trying lightroom 3 at the moment, but I can't seem to remove the flickr plugin. It's rather an eye-sore in the UI, and since I don't want to use it (after all, who decided that every person in the world uses flickr?) I want it gone. However, going to the plugin management, I can't remove it, and I can't disable it either, despite it being a "plugin", and not a baked-in program feature. I can "hide" it in the UI, which is a decent intermediary solution, but it doesn't solve the fact that there's a mystery plugin installed that I can't remove. (and I hate adobe's tendency to put stuff on my HD I didn't ask for, nor would have consented to if asked)
    So: how do I uninstall and remove this plugin?

    Hmm, Not being familiar with MacOS's package management, I have no idea where to even look for what you describe in Windows. There's only in-program plugin management, using file -> plugin manager (In this manager I can disable the plugin, but not remove it), and there's the Windows "programs and features" control, which is Windows' installed package manager, but it only offers me the option to repair or uninstall all of lightroom, but not individual parts of it.

  • LR 5.5 - Cannot export/publish to HDD or Flickr from video frame capture - "An internal error has occurred: assertion failed"

    Basically as the title states, I cannot publish a set of photos that originated as video frame captures, whether to my hard drive or using a service plugin for Flickr. I have tried multiple publish service plugins for Flickr and everything fails precisely the same way. This only happens when I add photos to the collection that are JPG's derived from video, and it only started doing this recently. I have other frame captures that I uploaded just fine, but it appears that nothing from the set I worked on the other day wants to upload. Other NEF-derived photos from the same set work just fine.
    All I get is a Warning dialog stating that an error has occurred while the main dialog stops on "Preparing to export...", then it kicks me back with no action taken when I click OK. The status in the upper left says "Updating Published Collections". If I remove the new frame capture photo, it works fine, but as soon as I add one to the collection, it fails to publish.
    I updated from 5.4 to 5.5, tried new publish plugins, completely removed and recreated my local profile, reimported my catalog, all to no avail. Everything worked fine two days ago, then when I went to upload my latest edits yesterday, I started receiving the error and have had no luck fixing it.
    I used debugView to capture a log as the error occurred, so I can provide that for a developer or support contact if required.
    EDIT: I just tried choosing some different photos in the set, and most appear to work, so it is just some particular images that it does not like. I will try to narrow it down.
    Message was edited by: Andrew Morton

    I narrowed it down to one photo in particular that it does not like. It's not a deal-breaker, but I am still curious what is going on that is causing that one photo being in a set to break the publish process

  • Joost & Flickr Apps Video Out to TV

    Has anyone been able to watch Joost or Flickr on a TV from your Touch/iPhone?
    I am trying though a Zeppelin but can not.

    try this website:
    http://www.oreillynet.com/pub/a/mac/2005/11/18/video-ipod.html
    I think that will do the trick!
    just start reading where it says "What You'll Need"...it will be in bold...
    if you still have a problem; which I think you wont after you read it.....post a message back on!

  • Effects in exported video render incorrectly

    I've been trying to export a sequence that includes a rotated shot with greenscreen. The problem is every time I try to export the sequence in compressor the shot is rotated back to 0 degrees. Everything else including the greenscreen in the same shot exports correctly. If I render the shot in the timeling in FCP it looks correct. Any help is appreciated.

    Thanks for the quick reply. But then why does the still's properties (in my bin) show the pixel aspect ratio as 1.3333 (not square pixels, 1.0) and should it not appear incorrectly in both the preview renders and the exported video ? This seems inconsitent to me.

  • Video Format incorrectly display, strange stuff

    Hello,
    I have a Mac Mini with a Matshita DVD-R UJ-845 Firmware: D8PB / MMC-3
    I've been toasting DVDs in NTSC on my Mac Mini, when I open the DVD player and get disc info it reads Video Format: NTSC, BUT...
    But my TV-DVD player on my NTSC TV says it is the "cannot play, wrong system". So I double checked the DVD disc on my PowerBook Al 12" PPC G4 1.5ghz and it's DVD player is saying that the video format is PAL!!! It's 2 machines against my macMini.
    I'm wondering how this can be? And how can I fix it so my MacMini correctly identifies the correct format??
    Thanks,
    A.S.

    For the Quicktime issue try:
    [Perian codecs for Quicktime|http://www.perian.org] - plugins to add functionality to Quicktime for playing additional audio and video formats
    [Quicktime audio problems, Perian, VLC|http://discussions.apple.com/message.jspa?messageID=9013669] - read note about uninstalling prior DIVX support before installing Perian.
    I'm not sure if this works with iTunes. I don't use itunes to watch video, I use [VLC media player|http://www.videolan.org/vlc> - general media player that plays just about anything.

Maybe you are looking for