Results 1 to 8 of 8
  1. #1
    2 Star Lounger
    Join Date
    May 2001
    Location
    Columbia MD USA
    Posts
    107
    Thanks
    6
    Thanked 0 Times in 0 Posts

    'Muddy' results when importing pictures? (2002)

    I recently upgraded from Visio 2000 to 2002. I've used Visio 2002 to create a diagram for a user guide-- it consists of an imported "picture" (in this case, a .gif file) and callouts. The callouts look fine, but the picture looks "muddy", both on screen and on paper.

    It looks almost as if some sort of edge smoothing or anti-aliasing is going on. I've checked through Visio's menu options and online help, but haven't found any setting that would explain this change. (doesn't mean its not there, just that I haven't seen it <img src=/S/grin.gif border=0 alt=grin width=15 height=15> ) Interestingly, a drawing that is "muddy" in 2002 looks fine in 2000.

    Any advice would be greatly appreciated.

  2. #2
    Plutonium Lounger
    Join Date
    Nov 2001
    Posts
    10,550
    Thanks
    0
    Thanked 7 Times in 7 Posts

    Re: 'Muddy' results when importing pictures? (2002)

    I have imported GIF files to Visio 2002 without any problems. You may want to try updating your video drivers.

    Can you post your GIF file and I will import it and post it back in a Visio 2002 document?

    StuartR

  3. #3
    2 Star Lounger
    Join Date
    May 2001
    Location
    Columbia MD USA
    Posts
    107
    Thanks
    6
    Thanked 0 Times in 0 Posts

    Re: 'Muddy' results when importing pictures? (2002)

    Thanks for the offer!

    I've been doing some experimenting...I think my video drivers are OK, they are dated May 2003

    Interestingly, Visio 2000-based images still look fine, even when opened, saved and printed in Visio 2002. And the real doozy is: if I open a Visio-2000 based drawing in 2002, (which looks good), and import the exact same GIF file, the newly imported GIF image looks bad.

    Sample files are attached... I'm assuming you have WinZip. If not, let me know and I will post separately (the two files together came out to 102 k. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15> ).

    Thanks again for your help.

  4. #4
    Plutonium Lounger
    Join Date
    Nov 2001
    Posts
    10,550
    Thanks
    0
    Thanked 7 Times in 7 Posts

    Re: 'Muddy' results when importing pictures? (2002)

    When I opened your document from Visio 2002 I could see two nearly identical images, both had very sharp lines and corners and no apparent visual issues.
    I imported the supplied GIF file into the same document, I had to shrink it by about 50% to make it look the same but it was equally sharp.

    I still suspect your video drivers.

    StuartR

  5. #5
    2 Star Lounger
    Join Date
    May 2001
    Location
    Columbia MD USA
    Posts
    107
    Thanks
    6
    Thanked 0 Times in 0 Posts

    Re: 'Muddy' results when importing pictures? (2002)

    Thanks for checking for me. Would you mind printing it and looking at it that way?

    I'll do some more research on my video drivers.

  6. #6
    Plutonium Lounger
    Join Date
    Nov 2001
    Posts
    10,550
    Thanks
    0
    Thanked 7 Times in 7 Posts

    Re: 'Muddy' results when importing pictures? (2002)

    I opened the file again, imported the gif again and printed it at best quality on an HP Deskjet 990 cxi
    All three pictures appear to be of the same quality.

    StuartR

  7. #7
    2 Star Lounger
    Join Date
    May 2001
    Location
    Columbia MD USA
    Posts
    107
    Thanks
    6
    Thanked 0 Times in 0 Posts

    Re: 'Muddy' results when importing pictures? (2002)

    That leaves the display drivers then. I may also try rolling back to 2000 and see if that makes a difference....

    Thanks for your help.

  8. #8
    2 Star Lounger
    Join Date
    May 2001
    Location
    Columbia MD USA
    Posts
    107
    Thanks
    6
    Thanked 0 Times in 0 Posts

    Re: 'Muddy' results when importing pictures? (2002)

    Strange but true...

    Removing 2002 and installing 2000 in its place solved the problem. I still don't know what the underlying cause was, but hey it works. Thanks Stuart for looking at those files for me.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •