Bug Report: develop settings in tethered shooting

When shooting tethered and choosing "Previous" as my development setting on the tethered control panel every previous setting is applied EXCEPT process version. LR3 will apply PV 2010 even when my previous PV was 2003.
Mac os 10.5 - Canon 5D

Similar Messages

[Bug] Pasting develop settings from P2010 to P2012 reset sliders

I may have found a nasty bug.
I wanted to show how amazing is the new clarity slider between two versions of the same image, one with Process 2010 and another with the new one.
Realizing that I slightly changed color between the two (white balance for sure and maybe some other color treatment settings), I decided to copy those two settings from the P2012 one and paste on the P2010 one.
1. Copy settings from the fist image
2. These are the settings for the P2012 image
3. These are the settings of the P2010 version BEFORE pasting settings from the newer one
4. These are the ones AFTER the paste.
Basic settings have been reset just by pasting White Balance and Treatment (color).
Process version was set on 2012 without asking to do so.
You can get the same result even by copying the White Balance alone, which is not a P2012-dependent setting.

Lr 4 Beta always syncs process version when doing a sync. When syncing a 2010 to 2012 image, the Basic panel settings will be converted. This is the reason why this is happening.
That said, we're investigating more fine-grained approaches going forward.

Setting and holding White balance during tethered shooting

I came to Apeture from Capture One Pro. I used Capture when working for a photo studio, when I started shooting for myself I went with the much more affordable Apeture. I have been very happy with the workflow, but Apeture seems to be missing one of most basic settings for tethered shooting, setting and maintaining custom gray balance. I realize that I can shoot a frame with a gray card and white balance that frame, but the following frames revert to the pre-whitebalanced color settings. In Capture One, I would balance my first frame to a gray card, even add a manual tweek, and all subsequent frames would follow the new color settings. Perhaps there is a setting I have missed, some sort of automatic inheriting of the last frames adjustments. I realize that it is easy enough to adjust my color settings after the fact, but my color is off during shooting, and clients are not always able to envision the finished product. I really hope I'm missing something, because it's the most important feature to me for shooting tethered, right after the ability to shoot tethered.

It forces this yucky uber warm white balance. Just to make sure it was not shot that way, I then selected "as shot". It immediatly went to the color of the shoot and looks great.
When you select 'As Shot' do the Temp and Tint settings change? How about other settings, do any of them change? Just trying to determine what is actually causing the color change.
Did you try creating a new preset with the same settings, and see how it behaves when you uncheck White Balance? The original preset file may have been corrupted (i.e. damaged) and resaves are not fixing it. If this doesn't resolve the problem then it is likely a bug with tethered mode operation. Please let us know.

BUG report - Inconsistent IR settings in Builder

Apex 4.0.2
Most of the reports used in the App Builder have been converted to use Interactive reports which is great. But I find that the IR settings are not consistent across all the reports. I had reported this during the tryapexnow.com beta phase. Now that we can use the new apex_application_install API to load up the Builder apps into our own workpace so we can review how they are built, the Region Utilities > Update Interactive Report Settings page shows this. Or just run the query
select
page_id, name, allow_save_rpt_public, show_finder_drop_down, show_display_row_count, show_search_bar, show_search_textbox, show_actions_menu, show_select_columns, show_rows_per_page, show_filter, show_sort, show_control_break, show_highlight, show_computation, show_aggregate, show_chart, show_notify, show_group_by, show_calendar, show_flashback, show_reset, show_download, show_help
from apex_040000.wwv_flow_worksheets
where flow_id=4000My main annoyance is the "Save Report Public" checkbox. The IR saved report list shouldn't be cluttered with all the report settings saved by all the workspace developers.

Please submit an official bug report to Adobe at:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Alexander.
Canon EOS 400D (aka. XTi) • 20" iMac Intel • 12" PowerBook G4 • OS X 10.4 • LR 1 • PSE 4

Orientation is not reporting in Develop Settings

I can't seem to read the orientation value in the develop settings - always comes up nil (most other settings reporting OK).
Rob

Thanks for your reply. I appreciate it
i think we r missing ' in the statement
select replace(msg, '<'<') msg from testmsg
so, i tried this
select replace(colname, '<''<') from tablename(updated too)
but its still the same. It is good in database, if i do export to csv , i am having the column value '<' included in it.example "abc<ggggg"
but in the report its displaying just "abc" .

Bootcamp Version 3.1 --List of bug reports for the Development Team to fix.

Please create a list of bug fixes for the Development Team to address in the next version of Bootcamp (e.g., 3.2). This thread assumes that all users are presently running Bootcamp 3.1:
1. Sound should not be muted every time a user reboots a newer MacBook laptop using Windows 7 Ultimate, 64-bit. My sound is always muted when I load Windows 7 Ultimate, and I have to manually turn it on each time.
2. Left and right clicks on the trackpad should work out of the box using Windows 7 Ultimate, 64-bit. My left click operates a little less than 50 percent of the time -- i.e., I click it and nothing happens. I had to switch to "tap to click" as a workaround, however, I prefer the good old solid left click.
Please step right up and add to the bug report list so that the developers have a checklist of issues that need to be fixed. When the bug report list has grown to a respectable size, I'll send an official letter to the C.E.O. to facilitate the bug reports reaching the development team.
Message was edited by: lawlist

lawlist wrote:
Please create a list of bug fixes for the Development Team to address in the next version of Bootcamp (e.g., 3.2). This thread assumes that all users are presently running Bootcamp 3.1:
1. Sound should not be muted every time a user reboots a newer MacBook laptop using Windows 7 Ultimate, 64-bit. My sound is always muted when I load Windows 7 Ultimate, and I have to manually turn it on each time.
2. Left and right clicks on the trackpad should work out of the box using Windows 7 Ultimate, 64-bit. My left click operates a little less than 50 percent of the time -- i.e., I click it and nothing happens. I had to switch to "tap to click" as a workaround, however, I prefer the good old solid left click.
Please step right up and add to the bug report list so that the developers have a checklist of issues that need to be fixed. When the bug report list has grown to a respectable size, I'll send an official letter to the C.E.O. to facilitate the bug reports reaching the development team.
Message was edited by: lawlist
FWIW, I don't have the symptoms you describe. So I think before you call a symptom a "bug" I think you should confirm that it is indeed a "bug" and not a configuration, software, or hardware issue caused by something such as incorrect installation, incorrect setup, or any other third party or user caused action.
Also, FWIW, I don't think this forum is intended to be used as a survey for gathering "bugs". Apple has an official feedback page where they gather user experiences such as yours. I think if you post your "bugs" there they will get faster attention than posting them here in this user-to-user help forum.

The new Synaptics UltraNav: a few workarounds and minor bug report.

I only wanted to file bug report, but then decided to also share what I did with my touchpad configuration to make it more convenient for me. I have Thinkpad T540p so this might work differently or not work at all for other notebooks.
#1 Regedit
Configure as much as you can using UltraNav tab in mouse settings dialog. (It is mostly self-explanatory.)
If you didn't find some option, start regedit (using Win+R) and navigate to
HKEY_CURRENT_USER\Software\Synaptics\SynTP\something
This something is TouchPadSMB2c on T540p but you can find one you need by changing something in settings dialog and looking for changed values in regedit.
All the touchpad configuration registry keys are there. You need to relogin to apply changes made there.
But it might take a lot of trial and error to find out how these registry keys work.
#2 3-finger tap
As for me, I prefer tapping over clicking. While 3-finger press option is in settings dialog, 3-finger tap is not. But you can change it.
Set whatever option you want for 3-finger press. Then go to regedit and copy value from 3FingerPressButtonAction key to 3FingerTapAction.
#3 Button sizes and locations
You can change button bounds with keys like LeftButtonZoneX where X is L for left, R for right, T for top and B for bottom bounds. 0xFFFFFFFF ultimately means "unlimited in that direction". For finding other values defaults might be helpful. Trackpoint buttons keys are SlaveSomeButtonZoneX.
What for?
First, trackpoint buttons can cover the whole trackpad only when trackpad itself is disabled. By changing button sizes manually you can overcome this restriction. It is useful because trackpad does not respond well to pressing corners and when buttons cover it all you can press it somewhere in the middle.
Second, the same corner pressing problem exists for normal trackpad buttons so it is more convenient to use multi-finger taps or clicks. You can still hold trackpad pressed with one finger and use yet another finger to move mouse pointer.
At the same time when you tap or press with multiple fingers and one of them touches one of the buttons you get that button pressed instead of whatever you intended. It frustrated me a lot when I got context menu popups while trying to close chrome tabs with middle mouse button click. The solution is to set top bounds for left and right buttons to zero.
BUG (With the latest UltraNav drivers from support page)
When the middle trackpoint button (used for scrolling) is enabled, it is always enabled, no matter if you are using trackpont or touchpad. Left and right trackpoint buttons are properly disabled when you don't need them.
Even if you disable trackpoint completely without disabling that middle button first, it will remain enabled and will do nothing. (Blocking single- and multi-finger presses that touch it.)
I could not find a way to fix that problem with regedit.

Any problem can get official response and follow-up through a SR on Metalink/MOS (if you have a DB support contract), else you can post here and hope someone from development picks it up.
Regards,
K.

How do i use the bug reporter in ios 8

im trying to use the bug reporter for the beta ios 8 but i dont get to input anything. Maybe i dont understand how this works,so can someone please explain.either way i figure i should say somthing now.
-the infinity blade 2 app does not load
-my settings button doesnt load all the time,
-most of the apps dont load the first time i open them,if i switch to another menu then back it will load.
-just now i shut off my phone, plugged it into the charger. My phone then turned itself back on and had me reactivate it.
-the "sample" button in the ibooks app doesnt seem to do anything either
-most of the time scrolling down on anything rather large(e.g.songs,articles,facebook) there is alot of skipping or lagging effect
-when on safari i turn my phone sidways and it totally messes up where things should go and it wont return i have to exit and close to fix
anyways id just thought id put that out there

You need to ask this question in the Developer's forum, which as a registered developer you have access to. If you're not a registered developer, then you have no business messing with iOS Beta software, & discussing such, even bug reporting, is PROHIBITED in this public forum.
But, as a registered developer, you already knew that, correct?

Canon 5d Mark III and Lightroom 4.3 tethered shooting issues.

I bought a new Canon 5d Mark III and upgraded my lightroom to 4.3. I have been having issues shooting tehtered. I'll shoot and get some frames coming in and when I start plugging away the program bar will spin and I'll only get a few grey frames and it just kind of freezes. I don't know what to do.

LR4.3 was supposed to improve Lightroom's built-in tethering, but in my experience it still has some reliability problems - especialy in recovering from broken connections (not just unplugging USB but also if the camera loses power by sleeping or when changing a memory card).
Sorry if some of this is basic info, but I'd recommend you try a different USB cable - the cable end that connects to the camera is easilly damaged in a way that makes a connection possible, but unstable (I strongly recommend finding a cable with a 90 degree downward bend at the camera plug). Also, we often have to send a camera body in to have the USB port serviced. Canon has begun to provide a small rubber boot to reinforce the USB connection at the port, but they won't sell the part outside of a repair service. Be sure to use some kind of stress-relief for the cable at the camera. Tethertools sells one, but I've made mine DIY with a little string and a small binder clip... nearly free. Finally, be sure your cable is less than about 15 feet. If you need to go longer, I've successfully tethered with two cheap powered repeaters from Monoprice, but no single link should be over 15 feet.
Oh yeah, also set your camera to not sleep for a long time.
Beyond all that, is using EOS Utility for capture and LR Auto-import a viable option for you? It works very well for me. I use the Apple "Image Capture" app to tell my system to launch EOS Utility whenever the camera is connected - and set EOS Utility to launch into remote capture/camera control mode. It's very stable and recovers from disconnects or camera power loss and the remote camera control/live view can be pretty handy.
Another plus is that if you do need to disconnect USB and shoot to card, you can just copy new images from the card to your watched folder and they are imported to Lightroom with the same settings and location.
The only downsides for me is that there is no way to have a crop apply to new images using auto import -- and I have to re-save my develop preset each time I make a change. Using the "Same as Previous" option under develop settings in native tethering is so great for this and I'd love to see a similar option added to auto import.
Hope this helps.
-Andy

LR2 - Auto Import develop settings won't stick.

As the subject says, in LR2 changes made to the develop settings preference in the auto import settings dialogue do not stick. I can select a different develop preset, but after closing the settings dialogue, new images import with the original preset. If I open the settings window again, the develop settings preference has been reset to their original state.
I've tried two computers and have the same result on both. Trashing prefs does nothing, but creating a new catalog seems to reset the auto import prefs dialogue, but whatever develop settings I select becomes fixed and unchangeable.
I use LR's auto import feature to work tethered with my MF digital setup on every project - it is crucial to my current workflow. This bug is small, but significant and will probably have me going back to V1 until I can find a fix so any help is appreciated.
Thanks,
Andy
(oh yeah, both systems are intel macs -- an iMac and a macbook pro -- and are up to date running osX 10.5.4)

Yes, I get the same thing with the sliders being greyed out. Funny thing is that the sliders *are* set exactly as in my preset and when I click 'yes update' to 2010 standards, the settings don't change but only the sliders become accessible. The thing is that I really don't want to be doing that with every import, even if you can do the whole batch at once. What I don't understand is that when I import with the preset turned off and apply it in Lightroom's Develop Module, it accepts it without a problem but that when I use the same preset on import, it won't work properly.
Now what the poster in the other thread said was:
"When I saved a new preset and selected to also save the process version, a line in the preset was created: ProcessVersion = "5.7". When I cut and paste that into all my other presets then the sliders were all active when I used them."
I have no idea what he is talking about or how one would do that. When I create a preset I simply click the + sign and in the pop up window select what I want, give it a name and that's it.
Edit: Sorry, I apparently overlooked the Process Version box in the preset panel! Must have been a case of not seeing the forest for the trees. Problem solved. Thanks.

Copy-Pasting crop settings also affects other Develop settings?

I noticed the following behavior in my Lightroom 4.3. Let's say I have two almost identical pictures. Both have their Develop settings reset, no keywords and store some GPS info (so in the flimstrip both pictures have a "geotag" icon overlaid on them and no other icons).
Now, I go to Develop screen and crop the first picture. I leave other Develop settings untouched. This makes a "crop" icon to appear on the first picture in the filmstrip. All works as it should.
After that I ask Lightroom to copy the Develop settings from the first picture. In the selection dialog I leave everything unchecked besides the crop settings. I.e. I want to copy crop settings only, nothing else. Then I immediately paste these settings over the second picture. Expectedly, the second picture gets cropped in exactly the same way as the first one. It also acquires a "crop" icon in the filmstrip. However, in addition to the crop icon it also gets a "+/-" icon, as if some other Develop settings got changed by the paste as well. A quick inspection shows that all Develop settings (besides crop, of course) remain at their default values.
I wonder why the second picture acquires that "+/-" icon. Is there some hidden Develop setting that gets affected by my paste, even though I explicitly asked Lightroom to copy crop settings only? Or is it just a user-interface-level bug?

I reported this strange behaviour a year ago already for LR 3.4: http://feedback.photoshop.com/photoshop_family/topics/lightroom_3_4_1_wrong_activation_of_ badge_has_delevop_adjustments. LR 4.3 seems to have the same bug (at least I think it is a bug).
As far as I know, no "real" development settings are affected by this bug, however an internal flag for "has development settings" seems to be set when the "+/-"-badge appears. This means that such images are found by smart collections with "has adjustments = true". So it is not just an user-interface-level bug.

BUG: Copy / Paste settings

This bug has been reported in various forms. But I'd like to chime in.
I'm finding that the set of develop settings I copy are not pasting correctly onto other images. Sometimes settings I have NOT checked are pasted; other times settings I HAVE checked are being pasted. The bug does not seem to be related to the specific combination of settings checked and unchecked. Particularly I've found that copy/pasting UNCHECKED white point settings will not paste. UNCHECKED crop will paste. It's quite frustrating. I have not found a work around.
I am using LR 3.2 RC.

Mark, you can report this here. This would be most helpful. This forum is now mostly for user help rather than technical issues.

How many bug reports must I submit before I get a patch?

It seems that at every turn, PRE9 on my mid 2010 MacBook Pro with 8GB RAM, crashes. Editing titles, scrubbing through a video, exporting...
Are the bug reports I am submitting getting there? I wanted more flexibility than iMovie, but more and more I find myself back in there to produce simple videos.
The footage I am working with are either from a Canon 7D or a Kodak Zi8. Both seem to have issues.
This is a paid for, and registered copy of PRE9 (otherwise I couldn't work with Canon 7D video at all).
Thank you,
-Joe

Video from your Kodak may be iffy -- but the video from your Canon EOS should work perfectly in the program, if you're using the proper project preset.
Have you ensured that your Premiere Elements project is set up to match the specs of your camcorder's video? This setting is specific to your camera -- it is NOT AVCHD! (It also doesn't hurt to install your camcorder's software on your computer, since it sometimes includes important codec information.)
And note that this camera shoots video in up to 6 different frame rates and specs -- so you must ensure that your project settings match whatever settings you're using to create your video. This match is vital to a successful project. (My books, by the way, include a chart for figuring out exactly which project presets work with which camera source and setting.)
BTW, how powerful is the processor in your Macbook and how much RAM and free space do you have on your hard drive? Remember that most laptop computers are built for portability, not power (This is particularly true with Macbooks), so you may not have the power or drive space to work with such intensive (H.264) video.
Finally, note that this is a user-to-user forum. If you're looking for help working through your issues, we're glad to help you. But if you merely want to report a bug or contact Adobe, you've come to wrong place.
To contact Adobe, click on the Contact button at the top of this web page. We're all civilians here.

Bug Report: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Bug report: A keyboard layout is incorrect on the remote with Japanese keyboard

This is a bug report for Microst Remote Desktop
===================================================
## Summary
A keyboard layout is incorrect on the remote with Japanese keyboard
## Version Information, I tested
* Client
   * Case 1
       * MacBook Pro with JIS106 Keyboard
       * Mac OS X Lion 10.7.5
       * Microsoft Remote Desktop 8.0.24308
   * Case 2
       * MacBook Pro with JIS106 Keyboard
       * Mac OS X Mavericks 10.9.1
       * Microsoft Remote Desktop 8.0.24308
* Remote
   * Case 1
       * Windows 7 Professional Japanese
   * Case 2
       * Windows Server 2008R2 Datacenter Japanese
   * Case 3
       * Windows Server 2012R2 Datacenter Japanese
## Detail of bug
When login from Mac OS X with Microsoft Remote Desktop, the keyboard layout is always incorrect on the remote.
The client machine have a built-in keyboard of JIS 106 layout,
and the primary language is set to Japanese.
But on the remote, the keyboard layout is US 101.
So a input of Shift+2 does not result " but @.
I've seen the above behavior on the 3 remote enviornments described the above.
This bug did not occcur with Microsoft Remote Desktop Connection Client for Mac 2.1.1, even if the system language is English and keyboard layout is Japanese.
## Captures
I've took some of screen captures.
I'm sorry for the capture includes Japanese words, so I added description in English.
Capture 1:
Mac OS X Keyboard Setting
Capture 2:
Windows Server 2012R2 Screen Keyboard
Capture 3:
Windows Server 2012R2 Screen Keyboard, with a additional registry key configured.

This bug also affects the Canadian English settings. If the client is set to Canadian English with a US keyboard the remote server is setup using a Canadian French keyboard. Using the language selection in the toolbar you can temporarily correct
the problem but the keyboard resets to french at the most inopportune times. The was a problem in the earlier RDP client and was fixed so it's sad to see it reoccur in the new client.
Lawrence

Bug Report: develop settings in tethered shooting

Similar Messages

Maybe you are looking for