Title designer coordinates bug

I'm having an issue with CS6 Premiere Pro's title designer.
If I place text in the title, add it to my timeline, and then reopen the title for editing, I find that the coordinates of the placed text read as X 100 & Y 100, regardless of where they are actually placed. As soon as I click on either coordinate text field, the text will jump to X 100 or Y 100, depending on which field I click on. I have revisited this a few times, and consistently, the coordinates for placed text read as X 100 & Y 100. In CS5.5, they simply retain their proper coordinates. Am I doing something wrong, or is this a bug???
System info:
CS6 Premiere Pro 6.0.1 (MC: 264587)
6-core MacPro5,1
16GB RAM
OSX 10.6.8
ATI  Radeon HD 5870 video card
Permissions repaired and disks checked (ONXY & Disk Warrior)
Here's a screen shot of some text's position coordinates after being placed:
Here's what I get when I double click the title to open it for editing. Note that the text is still in its original location in the title, but the coordinates now read as X 100 & Y 100:
This is mostly a major annoyance as I can manually reposition the text, but if I want to match text postions of a few titles via numerical coordinates, I have to enter both X and Y values.

No they don't, if you want it fixed you need to file a bug report.
Adobe - Feature Request/Bug Report Form

Similar Messages

  • Can't move credits in title designer

    Ok, this may be a very simple question because I know I have done this before.
    I created a long list of credits in the title designer and I just want to animate them on the timeline
    with 2 points, at the beginning and at the end so they will scroll up the screen.
    When I move the position of them in the timeline...they just disappear?
    What am I doing wrong that they are not scrolling up the screen but disappearing?
    Thanks!

    Danged thing is still queued.
    Until then, and after you send your PRPROJ to Eddie as a .TXT file. Here are the setting you should have in the Roll/Crawl Options:
    Title Type = Roll (radio button)
    Direction (doesn't matter, as we have a Roll, not a Crawl)
    Timing (Frames):
    Start Off Screen = checked
    End Off Screen = whatever you want it to do
    Preroll = 0
    Ease-In = whatever you need to look smooth
    Ease-Out = whatever you need to look smooth
    Postroll = 0
    Click OK.
    Now, in the Titler, use the Selection Tool and click on your Text Box. You should see the Bounding Box around the type. Move it until the top of the Text Box is right at the top of the Title-Save highlight. Note: you can move it up even more, if you want it quicker, because you have checked Start Off-screen.
    Since you moved the Text Box, I'd hit the Vertical Center Tool to the Toolbox. It's to the right of the Horizontal Center Tool, and both are between the Align and the Distribute Tools.
    Now, test it in your Timeline. If you want it to start even more quickly, go back and use your Selection Tool to move the Text Box up even higher, say to the top edge of the screen. That'll start it pretty quickly.
    Good luck, and I hope that it's a setting issue, and that Eddie doesn't find something really amiss with your Project.
    Hunt
    PS, I still think that Keyframing this puppy would get you what you want and need in less time than the screen-cap is spending in the queue.

  • Using the Premiere Pro Title Designer

    I keep seeing lots of discussions about the limitations of the Premiere Pro Title Designer.
    It seemed like a good idea to point out some of the good things about it, just to get it out there for people new to Premiere Pro, or people who have not used the Title Designer much.
    Just to get a couple of things out of the way, there is a problem with the way it handles partial transparency of Photoshop files and other images with an alpha channel, and no, you still can't animate individual parts of the title without making more titles to do the job. But you can put a logo from Photoshop on its own layer, and you can animate individual titles.
    That said, have you looked lately at the ease in which you can create interesting fonts and shapes? Faster and easier in a title than in Photoshop or After Effects.
    Something like this for example. I would not know where to begin to make this in After Effects or Photoshop or Illustrator.
    And even more interesting is that the same exact font style can be applied to a shape. Like this:
    Or this:
    You can imagine how great it would look if I actually had any artistic ability!
    Every time you do something to a font, you can save it as a new style in order to use it again later. In the same project, or a new one a year from now. You can group styles into libraries, you can replace the ones that came with Premiere Pro, (and get them back with a simple reset). You save the styles you use on shapes as a style.
    For over a decade I have had Tim Kolb's free font styles and some templates on my web site here: http://www.stevengotz.com/title_styles.html
    They are free. Have you been using them? If not, why not? And recently he has been putting more free styles on his own web site along with regularly releasing new, free, templates on his BLOG site at http://style4type.blogspot.com/
    All I am saying is that if you have not looked at using the Title Designer lately, then perhaps you might want to take another look. Especially now that with Premiere Pro CC, it is so easy to make unique copies of existing titles without fear of overwriting the original.
    Don't have CC? No sweat. These work with all versions of Premiere Pro as far as I can tell. (Please let me know if you discover otherwise.) The Title Designer has not changed much. Unfortunately. But it is still quite usable and I hate to see people go out and buy titling programs just to do something they could do for free in Premiere Pro.

    Well, I have often wished we could animate the source text like we can in After Effects. Or wished we could have the great font style capability in After Effects that we have in Premiere Pro.
    I just can't get both.
    That is why I came up with the way to create many titles from one, using a Microsoft Word macro, but I can only get it to work in English, or, rather, I can't get it to work with non-ASCII characters.
    The method that was found to do it with Adobe InDesign is great, but no font styles there either.
    The magic that Tim makes with his font syles and backgrounds is just too strong a reason to work completely in Premiere Pro. So making a new title from another is the only way for me to to much of what I want to do. But once I get past a couple of dozen titles or so, I use the macro.
    http://forums.adobe.com/message/5983278#5983278

  • Title designer presets for Premier cc

    where can I find title designer presets for Premier cc? I could download for C6 but not for CC.

    As I recall, I copied the CS6 templates to my CC directory. I am not on that PC, so unless someone else provides the info, I should be able to tell you what directory to put them in when I get home this evening.

  • Title designer CC

    I'm sure it must be my setup but I find the space bar does not work as it should in title designer. If I press it once nothing happens, if I keep it pressed 5 or more spaces come at once. The space bar works ok in every other panel and in every other program.

    I solved my issue. Title designer is working now. I was using a Black Magic
    Design sequences for this project and something must have glitched out with
    it. I made a regular adobe sequence and it works. So I opened a new project
    and made a BMD sequence and it works... weird.
    Went back to project I was having issues with and made a new BMD sequence
    and it works. So I am copy and pasting everything into me sequences and it
    seems to be working now. I don't know what caused this to happened to all
    the sequences I made the past few days... Maybe something got corrupted or
    I updated premiere and there was some compatibility issue between the
    sequences I made and the latest build of premiere. Working now though!
    Hope this helps people track the issue down. Look at any 3rd party things
    you are running. That is what is probably causing the issue.
    On Aug 5, 2013 5:51 PM, "joe bloe premiere" <[email protected]

  • How do I install Title Designer Presets in Premier Pro CC?

    I follwed the precedure on the link to install Title Designer presets in Premier Pro CC. When I re-launched Premier Pro the presets had not been install. Also, the link took me to instructs for CS6 and CS5 versions. No CC version.

    The fuctional content for CC is the same as for CS6.
    http://helpx.adobe.com/x-productkb/multi/library-functional-content-missing.html

  • Flash Builder Design Mode Bug Workaround (!!!)

    I've been fighting this annoyance since FB4 came out, and while I still don't think that custom/embedded fonts in design view are fixed by this, I've been able to reproduce this "fix" (workaround) to get design view to show fonts/theme correctly under some very specific circumstances on two separate PCs.
    If anyone from Adobe sees this I'd like to know whether this sounds familiar or is possibly logged as a bug already somewhere in JIRA.. if not I could probably do that as long as it won't be a wasted effort.
    The problem:
    You're using a Halo theme but certain CSS settings (specifically and possibly limited to FONTS) don't work properly in design view even though they work fine in Flash.  Essentially this makes design view practically useless since choice of font family, size, and weight can effect component sizing if you aren't hard-coding component sizes (ugh)... ruining your efforts to use design view for UI design if your UI has any level of complexity (or uses absolute positioning at all).
    The specific circumstances seem to be:
    You're using the Halo theme (you have no special 'skinning' requirements and want Halo defaults w/only CSS customizations)
    You've upgraded a Flex 3 project to Flex 4 SDK (not sure if this is needed to reproduce the issue)
    Using a regular non-embedded font (embedded fonts still do crap out, but even this 'workaround' doesn't fix that problem)
    You're using swc library files such as the Swiz lib, Mate, Flexlib, etc. (I think it's ANY swc, not specific to any one)
    This may also only apply when using an "mx only" project (no Spark), since we're using Halo here
    The two part fix (as far as I can tell you need BOTH before design view works correctly):
    In .actionScriptProperties, add the following bolded line after the compiler tag like so:
      </compiler>
      <theme themeIsDefault="false" themeIsSDK="true" themeLocation="${SDK_THEMES_DIR}/frameworks/themes/Halo"/>
      <applications>
      (I think this may only apply to 'upgraded' projects, as the line does seem to be present in newly created FB4 Halo projects.  My guess is that an "upgraded" project should have such a line added, but doesn't get it due to an oversight/bug.)
    The somewhat painful, and definitely odd part.  Remove all your SWC library files from /libs.  Grab the source code for the libraries and drop them into your project's /src folder as if you'd written them yourself.  (This may require some research and knowledge on special requirements to build the libs, such as with Swiz's compiler metadata compiler settings which you need to put into your project's settings.)  After you get things set up right and the project compiles again, doing a refresh of design view should finally give you proper looking Halo controls and fonts so they look identical to the Flash runtime view.
    Why this works, I've no idea.  I suspect it has something to do with that stupid and annoying (and supposedly 'harmless') design mode warning message you get when you include a library like Swiz or Mate in your project.  (Design mode could not load xxxxxxxxxxxxx.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)) - this warning doesn't break your application, people seem to think it's just a harmless warning..but is it breaking design view?
    If anyone has any idea what's going on here, why this 'fixes' the problem (a better work around), or has any other insight I'd love to hear it.  The combo of needing to do two things (in my specific case) to fix the problem really made this a ROYAL PAIN, I still can't believe I found it.

    Hi Fernando, sorry for the delayed response.  CSS Design Mode is not available for Flex 4 projects, but it is still available in Flex 3 projects.  The reason for this is that designing components in Flex 4 is often a lot different, since it relies highly on the new spark skinning architecture.  There is, however, an Appearance panel available in design view which supplies a set of the main inheriting styles. Setting these styles in the Appearance panel will result in assigning values to a global style selector.
    I hope this helps,
    Rob

  • Slow motion video. By design or bug?

    If I create a slow mo video and share it by iMessage the recipient views it correctly but if I view it in the thread it plays at normal speed throughout.
    Is this a bug or by design?

    I'll take this feature request to product management.  I can't say if or when such support will be available.  In the meantime, as a workaround use iMovie to export your video with the slo-mo effect to your Camera Roll so Revel can import the processed version.

  • How to report Safari title bar rendering bug?

    I have captured a screenshot of a Safari for Windows bug where the title bar renders incorrectly when the "Develop" menu is turned on. Where can I submit this information?

    Click Help -> Report bugs to Apple...
    This method allows you to send your bug report directly to Apple. Thanks for sharing this info with the forum. I was not able to reproduce this error.

  • Space Designer Surround Bug

    I'm pretty sure this a new bug...
    In a surround session choosing a Surround IR in Space Designer results in a significant delay to the reverb. (not the case with a stereo IR) ... Anyone?
    Logic 9.1 Snow Leopard 10.6.2
    Keith Moore

    Yep, same bug here…
    A 5.1 impulse on an aux, give me about 2 seconds delay…
    Same song opened with 9.0.2 aren't affected

  • Convert pane to panel coordinates bug ?

    The attached VI uses invoke node Convert Pane to Panel Coordinates.  It's in LabVIEW 8.2. 
    It returns 0, 46 when run in 8.2.
    It returns 0, 0 when run in 8.5.1, and 8.6.
    It returns 0, 51 when I copy everything on the diagram to a blank VI in 8.6.
    Look like a bug to me.  Did I miss something ?
    George Zou
    http://webspace.webring.com/people/og/gtoolbox
    Attachments:
    Untitled 1.vi ‏11 KB

    It depends on the position of the scroll bars.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • MAS - Title design screen is blank

    Hi all,
    I have a problem, on MAS 5, sp09.
    When I double-click a title, the design window don't open (it does the property window).
    So I make double-click again and the design window is showed, but is blank.
    The preview window looks fine.
    Anyone can help me?
    Thanks.

    Hi Lluis,
    I'm Daniel from Madrid. I have the same problem with MAS 50 sp09 only with XP OS.
    May you help me with this?
    I can't find any solution.
    Thanks a lot.
    D.C.
    Edited by: Daniel Cabezas on Feb 29, 2008 1:54 PM

  • Title WIndow + DataGrid BUG

    I am using the PopUpManager to create as a pop-up a
    TitleWindow which contains a DataGrid with some elements.
    Whenever i select an item from the DataGrid i dispatch an
    event to notify the parent application and then I remove the PopUp
    like this:
    <mx:DataGrid change="myFunction(event)/>
    public function myFunction(event:Event):void
    //Logic to dispatch a custom event
    PopUpManager.removePopUp(this);
    The thing is this is causing an error in the Flex SDK
    classes, the error says:
    TypeError: Error #1009: Cannot access a property or method of
    a null object reference
    at
    mx.controls.listClasses::ListBase/::mouseIsUp():[ListBase.as:7029]
    at
    mx.controls.listClasses::ListBase/mx.controls.listClasses:ListBase::mouseUpHandler():[Lis tBase.as:7060]
    at
    mx.controls::DataGrid/mx.controls:DataGrid::mouseUpHandler():[DataGrid.as:4211]
    So what's the deal here??? I am removing the popUp on the
    change event of the DataGrid and it fails, why is that?
    If i change it so the change event only dispatches the event
    and then I manually close the popup using the close button then it
    works, but it doesn't work when i try to close the PopUp from the
    change event of the DataGrid.
    Any ideas? is it a bug?

    This is what the DataGrid tries to do after the popUp is
    closed:
    TypeError: Error #1009: Cannot access a property or method of
    a null object reference
    at
    mx.controls.listClasses::ListBase/::mouseIsUp():[ListBase.as:7029]
    at
    mx.controls.listClasses::ListBase/mx.controls.listClasses:ListBase::mouseUpHandler():[Lis tBase.as:7060]
    at
    mx.controls::DataGrid/mx.controls:DataGrid::mouseUpHandler():[DataGrid.as:4211]
    This didn't happen in Flex 2.0, which makes me believe it is
    a Flex 2.0.1 bug, and i hope Adobe can solve it (it worked before)
    for a next update.
    It seems that the workaround will be to delay the call to
    RemovePopUp as you mention, either by using a timer or by using the
    CallLater( ) method.
    I would like to know if Adobe has a better workaround and if
    they are aware of this bug

  • Adobe Title Designer: Missing Font EdwardianScriptITC replaced with Courier

    Where do I find this missing font? Edwardian Font was loading perfectly. Now it is missing why?

    In the AME preferences, can you please try turning off Native Sequence Loading then run the export again. Please let me know if that fixes the issue so we can get a bug logged.

  • "Design" view bug?

    I've created a simple menu with CSS. The menu displays differently in "Design" view within DW than it does as an actual rendered HTML page. WTF?
    See below the sample I put together that illustrates the difference. The background color is different, the extent of the back color is also different, and even the size of the boxes is slightly different. The DW view is inaccurate, but why?

    Hi
    Design view is only an approximation and depending upon you code can be a very rough approximation.
    PZ

Maybe you are looking for