ANOTHER Lightroom 5 Bug??

This is another bug that I had during the Beta which I hoped would have been solved. It is difficult to reproduce but happens frequent enough to be a real pain.
Using the adjustment brush or gradient tool, I can apply settings to photos. Then when I switch to a new photo, I can select the brush or gradient, but I cannot apply it to the photo. Nothing happens when I paint or drag gradients. I can select and deselct the tool as many times as I want and even switch between tools. Only way to get it working again is to restart Lightroom.

True.... except that in the Beta it was more the gradient tool causing this issue and now it is mostly the adjustment brush. I am not ruling out the fact that it can be something on my side... Could be a plugin or something causing this too. Once I can replicate the problem I will post the steps - but for now I am just keeping an ear out to see if anyone else have this issue.

Similar Messages

Another Lightroom 3 bug

Occasionally, I insert a card to import and get the message that LR cannot import because card is unreadable. I try to read the images from Bridge, and there they are, all images can be opened without any drama. Images can also be read and downloaded if I use Finder (Mac OS X), or any other software for that matter. Used to happen at least once a week on LR3, but never on the previous versions.
I thought this bug was fixed in LR3.2, but today it just happened again. Very annoying and frustrating. Eventually, after several tries, Lr will budge and import the photos from the card.
Also worried because Lr3 has been corrupting images for me when converting to DNG.

EricKeithScott wrote:
I again suggest you get a life and do something with your family. I do not use LR for any fun. I use it for work and only work.
This is a pretty funny group of sentences.
Yes, I use LR at work (I do wind energy research and use it for engineering photography):
I use LR at home for family pictures:
I use LR for pictures I take while on vacation with my family:
And I use LR for pictures of my own fun with my own hobbies, such as R/C aircraft:
And planetary photography:
Among others...
I'm sorry you aren't having any fun with photography.

Another iPhoto 6 bug

Amusing but yet another iPhoto 6 bug (6.0.2). Boy, does this program need some work.
I created a new library, set alias on so it loads from my iView MediaPro layout, and am busy importing. In the information tab on the bottom left, it tells me its busy importing 1595 photos with a total size of 15066192772 GB. I wish.
iBook 14" 1.42 Mac OS X (10.4.3) 1.5GB

Paul:
Did it finish loading the iView files? If so check the size at the bottom. If it's still incorrect and extremely large try rebuilding the library, launch iPhoto with the Command+Option keys depressed, follow the instructions to rebuild the library, while selecting only the database option. That may clear up the problem.
I didn't note the size when I was importing my iView collection but iPhoto does reports the correct size now.

Another SQL Developer bug - End of file in comment

I found another SQL Developer bug in version 3.0.0.4.
If I try to compile some package from file (so I open file with package body in SQL Developer and assign it to some connection) with this kind of comment: /* comment */ behind end of package, I get this error
I got Error(1250,28): PLS-00111: end-of-file in commentFunny is, that when the package is compiled directly from the database - it works.
When I try to compile the package from file with this kind of comment --comment behind the end of package, it also works...

Hi, I think I finally got it. This looks like an ugly fat bug :)
First, we are not using the .sql extensions. For package specification - we use .pks. For package body - we use .pkb.
Create this script:
CREATE OR REPLACE PACKAGE TEST_xxx AS
PROCEDURE TEST_PROCEDURE;
END TEST_xxx; /*0123456789*/Now save this as e.g. "TEST.pks" file. Open this file in SQL Developer and compile it. You will get the "Error(3,27): PLS-00111: end-of-file in comment".
Now look at the result in the database -> Open the package specification from the database and you see this:
create or replace
PACKAGE TEST_xxx AS
PROCEDURE TEST_PROCEDURE;
END TEST_xxx; /*0123456789*The last slash is missing...
Now go back to the file with the package specification and delete one letter from the comment. Compile it again... it works now.
It looks like the length of this kind of comment is limited to 9 characters.
The limitation is there only when:
1) Compiling from file with different extension than .sql !!! If you rename the file to "TEST.sql", SQL Developer opens it as a script file and runs it as a script, so there is no problem with it.
2) It has to be this kind of comment: /* */. One line comments are not limited.

FB3 Beta 3 - another organize imports bug

I'm getting lucky :-) Here is another organize imports bug in
FB3 Beta3...
If you have some simple hierarchy where base class defines
public (or protected) method, and sub class tries to override this
method you will encounter this bug. Let say that base class looks
like this:
package test {
import flash.display.Shape;
public class BaseClass extends Shape {
public function BaseClass() {
public function myMethod():void {
trace("In BaseClass.myMethod()");
and that sub class looks like this
package test {
public class SubClass extends BaseClass {
public function SubClass() {
super();
Now, if you try to override myMethod() from BaseClass and
start typing in subclass something like
override public function m
and use Ctrl+Space, FB will insert appropriate method but it
will also insert errorneous import statement like this:
import test.BaseClass.myMethod;
So you will end up with sub class which looks like following:
package test {
import test.BaseClass.myMethod;
public class SubClass extends BaseClass {
public function SubClass() {
super();
override public function myMethod():void {
Wrong import is correctly marked as error but issuing
"organize import" does not remove it so it must be removed
manually.
Regards,
Damir Murat
PS: Sorry for bad code formatting but there is no option for
inserting in-line code and attach code is a little bit
awkward.

Damir Murat,
Did you already file a bug for this? If not, would you mind
adding it to the public bug base so we can track the issue.
Thanks,
Peter

Lightroom 5 - Bug in Survey view?

Hi all,
Sorry if this isn't the right place for this, it's the first time I've used these forums and I couldn't find anywhere else to submit a bug report.
I've recently started using Lightroom and have started with Lightroom 5. I've found that sometimes when switching between Loupe view and Survey view the images in Survey view are different sizes or in the wrong place:
I think it's after something has happened which will remove an image from the current selection while in Loupe view, on returning to Survey view not all images have been re-sized and re-positioned. It only seems to happen if Lightroom is trying to catch up after a lot of activity.
So the sequence I used to cause the second image was to go from Survey view to Loupe view using the E key shortcut, navigate between various images in the selection with the cursor keys (I did this quite quickly, so Lightroom was slightly delayed in its responses), press X to reject one of the images, which caused the image to no longer match my filter, then quickly after press N to return to Survey view. Doing anything which would cause a refresh of the images, such as contracting and expanding the section on the right, causes the images to sort themselves out.
I'm using Lightroom 5.0 on Windows 7, let me know if you need any more details.
Thanks,
Andy

I haven't seen this in GRID view but there is a problem with phantom images being selected in Compare View and after leaving Compare View. This is another of many LONGSTANDING bugs still not fixed in LR5.3. This was reported almost a year ago. This is a SEVERE bug as you can accidentally delete or change images after using compare as images are selected that you don't know about.
A couple threads
http://forums.adobe.com/message/5835956#5835956
http://forums.adobe.com/message/5564937#5564937
http://forums.adobe.com/message/5805625#5805626
http://forums.adobe.com/message/5465076#5465076
As you can see in this clip, no photos are selected in the film strip, one photo is selected in the main window and the info line says there are two photos selected. If you switch to GRID it will show no photos selected but if you do a remove photo command, two photos will be removed. Severe bug as far as I am concerned.

Lightroom features/bug fixes I would like to see in next version

I love the Adobe Lightroom Application. It is very intiutive and out of the different RAW processing programs I've tried, it is the only one that has most of the features I need and has the least amount of complications. However, I think there are still places to improve upon:
* Decouple raw processor from the monolithic software executable so that updates to the RAW camera component to add new cameras can be made without requiring huge downloads or reinstallation of a new software program but simply updating a few DLLs and files.
* Improve performance of the Develop panel. It is extremely slow on my laptop running 32bit Windows 7 and 3GB of RAM with dual core processor (pre-Core duo). 8 to 10 seconds for the "loading" message to disappear per image no matter how often I have loaded or edited the image. No caching is being done at all.
* On my higher powered Desktop (Quad Core2 processor/4GB RAM,Windows 7), Adobe Lightroom frequently will start behaving strangely after only a few hours of running. It seems like it is leaking resources or something because eventually functionality will start failing. Specifically, right clicking on images will no longer bring up menus for example. If i shutdown and restart the application, the problem goes away.
* Photoshop-like healing brush. Many times I want to "brush" over areas of image defects but the only choice in Lightroom is the healing tool which always creates a circle and does not allow "brushing". This only works if the defect is a spot and not an irregular area.
* Adjustment with Arbitrary Mask tool. Bibble 5 has this nice concept where you can mask out a section of an image and then apply adjustments to it without affecting the rest of the image. You simply draw a mask and then you can apply adjustments to it. The only option in Lightroom is to select the "Mask" option but that leaves the decision of where exactly you want to mask to Lightroom which only uses edge contrast to determine masking area.
* I'd like a way to tell Lightroom to update the metadata (write out) on all images that are out of sync. Right now the write metadata function will write out metadata to all files whether or not it is required. This means that it is inpractical to try to update your entire catalog as tens of thousands of files will be written to and not just those that are out of sync. This is very important as a way to preserve editing metadata in case of loss of the Lightroom catalog.
* Option to write import metadata to imported files. For example, I have an import metadata for copyright and keywords and I want the imported JPG or DNG files to permanently have this metadata so that even if individual files are copied my copyright and other metadata are preserved with it.
* Option to append text labels to automatically generated import destination folder names. So for example, I can still import into date based directories but append a description to help me remember what the folder contains when I'm later browsing it. Right now it is either/or. You can either choose the name of the import folder destination OR you can have the software generate one for you.
* A google-type search box at the top of the library panel so that ad-hoc searches can be done without having to fool around with the filters. Everybody is used to a single search box for simple textual searches.
* some way to filter images by whether they have been exported previously or not
* Please support lens and shooting information for Sony DSLRs in both JPG and RAW files. Also support 3rd party lenses on Sony DSLRs without assigning the wrong Minolta lenses to them. I want to be able to see both Lens name, max aperture, focusing distance (if available) etc...
* Some way to edit the Shooting lens information to support lenses which are not known to Lightroom, and if suggestion above won't be implemented, some way for the user to edit the lens id --> mapping table so that I can properly map my own 3rd party lenses.
* Facial recognition/tagging option. Some way to have Lightroom apply people tags after I have tagged representative images. Handle multiple people in a scene.
* Automatic (batch) export of images on schedule. I would like a way to configure Lightroom to automatically generate particular export configuration of all my images in a catalog (or some defined subset) such that new files or files that have been edited since last export are automatically exported on a schedule even if Lightroom is not running. Perhaps a Lightroom batch service. This is so that I can always have up to date processed versions of my images for use in my media center display. I would like to configure the Lightroom batch service to run weekly at say 2am every day, run a particular export function and export all new or modified images to a network share accessible by the media center. That way, I can always have access to cropped and edit images without manually doing exports all the time or having to remember which files I've edited and then export them. Also by doing this at off hours it would not slow down my computer while I'm using it.
* Better profiles for Sony DSLRs and support for their picture styles the same way that Canon and Nikon camera are supported.
* Teethering support for Sony DSLRs that have this feature
* Support for parametric plugins -- Plugins that do not require the image to be exported before running.
* Simple support for "picture frames" when exporting. Some way to apply a frame to an image as part of export with a dozen or so frames included and a way for 3rd parties to create more.
* A better way to safely share catalogs or pictures between multiple computers/users in a networked environment.

Did these come to you all at once, or have you been saving them up for a while?
Anyway, Adobe *should* be able to handle long lists of FR, but another option is to break them up and submit them for voting on the new FR/Idea site that will shortly replace this one: (It was really hot for a while, but has cooled down lately...)
http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightro om
HopeSpringsEternal2008 wrote:
I love the Adobe Lightroom Application...
Me too, and continue to push for improvements as well...
HopeSpringsEternal2008 wrote:
* Decouple raw processor from the monolithic software executable so that updates to the RAW camera component to add new cameras can be made without requiring huge downloads or reinstallation of a new software program but simply updating a few DLLs and files.
They are already decoupled - you can update ACR independently for new camera support, however it's released at about the same frequency as Lightroom itself, so that doesn't help much. Perhaps this should be reworded: "Provide more timely ACR updates..."
HopeSpringsEternal2008 wrote:
* Improve performance of the Develop panel. It is extremely slow on my laptop running 32bit Windows 7 and 3GB of RAM with dual core processor (pre-Core duo). 8 to 10 seconds for the "loading" message to disappear per image no matter how often I have loaded or edited the image. No caching is being done at all.
I've been complaining about this for a long time - ACR cache is worthless for me too - if dev image not in RAM cache, takes same amount of time to render whether in ACR disk cache or not. Some say ACR cache speeds things up for them - perhaps you need to *believe*...
PS - After new motherboard upgrade, this went from 15 seconds to 3 seconds average.
HopeSpringsEternal2008 wrote:
* On my higher powered Desktop (Quad Core2 processor/4GB RAM,Windows 7), Adobe Lightroom frequently will start behaving strangely after only a few hours of running. It seems like it is leaking resources or something because eventually functionality will start failing. Specifically, right clicking on images will no longer bring up menus for example. If i shutdown and restart the application, the problem goes away.
Yep - Lightroom still has some leaks - gotta restart it from time to time...
HopeSpringsEternal2008 wrote:
* Photoshop-like healing brush. Many times I want to "brush" over areas of image defects but the only choice in Lightroom is the healing tool which always creates a circle and does not allow "brushing". This only works if the defect is a spot and not an irregular area.
+1 vote - arguably the most desired addition to the dev tools. I bet Lr4 will have this (no inside info though).
HopeSpringsEternal2008 wrote:
* Adjustment with Arbitrary Mask tool. Bibble 5 has this nice concept where you can mask out a section of an image and then apply adjustments to it without affecting the rest of the image. You simply draw a mask and then you can apply adjustments to it. The only option in Lightroom is to select the "Mask" option but that leaves the decision of where exactly you want to mask to Lightroom which only uses edge contrast to determine masking area.
+1 vote - this is one of my highest hopes for Lr(4) too: sophisticated auto-masking + manual masking: to apply to all or at least most adjustments...
HopeSpringsEternal2008 wrote:
* I'd like a way to tell Lightroom to update the metadata (write out) on all images that are out of sync. Right now the write metadata function will write out metadata to all files whether or not it is required. This means that it is inpractical to try to update your entire catalog as tens of thousands of files will be written to and not just those that are out of sync. This is very important as a way to preserve editing metadata in case of loss of the Lightroom catalog.
Frequently requested - some use pre-startup database query + plugin to make collection in the mean time (I dont).
HopeSpringsEternal2008 wrote:
* Option to append text labels to automatically generated import destination folder names. So for example, I can still import into date based directories but append a description to help me remember what the folder contains when I'm later browsing it. Right now it is either/or. You can either choose the name of the import folder destination OR you can have the software generate one for you.
RC Importer supports this - its an import plugin that bypasses the import dialog box - not for everyone...
HopeSpringsEternal2008 wrote:
* A google-type search box at the top of the library panel so that ad-hoc searches can be done without having to fool around with the filters. Everybody is used to a single search box for simple textual searches.
Maybe the seeds of a good idea here, but may be worth some refinement/clarification - what would be searched? Would special syntax be supported? Personally, I mostly hate all 1-box search fields, because one never knows what's being searched and how, e.g. does it search the whole catalog?, is it case sensitive? On the other hand, I get the convenience factor... - I think if accompanied by help and/or the ability to pop up a dialog box for refinement or options, this might make a nice addition. Along these lines, I sometimes think a quick-smart-collection would be nice too - for when one wants to search 2 text fields, instead of just one. I keep a temporary smart collection just for this purpose, but still...
HopeSpringsEternal2008 wrote:
* some way to filter images by whether they have been exported previously or not
Change detecting export plugins have mostly solved this for me (and publishing for some folks), although adding export info (and metadata change info) to catalog for searching / sorting still sounds like a good idea to me...
HopeSpringsEternal2008 wrote:
* Automatic (batch) export of images on schedule. I would like a way to configure Lightroom to automatically generate particular export configuration of all my images in a catalog (or some defined subset) such that new files or files that have been edited since last export are automatically exported on a schedule even if Lightroom is not running. Perhaps a Lightroom batch service. This is so that I can always have up to date processed versions of my images for use in my media center display. I would like to configure the Lightroom batch service to run weekly at say 2am every day, run a particular export function and export all new or modified images to a network share accessible by the media center. That way, I can always have access to cropped and edit images without manually doing exports all the time or having to remember which files I've edited and then export them. Also by doing this at off hours it would not slow down my computer while I'm using it.
Yes, better export management would be welcome. Export Manager might help you (if you have multiple export destinations to update), but its not a panacea... Many of us ultimately "consume" our photos outside Lightroom, having the consumption copies kept up to date more fluidly would be good. Using change detecting export plugins (along with export-manager) and/or publishing helps..
HopeSpringsEternal2008 wrote:
* Support for parametric plugins -- Plugins that do not require the image to be exported before running.
Yep - much room for plugins to get better integrated with Lightroom proper, to participate in image enhancement, as well as other things...
HopeSpringsEternal2008 wrote:
* Simple support for "picture frames" when exporting. Some way to apply a frame to an image as part of export with a dozen or so frames included and a way for 3rd parties to create more.
That would be nice. Although support for 3rd parties to add frames *upon export* already exists (export filter plugin + export post-process actions), as well as adding text overlays and such. But since its not built into Lightroom, one has to find them and configure them... And there is no good way to preview them in Lightroom... I think this would go nicely with the previous request - ability to feed image data to plugins for preview in Lightroom. Even if these updates were not built-into the dev module - i.e. weren't kept updated automatically whilst editing - just being able to click a 'see final' button or have it rolled into the build-previews function, so one could have post-process imaging plugins (with preview before export) - might be a nice compromise until true imaging plugins (that fit into dev pipeline) are supported.
The end - for now...
-R

I have a dual monitor setup. When I paste develop settings from one image to another, Lightroom switches the active window.

Strange problem. Lightroom 5.5. Windows 8.1. Dual monitor setup.
I'm processing a large batch of photos. I have Monitor #1 set as my main develop window, with Monitor #2 set only to display a larger version of the image I'm working with. If I copy the develop settings off of one image and try to paste them onto another image, Lightroom will switch from Monitor #1 to Monitor #2 as the main develop window, and will not display anything on Monitor #1.
If I then try to paste develop settings onto another image on Monitor #2, LR will then display a larger version of the image I'm working with on Monitor #1.
To work the way I want to, I have to continually drag my develop window back to Monitor #1 every time I try to paste develop settings onto a new image. How can I make this stop?

I just tried what I think you’re saying you’re doing and I don’t have the problem with LR 5.5 on Windows 7 SP 2.
Does the same thing happen whether you use the key shortcuts vs the Settings / Copy/Paste options on the menu?
I ask this because if you’re using the keyboard shortcuts, maybe you have some display-manager program that has bound itself to the Ctrl-Shift-V (paste settings) to the function of move-to-other-monitor which would do at least part of what you describe.
You can also test this theory by doing a Ctrl-Shift-V with an application other than LR as the active window and see if it moves. I suppose Ctrl-Shift-C might also play into it so try both of these hot-key combinations with a program that isn’t LR.
If none of this sheds any light on the situation, then give a more detailed description of the low-level functions you’re doing to accomplish the copy-paste of settings, so someone else could replicate the steps exactly.
Specific detailed steps, like:
left-click on source photo’s thumbnail in the filmstrip
press Ctrl-Shift-C to copy the settings
click Check-None
enable the white-balance and calibration checkboxes
click Ok
left-click on destination photo's thumbnail in the filmstrip
click on Settings / Paste Settings in LR’s menus to paste the settings to the selected photo

Lightroom 4 Bug: can only see photos in Library mode, not develop mode

This may be related to other imported catalog bugs, but does not seem to be quite the same. In Lightroom 4, with an upgraded Lightroom 3 catalog:
1. Select a photo in Library mode.
2. Click on Develop to go to Develop mode
Screen shows "No photo selected". I cannot edit photos in Develop mode.
I can see and edit photos that are found in smart collections, but not photos that are simply in my collections from 2012, 2011, etc. folders

This happened to me, too, after importing a couple older LR3 catalogs (upgrading/consolidating). I could see the photo in Library module but when I pressed "D" (single photo selected) I was getting the "no photo selected" error message--for every photo I tried. I wasn't able to open any photos at all in the develop module. (These were photos that were fine before installing LR4 and upgrading.) Photos were from imported LR3 and LR4 Beta catalogs.
I restarted and everything seems ok--for now!
So if you come across this thread with this same issue, restart and see if that helps. (Before restarting LR I optimized as suggested above, which did nothing for the "no photo selected" issue. And this isn't related to the parent folder issue, I left my photos in the same place and didn't have more than 3k photos in any of the parent folders. I read in other threads that people had the issue again after importing other catalogs. I'm about to do that so I'll report back.

Another XAV-72BT BUG

I've checked the format of the JPG files that don't display when playing the MP3 files in the same folder. None of them use the progressive JPG format. And these same JPG files do display if I select 'Images' instead of 'Audio' from the XAV72bt user interface. This appears to be a software bug to me. I'd very much appreciate it the appropriate support team would take a look at this.
Thanks

I've discovered another design problem withthis unit. I recently ripped a video from a music DVD to an MPEG4 file. The format of the file is well within the limits given in the user's manual but this head unit will not play it I read the disclaimer in the user's guide indicating that there is no guarentee that a file can be played even if it is within the limits given.
The real problem is with the USB menu. The USB drive contains many audio files and this one video. From the menu I selected video and the unit quickly responded with "no playable media found". The problem is that there is no immediate recovery for using this USB. There is no way to go back and select for audio files. No user menu options appear. If I unplug the USB and plug it back in, nothing is changed. The unit recognizes that a USB device has been reconnected but it remains in video mode. I can probably take the USB back to my computer and delete the video file but that seems to be a poor solution. This is yet another example of how this unit seems to have gotten to the market before it was ready. See my other posts in this forum.

Another preview related bug???

Recently I reported an issue (bug) with preview and
non-auto-update variable. See
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=65&catid=449&threadid =1364202&enterthread=y
I have another issue with preview:
- I update text within the body of a topic (I DO NOT toch
header/footer that are set in template)
- Do a preview
- Close/save topic
- RH comes up with dialog saying:
"This topic was created from a template and the header of
footer has been modified.
What would you like to do:
- Apply this modification to all topics created from the
template
- Apply this modification to this topic only"
Again, I never touched header/footer.
Can anyone using 7.0.2 confirm this behavior?
Herman

> See if this helps. Suggests turning off auto update.
This doesn't help because a preview updates the date
variable, even when auto update is set to off. When the topic is
not edited, RH doesn't prompt to save the topic and consequently
the updated date isn't saved . With edits, save dialog comes up and
additionally header/footer dialog because date in footer has
changed.
See also my earlier post here:
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=65&catid=449&threadid =1364202&enterthread=y
Secondly, I really need it on auto because I'm running
everything through batch files
I think that we need an option like Colum McAndrew described
in the thread you're referring to. An option not to update a
template variable when applied to a topic, or when previewing a
topic.
Herman

Another -C check bug

Here is an interesting run-time check bug. I have an internal subroutine where an array index is changed in another internal subroutine by host association. The run-time check misses the fact that the index has been updated. Here is an example. It seems to relate to the use of a derived-type as well.
program test
implicit none
type my_type
integer, allocatable :: type(:)
integer :: size=0
end type my_type
type(my_type) :: obj
allocate(obj%type(10))
call sub1()
contains
subroutine sub1()
call incr()
write(*,*)'obj%size=',obj%size
obj%type(obj%size)=1
end subroutine sub1
subroutine incr()
obj%size=obj%size+1
end subroutine incr
end program test
Here is my result:
obj%size= 1
****** FORTRAN RUN-TIME SYSTEM ******
Subscript out of range. Location: line 14 column 12 of 'test2.f90'
Subscript number 1 has value 0 in array 'TYPE'
Abort

OK, I figured out the problem. I am getting the __SUNPRO defines, but used them in a way that fpp did not substitute them. The problem I have not is that -xpp=cpp does not work because the flag -Y<path> is given, which is not a standard cpp flag, and I just get an error message.
I am guessing that Sun cpp accepts a -Y flag, and sun Fortran assumes that it is standard. If so, maybe a good solution would be just to distribute Sun's cpp along with fpp. Another problem is that cpp is called with a specific path, so there is apparently no way to override it. So, it looks to me like this is a bug. But, it seems unlikely that nobody would have noticed it, unless everybody sticks with fpp, or if the -Y flag is new in this release.

Another spanned clips bug?

I've read that Adobe recently fixed a spanned clips bug. Well here's another one (at least on my system):
I have several spanned clips recorded with my Sony FS700 (MTS-files in AVCHD-container) and my Panasonic P2-camera (P2 MXF-files). When using Adobe Media Encoder (AME) to convert to ProRes, the spanned clips are joined right, but AME encodes the same material several times. The result is several copies of the exact same encoded material written to disk.
Here's how it works:
In one case, my camera had split my recording into 4 individual files. I expected AME to a) either join them and output one long file or b) not to join them and just output 4 individual ProRes files. Instead I ended up with 4 joined identical 32 GB files on disk. I did it again and noticed that AME actually encoded the same material 4 times in a row. What a waste of time and space …
When using Sony MTS-files, AME creates different filenames for each clip (0001.mov, 0002.mov, 0003.mov. When using Panasonic MXF-files, AME put _1, _2, _3, etc. at the end of the filenames.
In my opinion, AME should have a tick box where you can chose "join spanned files" or not. If it had such a box, it would chose to leave it off most of the time. That way it would be much easier to check if AME has converted all the files or not. It would be 32 files in = 32 files out, not 32 files in = 2 spanned files + x small files out … Nowadays, I have to doublecheck everything before formatting my cards.
I'm using Adobe Media Encoder v. 7.2.0.43 (64-bit) and OSX Mavericks 10.9.1 on a late 2013 Macbook Pro 15-inch Retina 2,3 GHz i7 16GB RAM 512 SSD.

Jim Simon, let me explain:
1. When I drag MTS-clips into AME, the software generates several copies of the same spanned clip during conversion. (They pop up in the queue while AME is converting).
2. When I drag MXF-clips into AME, the software generates several copies of the same spanned clip before conversion. In the screenshot, which was taken after conversion, you'll see that the file numbers begin with 0018, 0019, 0019, 0019, 0019, and then jump to 0023, 0023. Well, what I dragged in was 0018, 0019, 0020, 0021, 0022, 0023, 0024 etc. So I believe AME skips filenames that are elements in a spanned clip, and then multiplies the the process all by itself. But, yes, I could manually examine the queue and erase identical clips after I drag files in. But that is just not a good way of working …
So, AME behaves differently with spanned MXF and MTS-files, but none of them are handled right.

Another iOS packager bug

Came across another bug in iOS packager. In my project I have a function looking like this:
private function sample():Object
var iValue:int = 10;
return false ? iValue : null;
It correctly returns 'null' if packaged in ipa-debug-interpreter, apk-captive-runtime modes or if running in ADL. But it returns '0' if packaged in ipa-ad-hoc mode. I had to spend a whole day to figure out where is the problem. This is not the first type cast issue I came across. And it takes a lot of effort everytime to debug (10 minutes to build the project!). I'm breaking a dead line giving my customer an excuse that 'Adobe packager for iOS does not work right'. Which sounds like total BS of course. Adobe, please, get this straight. It is hard enough to develop with AIR for mobile. Bugs like this one make it much worse. Either way, I'm planning to advocate for using native tools in our next projects.

I'm still using AIR 3.2. Unfortunately, I don't have a chance to try latest AIR 3.4 at the moment. But I will check the same code when I update AIR SDK.
The code I posted is not a real code of course. I had to strip some logic and modify operators a bit. But I had hoped the bug would still reproduce. From my experience, most of the iOS packager bugs are caused by the rules of type casting that are not AS3 compliant. I have an impression that type casting rules used in the packager are more like classic C type casting rules. As the result, same code executes differently on iOS and Android|Windows. And it has being a huge problem for me.

Another Mountain Lion bug

Hi all.
I have discovered another bug in Mountain Lion.
I have Adobe Creative Suite 6 Installed (including InDesign CS6) and have had to also install my old InDesign CS4 to work with clients that use it.
I have chosen an InDesign document that was created in CS4 (and hasn't been opened in CS6) and right clicked - 'Get Info'
Changed the 'Open With' default from CS6 to CS4.
So far so good.
I then clicked "Change All", I get the confirmation message box, and as soon as I click "Yes, please change All to CS4" It immediately changes the default setting back to CS6.
If I change the "Open with" default for a file to CS4, and leave it at that, it works fine for that file,
but the "Change All" function seems to be broken.
The Change All function seems to work fine on Leopard and Snow Leopard. I haven't tried Lion, but I suspect that is where the trouble starts. (It has with other bugs.).
Any light that any of you could shed on this, or even fixes involving the Terminal and the Unix commands, would be greatly appreciated.
Thanks for your time.
Also this forum has a problem with the question form.
below it has asked me for my product - "Macbook Pro"
Then Operating System - and it gives me a choice of iOS from 4 to 7
As far as I know, Apple hasn't inflicted mobile phone operating systems on computers. yet.
perish the thought.

Change All works quite well for me for every version of Mountain Lion and on several different computers. It's not an OS X problem. You have some other problem such as possible file permissions' issues. You might try repairing ACLs and permissions in your Home folder by using the "resetpassword" Terminal command that you may access via the Recovery HD. You will not be resetting passwords, btw.
Reset User Permissions and ACLs in Lion/Mountain Lion
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
From the Utilities menu select Terminal. At the Terminal prompt enter: resetpassword. Press RETURN. When the window opens select your startup drive where it says "Select the volume containing the user account:" At the bottom of the window you will see, "Reset Home folder permissions and ACLs." Click on the Reset button.

ANOTHER Lightroom 5 Bug??

Similar Messages

Maybe you are looking for