MXO Calibration tool bug...and a fix

Last June Matrox posted this warning in their forums:
http://forum.matrox.com/mxo/viewtopic.php?t=884
Posted June 16, 2008:
"There is currently a known issue with Quicktime 7.5 and our latest MXO 2.1.3 drivers, in which our Proc Amp utility will not properly load our test bars for calibration purposes. Please note that this does not effect calibration profiles made prior to Quicktime 7.5, we apologize for any inconvenience this has caused and urge you to check back regularly for any updates regarding this matter
Matrox Support"
This only effects the Proc Amp monitor calibration of computer monitors like the Apple or Dell. All the other functions operate normally.
Now...because I don't read those forums, this snuck under my radar. It apparently has been an issue all summer.
I blogged about the issue (www.lfhd.net) and received a bug fix from Matrox today. That can be downloaded here. This fixes the calibration bug with QT 7.5.
Shane

ftp://vidsupp:[email protected]/private/quicktimemxo
http://forum.matrox.com/mxo/viewtopic.php?p=3609#3609
Oh...Looks like Andy got that covered.
Shane

Similar Messages

[svn:fx-trunk] 10131: Fixes to several effects bugs and one styles-related bug.

Revision: 10131
Author:   [email protected]
Date:     2009-09-10 14:25:42 -0700 (Thu, 10 Sep 2009)
Log Message:
Fixes to several effects bugs and one styles-related bug.
QE notes: Fixes to all filed auto-center feature bugs.
Doc notes: None
Bugs: sdk-22994, sdk-22992, sdk-22990, sdk-21850, sdk-22973
Reviewer: Jason (+Glenn for RadioButton/CheckBox changes, 21850)
Tests run: checkintests, Mustella (transform effects, Slider, DataGrid - all passed last week, prior to skin/test changes)
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-22994
    http://bugs.adobe.com/jira/browse/sdk-22992
    http://bugs.adobe.com/jira/browse/sdk-22990
    http://bugs.adobe.com/jira/browse/sdk-21850
    http://bugs.adobe.com/jira/browse/sdk-22973
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/CheckBox.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/RadioButton.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SoundEffectInst ance.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Move.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Move3D.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Rotate.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Rotate3D.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Scale.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Scale3D.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
    flex/sdk/trunk/tools/dependencychecker/frameworkSwcExceptionsList.txt

[svn:fx-trunk] 11601: Integrating Min' s recent fixes to FXGUtils for a group of attribute parsing bugs and clarification of error messages .

Revision: 11601
Author:   [email protected]
Date:     2009-11-09 22:00:50 -0800 (Mon, 09 Nov 2009)
Log Message:
Integrating Min's recent fixes to FXGUtils for a group of attribute parsing bugs and clarification of error messages.
QE notes: Please confirm test cases.
Doc notes: N/A
Bugs:
SDK-22982 - FXG compiler fails on percentage lineheight inside formatted text content
SDK-24093 - If a
tag has children, you do not get a compile error.
SDK-24092 - You get a compile error if you set justificationStyle="prioritizeLeastAdjustment"
SDK-24097 - Setting an invalid verticalAlign style on RichText has a typo in the error message
Reviewer: Min
Tests run: Checkintests, Bug test cases
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22982
    http://bugs.adobe.com/jira/browse/SDK-24093
    http://bugs.adobe.com/jira/browse/SDK-24092
    http://bugs.adobe.com/jira/browse/SDK-24097
Modified Paths:
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/fxg/FXGException_en.properties
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/RichTextNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich BlockTextNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich TextLeafNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/AbstractRich TextNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/BRNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/ImgNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/TabNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/richtext/TextHelper.j ava
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/dom/text/AbstractCharacte rTextNode.java
    flex/sdk/trunk/modules/fxgutils/src/java/com/adobe/internal/fxg/sax/FXGSAXScanner.java

Dear Pallavi,
Very useful post!
I am looking for similar accelerators for
Software Inventory Accelerator
Hardware Inventory Accelerator
Interfaces Inventory
Customization Assessment Accelerator
Sizing Tool
Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
Request help on such accelerators... Any clues?
Any reply, help is highly appreciated.
Regards
Manish Madhav

Subscriptions for fimware/software new releases, bugs and fixes

Hi,
Where can I subscibe for MDS 9000 Firmware/Software releases, bugs and fixes?
Thanks,

You have the "Cisco Notification Service" tool where you can setup a profile:
http://www.cisco.com/en/US/customer/support/tsd_most_requested_tools.html
- Filiph

When I enable imatch on my iPhone 4s it takes approximately 30 minutes before other data fills 13.2gb of usable data. This problem does not occur when I manually sync music to my phone. Is this a common bug, and if so; is there a fix?

When I enable imatch on my iPhone 4s it takes approximately 30 minutes before other data fills 13.2gb of usable data on the phone. This problem does not occur when I manually sync music to my phone only when I access imatch. Is this a common bug, and if so; is there a fix?

yes it is. you can sign out of itunes account then sign back in. use http://support.apple.com/kb/ht1311 to sign out.

HT1880 Is there a calibration tool foor iPhoto and the printing of books (dark results)

Hi, Not satisfied with the result of a very expensive and therefore unusable iPhoto Book, due to the dark prints of the images, I am looking for a calibration tool. Does anyone know of its existence? Or is it just aquestion of lowering the color density of your photo's before, with iPhoto? And, if yes, at what rate do they have to adjusted?
Thank you for an answer, sicerely, Jos

Don't know if you can set the camera to use a different RGB profile for future photos.
To convert existing files to sRGB you can download and use this Automator workflow application, Convert to JPG anbd Embed sRGB profile, on the original files. However, you would have to export the orignals out of iPhoto, run the app on them and reimport them. You can download the app from Toad's Cellar.
For future photos you can upload them to a folder on the Desktop and run the app on them there before importing.
Contact Apple, tell them about the problem and they probably will refund the purchase price. If you reorder then you're on your own from then on. Be sure to create a PDF of the book as described in this Apple document, iPhoto '11: Preview a book, card, or calendar before you order or print it, before you order it and save the pdf for comparison to the printed version after you receive it.

[svn:fx-trunk] 11810: Fixing up some logic around pauseWhenHidden ( there were some bugs) and also changing some logic around enabling/ disabling.

Revision: 11810
Revision: 11810
Author:   [email protected]
Date:     2009-11-13 17:07:56 -0800 (Fri, 13 Nov 2009)
Log Message:
Fixing up some logic around pauseWhenHidden (there were some bugs) and also changing some logic around enabling/disabling. Also fixing a small documentation bug on VideoPlayer2.scaleMode.
When a video component (or one of its ancestors) becomes disabled, the video pauses. When it becomes re-enabled, we do not play the video. This behavior is baked in to VideoDisplay and does not depend on the pauseWhenHidden flag.
QE notes: -
Doc notes: -
Bugs: SDK-24182, SDK-24181, SDK-24193
Reviewer: Kevin
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24182
    http://bugs.adobe.com/jira/browse/SDK-24181
    http://bugs.adobe.com/jira/browse/SDK-24193
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoDisplay.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer2.as

Thanks Erik,
If nothing else, this huge list of updates and fixes, shows clearly that the Logic Dev team is working hard on fixing and improving LPX to a major degree.... and from the list of fixes done.. show they do read the bug reports submitted!
As an aside....
I recall how all the 'naysayers' prior to LPX (and in some cases, since...) were proclaiming how Logic was dead, the team was being disbanded, we won't see any further development, the Dev team doesn't listen or care... and so on....... I wonder where those people are now?

So a number of my apps (ie., United, ES File Explorer, etc..), which worked a few days ago, are now crashing on start-up or shortly thereafter. Have you recorded this bug and is a fix forthcoming? Anxiously awaiting an update.

So a number of my apps (ie., United, ES File Explorer, etc..), which worked a few days ago, are now crashing on start-up or shortly thereafter. Have you recorded this bug and is a fix forthcoming? Anxiously awaiting an update.

There are a number of threads about this issue on the forum if you want to do a search. Basically, you need to uninstall the latest update to Android System Webview:
http://www.droid-life.com/2015/04/27/apps-crashing-android-system-webview/#more-166266

ACR 7.x known bugs and fixes

Since Adobe stopped supplying Camera Raw downloads, I've noticed that it's become harder to track bugs and fixes. Hopefully, someone here can put me straight on the current state of play.
Can anyone summarise the well-known problems with version 7, and when they were fixed (or are still ongoing)? Is there a 'changelog' somewhere? What is/are the main outstanding issues at the moment?
Unfortunately, I'm getting to that age where my short–medium term memory isn't very good at retaining this sort of information, so it's good to have it written down!

Jeff,
I have been dealing with this since November. Steve G knows about it but hasn't had time to do anything. Here's the deal...I am on Windows 7 and Photoshop CS6. I shoot with a Canon 7D and G11. I do all my initial work in the metadata template...my own info, description, keywords, location, etc. etc. This creates an .xmp file. When the update from RAW 7.2 to 7.3 came through in November, I downloaded it, as I have all other updates. Then, suddenly, all images in folders with RAW files that had ANY metadata applied, would regenerate endlessly. This only happens with RAW files, not with folders containing jpegs or tifs.
I tried resetting preferences. I tried creating new folders. I have asked if this problem is seen with Nikon RAW files and I'm not sure there has been an answer. I think people have recreated this even with DNG files tho I am not sure. I do know that someone in Adobe has recreated it.
I then discovered that previous .8bi folders were no longer readily available. Getting to one is way, way, way above my ability and involved all kinds of ridiculous backflips but I finally got one. Then followed a solid week of me trying replace the 7.3 .8bi file with the 7.2. Of course, with no instructions, I was putting the wrong file in the wrong folder (32 bit and 64 bit). When I finally got THAT straightened out, it still didn't work. It took someone at Adobe taking over my computer to successfully revert to 7.2.
I lost hours and days of work time trying to deal with this. Meanwhile, should I buy a new camera, I won't be able to see my own RAW CR2 files and will, instead, have to convert to DNG, which, frankly, I find to be a royal pain. Am I peeved. You bet I am. I've been asking, pleading, begging for something to be done since November. Some thoughtful soul suggested I try updating to 7.4 to see if it fixed the problem (the 'fixed problems' listed for 7.4 does NOT mention the recalibration). You can understand, after the problems I had in November, why I will NOT do this until I am absolutely sure the current, latest update has fixed my problem. And I will NOT spend another two hours on the phone with adobe alleged tech help to finally get someone in India who doesn't know what I am talking about. This forum has been far more helpful but please underestand, I am an old school film photographer who has had my share of problems understanding this digital stuff and mucking around with the basic technology of my computer only leads to horrifying outcomes for me.
Jeff, are you with Adobe? Can you look into this?

[svn:fx-trunk] 5114: Fix FxRadioButton doc bug and fix the bug fix I messed up yesterday.

Revision: 5114
Author: [email protected]
Date: 2009-02-27 12:50:47 -0800 (Fri, 27 Feb 2009)
Log Message:
Fix FxRadioButton doc bug and fix the bug fix I messed up yesterday.
QE Notes: mustella gumbo/RadioButtons passed
Doc Notes:
Bugs: SDK-19475, SDK-19531
Reviewers:
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19475
http://bugs.adobe.com/jira/browse/SDK-19531
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxRadioButton.as

Recently updated iOS 7.1 additional fix bug and my phone keeps restarting

Recently updated iOS 7.1 additional fix bug and my phone keeps restarting

Yeah that is what I thought, but the passcode used to be alpha numeric and just changed to being 4 didgets and I don;t recall making that change. This is only to approve updates on my iPhone. The other issue is on my mac pro.

Master Pages and Buttons - Bug and Fix Request

I think I'm the only person in the world who has encountered this bug, and I've filled out the bug report form on the Adobe site twice in a couple of years.
Just wondering if anyone else has encountered it, and I'm curious to know if it still exists in Creative Cloud (I'm still using CS6). However, I think this bug appeared in CS5.5, prior to that, results were as one would expect.
So here's the gist of it . . .
Prior versions of InDesign allowed you to put a button on a Master Page, then upon export to PDF the page number would be appended to the button name. CS6 appends random numbers to the button names on export. (It seems the number appended to the button names is the instance count of the button in question.) This problem becomes incrementally worse if you use different combinations of master pages, some with buttons and some without.
Steps to reproduce bug:
Create a button, named "menubutton" and add it to a master page
Apply that master page to 10 pages.
Export the ID file to PDF enabling buttons and interactive elements.
Check the button names in the PDF from Acrobat
Results:
In CS6, this now appends the page number, and an arbitrary number to the button name. CS6 results are like such: "menubutton.Page 1", "menubutton.Page 21", "menubutton.Page 32", "menubutton.Page 43", etc.
Expected results:
The button names should become "menubutton.Page 1", "menubutton.Page 2", "menubutton.Page 2" , etc. (As in prior ID versions)
The problem becomes a lot worse when you use combinations of master pages . . . for example:
Master A – contains one button – menubutton
Master B – contains one button – otherbutton
Apply those masters to alternating pages, like below and export to PDF, this will be the crazy result:
Page 1 (A)        “menubutton.Page 1”
Page 2 (B)        “otherbutton.Page 2”
Page 3 (A)        “menubutton.Page 31”
Page 4 (B)        “otherbutton.Page 41”
Page 5 (A)        “menubutton.Page 52”
Page 6 (B)        “otherbutton.Page 62”
Page 7 (A)        “menubutton.Page 73”
Page 8 (B)        “otherbutton.Page 83”
So, can anyone else attest to this? It makes scripting buttons incredibly hard!

Hi johnjohn123,
1. I would definitely make a copy of the EnterpriseWiki.aspx page layout and make changes to that. You can then set your pages to use your custom page layout. Typically, I provision these via Visual Studio and a module for uploading them to the SharePoint
master page gallery.
2. For the master page, the html version is new to 2013 and is meant to simplify branding, however, it's not required. You can still work within master pages and provision those via features if you'd like. The key is to create your own master page and never
modify the default.
If you need code samples for any of the above, let me know and I can supply it.
Shereen Qumsieh http://sharepointdeveloperhq.com @msshushu

Pen tool bug

I'm sure this has been discussed, but I don't find the thread. Here is my issue:
When closing an open path by clicking the end point, AI does not recognize "Option" or "Spacebar" modifier keys as it should. The option key should allow me to control the direction point independant from the corresponding anchor point, while the spacebar should allow me to move the active anchor point, while the mouse is still down. This is exactly how Photoshop CS6 works (this was an upgrade for Photoshop).
Here is a short video illustrating the "bug" in Illustrator:
http://www.youtube.com/watch?feature=player_detailpage&v=g5ViHSLJ_SM
Please let me know if you share my concern about this pen tool bug.

Thanks, Monika. I'd like to see this fixed. We need parity with pen tool between PS and AI.
Funny, I saw my error on "parody" just now.
While I'm on "parity"; I'd like to see the zoom feature act the same in AI and PS. Now that I'm finally used to "click-drag" zooming in PS, I'm driving myself crazy in AI, trying to do the same thing.
Message was edited by: rcraighead

I lost my bottom tool bar and the apps I was running down there. I need to have it back but your update removed something that I use.

I have run a Hebrew calendar that sits in the bottom tool bar. I have used this calendar and rely on it, but your Firefox 5 update has removed the bottom tool bar and I want my Hebrew calendar restored. What good is updating a piece of software that works by creating something that does not work? I will stop using and stop recommending my end users to switch to Firefox if you keep removing parts that are needed.
I am help desk support for a large federal government agency and until you broke Firefox with this latest update, I would suggest that my users switch to Firefox, but unless this bug is fixed I will stop doing that.

Does the Add-on Bar have a check-mark?
*Firefox menu button > Options
*View > Toolbars (press F10 to display the hidden Menu bar)
You can check for problems caused by a corrupted localstore.rdf file.
*http://kb.mozillazine.org/Corrupt_localstore.rdf

Mooing and heat fixes: what does each method do?

My black MacBook used to have both the whine & mooing + it was hot. (I started with a black MacBook with idle CoreDuoTemp of 66~69C.)
So I searched and searched and tried a LOT of things posted on this forum.
Now I actually understand WHAT these tricks do, so I thought I'd share my experiences AND ASK, "DOES ANYONE KNOW OF ANY BETTER/OTHER METHODS?"
1. Unplug the battery trick
Others have found that unplugging the battery causes the CPU to operate at 1Ghz, lowering the temp. However, the CPU will be stuck at 1Ghz even when you load it.
I finally found out what this does by using Apple's free developer tool Reggie SE. (Don't fool around with Reggie SE since it can kill your computer) For some reason I cannot understand, unplugging the battery trips the "Thermal trip indicator."
The exact words from Reggie SE when the battery is unpluged:
"Thermal trip indicator event is active. This indicates that the processor is above the recommended operating temperature. This bit is read-only and cleared once the temperature drops below recommended operating temperature".
Effectively, the CPU thinks that the temperature is unstable and automatically fixes your freq to 1Ghz.
So this fix is definitely a result of a bug from Apple. My best guess is that they didn't write the parameters inside the ACPI drivers to handle such an event since they don't expect users to run their MacBook minus the battery.
2. Delete the IOPlatformPluginFamily.kext trick
According to apple documentation, "The MacBook uses an advanced system management controller (SMC) to manage thermal and power conditions, while keeping the acoustic noise to a minimum. The SMC is fully independent of the operating system."
http://developer.apple.com/documentation/HardwareDrivers/Conceptual/MacBook0605/Articles/MacM42DeveloperNote.html#//appleref/doc/uid/TP40004263
So why does trashing a file (last time I checked, file-on-harddrive=software) change things? Because the CPU throttling is controlled by OSX.
Inside IOPlatformPluginFamily.kext, there is a section describing CPU throttling. It's a bunch of characters that I can't decipher, but what IS interesting is that it is the exact same setting for the Macbook, Macbook Pro, and the updated Macbook Pro.
When this file is trashed, some users (including myself) will notice that the "mooing" disappears. What actually happens is the CPU throttling is disabled, causing the CPU frequency to be fixed at 1.667Ghz. Normally, the CPU will throttle between 1.5Ghz and 2Ghz. The operating temperature INCREASES and the mooing disappears since mooing only occurs over a very narrow temperature range. This also gets rid of the CPU "whine," for reasons related to CPU throttling that I don't understand.
With this "fix," my CoreDuoTemp went from 66~69C to 71~73C. If you have a 1.83Ghz macbook, the numbers are probably different.
Anyway, we can probably agree that we'd rather get rid of the mooing by LOWERING the temperature rather than INCREASING it.
3. Removing the plastic piece covering the vent-fix
If there is a plastic cover on your vent, the solution is simple! But I think this is a minority event.
4. Reapplying thermal paste
I have not personally tried this method, although I agree that it should work. But it'll only work if Apple screwed up when they manufactured the MacBook, i.e. used inferior paste.
5. Re-seating the heat sink
This works the same way as #4 - by properly distributing the thermal paste and making a good thermal contact at the CPU/Heat sink interface.
http://discussions.apple.com/profile.jspa?userID=396441
Joe said that his seat sink was a bit "loose," and that he tightened the screws. Well I checked mine and the screws were fine.
So here's what I did:
1. Very slightly loosen the 4 screws holding the heatpipe in place (1 rotation)
2. VERY gently push down on the heat sink and wiggle it around in an effort to evenly spread out the thermal paste
3. tighten the screws.
That lowered my idle temp from 66~69C to 59~63C. Since my particular MacBook mooed at 66-69C, the mooing is now GONE! And now I have a cooler laptop!
6. Use less mem-persistance programs.
I noticed that running apps like little snitch and sizzling keys (or any kind of app that runs in the background) increases the temperature by a degree or two. This really isn't a fix though, since that's like saying "don't use your computer if you want to keep it cool."
7. Disable a core (use as single processor)
Well this isn't a very attractive options since I paid all that money to get a dual-core laptop!
What's worse, disabling a core doesn't decrease my temperature at all, even though I thought it should work. If anyone has evidence contrary it'll be interesting.
Well, does anyone have other ways to lower their MacBook temperature and/or get rid of mooing?

http://cnscenter.future.co.kr/resource/rsc-center/presentation/intel/spring2001/ epis102.pdf
This is the pdf from Intel Developers Forum, that descript what effects on the processor temperature. As you can see from the pp. 17-19, the surface flatness is the significant factor, so the other way of decreasing the temperature is to check if the cooler basement is flat and, if it's not, to polish it.

MXO Calibration tool bug...and a fix

Similar Messages

Maybe you are looking for