More Gamma Issues
Today, I wanted to focus on the current state of RAM Preview.
Last week, I went through exhaustive testing of color accuracy through an After Effects workflow, with source material generated out of Final Cut Studio 2 & 3, all 1920x1080 29.97i. I performed tests through After Effects CS3, CS4, and CS5. In all cases, we used both Tektronix 601A and The results were eye-popping.
After going through your notes about the recent gamma issues, I made your recommended changes to the Interpretation Rules, as well as the MediacoreQTGammaRulesCSx, along with the proper color management settings (Rec 709).
Setup:
MacPro 3GHz 8-core (MacPro2,1)
16GB of RAM
AJA Kona 3 v.7.5.1 or v.8 drivers
OS 10.5.8
QT 7.6.4
In the case of CS3, gamma accuracy simply can not be had either via RAM Preview nor via rendered files. In CS4, one can clearly see that Adobe did a very good clean up job on gamma accuracy but those fixes are limited to rendered files. RAM Preview using the QuickTime Output Component through an AJA Kona xx card aren’t even close when looking at Gamma. As a result, black levels are several IRE too low. If we use the AJA Adobe Plug-ins for 7.5.1, I can get accurate Gamma BUT I can’t get real-time frame rates if I use a Project bit depth > 8bit.
So I have a choice, inaccurate Gamma or bit limited RAM Preview. So why is running a project in 8-bit mode bad? Banding and color skew. Most camcorder acquisition formats are 8bit YUV. Doing conversions from 8bit YUV to 8bit RGB are simply bad. You are converting from a scaled color space in which your usable levels are 16-235 (YUV) over to 0-255 (RGB). As a results, you are going to have plenty of errors. By converting to a 16-bit RGB space, those errors are virtually eliminated.
Now we both know that RAM Preview desperately needs a “do-over” and has for years. But, it is what we have today and our clients desperately need a solution that offers both gamma accuracy and real-time frame rates in 16 & 32bit modes.
Thank you for listening
I tried the three solutions noted on the page, but none of them actually "address" what my problem is. I could not find the directory in the registry, nor could I create one. Is there any last-ditch attempt or solution? I was told I could turn the "time" back on my computer, though I don't want to lose my information or run the risk of nothing happening. For now, thanks for your help.
ADVICE WELCOME!
Similar Messages
-
Hi there Adobe folks
This is just a follow up post to see if any movement has been made on the gamma issue front.
Basically importing footage into AE and then exporting results in unpredictable shifts in brightness, appearing either darker or lighten than they appear in the composition window or even when played in the Quicktime player - as well as suffering a colour cast change.
So at the moment I am on a iMac i7 with CS4 AE and OS X 10.6.4 - and AE is almost unusual for me as I may spend hours carefully colour correcting a pieces of footage only to have my output look completely different, I have used AE professionally for over 10 years now and have never had these issues, when I used to render my final piece (usually as uncompressed or as Animation set at 100% Q) the resultant file is identical to what you see in the composition window - everytime, without failure.
Now trying to get the output look anything like the composition window seems next to impossible, I am not the only one suffering this problem, I was working in London last week at a fairly well known studio and their compositors have all but given up on AE for this very problem, we even - at one stage - ended up working in Photoshop (!!) to get around this problem.
So, any news on possible solutions out there yet ?
Cheers for any input.Musings on a disaster . . .
Worked my way through all the literature - some of it comes reasonably close to addressing the gamma / colour shift problems (after a lot of reading and testing and failing and frustration), nothing seems to correct it absolutely . . . . which ultimately renders After Effects unusable as a professional tool (up to CS4 at least - I have not upgraded to AE5 as the upgrade appears to be prohibitively expensive).
I understand that the real villain in all this is Apple/Quicktime, but it shocks me that Adobe (with AE) have not taken a much more robust approach to resolving this problem.
Most of the tools I used to depend on and trust on for my day to day work are very simply useless now, what point is there in sitting with a client for 6 hours grading a piece of footage only to find yourself unable to deliver what the day's work achieved, why bother using Colour Finesse when leaving the 'full interface' mode to view your work in the composition window you see a differing version - and so on.
What is more frustrating is that this problem simply did not exist a version or two ago, I happily spent well over a decade (professionally) being able to concentrate on making things appear as I wanted them to and then being able to deliver just that - this has seemingly gone.
Literally put, After Effects is broken.
I really appreciate all the help I have got from this forum in trying to resolve this, but nothing has come close enough that it could be considered a solution, it's simply no good telling a client: "It's a bit washed out and the colour is a little bit more red than we wanted, but it's pretty close".
So . . . . solutions (more correctly compromised work arounds) - I hope these might be of some help to others stranded on Adobe/Apple island.
Basically I suspect my requirements at output are much the same as others who do this for a job, firstly a master output for delivery/broadcast/tape - and a compressed output for client proofing.
For the compressed non-master - I used the latest x264 codec - simply download it (Google is your friend) - install it and ignore all those other codecs that you have used over the years - this actually works pretty well, your AE render looks identical to your AE composition (100% identical) when played back in QT7 - and only a little washed out when played back in QT10 (much less washed out than other codecs).
For the master output - forget the days of being able to render to 'uncompressed' and know all is well - those days are seemingly gone. But you can still come fairly close to rendering something to a lossless format that looks reasonably close to your composition if you stick to 'Animation' or 'ProRes' - the reason I am not more specific here is that your success would seem to depend on the particular project - sometimes ProRes get's 90% of the way, other times it looks overly saturated and Animation get's you closer - so experiment, but these two high-quaility codecs can often get fairly close.
(*ProRes is not, of course, 'lossless' - but in the circumstances if it renders closer to the look of your composition than Animation it is not a terrible compromise).
On a final note: I used to work at a post/facilities house in London (UK) who have used AE since at least 1998 (when I first worked for them) - I was freelancing there last week and they seem resigned to After Effect's death as a professional tool and are now looking at other compositing environments.
Additionally I managed a small coup recently in being able to steal a small piece of work (a single scene from an upcoming Christmas TV ad for UK TV**) from another major - perhaps the biggest, most respected - London post house - they floundered in being able to convincingly replace an actors face with a (much happier) replacement (using Inferno) - the Director handed me the scene - I got it to work really well, he much preferred my result, I was pretty happy with taking on a major facilities house and beating them - but the process of delivery was simply embarrassing, they used my (After Effect's) erratic output to - I suspect - win back some face at not being able to do the scene as well - after much battling with After Effects the decision was to use my render as a guide only for the Inferno operator - such was the inability of several professionals to output an identical file.
After 15 years in this game that was f*&king disappointing and not a little bit embarrassing as I am sure you might imagine. -
As a relative newbie on a very steep learning curve, I have just come across the Gamma issues when creating H264 videos on the Mac and then having them viewed on PC.
I've spent all day reading the thousands of comments on various websites regarding this issue and think I now have a basic understanding of the cause. However I am still quite confused as to the solution.
In Ken Stone's brilliant tutorial 'Compressor H.264 movies from FCP for the web' he states that H264 handles Gamma correction by burying 'Colour Sync' profiles into the QT movies so that at playback, the H264 QT movie will check the platform of the viewer and adjust Gamma correctly. So I thought all of the stuff I was reading must have been prior to Ken's comments.
After compressor had made an amazing job of my video, I sent it over to the PC ready for a first test and yes, it looked bad and clearly the Gamma was wrong.
I then found a workaround that literally hundreds of people had used: where by the finished QT file was adjusted as follows:-
"After rendering into a QuickTime/h.264 file, open it up in QuickTime and select “Show Movie Properties.” Highlight the video track then click on the “Visual Settings” tab. Towards the bottom left you should see “Transparency” with a drop-down box next to it. Select “Blend” from the menu then move the “Transparency Level” slider to 100%. Choose “Straight Alpha” from the same drop-down and close the properties window and finally “Save.”" More details of that here - http://www.videocopilot.net/blog/2008/06/fix-quicktime-gamma-shift/
I have now made different versions of the video, with and without the changes outlined above. When they are viewed either 'standalone' on my PCs and laptops or downloaded from my website, compared to how they looked on the Mac, just look completely dull and flat.
I’m trying to work my way through this problem but in the meantime if anybody can help, I would be eternally grateful..?
ThanksAs a relative newbie on a very steep learning curve, I have just come across the Gamma issues when creating H264 videos on the Mac and then having them viewed on PC.
I've spent all day reading the thousands of comments on various websites regarding this issue and think I now have a basic understanding of the cause. However I am still quite confused as to the solution.
In Ken Stone's brilliant tutorial 'Compressor H.264 movies from FCP for the web' he states that H264 handles Gamma correction by burying 'Colour Sync' profiles into the QT movies so that at playback, the H264 QT movie will check the platform of the viewer and adjust Gamma correctly. So I thought all of the stuff I was reading must have been prior to Ken's comments.
After compressor had made an amazing job of my video, I sent it over to the PC ready for a first test and yes, it looked bad and clearly the Gamma was wrong.
I then found a workaround that literally hundreds of people had used: where by the finished QT file was adjusted as follows:-
"After rendering into a QuickTime/h.264 file, open it up in QuickTime and select “Show Movie Properties.” Highlight the video track then click on the “Visual Settings” tab. Towards the bottom left you should see “Transparency” with a drop-down box next to it. Select “Blend” from the menu then move the “Transparency Level” slider to 100%. Choose “Straight Alpha” from the same drop-down and close the properties window and finally “Save.”" More details of that here - http://www.videocopilot.net/blog/2008/06/fix-quicktime-gamma-shift/
I have now made different versions of the video, with and without the changes outlined above. When they are viewed either 'standalone' on my PCs and laptops or downloaded from my website, compared to how they looked on the Mac, just look completely dull and flat.
I’m trying to work my way through this problem but in the meantime if anybody can help, I would be eternally grateful..?
Thanks -
I jumped from using CS3 to CS5 so this may have popped up in CS4 and everyone else figured it out already.
I used to deliver files in QT Motion JPEG codec. However in CS5 when I output in that format everything looks washed out as though there is a gamma issue when playing back in QuickTime, or other editing software. If I open that QT file back up in After Effects it looks fine.
I'm not using color management, just an out-of-the-box installation at the moment.
I switched to delivering in QT Animation codec which solved the problem but the filesize was overkill for this particular project.
Any help is appreciated!This did fix the problem asuming I want to bring the footage back into after effects. When I do that everything matches.
But...
If I open the original source footage up with QuickTime, or in a 3rd party editing application and compare it to the AE render made with "Match Legacy After Effects QuickTime Gamma Adjustments" and also compare to a render made without that setting turned on I get very different results
The original source looks good, but both renders look equally incorrect (washed out like a gamma problem)
Is After Effects adding a pripriatary tag to the output file that only AE is resepecting when it's loaded back in?
Thanks! -
I know the 1.8 vs 2.2 gamma issue has been talked to death, but I don't know the answer to this specific question, hence this post.
Does the 1.8 vs 2.2 gamma issue occur when simply watching DVDs? I've made many DVDs which I can watch on my PC or TV or Mac and it looks good on all three. I also don't have any problems watching professionally made DVDs on my PC, Mac, or TV. But the latest DVD I made, while it looks great on a PC and a TV, it looks horrible on a Mac. And everyone I've talked to has said it is due to the gamma issue.
The only difference I can think of between this DVD and the other DVDs I've made is this the images in this one are darker. Also, its the first time I've ever crushed the blacks in color correction, which made the images even darker than they were to begin with.
But I've watched many professional DVDs with very dark images on my Mac and they look fine, so I don't know why my DVD does not.
Some information that might be useful:
Footage: DV anamorphic
Raw footage codec: DV/DVCPRO - NTSC, Integer (Little Endian)
Color corrected footage codec: DV/DVCPRO - NTSC
DVD image format: MPEG-2
Please note that this issue only involves watching the finished product. The footage has already been color corrected on a properly calibrated TV. I just would like to watch my DVD on my Mac!its the first time I've ever crushed the blacks in color correction, which made the images even darker than they were to begin with.
whats the reason for doing that, why are you not setting the black level at black point?
properly calibrated TV
not really the best piece of equipment to be trusted for colour correcting, even going to the expence of getting the TV calibrated (presumably by an engineer) the TV cant be compared to a professional programme monitor, the only real way to colour correct. -
I saw some posts about load more messages issues, but nothing seems to be the same as my problem. I'm new to iPhone, so I must be missing something obvious.
I was looking at my emails this morning and deleted all but 5. I responded to an email, but didn’t send because I forget change the server port for outgoing mail that our server requires. So I went into settings and changed the port. I went back to my inbox but can no longer see the messages I saved, instead there's an option that says “Load More Messages” with a note below it stating “5 messages total, 0 unread”. I have no other emails in my inbox. When I click Load More Messages, nothing happens. I can’t figure out how to get to those emails. I tried cycling the power on the iphone, that didn’t help.
I'm getting new messages normally. My mail is set to show 25 recent messages. Even if I change this, it still displays the "Load More Messages". As an extreme test, I set it to show 200 recent messages, went back to my inbox, hit the "Load More Messages" option, but that didn't help. What's more, I have a full signal and I'm running 3G.Hey man, your problem sounds similar to the one I'm having. I can't load more messages on both of my email accounts. But I think I might have figured out the problem. I recently re-installed my hotmail account and when I was looking through my,"Unread" inbox the, "Load more messages" command was working just fine. So I was continuing to go through my messages to make them read (because if your like me, I don't like to have any messages, "Unread." So when all my messages were read there was about 80 in total, and my setting was set to show the 25 most recent. So I backed out of the mail app, did a few more things and came back hoping that there would only be 25 showing with 0 unread and the ability to load more if i wished. Well, there was 25 showing but the box with the load more messages command was gone and no matter how many times I tried to refresh it would not come back.
So my theory is this; there always has to be an unread message in your inbox for the load more messages to work. Sorry about the long post. I'm going to test this theory out, knowing my luck, it won't work at all. Good luck bro!
Peace. -
Return delivery more than issued quantity
Hi,
I posted the goods issuance quantity 10 with mvt 201, when return delivery with mvt 202 then system allow to post more than issued quantity.
is there any restriction or standard error message to control this.
Regards,
AliHi
Are you not cancelling the document with reference to the original document. In this system will not allow you to change the quantity.
Also, refer to enhancement MBCF0005
and BADI: MB_QUAN_CHECK_BADI
Thanks
Sachin -
I seem to have a problem with gamma in FCP6 on snow leopard. Rushes in QT are fine, but appear very dark in FCP. I have read on Creative Cow forums that the fix is to upgrade to FCP 7 (!!) but I was rather hoping I could avoid this extra expense just now.
Any other suggestions? I don;t understand why FCP6 would not display colours correctly.
Is there a user setting I need to adjust in FCP? I can see a difference between setting the play back gamma to "accurate" and "approximate". Does this mean that QT is not displaying gamma correctly? Would be nice to get both to match.
Thanksajophoto wrote:
Any other suggestions? I don;t understand why FCP6 would not display colours correctly.
The COW thread you linked to explains that FCP adjusts the gamma to approximate what it would look like on a broadcast monitor which causes problems with Snow Leopard as it changes the default gamma profile of the OS. I cannot confirm whether or not this is fixed in FCP 7.
I seem to have a problem with gamma in FCP6 on snow leopard. Rushes in QT are fine, but appear very dark in FCP. I have read on Creative Cow forums that the fix is to upgrade to FCP 7 (!!) but I was rather hoping I could avoid this extra expense just now.
Why does it matter if you are offlining? Even if you had FCP 7 and it fixed the gamma issue, I would still not recommend relying on it for accurate image reproduction.
Is there a user setting I need to adjust in FCP? I can see a difference between setting the play back gamma to "accurate" and "approximate". Does this mean that QT is not displaying gamma correctly? Would be nice to get both to match.
There is no setting in FCP, only "Final Cut Studio color compatibility" in QuickTime 7. But there is still some discrepancy between the two, even on Leopard. I never rely on this. -
N8 Belle more of issue than fun
I am using Belle for more than a month now and came up with these issue.
1. when i am using foursquare app with mobile data just connected, it hangs the device.
2. Once I disconnect from a Wi-Fi network, after a second or so all the icons reinitialize for all the screens.
3. Using app stop to kill all the apps excluding clock sometimes hangs the device.
Due to these issues i have to restart the device once a day to keep it working properly and which is very annoying. Are these normal issue with Belle or something terribly wrong with the device.
Thanks.
If I have helped at all, a click on the White Star is always appreciated. You can also help others by marking 'accept as solution'.Also i found concerns in the existing camera with worked great with Anna update. I have default camera then camerapro and cameralover.
4. When using camerapro with 'single' AF it shows red box for initial 2-3 tries and then focus correctly.
5. The quality of autofocus for default camera has also decreased and gives blured snaps.
Not sure anyone facing the same issues, but these are major applications and feature for N8.
And if they perform like this then it is a pain.
If I have helped at all, a click on the White Star is always appreciated. You can also help others by marking 'accept as solution'. -
More Major Issues with ZFS + Dedup
I'm having more problems - this time, very, very serious ones, with ZFS and deduplication. Deduplication is basically making my iSCSI targets completely inaccessible to the clients trying to access them over COMSTAR. I have two commands right now that are completely hung:
1) zfs destroy pool/volume
2) zfs set dedup=off pool
The first command I started four hours ago, and it has barely removed 10G of the 50G that were allocated to that volume. It also seems to periodically cause the ZFS system to stop responding to any other I/O requests, which in turn causes major issues on my iSCSI clients. I cannot kill or pause the destroy command, and I've tried renicing it, to no avail. If anyone has any hints or suggestions on what I can do to overcome this issue, I'd very much appreciate that. I'm open to suggestions that will kill the destroy command, or will at least reprioritize it such that other I/O requests have precedence over this destroy command.
Thanks,
NickTo add some more detail, I've been review iostat and zpool iostat for a couple of hours, and am seeing some very, very strange behavior. There seem to be three distinct patterns going on here.
The first is extremely heavy writes. Using zpool iostat, I see write bandwidth in the 15MB/s range sustained for a few minutes. I'm guessing this is when ZFS is allowing normal access to volumes and when it is actually removing some of the data for the volume I tried to destroy. This only lasts for two to three minutes at a time before progressing to the next pattern.
The second pattern is categorized by heavy, heavy read access - several thousand read operations per second, and several MB/s bandwidth. This also lasts for five or ten minutes before proceeding to the third pattern. During this time there is very little, if any write activity.
The third and final pattern is categorized by absolutely no write activity (0s in both the write ops/sec and the write bandwidth columns, and very, very small read activity. By small ready activity, I mean 100-200 read ops per second, and 100-200K read bandwidth per second. This lasts for 30 to 40 minutes, and then the patter proceeds back to the first one.
I have no idea what to make of this, and I'm out of my league in terms of ZFS tools to figure out what's going on. This is extremely frustrating because all of my iSCSI clients are essentially dead right now - this destroy command has completely taken over my ZFS storage, and it seems like all I can do is sit and wait for it to finish, which, as this rate, will be another 12 hours.
Also, during this time, if I look at the plain iostat command, I see that the read ops for the physical disk and the actv are within normal ranges, as are asvc_t and %w. %b, however is pegged at 99-100%.
Edited by: Nick on Jan 4, 2011 10:57 AM -
Interface/Gamma issue - Display profiling
If you profile/calibrate your display (with professional software) to Gamma L* - darkish, grey boxes appear in some application-windows. Never happend in Tiger so I figure it's a Leopard issue.*
If you use Gamma 1.8, the Apple default, Photoshops windows (in my case) look perfekt. With Gamma 2.2 they're barely noticable (pretty much only if you know the boxes are there).
All the other settings you can choose while profiling - like temperature, luminance, chromatic adaption, profile-type etc. don't influence windows in this way - but as soon as you change the gamma those boxes appear.
I would very much like to know how you guys deal with it - do you profile your display to 1.8/2.2 (like a CRT) OR do you use L* and live with the boxes OR have you profiled your display properly/with L* but you don't have this nuisance? (!?)
Any help/info would be greatly appreciated.*So here's what I think happens (+ my idea to solve the grey-boxes issue):*
Some applications use the monitor-profile to draw their interface. Like Photoshop and Graphic Converter. (The only 2 I've installed, I'm sure some video-editing-applications, even players are concerned that's maybe the reason some people think it's 'random'). I think these apps do so to immediately can reflect a change in the profile, without restart.
Now Mac OS X Leopard seems to not allow these applications to do so in certain parts of the interface. (Must be new, that's why there were no issues with Tiger) The window itself is drawn by the OS. That's the reason only elements like the text and buttons are affected.
And the problem is that the OS uses its 'Generic RGB Profile.icc' which contains Gamma 1.8. So if you calibrate your display with Gamma L* (which you really should do and most profiling-software does by default) those grey boxes appear in said applications.
The solution is easy. Replace the system-rgb-profile with one that supports L* - like the eciRGB profiles.
To do so you have to rename the .icc file in finder but also edit the information inside (which can be done with the ColorSync Utility). Then copy it to the System/Library/ColorSync/Profiles folder.
*After that the grey boxes dissapear and everything is back to normal.* There's some difference in the tabular data like the CMM and a chroma-entry, so you might want to re-write your display-profile just to make sure everything's alright.
I haven't seen anything yet but could imagine that the rendering of webpages in safari might be affected. Or rather some webbrowsers' without colour management. (Just a theory, hopefully not...)
*Problem 1:*
Some Adobe apps can see that the current system-profile is identical to your working-space-rgb and reset your rgb-choice to the Generic RGB profile after a restart. (Without changing the 'Colormanagement SYNC'd icon/setting.) This probably could cause trouble if you export or open files.
Solution:
Use a different profile for your system than your Adobe-RGB setting. I used the 'L-Star RGB v2' for the system and the 'eciRGB v2' for Adobe. They're technically identical but for some reason Photoshop and esp. Illustrator now respect my choices and don't reset anything. Works fine for me.
*Problem 2:*
Besides the aforementioned chroma-entry in the Apple default profile (which loss shouldn't cause any issues) there's also the localisation information. Because the profile is named differently in different languages of OS X. I haven't found anything causing trouble (probably because if the profile isn't found it resets back to the english version by default).
Solution:
This would be easy if someone knows about a .icc file editor. If we could add those localised names from the Apple profile no application would ever know. I've only found hexadecimal editors but won't put something like that on my machine, especially since everything works fine.
*I hope Apple comes up with a real solution soon, this seems like too much of a hack - considering the delicate nature of colour management.*
*If you read this and know what I'm talking about and disagree or know any reasons why one would not want to do this - please speak up! I'm sure I'm not the only one who would like to know.*
This is pretty much mirrored on the Adobe forums btw. -
Network printing, more driver issues
A simple HP990 connected to an IP print server is a disaster under OS X.
1) HP provides drivers that work wonderfully - as long as it's USB (wired)
2) HP drivers dissapear if ADD PRINTER cannot physically find printer during install
3) GIMP drivers are latest - and they are almost 2 years old
4) No 2-way comm w/printer - this is NOT an IP issue
5) Dozens of printer features are unavailable to OS - show ink etc
6) Duplexing is just plain broken
7) Although HP drivers are installed, they will NOT be available to you if printer is not connected via a WIRE. This is rediculous.
8) IP "Find Printer" does not work. Cannot even find Linux printers, much less Windows, netBeui, or Wireless printers.
9) If you force printer model, you cannot use proper HP drivers. Must use GIMP.
10) Once printer is installed/configured, you CANNOT change ports. Again this is redic.
I was told OS X was VERY problematic with printing. It's the achilles heel in an otherwise wonderful OS environment.
Come on, Apple. Fire the printer guy over there and get this stuff straight.THe HP deskjet driver does not support printing to a DeskJet 990 connected to a generic TCP/IP print server.
In Mac OS X 10.0 and 10.1 the printer drivers had to enumerate the communication protocols that they supported. This requirement was removed in 10.2 but many of the printer manufacturers still provide drivers that are tied to specific protocols. The HP provided DeskJet 990 driver support USB and AppleTalk. It may also support printing over TCP/IP to an HP JetDirect server but I've never tried that.
The Gimp-Print drivers are written so that they are independent of the communications protocol used. The Gimp-Print drivers will work over USB, Bluetooth, LPD, IPP, AppleTalk, socket, SMB, and other protocols. The Gimp-Print project is very active. It is currently closing on the release of version 5. The project has been renamed Gutenprint. You can find more information here: http://gimp-print.sourceforge.net/
1. HP drivers work over USB and over TCP/IP depending upon the printer model. For example the Photosmart 2510 driver works great over a wireless connection using TCP/IP to that printer.
2. I'm not sure what is being described in this bullet item.
3. The latest version of Gimp-Print is v5.0rc2. As noted above the project is now called Gutenprint.
4. The HP drivers support bidirectional communication. The Gimp-Print drivers do not support bidirectional communications yet but they will likely do so soon.
5. Some drivers support low ink detection and some do not. The drivers that do support low ink detection show it in the print dialog and in the desktop printer. Most drivers also come with Utilities for checking ink levels and these are linked to by the desktop printer.
6. Duplexing works fine using the HP drivers. Are you having a problem with duplex and the Gimp-Print driver?
7. As discussed above the HP drivers can not be hooked to a communications protocol they do not explicitly support. This has nothing to do with wired versus wireless.
8. The Add printer browser shows locally attached printers, AppleTalk printers, Bonjour TCP/IP based printers, and printers shared from Linux CUPS servers. Other printers can be found by hitting "More Printers."
9. Again, yes, the HP drivers can not be used over a generic TCP/IP connection such as LPD, IPP, or socket. The Gimp-Print drivers do work over these connections. So do the HPIJS drivers. The HPIJS drivers can be found here: http://www.macupdate.com/info.php/id/9979.
10. This is true. If the TCP/IP address changes on a printer then you need to re-add the printer.
I hope this is helpful. -
I posted this on September 12th, and concluded I needed a new power supply.
I purchased an Enermax EG475P 470W PSU, since that seemed to be the likely conclusion of my problems.
I went from my old PSU with these specs:
Ultra ATX Switching 400W, Model #WIN-400PS
+3.3V = 15.0A
+5V = 30.0A
+12V = 17.0
-5V = 0.6A
-12V = 0.6A
+5VSB = 2.0A
To these specs:
Enermax EG475P 470W
+3.3V = 34A
+5V = 40A
+12V = 33A
I am still getting the crashes that I explained in my first thread.
Before buying the new PSU I had tried everything I knew to do. When I got these crashes even after installing the new PSU, someone told me to try underclocking my card to see if it might be a heat issue. I underclocked it more than 10%, with no changes.
It isn't a CPU heat issue either; I ran Motherboard Monitor 4 while stress-testing with a game and the temperature never went past 61C. That isn't ideal, I know, but I read threads on this board from people saying their Prescotts are running 70C, 80C, or even higher. According to Speedfan, my four case fans are all running at 100% RPM. At idle, the case temperature is 34C. Under load, it never goes past 37C.
I don't really know what to do. Any ideas?
Intel Pentium 4 Prescott 2.8GHz HTT w/ 800MHz FSB
MSI 865PE Neo2-PFISR motherboard (BIOS ver. 3.8)
2x512MB Kingston PC3200 DDR SDRAM @ 400MHz
Maxtor 6Y120M0 120GB HDD
Diamond Viper Radeon 9600XT 256MB (Catalyst 4.9s)
Creative SB Live 5.1 (driver ver. 5.14)I included them in my first post, but here they are anyway.
Intel Pentium 4 Prescott 2.8GHz HTT w/ 800MHz FSB
MSI 865PE Neo2-PFISR motherboard (BIOS ver. 3.8)
2x512MB Kingston PC3200 DDR SDRAM @ 400MHz
Maxtor 6Y120M0 120GB HDD
Diamond Viper Radeon 9600XT 256MB (Catalyst 4.9s)
Creative SB Live 5.1 (driver ver. 5.14)
Enermax EG475P 470W
+3.3V = 34A
+5V = 40A
+12V = 33A
And here's the problem:
Quote
Sometimes it will crash as I described in the other thread, the video and sound locks up, nothing responds, have to hit power button.
Other times it does something different. For example, while playing BF1942, when the server changes maps, each client does a CD check during which my screen resolution changes to some low resolution, then back to normal resolution (which is 1280x960x85, btw). Every few times* it does this, my system restarts itself. Back to the POST screen. My computer restarts normally after this happens. When I get back to Windows, I get a popup message saying "Windows has recovered from a serious error. Please send an error report, blah blah." I got these crashes before upgrading my PSU as well, but thought that the PSU was causing it. I thought that the resolution changes + CPU load from loading a new map was putting too heavy a load on my system, which my cheap PSU couldn't handle, and thus shut itself down. But these crashes are continuing after upgrading to a PSU which should be able to handle just about anything.
*It isn't a consistent pattern. Sometimes it will restart during the first map change. Other times it works fine for four or five or six times, then it will crash.
I also listed the Blue Screen error message in this thread too. You sure you read the right thread? -
Leopard - CS3 - Interface/Gamma issue
Hello there, switched to 10.5(.4) on a MacPro today and now check this out, it's only in Photoshop. Illy and Indesign and Bridge are fine. No other applications are affected.
If you profile/calibrate your display (with professional software) to Gamma L* - darkish, grey boxes appear in the Photoshop dialogue windows.
http://img297.imageshack.us/my.php?image=leopardphotoshop11zg0.png
If you use Gamma 1.8, the Apple default, Photoshop looks perfekt. With Gamma 2.2 they're barely noticable (pretty much only if you know they're there).
All the other settings you can choose like temperature, luminance, chromatic adaption, profile-type etc. don't influence Photoshop-windows in this way - but as soon as you change the gamma those boxes appear.
I would very much like to know how you guys deal with it - do you profile your display to 1.8/2.2 OR do you use L* and live with the boxes OR have you profiled your display properly but you don't have this nuisance? (!?)
Any help/info would be greatly appreciated.b So here's what I think happens (+ my idea to solve the grey-boxes issue):
Some applications use the monitor-profile to draw their interface. Like Photoshop and Graphic Converter. (The only 2 I've installed, I'm sure some video-editing-applications, even players are concerned that's maybe the reason some people think it's 'random'). I think these apps do so to immediately can reflect a change in the profile, without restart.
Now Mac OS X Leopard seems to not allow these applications to do so in certain parts of the interface. (Must be a new feature!) The window itself is drawn by the OS. That's the reason only elements like the text and buttons are affected.
And the problem is that the OS uses its 'Generic RGB Profile.icc' which contains Gamma 1.8. So if you calibrate your display with Gamma L* (which you really should do and most profiling-software does by default) those grey boxes appear in said applications.
The solution is easy. Replace the system-rgb-profile with one that supports L* - like the eciRGB profiles.
To do so you have to rename the .icc file in finder but also edit the information inside (which can be done with the ColorSync Utility). Then copy it to the System/Library/ColorSync/Profiles folder.
After that the grey boxes dissapear and everything is back to normal. There's some difference in the tabular data like the CMM and a chroma-entry, so you might want to re-write your display-profile just to make sure everything's alright.
I haven't seen anything yet but could imagine that the rendering of webpages in safari might be affected. Or rather some webbrowsers' without colour management. (I'm just guessing.)
b Problem 1:
Some Adobe apps can see that the current system-profile is identical to your working-space-rgb and reset your rgb-choice to the Generic RGB profile after a restart. (Without changing the 'Colormanagement SYNC'd icon/setting.) This probably could cause trouble if you export or open files.
b Solution:
Use a different profile for your system than your Adobe-RGB setting. I used the 'L-Star RGB v2' for the system and the 'eciRGB v2' for Adobe. They're technically identical but for some reason Photoshop and esp. Illustrator now respect my choices and don't reset anything. Works fine for me. (!)
b Problem 2:
Besides the aforementioned chroma-entry in the Apple default profile (which loss shouldn't cause any issues) there's also the localisation information. Because the profile is named differently in different languages of OS X. I haven't found anything causing trouble (probably because if the profile isn't found it resets back to the english version by default).
b Solution:
This would be easy if someone knows about a .icc file editor. If we could add those localised names from the Apple profile no application would ever know. I've only found hexadecimal editors but won't put something like that on my machine, especially since everything works fine.
I hope Apple comes up with a real solution soon, this seems like too much of a hack - considered the delicate nature of colour management.
If you read this and know what I'm talking about and disagree or know any reasons why one would not want to do this - please speak up! I'm sure I'm not the only one who would like to know. -
i'm so upset with dvdsp, i feel like every dvd i make ends up skipping in the clients' dvd players. i shot hdv, edited in native hdv 1080i60, used compressor to make a best quality 150 min ac3 and m2v, and used dvdsp to burn and it plays fine in my macbook pro but skips and stops playing in my ps3 AND xbox 360. what is my issue here? bad dvds? all my software is up to date and i'm using a hv30 and lacie 7200 external firewire 400 drive.
Don't jump to conclusion . Meters on players are terribly innacurate. Beside 3.7 is really low - you couldn't be happy with the quality Im sure at that rate! Re-do the encode again but make sure you've set the correct bitrate based on the length of your source. use a good bitrate calculator to get your target anf peak bitrate settings. Try another batch of good media and play the disc again. Try more than one player if need be.
here's a good calculator:
http://www.videohelp.com/calc.htm
Message was edited by: Eric Pautsch1
Message was edited by: Eric Pautsch1
Maybe you are looking for
-
Can't get popup window to work, could use code help.
This is the first time I've tried to open a popup window in flash, and I can't get it to work. The site I'm building has the navigation buttons contained in an animated movie clip. All of the navigation buttons work fine. But there's a link that the
-
Not able to run diagnostics because these keys only work when they want to. Anyone know how to resolve without taking it in for service?
-
How to reconnect to a disconnected remote ssh session on solaris 10
hi all How to reconnect to a disconnected remote ssh session on solaris 10 is there a way to accomplish this
-
Mto strategy 40 - planned order generation problem
i have an fg, which is assigned to strategy 40. sales orders are created for that fg. however, when i run my mrp, tcode MD04 shows that the planned order generated for the FG is make to stock. how do i change this to make to order?
-
There is this tool bar, it says powered by wimba, it just showed up today. I have tried add block plus, I have googled and tried things suggested there, and yet I still have it. Please help me completely remove this annoying tool bar