Leica Raw conversion in Aperture

Hi all. Is there a plug-in available to view Leica Raw images in Aperture?
Thanks, David

I also use a Leica M8. Importing the RAW files into Aperture gave me small thumbnails which are actually 8KB Jpegs. These, I suppose, are files Leica uses for previews. Obviously Aperture does not support and convert DNG files, which are championed as a universal RAW format by Adobe. I think it is narrow minded and short sighted by Apple not to support that format. Consequently I downloaded the latest beta version of Adobe LightRoom and started working with this fierce competitor of Aperture. It works beautifully with my Leica files and a wide variety of other RAW files as well. Of course, Photoshop CS2 and CS3 (Beta) use the same converter. It can't be in Apple's interest to drive professional photographers who use Leicas into the arms of Photoshop Lightroom. It sure worked in my case - I now use Lightroom more and more and I'm charmed by many of its elegant features. Since Adobe has opened DNG to everyone I see no reason why Apple cannot support it. It is high time that the industry adopts a universal RAW standard rather than constantly updating software to a rapidly growing number of proprietary formats.

Similar Messages

  • RAW conversion with Aperture

    Has anyone compared the quality of RAW conversion of Aperture vs. Nikon Capture as well as other converters?
    I really like the quality of nikon capture and would not want to purchase aperture unless the conversion was at least equivalent.
    Thanks for any input.
    mark
    G4 17" Laptop   Mac OS X (10.4.3)  

    I've compared Aperture's conversion side by side with Adobe Camera Raw's. My method was to do some conversions with Camera Raw and save the result along with the RAW file. Then, in the Apple Store, I performed the conversions using Aperture.
    The results from Aperture are not good. They look okay at reduced size, but if you look more closely, the de-mosaicing Aperture performs is quite bad. On some images it is only "somewhat" worse than Camera Raw; on others it is so bad as to be unusable. Shadow detail suffers the most, but highlights are not immune. Some images showed color fringing that was not present in the Camera Raw conversion, even with all chromatic aberration adjustments set to zero in Camera Raw.
    I ignored differences in color and tonal rendering because I did not have enough time with Aperture to learn to get the best results out of it in terms of color. It takes a while to figure out how to get good color out of a RAW converter.
    In no case was Aperture as good as Adobe Camera Raw in terms of image quality. The difference was immediately obvious at 100% magnification.
    I would not use Aperture for RAW conversion.
    EDIT: I forgot to mention, in case it matters, my camera is a Nikon D2X.

  • Panasonic Lumex DMC-LX1 raw conversion for Aperture doesn't work.

    I've seen many people having raw conversion problems. Direct import of Lumex raw files to Aperture does not work.
    Adobe DNG conversion of raw to dng does not work.
    I'm running on Photoshop CS.
    Perhaps my DNG conversion settings aren't right? Tell me what they should be.
    Do I have to go as far as changing the raw.plist or whatever it's called.
    Would CS2 with the Raw conversion Plug-in work instead?
    Remember that..."If all the woman lived across the sea, what a great swimmer Yellowman would be"!
    2.0 Duelly G5 4gigs ram. 23" Flat Cinema   Mac OS X (10.4.6)  

    Joe,
    good to see that you are reading these posts. I am sure that many users whose cameras' raw files are currently not supported by Aperture would love to help out in any way they can.
    However, as we are living in a converging world, why doesn't Apple talk with Adobe and share some of the information used for RAW conversion? I'm thinking dcraw which (according to a note in its source code*) is using data provided by Adobe... and that same data is also contained in the Raw.plist.
    Thus, if Adobe knows something and shares it with dcraw, and Apple uses some of the dcraw code (at least the m2 matrices found in Raw.plist are equal to the dcraw ones), why can't you guys all share the same information, and thus speed up RAW support for all cameras?
    Just a thought.
    Kindest regards,
    Karl
    * This is the bit:
    Thanks to Adobe for providing these excellent CAM -> XYZ matrices!
    void CLASS adobe_coeff (char *make, char *model)
    powerbook G4 17 1.33 GHz   Mac OS X (10.4.6)  

  • Leica RAW conversion strangeness...

    the Leica RAW (.raw) format is NOT on the list of supported cameras...BUT, I am able to convert .raw files to .dng using Adobe's DNG Converter, and the finder displays the images (in a finder nested folder display), just fine. And, when I import these into Aperture, they appear for a moment and then disappear to the screaming red screen "Unsupported Image Format". I'm not sure what's going on, and in the past I've been able to display the .raw images in other applications with OSX (iView Media Pro)....so I'm perplexed. Any ideas? the actual format IS the same as for a supported camera (Panasonic), and I'm told I could hack the .plist file and make it work...but I'd really like a supported approach. Any suggestions?
    cheers,
    david

    the "appear for a moment" is probably Aperture showing the preview image in the .raw file, before deciding that it can't handle the raw image data.
    (If it is this, then odds are Finder will show the images but Preview.app will also fail to.)
    Clearly MacOS understands the .raw file format, but thinks that it doesn't have support for however your camera identifies itself in the EXIF data. Modifying the Raw.plist is the way to try, for now.

  • Weird RAW conversion using Aperture

    I'm shooting with an Olympus E-1 and I'm getting some weird patterns in high ISO shots. The pattern is not as noticeable in low ISO shots. Here's a sample.
    http://www.andy-kang.com/misc/pattern.jpg
    Anyone else experiencing this with other camera files?
    Power Mac G5 2GHz DP   Mac OS X (10.4.3)   3.5GB RAM, X800XT

    Ouch Andy - that is so bad it's almost cool.
    The Aperture raw converter is fundamentally broken, but I haven't seen anything quite this bad until your example.

  • 10.4.10 and Canon 1D Mark III RAW Conversion in Aperture

    I'm noticing bright reds are not being converted properly at all. Overall, most images look excellent; however, images with a large amount of red look terrible. I've tried converted the .CR2 files via DNG and then in LightRoom, and the red looks good.
    Has anyone else noticed this? I'll try and get some crops and place on Flickr tonight.
    PowerMac G5 Dual 2GHz   Mac OS X (10.4.9)   4 Gigs RAM, CalDigit S2VR Duo 1TB

    I haven't seen those problems. Did you post the samples on Flickr? How can I find them?

  • RAW Conversion between CS2 and Aperture``

    Has any one done any sort of comparison of RAW conversation out put from CS vrs; Aperture? Recently I've been using CS2 for my port processing work and really have noticed that the CS2 processing seems to be much clearer, better tones, and detail. Lately I don't seem to be able to get a decent print out of Aperture, I've been using it since it first shipped and I know it fairly well, just feels like I'm in some sort of a slump with it.

    If you search this forum for deer.nef you will find a couple of recent threads on that topic.
    I have done my own tests, converting several images using both apps. My conclusion is that both deliver a good conversion. Some images may come out better from on or the other but you will probably get the best result from the one you have the most familiarity with.
    Note: the current RAW converson in Lightroom is not as up to date as the one in the Photoshop CS3 Public Beta. That will change next Monday. Try your own images in both. You may have a personal style that works better withh one or the other.

  • Aperture 2 vs Aperture 3 RAW conversion

    I am new to Aperture and have been reading up on it. One point I thought was interesting was that v3 RAW conversion was considered improved over v2. I could understand that there could be a variance during the initial release of v3, but at some point v2 conversion would have been updated.
    Is there a difference between v2 and v3 RAW conversion?
    If so, how big of a difference? Would it be better to use Canon RAW converter instead?
    Thanks,
    Kenn

    You need to eyeball the various conversions using your own typical photos. Each different camera model is a different RAW conversion, and each individual's brain/eyes see them differently. With the Nikon D2x I prefer Nikon's conversion over Aperture's and Aperture's over Adobe's - but Aperture's workflow is superior by a lot so I use Aperture.
    If I was selling a thousand dollar large landscape print (I wish) shot on a D2x I would do the RAW conversion using Nikon Capture NX 2 rather than using Aperture, but that is just my personal preference with that particular camera model. And I see the difference as tiny, small enough that for most photography the workflow is more important.
    HTH
    -Allen

  • Aperture RAW conversion and noise

    I've been using Aperture for many years and have recently learned something useful about how to tweak the RAW conversion settings.  Until recently I just left them at the default settings for my camera, a Panasonic GH2.
    Anyhow I've not been entirely happy with shadow noise (otherwise I reckon it's a great camera).  Many web sites say that a degree of shadow noise is normal for this camera, so I didn't figure mine was any different.  I tried a variety of noise reduction approaches but none really made a worthwhile improvement.
    Until a few days ago when I tried tweaking the 'Raw Fine Tuning' settings - and I found a way to make things *much* better.
    Please note that the following comments may only be relevant to Panasonic RAW files, and maybe only for the GH2.  I don't know if they apply to other cameras (though I think they may.
    It turns out that for the GH2, the default 'Raw Fine Tuning' setting includes 'Sharpening' of 0.78 and 'Edges' of 0.79.  This is fairly aggressive sharpening, but I didn't really realise what it was doing to noise until I  discovered that was significantly increasing shadow noise -even at base ISO!
    If I set these both the sharpening sliders in the Raw Fine Tuning section to '0', the 'grain' in the shadows is much smoother - a massive improvement.
    But, of course, the image is a bit less 'sharp'.  Well, this isn't much of a problem with 16+ megapixel cameras.  Unless you are making huge enlargements from originals, and really look closely at the finest details at 100%, it makes very little difference if you give up this 'sharpness'.  But the reduction in noise is actually very obvious indeed.  It's much better! 
    Most of the sharpness I need on these less noisy images can easily be added by including the 'Edge Sharpen' adjustment, either at the defailt settings, or marginally toned down a bit.  I'm currently using Intensity 0.7, Edges 0.3 and Falloff 0.4.  This leaves most smooth areas untouched, so the 'noise' or 'grain' in smooth areas is as it comes from the sensor.  By toggling the Edge Sharpen on and off, I can easily confirm no change in 100% or 200% loupe views. 
    That level of edge sharpening is a bit subtle, but actually achieves most of what I got from the Raw Fine Tuning sharpening sliders.  It will be applied only to in-focus contrasty things like eyelashes or hairs or other defined edges, and very nicely.
    So I'm sharing this in case other people also find it helpful.  I strongly suggest removing the default sharpening entirely, and only using the Edge Sharpening slider in a cautious manner if you want to enhance sharpness.
    Some related web pages:
    http://www.jonroemer.com/blog/2011/01/aperture-3-too-sharp-tweak-the-default/
    http://www.twin-pixels.com/raw-processors-review-aperture-bibble-capture-one-dxo -lightroom/
    PS - there is a different issue with the default Raw Fine Tuning 'Boost' and 'Hue Boost' sliders, both of which are set to 1' by default.  It turns out that these introduce a very large amount of contrast and exposure gain - turn them down to zero and the image goes quite dark and flat!  The Aperture user guide says something about Hue Boost changing colours when Boost is set to '1' and this is the case.  So I've experimented with turning them both to zero, and instead using a custom curves adjustment to achieve a similar level of exposure and contrast to the default conversion and the camera's default JPG image.  By fine-tweaking the curves one can get better control of blown highlights and the overall contrast.  I'm not sure if the colours are 'better', but I think so.  I am fairly sure that I get smoother transitions in the mid-tonal ranges with this approach rather than just using Apple's default settings.  Maybe they are a but strong for my liking.  Certainly I can make curves that rarely require the 'Recovery' slider to fix over-boosted highlights.  Anyhow, you may also find that this tweak helps a bit.  Interestingly on a Canon RAW file the effect is not nearly as great in exposure terms, but there is also a definite colour change.
    PSS - the end result is that I have set my camera preset for RAW fine tuning to zero settings for boost, hue boost, sharpening and edges.  I then add contrast as needed using curves, and sharpen only with a little edge sharpening.  I've then saved a few Presets with slightly different contrast curves and all with a little edge sharpening.  I can very quickly select the level of contrast needed, and I am very confident that my results are quite a bit better, with better tonal gradations and much less noise.
    Hope this helps
    Chris.

    Nice observations, Chris.  I think the RAW Fine Tuning is often overlooked, even though it's a vital first step in RAW processing, and really the whole point of shooting RAW in the first place.  Too much boost yields horrible skin tones in my experience.  I have a default of .50 Boost and Hue Boost, Sharpening and Edges at .25, Moire .50, Radius 12.0 and Denoise .25.  I've found these are "mid range" settings for the Canon 5Dii, and first make small adjustments to the Fine Tuning brick before moving on to exposure adjustments. 

  • Aperture RAW conversion & sharpening

    If I use Aperture 3, edit in Photoshop CC (PS6) does that mean:
    Aperture applies sharpening when converting a RAW file?
    If so, is Apereture applying the default sharpening normally applied in Adobe ACR?
    If not, can use the NIK Capture sharpening plugin in Aperture, before editing in PS?
    Thanks,
    Brian

    The only way you will be able to correlate the setting in one converter to another is to run tests on each and compare the images. The numbers aren't useless they just don;t do want you would like them to.
    If you use PS as Aperture's external editor you are going to be seining PS a tiff or psd file not the Raw file so  I'm not sure your concern is justified.
    All I can do now is throw out the Fine Tuning default, set everything to "0" and go back to doing everything manually in Photoshop.
    Well if you are doing the conversion in PS then the settlings in Aperture have no effect anyway. And if you are doing the conversion in Aperture you are sending a tiff or psd file to PS (a I wrote above) and then the PS converter doesn't come into play.
    The only way your concerns would be something to worry about is if you are doing two separate conversions, one in Aperture and one in PS, and wanted the two separate images to be identical but I'm not sure why you would want to do this.
    regards

  • Aperture 2 raw conversion very bad with some subjects (like sunsets)

    Please take a look at this composite:
    http://amrosario.com/rawsun.jpg
    These conversions were done in Aperture 2 using only the three different raw conversion engines and no other adjustments. As you can see, the 1.1 version is more yellow than the other two. What, in fact, the scene actually looked like is closer to the 1.1 conversion. The other two are way off. Not to mention the extreme banding visible. What the heck is going on?
    The only way I was able to get something close to the 1.1 version using the 2.0 converter was to whack out some saturation to an extreme with not so goo results. I also processed the pic in ACR 4.1 and, even though I got a little banding around the sun, the initial color was correct. Also, the white balance is the same setting for all three images (including the one I processed in ACR).
    I mean, what's with all the red/pink in these conversions. I know Aperture 2 does away with some yellow in pix, but this is crazy. And the banding is quite unacceptable.
    Any thoughts?
    Antonio

    Yeah, thanks for that tip. I boosted and it helped, but I think it could be better. The color still runs a bit on the pink/magenta side. I'll keep trying and see what happens. Still, the change can be a little jarring if not expected.
    Antonio

  • RAW conversion, iPhoto vs Aperture

    I currently shoot in RAW, save the folder to my desktop, convert files in ACR and import into Photoshop for edits; I then create a master edited TIFF for each saved image a, plus make 3-5 variations (composites, B&W, etc) of every master image . When all that is in the (renamed) desktop folder, I then import that folder into iPhoto where finished files are routed to Smart Folders.
    For added security I routinely backup all the RAW files using Export to an external HD.
    The ideal workflow (for me) however, would be to use Nikon's free NX2 software to convert the RAW files into TIFF, do basic editing and import both the RAW and TIFF conversions directly into iPhoto.  So far, I can't get that to work without going through the extra step of NX2>Desktop>iPhoto.
    Am I missing something in iPhoto, or maybe it can't handle that?
    Would Aperture allow that direct NX2 > Aperture import? I'm a little unclear on the Aperture RAW conversion process, so could I import RAW files folder into Aperture and then convert those RAW files to TIFF and edit them within Aperture? That way the only time I'd have to go outside Aperture would be to do something in PS that Aperture can't handle.
    Brian

    No
    You simply have to set your editing program as the external editor for iPhoto - in the iPhoto preferences you can choose to send RAW to the external editor or not - if you do then once you edit the photo you must save it to the desktop and import the modified photo into iPhoto creating a new photo - if you do not pass it as RAW then you save in the editor and it is returned to iPhoto and the database properly updated
    As to the process iPhoto uses - all originals are saved unmodified - RAW , TIFF or JPEG.  as they are imported a small JPEG preview is generated for quick access by iPhoto and other programs - with RAW an additional large JPEG preview is saved  --  when you edit in iPhoto the edit steps are saved and applied to the preview and to the thumbnail - future edits steps are also saved so you always start yoru edit with the unedited original and add edits so you never are but one step form the original eliminating the multiple editing losses that cause some people to use TIFF rather than JPEG   --  hence my comment
    Both can import and convert your RAW photos and both provide lossless editing so using giant TIFFs would not be necessagy
    and
    Unless you have very unusual requirements your work flow seems uncessary and overly complicated to me
    as to
    but if I want to see the original RAW file, and the edited versions stored within iPhoto
    If you want to see both then they both have to be there - since iPhoto always keeps the original and while editing in iPhoto you can view it at any time by depressing the shift key most people prefer to simply their work flow and save the disk space and let iPhoto handle this
    It really sounds like you do not want iPhoto and yoru best choice is to shoose a different photo manager that works like you want - or learn and understand iPhoto (and most if not all Digital Asset managers - DAMs - which work much like iPhoto) and use it the way it works
    You can use what you please and do what you please, but if you use iPhoto you are making life very difficult by going against its standard procedures
    LN

  • Contact Sheets / Proofing and useful Aperture RAW Conversion

    All,
    I wanted to appeal to all of you pro photographers out there to share about how you handle the proofing stage (contact sheets) with your clients. I'm curious about how you all make this process as efficient as possible.
    Ok, say you have taken 1000 pictures for a wedding or some other event (forget the accuracy of that number, its just a round number for discussion sake). You need to present your photos to your client, but you need to present a subset of the 1000 photos for a few reasons:
    1) Not all photos you are going to take are going to be great. I've heard a general quote by some pro photographers that their "keeper ratios" (the percentage of pics that are really good from a shoot) run around 10%-20%. Fair enough, I don't want to debate this percentage, but it gives us a target number of 100 photos to present to a client from a 1000 picture shoot.
    2) Your client is probably not going to be happy if they have to sift through 1000 photos. I recently had a friend who paid several thousand dollars for a wedding photographer who sent them 1000 photos to choose from. They weren't particularly happy with this, and told the guy there was just too many to choose from. Personally, I felt that this was putting part of the photographer's responsibility on the client, but whatever.
    Ok...so for the sake of the example here, we have to get 1000 photos down to 100 photos, so the client can choose what 50 (for example) they want to purchase and have printed, put in their photo book, slide presentation, etc.
    Sorry for the long intro, but here is the issue at hand: we want to work quickly for the client, and get them their 100 photos as soon as possible. We also want to put our best foot forward, and give them high-quality photos. But at the same time, we want to work efficiently, and if possible not spend time doing final retouching on photos that the customer doesn't want, but rather focus this time directly on the photos the customer does want.
    I have two questions from this which pertain to Aperture's RAW conversion and workflow:
    1) Do you do any significant adjustments on photos for the contact sheets you present to clients (the 100 photos now)? Is it just a quick exposure adjustment, or are you retouching all 100?
    2) Despite Aperture's RAW conversion problems and other adjustment glitches, is it sufficient quality in your opinion for a contact sheet?
    My purpose in asking these questions is that perhaps the Aperture RAW conversion issue can be mitigated if we can get to the point of customer contact and review using Aperture-only conversion and adjustment tools, and then isolate photoshop use for only the final, significant edits. The problems with Aperture's RAW conversion are well-documented, but the question is, could it still be sufficient for small-scale proofs, understanding that for large-scale, high-res images, it won't be suffcient.
    Your opinons are valued!
    Brad
    Powerbook G4-1.33GHz-17" / Powermac G4-1.4GHz   Mac OS X (10.4.2)   PB: 1GB RAM, Radeon 9600-64MB / PM: 1.25GB RAM, Radeon 9000Pro-128MB

    ">-DELETE project from Aperture because I can't use the app for the delivery
    of finals:
    Forgive me if I've forgotten the detail you may have posted elsewhere about this. I have seen you mention this several times, but I am really interested in the specifics behind the problems you have encountered. I have some needs in finishing that are beyond just regurgitating a photo. I'll be basically augmenting my photo with text, borders, special effects, etc. for more professional presentation, and the ability to market a photo in different ways. This is one reason I cannot discard Photoshop from my workflow. Anyway, let's assume for a moment I'm able to do all my editing in Photoshop, and those PSD files are sitting within Aperture. From there, what problems am I going to encounter? I'm tapping your brain here, as the time I have spent in Aperture has been primarily oriented toward everything prior to the finishing stage. "
    Hi Brad,
    If I've imported images into Aperture that have previously been worked over in Photoshop, none of the layers I may have created in those files will be available to me from within Aperture. This does not break but severely sprains the functionality of Photoshop. I'm keeping the images around because I think I or my clients will need them later, so what might I do with them?:
    1) If I'd like to do more work on them I either have to abandon access to the previously created layers and their magic, or export the file from Aperture, work on it outside, import it back into Aperture. Every time I want to work with those layers I have to do the same dance.
    2) If I'd like to send jpg or tif versions of those files anywhere I can choose to use the tools within Aperture or Photoshop to do so. Aperture's tools for these conversions are simply not of professional utility: no compressed tifs, no layered tif support, no quality choices for jpgs and no jpg previews. And in either case, using Aperture or Photoshop, the conversions are created OUTSIDE of Aperture and not managed by it.
    3) When I decide to archive my older projects I'm faced with the incredible limitation that Aperture will not allow me any remote search of any archive that is not "live" within Aperture. Not even Spotlight will search Aperture libraries!!!!!
    So moving already created projects into Aperture has absolutely no advantages and a number of problems, any one of which might be a deal-killer by itself.
    If I'd like to use Aperture to manage work that I create going forward I've got those limitations already listed above, but I CAN access layers in PSD that are created from within Aperture. I cannot make layered duplicates of those files in order to work on versions of those images so once again the Photoshop workflow is hobbled.
    All of this makes it a bad idea for my projects to make anything but a brief trip in and out of Aperture for sorting/proofing.
    Regards,
    fp

  • Aperture 3 Raw conversion from Nikon D700 - Bad results - Anyone?

    I recently upgraded to a Nikon D700 and have noticed I am getting some really bad conversion results from my raw files which involve my having to do a lot of work to get decent images. Most images are too dark and with strong orange cast... Any ideas? I thought it might be the camera, so I tried another computer with photoshop raw converter and images are fine. I have noticed the original import settings are strange on Aperture but cannot seem to change them, they always revert back to maximum hue boost and max boost ect... Any help would be great! thanx!

    I have a Nikon D700 and have just tried the Aperture demo- same results as you guys, disappointing RAW conversion. Contrast and sharpness quite poor and blues are 'off'
    I currently use Capture NX and was looking for something a little less 'clunky'. Though it may not be as slick as Aperture, its RAW conversion is spot on (as you would expect from a Nikon sponsored app)
    It's easy to compare the differences- open an unedited RAW file in Capture NX and save as an uncompressed, 16 bit TIFF. Import this and the original RAW file into Aperture. Prepare for disappointment :-/

  • Aperture RAW conversion colour noise with Canon 1D Mark II

    I'm using Aperture 2.1 and am wondering if anyone here is having this problem - basically highlights end up with false colour with this camera/RAW conversion combination. The problems appears to have been introduced with the 1.1 RAW converter as 1.0 conversions don't seem to have the problem. I'm not sure if this is camera specific, or whether there is some tuning which can be done to the RAW converter to minimise the effect - attempts have so far failed with this approach.
    The best subject to produce the effect is strong reflections from water - i've attached a crop of an image which shows this problem, and I can supply a RAW with this problem.
    Conversion using RAW 1.0 (less or no colour pixelation):
    http://www.loftsoft.co.uk/pictures/KC7U5116%20-%20RAW%201.0.jpg
    Conversion using RAW 2.0 (colour pixelation):
    http://www.loftsoft.co.uk/pictures/KC7U5116%20-%20RAW%202.0.jpg
    Any suggestions as to what to do? Is this simply a RAW conversion problem which can be addressed or am I using the tool wrong?
    Many thanks,
    Cesare

    Hmm. I can see some color effects in the 1.0 conversion as well.
    Those are some touch photos... you have lots of specular highlights with the sun reflecting off the water and the railing.
    Aperture 2.x and 1.x handle the RAW conversion differently. I would suggest you try playing with the RAW Fine Tuning brick, specifically with the Moire and Radius sliders, and try fiddling with the Auto Noise Compensation checkbox.
    I don't know whether you'll be able to make the problem go away completely or not.
    With my ~30,000 1D Mark II files I've seen something similar to this (though much less extreme) on a couple of them. Always with specular highlights though -- off water or metal objects.
    Still, you may wish to submit Aperture feedback and include the RAW file.

Maybe you are looking for

  • Howto implement temporary changes / rollback in my model?

    First some background information: I'm building a project management tool. It's based on JEE, Struts 2 and uses AJAX. The model exists as a singleton within the application-server. The model is basically an object tree which consists of projects, rel

  • Convert OPML to Voracious' format

    I just stumbled on Xyne's Voracious feed aggregator, and liked the look of it (I had thought of writing something similar). I had a big fat OPML file though, which I didn't want to move into this new format by hand, so I wrote a Perl script to do it.

  • From a CRM training course to do SAP BI life time projects

    Hi, My name is Connie. I am currently doing Master's degree in Business Information Systems. I am working as a Software Tester.  I did SAP CRM training as well but have no work experience on CRM. I recently got an opportunity to be exposed to real li

  • Elements 11 - endless MAC pinwheel on loading a file

    Any solution to the endless pinwheel in 11 Editor (updates installed)?  I load a previously created PSD file, move a few layers around and the endless pinwheel appears.  Have to Force Quit. MAC OSX 10.8.3 

  • HTTP Post of ByteArray

    Hello, I hope this is the right place for this question. In the first set of code below, I create a request using a ByteArray as my binary data. The server doesn't recognise it as a valid file and does not work. If I perform all the same tasks but wr