PDA

View Full Version : Graphics issue with transparent GUI



bobt
17-02-2013, 5:42pm
This is more of a computer problem than a photography one ... but ... I've been using Adobe's DNG conversion for RAW files seeing that my camera is too new for my usual software to process them.

Something has got corrupted somewhere on my PC because now the interface comes up with holes in it which show through the the underlying screen. I've tried all the tricks I know to fix it, but nothing worls. The attached photo shows it on the AusPhotography site, and as you can see I can't fill in any details because they are now transparent and unresponsive. Any clues how to fix it?


97582

I @ M
17-02-2013, 5:53pm
Format your hard drive and start again?

Seems to be a regular occurrence for windows and adobe users.

ricktas
17-02-2013, 6:18pm
LOL @ ^^^

Have you tried uninstalling the DNG converter, then restarting your computer and reinstalling it?

Warbler
17-02-2013, 6:23pm
Update your version of Java and Adobe Flash. Also see if your video card has had a driver update.

bobt
17-02-2013, 6:30pm
LOL @ ^^^
Have you tried uninstalling the DNG converter, then restarting your computer and reinstalling it?

Yup .. that was my first "solution" ... now I'll try the driver upgrading suggestion! Mind you, it *was* working OK, so it's probably some other conflict.

Warbler
17-02-2013, 7:46pm
Not necessarily Bob. Go to the website of your graphic card manufacturer and download from there. Do that instead of just using the Microsoft Device Manager.

ameerat42
17-02-2013, 8:36pm
A long shot, but... Win Vista or Win & (??Or maybe even 8). The see-thru feature?? I know it bugs me with Firefox.
Just a long shot, F=1000mm, effete, just a sec, ISOtopic.
A(he)m.

davidd
19-02-2013, 9:54am
In Windows 7 you can turn off the transparency.

Right click on the screen, and click on Personalize...then Window Color at the bottom of the screen. Uncheck 'Enable Transparency'.

bobt
19-02-2013, 6:16pm
In Windows 7 you can turn off the transparency.
Right click on the screen, and click on Personalize...then Window Color at the bottom of the screen. Uncheck 'Enable Transparency'.
Mine doesn't have that checkbox, although I found it eventually in the menus (and it didn't make any difference). The odd thing is that if I click on one of the themes, then ADG suddenly decides to work OK, and continues working until I close it. If I subsequently reopen it, then it remains unresponsive until I pretend to change the theme again. It's a "workaround", but not very good. However, thanks for pointing me to an area which let me find an interim solution!!:rolleyes:

arthurking83
19-02-2013, 11:39pm
I'd love to use this opportunity for another jibe at Adobe for their marvelous software efforts .. but I get occasionally similar issues with Nikon's software too!

I dunno if it has anything to do with transparency at all(mine are really random) and some weeks go without seeing the issue at all, and some times it's relentless.

But I see it sometimes if I have ViewNX2 open, and use the Open with CaptureNX2 option on my raw files.

That is, I get over and underlays of CaptureNX2, with traces of ViewNX2 in various locations(kind of similarly to your screencap).

99.9% of the time, if I see this I close CNX2 and reopen the image again, even while VNX2 is still active and it disappears totally, so that CNX2 is properly displayed.

Once, maybe twice the problem persisted, to the point where I've tried to close down ViewNX2(suppsedly in the background, but still active).

Memory issues, graphics card memory issues .. dunno.

So .. in your case Bob, is the issue persistent, in that every time you open the DNG converter, this happens?
What if you only have the DNG converter open and active, and nothing else ... do the holes display the background/desktop image of your PC?

ricktas
20-02-2013, 8:06am
It really does sound like a memory buffer issue of some sort. Where either the computer or the graphics card memory cannot keep up with supply of data to the screen. Try using DNG without any other programmes running, not even the browser. If it works OK when its the only thing running, but this happens when you have DNG open, browser open, photoshop open etc, its a memory buffer issue. My guess is that this occurs when the system is 'under load'.

It would be interesting to know the memory specs of the computer and the graphics card.

With windows you can do Ctrl+Alt+Del then when the options screen comes up 'start task manager'. On the 'processes' tab, click on CPU or memory at the top (till they sort into usage order) and watch what is using your memory up while using DNG. Also look at the 'performance' tab and watch what is happening with your CPU and memory, again while using DNG. My guess is that when this transparency occurs, something will peak out, giving you a hint of the cause.

bobt
20-02-2013, 10:52am
So .. in your case Bob, is the issue persistent, in that every time you open the DNG converter, this happens?
What if you only have the DNG converter open and active, and nothing else ... do the holes display the background/desktop image of your PC?

Yup ... all the time, and I can't remember what changes I introduced that caused it (I install various bits of software all the time). The only way I can use it is the odd workaround I mentioned before. It's got to be some sort of conflict somewhere, but darned if i know how to un-conflict it!

Rattus79
20-02-2013, 2:15pm
Gee this would be an easy fix if your camera had a DNG workflow built in!

Oh! what? you don't have a Pentax??!! :D

looks and sounds like a video driver conflict to me. I'd be looking to upgrade your graphics card driver to match your fandangled new camera and Adobe software.

bobt
20-02-2013, 2:42pm
It really does sound like a memory buffer issue of some sort. My guess is that this occurs when the system is 'under load'.
It would be interesting to know the memory specs of the computer and the graphics card.


Stacks of memory, and not even a ripple on the CPU or memory when I open it - I downloaded one of those "fix all" programs, but that didn't help either. The graphics are just on-board graphics as I don't have a dedicated graphics card - but DNG worked well before the conflict appeared, and it works well if I do the workaround to get it started. I suspect that tongue in cheek suggestion to format the drive might be the only cure!


Gee this would be an easy fix if your camera had a DNG workflow built in!

Oh! what? you don't have a Pentax??!! :D
looks and sounds like a video driver conflict to me. I'd be looking to upgrade your graphics card driver to match your fandangled new camera and Adobe software.

I've got a Pentax ... I keep it with my other antiques! :lol:
I think you're right about the driver conflict though ...... probably my fault for having so many programs on the PC - I'm a bit of a software junkie.

Rattus79
20-02-2013, 5:12pm
When you go to your task manager, how many processes does it report in the bottom left corner.
This is usually a good indicator of system health. The fewer processess running, the more resources the system has available to it, the less chance of a conflict arising.

Generally I try to keep it below 80 on a newer machine. In the old XP days, anything over about 50 was going to make your system chug.

bobt
20-02-2013, 6:14pm
When you go to your task manager, how many processes does it report in the bottom left corner.
This is usually a good indicator of system health. The fewer processess running, the more resources the system has available to it, the less chance of a conflict arising.
Generally I try to keep it below 80 on a newer machine. In the old XP days, anything over about 50 was going to make your system chug.

It's got 90 at the moment, but even when I first boot up DNG has the transparency issue, and it was working fine. Unfortunately, the PC has more memory than I have (by a large factor) and so I can't remember what I have changed since it was OK. I have stacks of memory and spare processor - I might try starting in safe mode and see if it'll work that way.

Rattus79
21-02-2013, 10:36am
if not, then the good old:

C:/>Format C: /s Should do the trick :D