Minor bug: Info panel truncates text inspite huge free space.

Enter "Common Photo Settings" in the fields of the Info Panel. If entered in the 1st or second field, the text will be truncated in the middle and abbreviated by "...", but not so in the lowest line, in which the entire text appears.
Needles to say, considering the vast space on the screen between the image and the top panel, this is not necessary. It would be even better to provide the data a bit higher, space permitting, not overlapping the image and not requiring the switching between two Info panels.

Similar Messages

BUG: Info panel displays incorrect Hue values

Recently, I've been doing a lot of work with color in Fireworks and came across the following bug, which appears to be a longstanding issue within the application. Rather than keeping it to myself, I figured I'd post it here in addition to submitting a bug report with Adobe. So here it is...
Hue values displayed within the Info panel (in HSB mode) do not consistently match the values displayed in the Color Mixer panel—including basic colors such as pure Yellow, Cyan, and Magenta. The values are 1 degree off—most often below the Color Mixer value, but sometimes above (as with Magenta). This holds true whether using with the Eyedropper tool or the Color Picker swatches eyedropper, and whether sampling from the canvas or from swatches.
For example, the following inconsistencies were observed when sampling the centermost horizontal strip within CS6's default Color Cubes swatches picker. Note that over 50% of these colors are affected by the issue.
The Color Mixer seems to display the correct values, while the Info panel's values appear to be incorrect. Note that this issue affects the HSB mode only; the RGB and Hex values are consistent between both panels.
This bug has been observed in Fireworks CS6, Fireworks CS5.1 and Fireworks 8 on Mac OS 10.6.8 (Snow Leopard).
Here's the bug report submitted for this issue:
Product name: Fireworks
Product Version: 12.0.0.236
Product Language: English
Your operating system: Mac OS 10.6.8 (Intel-based)
******BUG******
Concise problem statement: The Info panel displays incorrect Hue values for many colors—including pure Yellow, Cyan, and Magenta. The Hue values are usually 1 degree below the value displayed in the Color Mixer panel (e.g., 59 instead of 60 for Yellow) but sometimes 1 degree above (e.g., 301 instead of 300 for Magenta). This is true whether using the Eyedropper tool or the Color Picker swatches eyedropper, and whether sampling from the canvas or from swatches.
Steps to reproduce bug:
In an open Fireworks document, open the Info, Color Mixer, and Swatches panels. Within the Color Mixer and Info panels, set the color mode to HSB.
Draw a Rectangle and set its fill to Yellow (#FFFF00) using the Color Picker.
Observe the Hue values displayed in the Color Mixer and Info panels.
Select the Eyedropper (I) tool, and sample the rectangle's fill color. Again, observe the Hue values displayed in both the Color Mixer and Info panels.
Results: In both steps 3 and 4, the Hue value for pure Yellow (#ffff00) appears as 60 degrees in the Color Mixer panel but 59 degrees in the Info panel.
Expected results: The Hue for pure Yellow (#ffff00) should appear as 60 degrees in both panels.
Note that this issue affects the Info panel's HSB mode only; the RGB and Hex values are consistent between panels. Also note that this bug affects over 50% of the "pure" hues within CS6's Color Cubes swatches palette. For more info, see the following forum post:
http://forums.adobe.com/thread/1083391
This bug has been observed in Fireworks CS6, CS5.1 and FW8 on Mac OS 10.6.8 (Snow Leopard).

I haven't done anything other than add my footage to the timeline. I have 2 layers (1 targa seq and 1 png seq). As I move my mouse from the Timeline to the Comp Panel, the color values flash for a split second and go away. If I press Opt+1 (2, 3, and 4) the Info Panel displays the color for that one pixel but the values go blank as soon as I move my mouse. This happens in the Comp Panel mostly. If I open a Footage or Layer Panel, sometimes the values show, sometimes not. Never had this issue in previous versions.

What actually happens @Completed filling free space info for database

Hello,
i see some strange thing with my 15.7 Ase server
Earlier for a very big db of around 1TB the recovery time would be around 15Mins( i mean for the 1TB db to come online).
Now its taking only seconds to come up.
so wanted to check what actually happens in this stage.
Started filling free space info for database 'xxx'
Completed filling free space info for database 'xxx'
The difference is that we have created new server and bcpd the data into it.
Please can someone explain.
Thanks

ASE keeps counters in memory of the amount of free space available on devices and segments. When ASE is shutdown cleanly (aka "politely"), these values are flushed to disk and used to initialize the in-memory counters on reboot. If ASE is shutdown abruptly, the values have to be recalculated, a process which involves either reading every OAM page in the database or every Allocation page.

Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata

The cmd-keys / shortcuts doesn't work in the xmp file info panel btw. in the xmp / iptc fields (e.g. cmd+c, cmd+v, ...) of Adobe Bridge CS6 (Mac OS 10.6.8 and 10.7.3). You are not able to cut and paste info from one box to another like previous versions.
This bug only appears in the xmp file info window (opened via alt+i) in Bridge CS6 - if you edit information or metadata in the file info panel in Photoshop CS6 copy and paste from one field to another works.
The shortcuts also work under Windows (tested under Vista).
I noticed this minor bug already one in the Photoshop CS6 Beta more than one months ago. I hoped that this was corrected in the official test version, but unfortunately it is not. Although it is a minor bug, it is IMHO a basic function and would be very helpful in my daily work - it is too bad, that such a small thing is making working with the application a little bit annoying.

Thanks! If there is a workaround or simple solution, I would be very glad if you could inform me.
Christian
(signature removed by the Admin)
Am 14.05.2012 um 13:49 schrieb FrankBiederich:
Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata
created by FrankBiederich in XMP SDK - View the full discussion
Thanks for your report; we'll look into it.
Frank
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata
To unsubscribe from this thread, please visit the message page at Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in XMP SDK by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.
Message was edited by: Arpit Kapoor

How to make my old file info panel from photoshop work in xmp

Help. Not a photoshop guy but rather a genealogist. Many years ago downloaded a custom file info panel for photoshop which I used to enter meta text about the family photos I scanned. Currently using adobe creative cloud but cant figure out how to use panel or see most of my metatext last few version. Below is information about the panel. All I really want to do is install my panel and get back to genealogy. I apologize but not sure I need to understand the basics of photoshop..
john weis
[email protected]
This is the authors description of the panel:
Genealogy Photo (Private Collection) Custom File Info Panel 1.0 for Photoshop. 11 FEB 2007
Developed by Ron Reiger [email protected]
Please contact me to suggest improvements.
1. BASIS FOR THIS CUSTOM FILE INFO PANEL
2. DESCRIPTION OF EACH PROPERTY NAME
3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
1. BASIS FOR THIS CUSTOM FILE INFO PANEL
The Custom File Info Panel is used to capture metadata about a genealogy/family history photo that is privately held (that is, the photo is not in the possession of a library). The metadata property names on the File Info Panel are based on my interpretation of the recommended primary citation for a photograph (private possession) (annotated, with provenance) as described on page 95 of Elizabeth Shown Mill's "Evidence! Citation & Analysis for the Family Historian" and on my interpretation of recommended primary citation for an Electronic File (Image from Private Files - Annotated), Mills, "Citation!", page 81. I added a few more property names for location and date the photo was taken and keywords (to ID people by number rather than by name), the name of the person who provided the description, a surety for their description, and an informal description. Each field is discussed below.
2. DESCRIPTION OF EACH PROPERTY NAME
Date Scanned: This is the date the photo was scanned. Date is populated by Photoshop and is not editable.
Provider: The owner of the photo as of the date it was scanned. A researcher in a future generations will know who had the photo at a particular point in time.
Provenance: Describe as best you can how the photo got from the person in the photo to the Provider.
Description Provided By: List the person who identified the people and location in the image.
Description Surety: (This is an open text field. You can use any surety rating system you want.) Describe or rate the quality of the Description of the image's people and location. Note any uncertainties regarding any particular people in the photo.
Complete Subject Description: List the full name of each individual in the image, in order. You may want to list the location and date of the image even though there are separate property names for that data.
Informal Subject Description: An optional non-genealogical description of the image, perhaps for using the photo outside of genealogy. Example Informal Subject Description: "Grandpa as a young man."
Media Description: Describe the paper photo you scanned. Dimensions, border, frame, damage, etc. Your ancestors will have an easier time finding the paper photo later if you describe it well!
Annotations: Copy any annotations on the front or back of the photo and frame. Transcribe any photographer embossing/imprint; this is a clue for dating/locating photos.
Special Editing/Alterations: Describe any restoration you performed on the digital image. Did you correct for the lateral reverse of a tintype or daguerreotype?
City/County: List the City/County where the image was taken.
State: List the State where the image was taken.
Country: List the County where the image was taken.
Photo Date: List the date the image was taken.
Keywords: This is the standard keyword entry. Commas or semicolons can be used to separate keywords. I type the TMG ID number of each person in the photo here so I can search for all photos of the person without typing their name.
3. WHERE EACH PROPERTY NAME MAPS & OTHER NOTES
I have not created a working namespace URI or rdf ala http://purl.org/dc/elements/1.1/ for this panel. I have not created localization dictionary files for this panel. Data entered into the panel will appear in Adobe Bridge. As you can see below I re-used lots of pre-existing property names and dumped all my new property names into the photoshop namespace. I don't know if this approach has drawbacks.
Date Scanned: xmp_path: 'CreateDate' Pre-existing property name
Provider: xmp_namespace: photoshop, xmp_path: 'Credit' Pre-existing property name
Provenance: xmp_namespace: photoshop, xmp_path: 'Provenance'
Description Provided By: xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy' Pre-existing property name
Description Surety: xmp_namespace: photoshop, xmp_path: 'DescriptionSurety'
Complete Subject Description: xmp_namespace: photoshop, xmp_path: 'Description' Pre-existing property name
Informal Subject Description: xmp_namespace: photoshop, xmp_path: 'Caption' Pre-existing property name
Media Description: xmp_namespace: photoshop, xmp_path: 'MediaDescription'
Annotations: xmp_namespace: photoshop, xmp_path: 'Annotations'
Special Editing/Alterations: xmp_namespace: photoshop, xmp_path: 'SpecialEditing'
City/County: xmp_namespace: photoshop, xmp_path: 'City' Pre-existing property name
State: xmp_namespace: photoshop, xmp_path: 'State' Pre-existing property name
Country: xmp_namespace: photoshop, xmp_path: 'Country' Pre-existing property name
Photo Date: xmp_namespace: photoshop, xmp_path: 'DateCreated' Pre-existing property name
Keywords: xmp_path: 'Keywords' Pre-existing property name
4. WHERE TO INSTALL THE CUSTOM FILE INFO PANEL
I have tested this panel with Photoshop CS2 and Adobe Bridge CS2 only. It may not work on earlier versions. FWIW a malformed Custom File Info Panel will fail to load in File Info; it won't crash Photoshop.
The following was taken from "XMP Custom Panels," Adobe, Oct 2003.
Each time an Adobe application opens the File Info dialog, it scans all the files in these directories and appends them to the file list. If more than one of the description files has
the same panel name, the one found in the last file to be loaded is added, and others are ignored.
Changes to the contents of the directories do not require you to reload an application; changes are automatically reflected in the dialog the next time it is opened.
The panel description and localization dictionary files must reside in the following locations for use with Adobe Creative Suite applications:
Mac OS X
{Root Volume}/Library/Application Support/Adobe/XMP/Custom File Info Panels
{Home Directory}/Library/Application/Adobe/XMP/Custom File Info Panels
Windows
\Program Files\Common Files\Adobe\XMP\Custom File Info Panels
\Documents and Settings\<user>\Application Data\Adobe\XMP\Custom File Info Panels
The panel description and localization dictionary files must reside in the following locations for use with Adobe Acrobat 7.0 or 6.0:
Mac OS X
{Root Volume}/Library/Application Support/Adobe/Custom File Info Panels
{Home Directory}/Library/Preferences/Adobe/Custom File Info Panels
Windows
\Program Files\Common Files\Adobe\\Custom File Info Panels
\Documents and Settings\<user>\Application Data\Adobe\Custom File Info Panels
I actually do not understand how to write a panel but here is the actual panel:
<?xml version="1.0">
<!DOCTYPE panel SYSTEM "http://ns.adobe.com/custompanels/1.0">
<panel title="$$$/CustomPanels/Acro/PanelName=Gen Photo (Private Collection)" version="1" type="custom_panel">
group(placement: place_column, spacing: gLargeSpace, horizontal: align_fill, vertical: align_top)
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned:', font: font_small_bold_right, vertical: align_top);
date_static_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/DateCreated=Date Scanned', name: '$$$/AWS/FileInfoLib/Panels/DateCreated=Created', xmp_path: 'CreateDate', horizontal: align_fill, vertical: align_top, truncate: true, locked: true);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Provider=Provider:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Provider=Provider', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Credit', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Credit', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Provenance=Provenance:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Provenance=Provenance', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Provenance', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionProvidedBy=Description Provided By', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionProvidedBy', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/DescriptionSurety=Description Surety', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DescriptionSurety', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Description=Complete Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Description', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Caption=Informal Subject Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Caption', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Caption', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/MediaDescription=Media Description', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'MediaDescription', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'MediaDescription', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Annotations=Annotations:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Annotations=Annotations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'Annotations', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Annotations', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/SpecialEditing=Special Editing/Alterations', horizontal: align_fill, height: gTextViewHeight, xmp_namespace: photoshop, xmp_path: 'SpecialEditing', v_scroller: true);
mru_popup(xmp_namespace: photoshop, xmp_path: 'SpecialEditing', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/City=City/County:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/City=City/County', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'City', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'City', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/State=State:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/State=State', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'State', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'State', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/Country=Country:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/Country=Country', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'Country', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'Country', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date:', font: font_small_bold_right, vertical: align_top);
edit_text(fbname: '$$$/CustomPanels/Genealogy/PhotoDate=Photo Date', horizontal: align_fill, font: font_small, xmp_namespace: photoshop, xmp_path: 'DateCreated', vertical: align_top);
mru_popup(xmp_namespace: photoshop, xmp_path: 'DateCreated', container_type: alt_struct, no_check: true, vertical: align_top);
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text( name: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords:',font: font_small_bold_right, vertical: align_top);
cat_container_edit_text(fbname: '$$$/AWS/FileInfoLib/Panels/Description/Keywords=Keywords',horizontal: align_fill, height: gTextViewHeight, xmp_path: 'Keywords', container_type: bag_struct, v_scroller: true);
mru_popup(xmp_path: 'Keywords', container_type: alt_struct, no_check: true, vertical: align_top);
</panel>

You are not going to be able to run your old system from the backup on this old computer as the hardware is incompatible.
You need to get a new computer or a refurbished one.

After Effects and Rotoscoping causes fps loss in info panel

Hello,
I am pretty new to after effects, so please take it easy on me if this is an easily fixed issue or if I am doing something wrong. Here is my whole process.
I have a canon xl2, shooting in 24p with 2:3 selected. I then import the video from the camera to premiere using capture. This was filmed at 16:9.
In PP I open a new project, I use DV - 24p Widescreen 48khz. I have the time code set to auto detect in capture.
I then import the captured video to after effects. I am trying to get better at rotoscope brush, so this is where the problem is.
I import the file, drag the source to the new composition icon, then double click the layer in the composition. I select rotobrush and brush the object.
I then select play, which will go thru and play the file, adjusting the rotobrush. As I view the file, my info panel is up and it begins by showing 23.976 (realtime). The preview panel is showing 23.98 fps.
After a few seconds, the rotoscoping fails and the info panel shows my actual fps vs the file fps. SO in red it shows something like 7.005/23.976 NOT realtime.
I've tried to do some research on this, and I am not sure if everything is set up right. I have read that its best to work on noninterlaced video in AE, i believe it is seperating. In interpret footage it is showing under fields and pulldowns area: lower field first and then it is removing pulldown with WWSSW. Showing a effective framerate of 23.976. Under frame rate area i have selected [conform to frame rate] and 29.97 is in the window. Under pixel aspect i have widescreen 1.21.
I know this is a huge wall of text, but I'd rather swamp you with info then not have enough. Any ideas on what I am doing wrong? Why the fps drops out so much on the rotoscope? Also note, I am only losing fps after pressing play to have rotoscope find the edges itself.
Thank you for any help on this matter.
further info:
Running window 7 pro - 64 bit, adobe CS5 production premium. At the moment its the trial version - get my copy in the mail tommorrow.
PC is i7 920 oc'd to 3.6, 6 gigs ram, 7200 rpm HD with 64Mb cache, gtx480 with 1500Mb Vram. Using the latest Nvidia drivers.
I believe I am using OpenGL for rendering, but not positive.

Ok, awesome. Thanks a ton for taking the time to explain it to me and make sure that I understand the proper way to reference it.
With all this considered, is there any reason why someone would do the traditional rotoscoping vs using the rotobrush to create a matte?
To me it seems like the roto brush pretty much replaces traditional rotoscoping. If thats the case, wouldn't it almost be considered a new rotoscoping method.
Like in the past, people used to dig holes with shovels and by hand. Excavating holes this way was hard and took alot of time.
Over the years, technology made it possible to use a backhoe to dig holes, making it super easy. Both methods are excavating, one is just using an easier method.
I guess thats where my confusion came in, I guess the way I look at it, due to never having done the traditional rotoscoping method, I just considered it the same thing.
Anyway, I hope I dont look like a giant *** with my posts. Cuz anyone willing to take time outta there day to help someone else in a courteous manner deserves all the praise I can give.
Thanks again.

Pages 5.1 truncates text in tables

Just discovered that Pages 5.1 truncates text in tables when exported to Pdf's even when created in Numbers and pasted. Superscripts were missing. Sometimes regular text after superscrips were missing. Too bad.

It's a bug. Until fixed, you'll have to avoid baseline shift or use an earlier version of Pages. Submit Feedback from the Pages menu to let Apple know you are finding this bug.
Jerry

Custom File Info panels from PS into LR

I have a large number of Custom File Info panels created for use within Photoshop that are imperative to our workflow of different departments. These Metadata strings are later read by Extensis Portfolio as our DAM tool of choice.
I don't see to be able to find where to change this other than making minor tweaks to existing Metadata presets. Any clues hmmm? Ta

alanterra wrote:
there is no way to get the data in the original into the derived copy except by doing it by hand
Better ways:
1-1 or 1-many:
(on the file menu: plugin extras) which brings up:
If you want to do "many to many-others-like-them", you have to use a different plugin, like Relative Antics..
alanterra wrote:
If I understand it correctly, "Custom File Info panels" for xmp data should just solve this problem.
Many of us are hoping Adobe enhances Lr to provide better support for custom metadata - as you've noticed, Lightroom is not one of those "Standard Adobe Applications" referred to in the above link.
Rob

Custom File Info Panel Multi select options

Hi,
I have created a custom file info panel and working on simple properties.
it does not have options for provisioning a multi select list box. Say for example, I want to select multiple values from the dropdown values.
How should i do it? Any help is much appreciated.
Thanks,
Sriram

Hi,
Following is my sample property file. I want to make the property "Line Year" to be multiselect.
<xmp_definitions>
</xmp_schema prefix='x' namespace='x....'
 <xmp_property name='LineYear' category='external' label='Line Year' type='closedchoice' element_type='text'>
 <xmp_choice raw_value="2007" label="2007"/>
 <xmp_choice raw_value="2008" label="2008"/>
 <xmp_choice raw_value="2009" label="2009"/>
 </xmp_property>
 </xmp_schema>
</xmp_definitions>

Custom File Info Panels Doc Available !!

Documentation for creating your own custom file info panels is available at:
http://www.adobe.com/products/xmp/custompanel.html
I'm interested in hearing your feedback!
The custom File Info panel for XMP metadata allows you to define, create, and manage custom metadata properties using standard Adobe applications. You can do this by creating a Custom Panel Description file, and placing it in a common location referenced by Adobe applications that support this feature. You can also supply localization dictionary files to localize the contents of your Custom Panel Description files. The resulting custom dialog panel is seen by users when they select the File Info menu option.
The File Info panel allows you to support paths to metadata properties which are not defined in default or other standard XMP schemas, but are needed for your application, company, or industry. By using XMP for that metadata, you take advantage of the potential of XMP for interchange and participation in asset management systems, while providing the ability to use standard Adobe applications to manage it.

Mark,
The PDF/A extension schema provides a big step to the self-sufficient functionality that you are asking about. It permits the XMP schema description information of custom XMP schemas to be embedded into the XMP as payload so that the file can be opened in years to come and the target metadata acurately interperted. Currently, PDF tools are active candidate to make use of this facility. However, there is nothing preventing future use with other file formats, and other tools (via plug-ins?).
It does not include vocabulary, static text, and panel presentation layout information.
http://www.pdfa.org/doku.php
It defines a "known" subset of standard XMP properties from the 2001 XMP Spec. Everything else is "custom".
You could craft a custom File Info "template" with the PDF/A extension for your custom XMP fields. Then import the template into each file.
The PDF/A extension schema itself is implemented with multi-dimensional XMP arrays. MetaGrove Plug-in dialog screen shots can be viewed on http://www.poundhillsoftware.net/Acrobat.htm
Regards,
Carl Rambert

Custom File Info Panel CS2- CS4

I have a Custom File Info Panel that has been created in Adobe Photoshop CS2 and works in CS3. I am having trouble figuring out how to get it to work in CS4. Is there a way to port the Custom File Info Panel into CS4 without entirely recreating it?
I am seeing references to FileInfo SDK and creating a new Flex UI but I can't seem to find a definitive method on this pre-CS4 File Info Panel to the new UI - and I am in unfamiliar territory.
Any assistance or points in the proper direction would be most helpful.
UPDATE: Answering at least some of my own questions, I have followed the procedure here:
http://blogs.adobe.com/gunar/2008/11/customizing_metadata_ui_in_cs4.html
I am still having some trouble with a couple of the unique properties but I expect that they will be typos... I hope...
Any good reference information is still welcome.

Thank you for suggesting the PS Scripting forum but I think the next stop might be the XMP SDK Forum as there are a few similar questions there such as http://forums.adobe.com/thread/540397. But before I go impolitely cross-posting...
I've had some success and it appears that my custom file info metadata edited and saved in CS2 is now visible in CS4 and the reverse is also true - metadata edited and saved in CS4 is visible in CS2. This was built using the Generic Panel from the SDK according to the instructions shown at the link in my original post.
The only problem is that the external application that relies on the custom metadata doesn't see the CS4 version of the metadata. I suspect that this is just some general namespace issue. Perhaps if an XMP expert would be willing to comment on the conversion of the Custom Info Panel based on the following single portion of the metadata to see if I am doing it correctly - I would very much appreciate it.
In the CS2 Custom Info Panel XML I have this field:
<panel title="$$$/CustomPanels/XYZ/PanelName=XYZCorp Graphics MetaData" version="1" type="custom_panel">
group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top, reverse: rtl_aware)
static_text(name: '$$$/CustomPanels/XYZ/fullName=Full Name/Title of Graphic', font: font_big_right, vertical: align_center);
cat_container_edit_text(xmp_ns_prefix: 'xyzcorp', xmp_namespace: 'xyzcorp', xmp_path: 'FullName', container_type: seq_struct, horizontal: align_fill);
mru_popup(xmp_ns_prefix: 'twcable', xmp_path: 'FullName', no_check: true, vertical: align_top, container_type: seq_struct, mru_append: true);

</panel>
In my CS4 properties.xml the corresponding field:
<xmp_definitions xmlns:ui="http://ns.adobe.com/xmp/fileinfo/ui/">
<xmp_schema prefix="custom" namespace="xyzcorp" label="$$$/Custom/Schema/Label=XYZCorp Graphics MetaData" description="$$$/Custom/Schema/Description=CS4 Version of XYZCorp MetaData Custom Panel.">

<xmp_property name="FullName" category="external" label="$$$/Custom/Property/FullName_Label=Full Name/Title of Graphic:" type="seq" element_type="text"/>

<ui:separator/>
</xmp_schema>
</xmp_definitions>
It seems that the following CS2 => CS4 translations should be true:
"xmp_namespace" => xmp_schema namespace property (in this case "xyzcorp")
"xmp_path" => xmp_property name property (for this one property, "FullName")
is there another translation that I am missing? I am betting it has something to do with the CS2 "xmp_ns_prefix" but I am not entirely sure how to map this. Also perhaps something in manifest.xml (though it didn't seem like it)?
Many thank you's to anyone that can offer words of wisdom.
j

CreatorContactInfo struct in Generic File Info Panels

Hi all,
I developed a custom panel with custom metadata in Adobe Bridge CS4, using the Generic File Info Panels.
In this panel, I have to include custom metadata and the IPTC Contact metadata.
No problem with custom metadata, I have a problem with IPTC Contact:
If I insert value in the IPTC Panel provided by Adobe, I see that metadata is written in this way:
<Iptc4xmpCore:CreatorContactInfo
 Iptc4xmpCore:CiAdrExtadr="value"
 Iptc4xmpCore:CiAdrCity="value"
 Iptc4xmpCore:CiAdrRegion="value"
 Iptc4xmpCore:CiAdrPcode="value"
 Iptc4xmpCore:CiAdrCtry="value"
 Iptc4xmpCore:CiTelWork="value"
 Iptc4xmpCore:CiEmailWork="value"
 Iptc4xmpCore:CiUrlWork="value"/>
If I insert values in my custom metadata I haven't CreatorContactInfo structure:
<rdf:Description rdf:about=""xmlns:Iptc4xmpCore="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/"
Iptc4xmpCore:CiAdrExtadr="value" Iptc4xmpCore:CiAdrCity="value" Iptc4xmpCore:CiAdrRegion="value"
Iptc4xmpCore:CiAdrPcode="value" Iptc4xmpCore:CiAdrCtry="value" Iptc4xmpCore:CiTelWork="value"
Iptc4xmpCore:CiEmailWork="value" Iptc4xmpCore:CiUrlWork="value"
xap:MetadataDate="2010-04-20T09:07:47+02:00">
<tiff:BitsPerSample> <rdf:Seq> <rdf:li>8</rdf:li> <rdf:li>8</rdf:li> <rdf:li>8</rdf:li> </rdf:Seq>
</tiff:BitsPerSample> </rdf:Description>
Is there a way to reproduce the orginal (and standard) structure??
There is my custom properties.xml (only the IPTC rows):
<xmp_schema prefix="Iptc4xmpCore" namespace="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/" label="$$$/Custom/IPTC Contact=IPTC Contact" >
 <xmp_property name="CreatorContactInfo:CiAdrExtadr" category="external" label="$$$/Custom/Property/Address=Address:" type="text"/>
 <xmp_property name="CreatorContactInfo:CiAdrCity" category="external" label="$$$/Custom/Property/City=City:" type="text"/>
 <xmp_property name="CiAdrRegion" category="external" label="$$$/Custom/Property/State/Province=State/Province:" type="text"/>
 <xmp_property name="CiAdrPcode" category="external" label="$$$/Custom/Property/Postal Code=Postal Code:" type="text"/>
 <xmp_property name="CiAdrCtry" category="external" label="$$$/Custom/Property/Country=Country:" type="text"/>
 <xmp_property name="CiTelWork" category="external" label="$$$/Custom/Property/Phone=Phone:" type="text"/>
 <xmp_property name="CiEmailWork" category="external" label="$$$/Custom/Property/Email=Email:" type="text"/>
 <xmp_property name="CiUrlWork" category="external" label="$$$/Custom/Property/Website=Website:" type="text"/>
 <ui:separator/>
 </xmp_schema>

Edited reply:
Try:
name="CreatorContactInfo/Iptc4xmpCore:CiAdrExtadr"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrCity"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrRegion"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrPcode"
name="CreatorContactInfo/Iptc4xmpCore:CiAdrCtry"
name="CreatorContactInfo/Iptc4xmpCore:CiTelWork"
name="CreatorContactInfo/Iptc4xmpCore:CiEmailWork"
name="CreatorContactInfo/Iptc4xmpCore:CiUrlWork"
Carl

Problems with Custom File Info Panel and Dublin Core

I'm creating a custom file info panel that uses the values of the dublin core description and keywords (subject) for two of it's own fields. I'm having problems with the panel saving if they enter the description on the custom panel first, and with the keywords not echoing each other, or reappearing after a save. Here is the code for the panel <?xml version="1.0"> <!DOCTYPE panel SYSTEM "http://ns.adobe.com/custompanels/1.0"> <panel title="$$$/matthew/FBPanelName=Testing for Matthew" version="1" type="custom_panel"> group(placement: place_column, spacing:gSpace, horizontal: align_fill, vertical: align_top) { group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top) { static_text(name: '$$$/matthew/keywords = Keywords', font: font_big_right, vertical: align_center); edit_text(fbname: '$$$/matthew/keywordsFB = Keywords', locked: false, height: 60, v_scroller: true, horizontal: align_fill, xmp_ns_prefix: 'dc', xmp_namespace: 'http://purl.org/dc/elements/1.1/', xmp_path: 'subject'); } group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top) { static_text(name: '$$$/matthew/description = Description', font: font_big_right, vertical: align_center); edit_text(fbname: '$$$/matthew/descriptionFB = Description', locked: false, height: 60, v_scroller: true, horizontal: align_fill, xmp_ns_prefix: 'dc', xmp_namespace: 'http://purl.org/dc/elements/1.1/', xmp_path: 'description'); } group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top) { static_text(name: '$$$/matthew/season = Season', font: font_big_right, vertical: align_center); popup(fbname: '$$$/matthew/seasonFB = Season', items: '$$$/matthew/Season/Items={};option 3{option 3};option 2{option 2};option 1{option 1}', xmp_namespace:'http://monkeys.com/demo/testingmatthew/namespace/', xmp_ns_prefix:'matthew', xmp_path:'season'); } group(placement: place_row, spacing: gSpace, horizontal: align_fill, vertical: align_top) { static_text(name: '$$$/matthew/ltf = Limited Text Field', font: font_big_right, vertical: align_center); edit_text(fbname: '$$$/matthew/ltf = Limited Text Field', locked: false, horizontal: align_fill, xmp_namespace:'http://monkeys.com/demo/testingmatthew/namespace/ ', xmp_ns_prefix:'matthew', xmp_path:'ltf'); } } </panel> Thanks for the help

To answer my own question:
The documentation really sucks.
I found this reply from Adobe <http://forums.adobe.com/message/2540890#2540890>
usually we recommend to install custom panels into the "user" location at:
WINDOWS XP: C:\Documents and Settings\username\Application Data\Adobe\XMP\Custom File Info Panels\2.0\panels\
WINDOWS VISTA: C\Users\username\AppData\Roaming\Adobe\XMP\Custom File Info Panels\2.0\panels\
MAC OS: /user/username/Application Data/Adobe/XMP/Custom File Info Panels/2.0/panels/
The reason why your panels did not work properly was a missing Flash trust file for that user location. Without such a trust file the embedded flash player refuses to "play" your custom panel.
Please see section "Trust files for custom panels" in the XMPFileInfo SDK Programmer's Guide on page 50 for all details on how to create such trust files.
After many wasted hours I have now the simple panels running.
Cheers,
H.Sup

Is there a date entry widget for XMP custom file info panels?

Looking through the Custom File Info Panels documentation, the samples, and the default info panels presented in Photoshop, I can't find any reference to a date entry widget - the closest I've seen is the date_static_text widget.
Is there any way to present an editable, validating date entry field to our end-users through the File Info panel?
(the info we're wanting to store is a release date so it's user-specified, and not derivable from the file in any way)

Mark,
The PDF/A extension schema provides a big step to the self-sufficient functionality that you are asking about. It permits the XMP schema description information of custom XMP schemas to be embedded into the XMP as payload so that the file can be opened in years to come and the target metadata acurately interperted. Currently, PDF tools are active candidate to make use of this facility. However, there is nothing preventing future use with other file formats, and other tools (via plug-ins?).
It does not include vocabulary, static text, and panel presentation layout information.
http://www.pdfa.org/doku.php
It defines a "known" subset of standard XMP properties from the 2001 XMP Spec. Everything else is "custom".
You could craft a custom File Info "template" with the PDF/A extension for your custom XMP fields. Then import the template into each file.
The PDF/A extension schema itself is implemented with multi-dimensional XMP arrays. MetaGrove Plug-in dialog screen shots can be viewed on http://www.poundhillsoftware.net/Acrobat.htm
Regards,
Carl Rambert

Cluster VI Reference Minor Bug

Over on LAVA PJM_labview posted a video of a bug found in LabVIEW 2013 SP1. It is a minor bug with the block diagram when showing a cluster constant with a VI reference constant in it. Here is the video of how to reproduce the bug.
http://screencast.com/t/gfKwlvMcCsHI
And here is the original thread on LAVA.
http://lavag.org/topic/18297-cool-little-lv-2013-sp1-bug/#entry109757
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

I played with this and filed it as a CAR (#479432). Intriguingly, there are a couple workarounds:
Option 1
On block diagram:
1. Create cluster constant containing refnum with auto-sizing set as arranged (vertical or horizontal)
2. Create typedef
3. Unlink from type def
4. Change auto-sizing to desired value
5. Recreate typedef
Option 2
On front panel:
1. Create cluster containing refnum control
2. Create typedef
On block diagram:
3. Create constant from cluster typedef on block diagram.
4. Unlink constant from typedef, change auto-sizing as desired, recreate typedef
Christopher S. | Applications Engineer
Certified LabVIEW Developer
"If in doubt... flat out." - Colin McRae

Minor bug: Info panel truncates text inspite huge free space.

Similar Messages

Maybe you are looking for