Softproofing Anomaly??

Hi:
I have been experimenting with softproofing and I noticed what at least superficially seems like an anomaly.  When I duplicate an image and set the copy to generate a softproof by selecting a Custom Device to Simulate, even if i pick an off-the-wall device so that the color are totally skewed visually in the copy, if I use the Eyedropper to check the RGB values, they are the same for both images.  To be specific I had an image of a blue ceramic sculpture and the softproof copy had become purple but again the RGB values registered the same.  Can anyone explain this??
Herman R.

Hi:
I guess I'm being obtuse but if you have an original image that is blue and
the soft proof is purple, why shouldn't they change?  I thought the whole
point of soft proofing is to get the soft proof to look as similar as the
original as possible.   With the RGB values not changing you're stuck with
making adjustments the best you can visually.  Wouldn't it be better to be
able to make specific adjustments with RGB values??
Herman R.

Similar Messages

  • I am trying to softproof an image using a CMYK .icc file. I sent an image from LR 5 to PS CC 2014, opened the Camera Raw FIlter, but the hyperlink to access workflow is not showing up in the CR dialogue box... Any ideas why this might be?

    I am trying to softproof an image using a CMYK .icc file. I sent an image from LR 5 to PS CC 2014, opened the Camera Raw FIlter, but the hyperlink to access workflow is not showing up in the CR dialogue box... Any ideas why this might be?

    I am trying to softproof an image using a CMYK .icc file. I sent an image from LR 5 to PS CC 2014, opened the Camera Raw FIlter, but the hyperlink to access workflow is not showing up in the CR dialogue box... Any ideas why this might be?

  • Serious issue w/LR5.3: Softproof is invisible!

    Hello all,
    I've just noticed that I have a really strange problem with soft proofing in Lightroom 5.3. I can activate it and select all the ICC profiles that are installed on my system, choose between relative/perceptive/show paper color, and the histogram changes accordingly, just like it is supposed to do. Unfortunately, the image preview does not! The displayed colors remain the same!
    I have checked this with several files and made screenshots to compare them for differences - there really are none.
    Next thing I tried was this: Buy a brand new SSD, install Windows 7 SP1 64bit, install all Updates, install the latest AMD Catalyst pack, install Lightroom 5.3, then try again. The result is basically the same, with one small difference: When I activate the softproof now, I have a small chance to see the "corrected" preview, however it'll be gone as soon as I zoom in, for example. Switching between relative/perceptive/show paper color yields wildly different results each time, ranging from no change over a slight change to a visible change in a totally non-predictable manner. This works best with zoom to fit; at 100% zoom there's mostly no visible change, and it's gone again as soon as I zoom in or out.
    I'm running an Intel Core2 Duo E7300 on a Gigabyte GA-EP45UD3 with 4GB of RAM, Windows 7 Pro x64 SP1 + current updates, Crucial M500 SSD, SAPPHIRE HD 7750 ULTIMATE with the latest Catalyst installed.
    System Information is this:
    Version von Lightroom: 5.3 [938183]
    Betriebssystem: Windows 7 Business Edition
    Version: 6.1 [7601]
    Anwendungsarchitektur: x64
    Systemarchitektur: x64
    Anzahl logischer Prozessoren: 2
    Prozessorgeschwindigkeit: 2,6 GHz
    Integrierter Speicher: 4094,4 MB
    Für Lightroom verfügbarer phys. Speicher: 4094,4 MB
    Von Lightroom verwendeter phys. Speicher: 285,9 MB (6,9%)
    Von Lightroom verwendeter virtueller Speicher: 249,5 MB
    Cache-Speichergröße: 39,6 MB
    Maximale Anzahl Threads, die Camera Raw verwendet: 2
    DPI-Einstellung des Systems: 96 DPI
    Desktop-Komposition aktiviert: Nein
    Monitore/Anzeigegeräte: 1) 1280x1024
    Anwendungsordner: C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.3
    Bibliothekspfad: C:\Users\root\Pictures\Lightroom\Lightroom 5 Catalog.lrcat
    Einstellungen-Ordner: C:\Users\root\AppData\Roaming\Adobe\Lightroom
    Installierte Zusatzmodule:
    1) Behance
    2) Canon Tether-Zusatzmodul
    3) Facebook
    4) Flickr
    5) Leica Tether-Zusatzmodul
    6) Nikon Tether-Zusatzmodul
    Config.lua-Flags: None
    Adapter Nr. 1: Anbieter : 1002
        Gerät : 683f
        Subsystem : e213174b
        Version : 0
        Grafikspeicher : 1010
    AudioDeviceIOBlockSize: 1024
    AudioDeviceName: Lautsprecher (Juli@ Audio)
    AudioDeviceNumberOfChannels: 2
    AudioDeviceSampleRate: 44100
    Build: Uninitialized
    CardID: 26687
    Direct2DEnabled: false
    GPUDevice: D3D
    MaxTexture2DSize: 8192
    OGLEnabled: true
    Renderer: AMD Radeon HD 7700 Series
    ShaderModel: 11.1
    Vendor: AMD
    VendorID: 4098
    Version: 1002:683f:e213174b:0000
    The newly set up system is totally clean, I didn't transfer one single file from my old system yet, so there's no old catalog here now. I simply got myself an ICC profile from Saal Digital and a monochrome JPG from the internet for testing purposes, but to no avail, like I said above.
    I have also tested several ICC profiles which work OK in other programs, so I won't blame them. Like I said, the histogram changes accordingly, i.e. it shows a noticeable color cast for monochrome images with a print profile, but only in the histogram and not the image itself.
    My monitor is not calibrated and using the Win7 system standard color management. I did try some monitor profiles from the internet that changed the color rendition of the monitor but didn't make any difference in Lightroom.
    Any ideas what might be the culprit here? Or what else I should try - maybe a new graphics card?
    Regards,
    Lasse

    First, ignore the histogram of the scan and all that. Too many variables in the process (scanning) to make a conclusion.
    You're probably right about too many variables, but the scan resembles what I actually see on the paper quite nicely. The print definitely has a color cast, which is easily recognised when I put it next to a print done with my monochrome laser, which obviously isn't able to produce a color cast.
    4. How you view the image is critical, especially if the papers are high in OBAs. The Lightsource can produce what appears as a color cast. At the very least, examine the print under different illuminants. Do they look the same or do you see a color shift?
    There's no metamerism here. It's simply a color cast due to the printer using colored inks instead of true black inks. I'm perfectly fine with that, however I'd like to move the color cast more into a sepia-like, "warm" direction, away from that violet-ish it is now. So my way of thinking is, If I see something violet-ish in the soft proof, I can tone the image in a way that is more appealing to me. Again: Is this a valid way of thinking? If it is, why doesn't it work the way I expect it to? If it is not, is there another way to achieve it?
    1. Actual device has changed behavior and the profile isn't reflecting that correctly.
    2. Actual ICC profile isn't all that good. Note too that these profiles have two tables. One affects the output, the other the soft proof. In a prefect world, they are in sync. But that isn't always the case.
    3. The driver wasn't setup on the Epson for the best neutral process (Advanced B&W) and with that process, ICC profiles are out of the loop anyway. That's a proprietary process and is really the best way to produce (if so set) pretty dead nuts neutral output from this printer.
    To me this would seem plausible if the soft proof and the final print would be "a little off". Now the soft proof is totally off from the print, since it's basically like the original without any proof.
    And then there's the histogram.
    Please do the following test:
    Fill an image with RGB 128,128,128. Look at it in Lightroom with activated soft proof, Relative, simulate paper & ink disabled, using the pearl profile. Note how the histogram changes. Now hover the mouse over the image and note the values below the histogram: In my case they read RGB 135,132,142, while the image itself still shows 128,128,128. You can check that with a screenshot. Now fill the image with the shown 135,132,142 and note the color cast. I didn't test it yet, but I'd bet that Saal's printer would not be able to print a neutral middle grey but something like what you see on screen with the 135,132,142 instead!
    Please don't get me wrong, I'm not trying to act stupid; I simply don't get it and am desperately trying to understand what's wrong here. Why does Lightroom "measure" 135,132,142 but continue to display 128,128,128?

  • CS4 project to CS5 anomaly

    Previous project was 1080 from a digital camera.
    When I imported a previous CS4 PAL DV project into CS5, all the sequences were set to 1080 not DV.
    I added a DV sequence, gave up and tried again.  This time the sequences were DV as they should have been originally.
    This suggests that there might be an anomaly sometimes when importing projects from CS4 to CS5 when they are of different types from the immediately previous work in CS5.
    Working OK now, but posted so there is a record in case others have the same problem.

    If I can repeat it, or others report the same issue, I'll certainly put in a bug report.  But as of now it could easily be a one-off from a particular project.

  • Display anomaly when waking from sleep

    Ever since the SL Upgrade when my MacBook Pro wakes from sleep the very bottom right one third section of my screen does not look as it should, this thin strip of incorrect graphics ( usually mostly white ) only appears for about one second then the desktop goes back to normal down there . . . so far this is not a problem at all, just an anomaly . . . I bought my MBP early summer 2008 and never had a single problem before and after SL, just this oddity now . . . I have a ViewSonic VP2250WB LCD display mirrored via DVI . . . so I am curious if anyone else has this happening and possible reasons for it . . .

    Matteo : I guess it is a good sign that only 2 of us have reported this minor glitch here . . . I may experiment with switching to a different desktop pattern and / or screen saver to see if it persists . . . also, since installing SL I have only done Sleep and of course restarts after getting the 10.6.1 update and a few others so I need to do an actual Shut Down and later start up fresh and see what happens.

  • 24" iMac 2.8 GHz Intel Core 2 Duo OSX v10.5.5 shutdown anomaly

    24” iMac 2.8 GHz Intel Core 2 Duo OSX v10.5.5 shutdown anomaly.
    I have noticed that when my iMac shuts down, that initially the One Touch Maxtor 500G external drive attached to the Firewire 400 port also does a normal shut down and the light goes out. Within a few minutes I noticed that the light on the Maxtor is back on. This does not happen if I use the USB 2.0 port to attach the hard drive and iMac, the light remains off. It appears the FW400 port is active on the iMac even when in the shutdown mode. Is this normal for the iMac?
    I have a 13”MacBook 2.4Ghz that does not activate the same Maxtor when it is shut down. I attach it via the MacBook FW400 port.
    I hooked up an ammeter to the iMac power cord and observed the following readings:
    iMac Off: From 50ma to 180ma cycling at a rate of 23 cycles/minute. Using the Watt reading of the instrument, that amounted to cycling from 0 to 5 Watts every 4 seconds.
    iMac On: 1.16A 133Watts.
    This iMac is new, 1 week old, does it need repair or is this normal? I like to get a FW800 external HD, but I don’t want to have to pull the plug on the HD every time I want to shut down.

    Since my Maxtor doesn’t have an on/off switch, the best solution I have found so far is to use my APC 750 UPS to turn off the Maxtor. This APC has a master plug outlet that senses when the computer is turned on and activates 3 other outlets to on when the computer reaches a certain power threshold. Fortunately the threshold is user adjustable and I was able to set it high enough to turn off the Maxtor outlet when the iMac is off.
    Is anyone else able to confirm that their iMac cycles like mine does, or is this peculiar to my iMac? It is new and if it needs service I would prefer to do it while it is covered under warranty.

  • MFP Anomaly Detected Access Points are moving from one wlc to another and vice versa

    Hi together,
    a customer has lost some Access Points to another WLC with 7.2  and then they come back after 15 minutes to the origin WLC with 7.5
    Attached the messages
    MFP Protection is configured as optional
    152
    Wed Nov 27 05:33:26 2013
    MFP Anomaly Detected - 1 Not encrypted event(s) found as   violated by the radio 58:bf:ea:0f:67:4a and detected by the dot11 interface   at slot 1 of AP 58:bf:ea:0f:67:40 in 300 seconds when observing . Client's   last source mac 70:11:24:e4:43:0f
    153
    Wed Nov 27 05:31:40 2013
    AP Disassociated. Base Radio MAC:88:43:e1:56:91:d0
    154
    Wed Nov 27 05:31:40 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:88:43:e1:56:91:d0 Cause=New Discovery Status:NA
    155
    Wed Nov 27 05:31:33 2013
    AP Disassociated. Base Radio MAC:58:bf:ea:0f:73:d0
    156
    Wed Nov 27 05:31:33 2013
    AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:58:bf:ea:0f:73:d0 Cause=New Discovery Status:NA
    157
    Wed Nov 27 05:31:33 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:58:bf:ea:0f:73:d0 Cause=New Discovery Status:NA
    158
    Wed Nov 27 05:31:28 2013
    AP Disassociated. Base Radio MAC:58:bf:ea:0f:fc:20
    159
    Wed Nov 27 05:31:28 2013
    AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:58:bf:ea:0f:fc:20 Cause=New Discovery Status:NA
    160
    Wed Nov 27 05:31:28 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:58:bf:ea:0f:fc:20 Cause=New Discovery Status:NA
    161
    Wed Nov 27 05:31:17 2013
    AP Disassociated. Base Radio MAC:b4:e9:b0:e4:02:20
    162
    Wed Nov 27 05:31:17 2013
    AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:b4:e9:b0:e4:02:20 Cause=New Discovery Status:NA
    163
    Wed Nov 27 05:31:17 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:b4:e9:b0:e4:02:20 Cause=New Discovery Status:NA
    164
    Wed Nov 27 05:31:15 2013
    AP Disassociated. Base Radio MAC:a4:18:75:eb:da:b0
    165
    Wed Nov 27 05:31:15 2013
    AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:a4:18:75:eb:da:b0 Cause=New Discovery Status:NA
    166
    Wed Nov 27 05:31:15 2013
    AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:a4:18:75:eb:da:b0 Cause=New Discovery Status:NA
    167
    Wed Nov 27 05:28:26 2013
    MFP Anomaly Detected - 35 Not encrypted event(s) found as   violated by the radio d8:24:bd:2f:df:6f and detected by the dot11 interface   at slot 1 of AP d8:24:bd:2f:df:60 in 300 seconds when observing Deauth.   Client's last source mac 00:23:14:a7:e3:54
    168
    Wed Nov 27 05:23:26 2013
    MFP Anomaly Detected - 23 Not encrypted event(s) found as   violated by the radio f8:4f:57:a5:40:b2 and detected by the dot11 interface   at slot 0 of AP f8:4f:57:a5:40:b0 in 300 seconds when observing . Client's   last source mac 44:4c:0c:ba:27:77
    Don´t know at the moment how to handle it.
    Regards
    Alex

    Hi lAlex,
    Disable Client MFP under WLAN advanced tab & see if  this still occur
    Regards
    Rasika
    **** Pls rate all useful responses *****

  • Softproof in Lightroom different from Photoshop

    Hi all, I've just recieved a print from Photobox. It looks ace, except for a big band in the sky graduation. Stupidly I hadn't looked on the web site to see if they had a colour profile before sending . As it happens they do, and softproofing the image in Photoshop CS5.1 I can see the same band. However I work in Lightroom (4), so wanted to make any changes there, but when I turn on soft proofing with the same colour profile I get a completely different result, and one that doesn't match the print. Am I doing something wrong? Any help would be much appreciated.
    Jez
    Here's a comparison:
    Lightroom:
    Photoshop:

    Leaving soft proof out of it for now, do you see any differences between Lr and Ps with the same image? They should be absolutely identical, since they're both fully color managed and convert from source profile to monitor profile.
    So next question then becomes if your monitor is calibrated and how? Recalibrating is always the first step in troubleshooting.
    Differences can happen if there's a problem with either profile (source or monitor). This is because the source is different. In Lightroom it's linear gamma ProPhoto, in Photoshop it's the document profile whatever it is (sRGB, Adobe RGB, ProPhoto). So the conversion itself, or transform as some like to call it, is different.
    By extension I suppose it could also happen if there's a problem with the proof profile. Try a different one.
    BTW sky blue is a very sensitive color to profile issues, and problems are easily seen there. It's usually very near the gamut boundary in both sRGB, Adobe RGB and monitor profiles, with the red channel very near zero. So the exact position of the red primary (which varies a lot between most monitors on one hand and sRGB or Adobe RGB on the other) makes an obvious difference.

  • Will I always get color discrepancies when lab printing images softproofed on a 75% on AdobeRGB monitor?

    Hi,
    I am struggling to get  printed output from a professional printing service to match what I see when I softproof on my monitor. The printed image always looks considerably more green and warm, although whites are ok. Blue skies tend to get warm greenish. The printed image often looks like a warm instagram filter had been applied.
    I have two (different generation) Dell U2412M monitors (Dell U2412M = Standard gamut = 71% NTSC, 74.3% Adobe RGB, 95.8% sRGB).
    These are the steps I have taken to try to achieve color consistency between monitor and print:
    I have calibrated and profiled with a Spyder 3 Express using BasICColor Display 5 software, previously also used the Datacolor software that came with the calibrator. After this, what I see on my monitor "looks normal" (skin tones, landscapes etc.)
    I shoot RAW with a Sony NEX6, develop in Lightroom 4 using ProPhoto 16 bit color space.
    I softproof in Lightroom using an ICC file provided by the printing service.
    I use Lightroom to print to file tagging it with AdobeRGB profile. Either as TIFF or as JPG 100%.
    I print with the direction to the printer to "not make any auto corrections to my file".
    I have Windows 7 64bit.
    I thought this would mean that I would get - probably not perfect - but at least a very strong match between softproof and printed image.  But I do not.
    Are these rather strong color discrepancies to be expected given my hardware?
    Is my Spyder broken (it's out of warranty)?
    Or is my workflow erroneous?

    Guermantes wrote:
    I am struggling to get  printed output from a professional printing service to match what I see when I softproof on my monitor. The printed image always looks considerably more green and warm, although whites are ok. Blue skies tend to get warm greenish. The printed image often looks like a warm instagram filter had been applied.
    I have calibrated and profiled with a Spyder 3 Express using BasICColor Display 5 software, previously also used the Datacolor software that came with the calibrator. After this, what I see on my monitor "looks normal" (skin tones, landscapes etc.)
    Could be the calibration targets (how you asked to celibate white point etc). Could be the output. Could be the ICC Profile. Could be your file. You have to decide which is which.
    Start here: Why Are My Prints Too Dark
    Then download a good color reference file like this one: http://www.digitaldog.net/files/2014PrinterTestFileFlat.tif.zip
    Soft proof and see if any green or odd color cast appear. If so, probably the  profile but use it and have a print made. The output should look good (neutral in neutrals, reds that don't appear yellowish etc).
    Generally speaking, if you send Adobe RGB (1998) and the other side assumes it is sRGB, you will end up with desaturated colors. This isn't the fault of Adobe RGB but rather assuming that data is sRGB which it isn't.

  • Interesting performance anomaly during video encode

    I just noticed an interesting anomaly while my iDVD6 project was encoding video. I found that if I cover up the 'Creating Your DVD' progress bar and preview window with a Finder window, that video encoding seems to move a whole lot faster. I could tell by listening to the disk activity which seemed to be occurring about twice as fast. When I moved the Finder window away and exposed progress bar/preview window, then disk activity slowed down.
    I opened Activity Monitor and looked at CPU% which showed about 70-80% with progress bar/preview window exposed. After covering up, the CPU% increased from 125-150% So apparently exposing progress bar/preview window slows things down quite a bit during video encode. I tried same trick during audio encode, and it made no difference. CPU% was about 7-8% during audio encode.
    I was wondering if anyone in this discussion group noticed this performance anomaly previously.
    Paul

    Hi Paul
    Yes I noted some relatively related phenomena during the rendering process
    in FinalCutExpress that just selecting Finder seemed to speed things up.
    Second: Please don't rely on the Activity monitor and most so when it says
    iDVD doesn't answer. It's just rubisch. iDVD keeps on working - just wait and see.
    Yours Bengt W

  • Strange behaviour softproof and Gamut warning

    When I have a softproof selected (using Relative Colormetric ; Blackpoint Compensation and Simulated paper color)  I am seeing a difference in the soft proof when I toggle the gamut warning on and off.
    This is not due to out of gamut colors which I have set to show up as a 100% medium gray.
    What I am seeing is a difference in the shadow detail on the softproof, when I have the gamut warning on or off. More detail with it off and less with it on.  I have tried different printer profiles and see the same effect.
    I had not noticed this before, but today I was printing some sunset pictures and having trouble getting the shadow detail to match on screen and in print. My expectation of toggling the gamut warning is that it would only highlight (in gray) the out of gamut colors and have no impact on other parts of the picture. Incidentaly - the view with gamut warning "on" appears to match the print correctly.
    I am using CS5 on Windows 32bit. Am I doing something wrong, or have I misunderstood the gamut warning?
    Dave

    Noel,
    Thank you - you are spot on - that did get round the issue.
    I read through your thread and can see how the banding issue you described would impact. The dark areas in my pictures tended to be shades of gray and when softproofing using simulate Paper Color went a slightly lighter shade (with banding in those areas). I tried this on a gray ramp and the problem is very visible (as it was in your thread).
    It is puzzling as to why turning gamut warning on and off altered the banding but hopefully if Chris or his colleagues see this thread it may help them locate the root cause of the problem.
    Thanks again
    Dave

  • AP PHY Data Rate Anomaly

    I did a scan using the airmagnet WiFi anaylizer and it informed me that the one of the alarms is the following AP PHY Data Rate Anomaly: APs are using data rates of 48M, 54,M which is not included in the user defined data that is allowed in the system. I checked the controller and I have both those data rates enabled?
    Thanks      

    Thomas:
    So the only problem you have is the AirMagnet alarm?
    I never worked personally with AirMagnet but you better check the settings if there are defined data rates?
    I think the message says the AP has 48 and 54 Mbps data rates enabled while the AirMagnet is not configured to allow those data rates.
    Just an idea. hope it helps.
    Amjad

  • Anomaly detection using ODM

    I was asked the following question:
    "My question is very simply, we are doing a monitoring system for a
    website that helps the admin to mine on specific data (using ODM to
    produce Web mining) so we want to apply the anomaly detection. We dont
    know what we should do and what we should produce as a results."
    A couple of suggestions come to mind:
    1) For an overall discussion of intrusion detection in general using the Oracle RDBMS as an analytical platform the following paper might be useful:
    http://www.oracle.com/technology/products/bi/odm/pdf/odm_based_intrusion_detection_paper_1205.pdf
    2) A couple of things to think about and do:
    (a) Define what is the "mining case", that is, the "object that defines what is the concept you want to mine. For example, in web mine you may want to detect anomalous session activity. This can be defined over the whole activity of a session or over time windows. In the first case each session will define a mining case (it will be a row in the training data). In the second case each section will generate many mining cases, one per time window. Let's assume for sake of discussion that the goal is to identify anomalous session activity. Then the training data will consist of the session activities (e.g., clicks, pages visited, and/or information from forms; or more generally, http requests). There will be one row per session in the training data. If we know beforehand that some of those sessions where intrusion or anomalous in some sense we can also capture this data as a target for supervised modeling.
    (b) Decide what modeling to do. Two types of modeling can be performed (see the paper above for examples):
    (i) Supervised modeling - case there are examples of anomalous cases as well as normal cases
    This can be done by building a classifier on the training data. It is also possible to measure the quality of the classifier on a held aside sample.
    (ii) Unsupervised modeling - this should be done as well even if we can create a supervised model
    Unsupervised approaches don't provide a measure that indicates how good the model is at predicting anomalous events. These models are better at ranking cases by how anomalous the model believe they are.
    Two common unsupervised techniques for anomaly detection are: Clustering and One-Class SVM. The latter is considered a state-of-art in many problem domains and it is the one implemented by ODM. ODM also has clustering but it does not return distance of a row to the center of cluster. This information is necessary for using it clustering for anomaly detection. If one wants to use clustering, the Oracle Data Mining blog has a post that can help compute distance from rows to centroids:
    http://oracledmt.blogspot.com/2006/07/finding-most-typical-record-in-group.html
    It is important to note that the method described in the post doesn't support nested column attributes.
    When building unsupervised models, only the data for normal cases should be used to training the models. The unsupervised models can be seen as defining what is normal. It will recognize that something is anomalous when it does not match the definition of normality learned by the model.
    (c) Use ODMR to help with modeling
    (d) As new session information is gathered it is possible to score in real-time the session to detect anomalous behavior. One should score both supervised (if information was available) and unsupervised models to detect anomalous behavior. See the above paper for some discussion on this.
    The supervised model will indicate if a case is anomalous or not based on known types of anomalous behavior. One should use ROC tuning in ODMR to find a good operating point for the model. This is necessary because the number of anomalous cases is usually small compared to normal ones.
    The unsupervised model (one-class SVM) will provide a ranking. The higher the probability of belonging to class 1 the more normal. A 0.5 probability for class 1 indicates the boundary between normal and not normal. In reality it marks a boundary where normality dominates. There can be some anomalous cases with probability higher than 0.5 and some normal cases with probabilities less than 0.5. If working in batch mode we can rank the probabilities in ascending order and select the first K rows for investigation.
    --Marcos

    A suggestion to speed up the process: provide more information about your data (e.g., schema) and how you are invoking the algorithm (GUI, API, settings). Case you are using the APIs, have you tried the sample programs for anomaly detection?
    Regarding the Apriori algorithm it does not support timestamps and dates columns. In fact, none of the algorithms in ODM does (see the documentation for Oracle Data Mining for the supported column data types). the dbms_predictive_analytics package does. Are you trying to do sequential association rules or just trying to do plain association rules using data from a date column? ODM does not support the former. The latter can be done by converting the date column to a VARCHAR or NUMBER column.
    --Marcos                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Missing warnings while using softproofing ?

    First, congratulations for all the new or enhanced features !
    Especially the softproofing function is great : the histogramm is now showing what is happening in the destination color space.
    My question is about the warnings on the image while using softproofing : after activating both monitor and destination warnings, and evenif my image is voluntarily completly blown up with highlights, i see very few warnings on the image.
    Am i doing something wrong or the warning function is not working well ?
    Charles, France

    I suspect but could be totally off, that a single color channel will not cause the OOG overlay. You should be able to see this anyway in the normal Histogram (in this case, a blue spike on the end of the Histogram). Again, going out on a limb, I suspect that the profile has to be used to tell LR that all three channels fall outside of gamut, in other words, this isn’t a channel by channel OOG but the entire group. Maybe someone from Adobe can comment.
    I can get the OOG warning to show up with only one or two channels saturating. It appears to have been done correctly. See the screenshot below. The channel info shows only red saturating at 255 in the red-masked OOG area
    Now I can say that I think there is a zoom bug in terms of the OOG in that I’ve seen some overlay colors appear or disappear based on the zoom ratio. Even saw this in Julieanne’s video demo. So you may want to zoom in at 100% (1:1) to get a more accurate OOG preview.
    I am not so sure whether that is a bug or simply a cause of how the Develop preview is generated. LR has to render a low resolution preview and inevitably that involves some downscaling and resharpening (LR has been doing some sharpening on the develop preview for a while now). It is possible that if you are on the edge of being out of gamut, the lower resolution preview can get pushed out of gamut by the sharpening and perhaps by noisy data that is not smoothed away by the noise reduction that would happen at 1:1 but doesn't happen the same way zoomed out at fit or fill.
    P.S. as we found in the thread linked above there are some minor bugs in the softproof notably with proofing for sRGB. So I wouldn't trust it too much yet and just look at it as a preview of how it might or will be implemented in the release.

  • Where do I save other ICC Profiles so I can use them in softproofing in Lightroom 4?

    I am starting to use an online photo printing service and the photos are not an accurate representation of what I see on the screen so I want to download their color profiles which are specific to their printers and various papers. Where do I save the files so Lightroom4 can access them in softproofing?

    On a mac, it's Library/ColorSync/Profiles either in the root or user level (under 10.7, that folder is hidden)**
    **In the Finder, choose Go > Go To Folder.
    In the Go To Folder dialog, type Sudo ~/Library Click Go.
    OR
    This method makes the user library folder permanently visible but requires the use of Terminal (not for the novice user):
    Launch Terminal from the Utilities folder.
    In Terminal type the following command and type Return key:
      1. chflags nohidden ~/Library
    Enter administrator password and then type Return key.
    Type Exit and quit Terminal.

Maybe you are looking for