Image size different in debug and publish

My project is purely actionscript based movie. I am trying to
display an image file (jpg) that is received from the movie server.
The image file displays with corect zoom dimensions when in
development environment but after the movie is published...the
image displays full size (612x494). It gets more
wierd...occassionally it works correctly (displays image with
correct zoom) after several tries of publishing the movie.
Any ideas what might be the cause of this? Please help!!!
regards,
staylor
>>>>>>>>>More
Info:>>>>>>>>>
the following code is executed to size up the image after
image load is complete.
viewPort_width_ = 450;
viewPort_height_= 350;
var zoom : Number = 1;
var scale : Number = 100 * zoom;
image_.scrollRect = new Rectangle(0 / zoom,0 /
zoom,viewPort_width_ / zoom,viewPort_height_ / zoom);
image_._xscale = image_._yscale = scale;

The image on the left in PS looks the same in Picasa Image
Viewer (I selected it to be color managed based on the monitor profile), looks the same in Windows Image Viewer, and looks the same in the thumbnail.  The image on the right in LR is how the picture looks when I look at my image in Firefox but in Internet Explorer and in Chrome, the image looks like the image on the left in PS.  The image below shows how the thumbnail looks different from the actual picture when it's double clicked and viewed in Picasa.  The thumbnail (which shows the subjects having green skin) would be how I saw it online while the double clicked version is how I saw it in PS, even though it was sRGB (I checked the image properties to make sure of the color space).
I have a ATI 5470 GPU on my ASUS 17.3 inch laptop.  Not sure about the drivers.

Similar Messages

  • Image size different in debug and in publish

    My project is purely actionscript based movie. I am trying to
    display an image file (jpg) that is received from the movie server.
    The image file displays with corect zoom dimensions when in
    development environment but after the movie is published...the
    image displays full size (612x494). It gets more
    wierd...occassionally it works correctly (displays image with
    correct zoom) after several tries of publishing the movie.
    Any ideas what might be the cause of this? Please help!!!
    regards,
    staylor
    >>>>>>>>>More
    Info:>>>>>>>>>
    the following code is executed to size up the image after
    image load is complete.
    viewPort_width_ = 450;
    viewPort_height_= 350;
    var zoom : Number = 1;
    var scale : Number = 100 * zoom;
    image_.scrollRect = new Rectangle(0 / zoom,0 /
    zoom,viewPort_width_ / zoom,viewPort_height_ / zoom);
    image_._xscale = image_._yscale = scale;

    The image on the left in PS looks the same in Picasa Image
    Viewer (I selected it to be color managed based on the monitor profile), looks the same in Windows Image Viewer, and looks the same in the thumbnail.  The image on the right in LR is how the picture looks when I look at my image in Firefox but in Internet Explorer and in Chrome, the image looks like the image on the left in PS.  The image below shows how the thumbnail looks different from the actual picture when it's double clicked and viewed in Picasa.  The thumbnail (which shows the subjects having green skin) would be how I saw it online while the double clicked version is how I saw it in PS, even though it was sRGB (I checked the image properties to make sure of the color space).
    I have a ATI 5470 GPU on my ASUS 17.3 inch laptop.  Not sure about the drivers.

  • Projected Image size different using VGA and HDMI

    From my ipad mini with a VGA connector I get a full screen image on an Epson projector but a much smaller image using an HDMI connector - How can I get a full screen with HDMI?

    Good to know there are no menu's I have missed.   There are 2 things between the iPad and the projector - the HDMI cable and the mini display / HDMI adapter.  So as changing the HDMI cable did not help it must be the adapter.   Just to add I'm pretty sure the problem first arose after i upgraded to 8.1.2

  • Image size changes after saving and then reopening

    I'm using CS6. For example I change the image size to a 4X6 and then save it. Then when I open the file it will be 7.5X5. What's the fix? Thanks for your time.

    I'm using Photoshop CS6 on a Windows 7 - 64 bit system. I'm using the Image Size dialog box and saving the file as a 4X6 at 300 dpi from a psd file to a jpeg file. When I open the file it is 5X7.5 inches at 240 dpi. I've been playing with it and have just figured out that when I save the file as a psd file it stays the size I've created and it changes when I save as a jpeg file. This is change is recent. It's worked properly in the past. Thanks for your help.
    Steve

  • Compiling differently for debug and release

    I want to produce slightly different .class files for my debug and release compilations. For debug, methods like toString() should return rich information which should not be present in the release version. In fact, I want most of my debug specific code to not be included in the final release to keep ti's file size down.
    I realise I can do this by creating something like
    public interface MyGlobals {
        static final boolean DEBUG = false;
    }and implementing this on any class that needs to do debug specific work. However, I'm in a bit of a chicken and egg scenerio. This file needs to exist during development time so that every class that needs it can implement it - however, this would prevent me from dynamically changing it based on whether I'm doing a debug or release build. On the other hand, if the file is generated automatically at compile time, all the classes that need to refer to it will need to refer to a non-existant source file, which will cause problems in my NetBeans IDE.
    Is there a way around this? It would be nice if there was some sort of a configuration file you could specify to to alter how the code is generated. Something similar to C++ #ifdef.

    I realise I can do this by creating something like
    public interface MyGlobals {
    static final boolean DEBUG = false;
    /code]You should be careful about this, by the way, rember that this kind of constant value gets compiled in to classes that reference it, and java doesn't always pick up the need to recompile when the source of MyGlobals changes.
    On the other hand, if you don't declare it final then the compiler can't optimise out code that you want it to exclude for you.

  • 2 questions - change image size within print cell, and saving print template w/ specific images

    Hi,
    Searched the forums for the answer to these but couldn't find much.
    1. Is there a way to change the image size within a cell (under print module). For example, zoom in 140% on a a specific image but still have it within the original cell size?
    2. Say I create and fill in an elaborate print template with my images - is there a way to save the FILLED IN version of the template to edit at a later time? For example if I wanted to load it back up w/ all the original images layed out in the print template, but maybe change a few and resave as jpeg?
    Thank you!

    Hi
    I'm not sure but maybe you can use a rectangle to hold the .ai image, resize the rectangle and fit proportionally the image inside it
    hope this help
    Eli

  • In Lightroom CC images look different in Library and Develop modules. After output, images do not appear as they do in Develop.

    As above.

    Mac OS X 10.9.5 has a color management bug that can lead to colors appearing different in Develop and Library: Jao's photo blog: Serious color management bug in Mac OS 10.9 "Mavericks" . See also: Jao's photo blog: Further quantification of the Mavericks color management problem and Jao's photo blog: Color management in Safari is broken in Mavericks too. Sorry for all the links to my blog, but this bug really annoys me and it bugs me that it hasn't been fixed all these months that Mavericks has been out. This can lead to color shifts especially in the deep tones. You can sometimes work around it by turning on soft proofing and proofing to adobeRGB or sRGB. Adobe could fix this but they haven't so far. Apple could fix it too, but they haven't until now. They fixed some code that lead to Aperture working correctly but Lightroom still has the problem.

  • Image appears different in Library and Develop modes?

    I have an image that appears different depending on whether it is in the Library Module or the Develop Module. Only this one image does this. The develop module version is the one I want to work on in Photoshop. However, when I click on "Edit in Adobe Photoshop CS3" the resulting tiff that opens in PS has an appearance that matches that of the Library module version of the image. It makes no difference whether I click on "Edit in PS CS3" from the Library or Develop module, the tiff always matches the Library Module version of the raw file.
    Any ideas what might be causing this?
    Thanks.
    J.

    How are you calibrating your monitor? The only real difference between the Library and develop module is that the Library module shows a preview that is generally stored in the adobeRGB color space. The Develop module uses a color space based on prophotoRGB primaries and can encompass any color your camera can capture. It is possible that your green falls outside of adobeRGB and gets clipped in the library preview, while in the develop module it shows them. This is only possible to see if you have a wide gamut monitor, or when your calibration software generates a perceptual rendering intent. If you export and you do not use the prophotoRGB color space, you will loose these colors.

  • HT2946 Why is the contrast of my images totally different when processed and then opened in CS4?  Does anybody else have this issue?

    Why does the contrast in my images processed in Aperture look markedly different when opened in CS4?  The images look fab on the screen in Aperture - even if these are then opened in CS4 from Aperture they look different  - much flatter.  This is a new issue.  I am a wedding photographer and an album processed in Aperture has been sent back by my wedding album printer saying the images all lack contrast!  Can anybody shed any light on this!  I have checked colour spacing etc! 

    I Also have this problem!!
    In my situation, the screen simply started exhibiting the same symptoms a few weeks ago (early February) for no apparent reason.  At first I thought the screen was dead, but discovered the heat solution by accident.  Now I turn it on and keep it from going to sleep until I go to bed.  Thank goodness the battery is still awesome on this thing.
    I bought it new and still has the original screen, I keep it at home (never below 62 degrees).  Coincidentally, this happened a day or two after the expiration of the warranty!!  Any help figuring this one out would be eternally appreciated.
    iPad mini retina Wi-Fi, iOS 8.1.3

  • Image Displays Differently in PS and Br CS4

    I have a gs tif file that I converted to cmyk. In PS the cmyk version looks virtually identical on screen to the gs version although when you hold the eyedropper over the image, cyan displays as a higher percentage than m or y, with k lowest in both the cmyk conversion and the grayscale original...what do I have set wrong!  In Bridge the cmyk version clearly shows a cyan cast.
    Color settings are synchronized in CS4.
    Can anyone tell me why: 1, the images are displaying differently, and, 2. using Convert To Profile, cymk, Working CMYK US Sheetfed Coated v2, image appears to have a distince cyan cast? And why, for that matter, is the GS image showing uneven cmyk percentages?
    Thanks in advance
    J

    the images are displaying differently
    Have you proofing enabled in both of them? Even if the profiles match otehrwise, that option still has to be toggled.
    image appears to have a distince cyan cast?
    Well, if you print CMYK, you want "rich black", which means that it needs to be underprinted with another color to not look like a dull gray. Only spot black/ text black does not require that. That's not the point here, though. It's really due to the conversion being done wrong. If you really want to retain the blacks as a pure channel, use the method described. Also, if you can, in the future simply start out in CMYK to avoid these issues.
    Mylenium

  • Size difference between recorded and published?

    I'm launching a custom sized window using javascript for a
    e-learning course that has a nav bar at the bottom (my own, not
    captivate related - including next and back buttons that navigate
    html pages). I'm recording my movies at 790x496. When the .swfs and
    the html outputed by captivate 2 are published it is adding 24
    pixels at the bottom. I'm using a captivate controller but it is at
    the top. If I try and manually go change the html back to my custom
    height the swf displays messed up. Anybody know how to get these 24
    pixels from being reserved/displayed at the bottom by the swf's?
    Just seems wierd to offer the ability to record at a custom
    size but then it automatically adds 24 pixels to the height.

    Hi theconfusedone and welcome to our community
    Hopefully I can help un-confuse you.
    Okay, click Project > Skin... > Borders tab. Note that
    the bottom border is the one selected. Further note the "Width"
    value. These are normally configured with the bottom border enabled
    so that the playback control doesn't cover any part of your
    project. So DE-select the bottom border and RE-select the top. This
    should allow space for your playback control and allow it to
    operate as you want.
    Keep in mind that this also creates an additional .SWF that
    will need to be included in your output. If you want no additional
    .SWF, you may DE-select the "Show borders" check box to force it
    all to be stored in a single .SWF.
    Cheers... Rick

  • Image looks different in Photoshop and Lightroom

    I started a forum on flickr and I have some issues with my images.  I have  calibrated monitor but my images look off online even though I saved them as sRGB.  Now my image looks one way in PS and then when I finish editing it and save it, I import it into lightroom and it looks different.
    Same image, but it looks different.
    http://www.flickr.com/groups/photoshopsupport/discuss/72157626443796391/#comment7215762645 5942911

    The image on the left in PS looks the same in Picasa Image
    Viewer (I selected it to be color managed based on the monitor profile), looks the same in Windows Image Viewer, and looks the same in the thumbnail.  The image on the right in LR is how the picture looks when I look at my image in Firefox but in Internet Explorer and in Chrome, the image looks like the image on the left in PS.  The image below shows how the thumbnail looks different from the actual picture when it's double clicked and viewed in Picasa.  The thumbnail (which shows the subjects having green skin) would be how I saw it online while the double clicked version is how I saw it in PS, even though it was sRGB (I checked the image properties to make sure of the color space).
    I have a ATI 5470 GPU on my ASUS 17.3 inch laptop.  Not sure about the drivers.

  • Is there a way to adapt image sizes for telephone, tablet and PC versions?

    I know Muse is not a CMS. Doing repetative actions all time, is timeconsuming and boaring.
    The ideal situation would be:
    Dump all pictures in a folder. Muse adapts the resolution of the pictures to match the requierements of the site for telephone, tablet and PC. Muse presents the pictures in a resolution apropriate to the device.
    Thank you for your time.

    1. Image placed in desktop version
    2. Same image (copy/paste) placed in phne version
    3. Exported files:

  • Image size different than the Bridge

    question. I shoot raw images and can export to jpeg in The Bridge at 6144 x 4096 (25.2 MP) 300 dpi. Opened in Photoshop that's a 20.4x13.6
    Why do the same images export from Lightroom at 3286 x 2191, 300 dpi??
    In photoshop that just under 11.6x7.7
    Where can I fix this in Lightroom please?

    There is no advantage to upresing until you go to print, and even then that's assuming the upresing you do is better than what the printer/printer driver does. The 1DII is an 8.2MP camera, and always upresing your images to 25MP sounds like a waste of disk space to me.

  • Same image displaying differently in FF and IE6

    This has me beaten
    http://wrfinn.com/map_leros.html
    (login/password fred) - the first image (I know it's out of
    alignment...
    later, later).
    What is displaying in FF is the original image before the
    circle/text was
    added.
    I have deleted it from the server and replaced it
    (desperation as it's fine
    in IE6) checked the scripts are there although I've tested it
    without the
    javascript with no better results. The DOM inspector is
    showing an error on
    the page in FF if this helps -
    [Exception... "'Permission denied to get property
    XULElement.accessKey' when
    calling method: [nsIDOMXULLabelElement::accessKey]" nsresult:
    "0x8057001e
    (NS_ERROR_XPC_JS_THREW_STRING)" location: "JS frame ::
    http://wrfinn.com/map_leros.html
    :: jspw3 :: line 43" data: no]
    <li><a href="#" class="p7PMtrg">About
    Us</a>
    Could somebody possibly throw some light on this?
    Jo

    josie1one wrote:
    > This has me beaten
    >
    >
    http://wrfinn.com/map_leros.html
    > (login/password fred) - the first image (I know it's out
    of alignment...
    > later, later).
    >
    > What is displaying in FF is the original image before
    the circle/text was
    > added.
    >
    > I have deleted it from the server and replaced it
    (desperation as it's fine
    > in IE6) checked the scripts are there although I've
    tested it without the
    > javascript with no better results. The DOM inspector is
    showing an error on
    > the page in FF if this helps -
    >
    > [Exception... "'Permission denied to get property
    XULElement.accessKey' when
    > calling method: [nsIDOMXULLabelElement::accessKey]"
    nsresult: "0x8057001e
    > (NS_ERROR_XPC_JS_THREW_STRING)" location: "JS frame ::
    >
    http://wrfinn.com/map_leros.html
    :: jspw3 :: line 43" data: no]
    > <li><a href="#" class="p7PMtrg">About
    Us</a>
    >
    > Could somebody possibly throw some light on this?
    >
    Hey Jo,
    did you get this resolved? - I don't see the problems that
    you are
    describing nor do I get a dom inspector error.
    The only thing I see is that the image which should reside
    under the
    side nav - you haven't set a path/source for this.
    chin chin
    Sinclair

Maybe you are looking for