Fuji raw conversion

Does anyone have any idea when Apple will add Fuji RAF file conversions to Aperture? I love my new E-X1 but their software is TERRIBLE. Any tips on getting around it? Seems like tiff export into Aperture will be my best worst choice.

This is such a common question. The answer is always the same: We're just users here so nobody knows when this may arrive.
Look at the 'related threads' over to the right ==>
If you want to see other people have asked the same question :-P

Similar Messages

Fuji Raw Conversion Software as External Editor in Lightroom

Anyone know whether Fuji's Hyper Utility RAW conversion software (if I remember the name correctly) will work as an External Editor in Lightroom. (Just read an article by a Nikon photographer who uses Capture NX this way in Lightroom and wonder whether the same is possible for Fuji.)

Thanks; I guess my question (which I did not state clearly) is whether if, at the end of processing in HV-S3 and "Save" the saved file (likely a TIFF) will automatically appear in the Lightroom Library associated with the original RAW file; this would be the chief advantage over just opening the folder with the file in HV-S3 to begin with, but it occurs to me that this may be a dumb question (as I've just downloaded and begun to use Lightroom and can't experiment with HV-S3 yet as it has not yet been released, but will be shortly). Thanks again.

Fuji X-trans raw conversion

I have both the Fuji X-E1 and the X100s. The conversions of the raw files in ligtroom, while much better than they were, still have a way to go to match raw conversion from programs like Photo ninja and Iridient. I'm wondering if Adobe is working on improving the raw conversion of X-Trans files in lightroom. Love lightroom, but the raw conversion of fuji files is still problematic in areas of fine detail, like tree branches and leaves. The effect is something like an halo around these features, and is worse once the files is sharpened.

I'm very interested in this topic, too. Actually, I'm sure there are tenth of thousands of photographers interested, including professionals. I just purchased Lightroom, but this is a great chance for Adobe's competitors to get clients. Let's see if Adobe answers to this thread, and if they will do something to fix the poor X-Trans (but also micro 4/3 like Olympus OM-D E-M1) support. They have the experience to do something in very short times, let's see...

Lightroom 3 raw conversion and fuji xpro 1

have just bought a fuji xpro 1 and found that lightroom 3 doesnt support raw conversion. i realize that lightroom4 has, but i dont want to spend x amount of dollars when lightroom 3 meets most of mr requirements. does anyone know if or when lightroom will provide the raw conversion

platen wrote:
have just bought a fuji xpro 1 and found that lightroom 3 doesnt support raw conversion. i realize that lightroom4 has, but i dont want to spend x amount of dollars when lightroom 3 meets most of mr requirements. does anyone know if or when lightroom will provide the raw conversion
Perhaps never. The last version in series 3 was: 3.6 and if you have got it then it will be the last one. If it is just one off thing then you can use the trial version of LR 4.1 otherwise you will have to buy an upgrade.
I take it you have done the upgrade by going to:
Help >> check for updates
Good luck and let us hope you can do something about this.

Fuji S5pro raw conversions turn dark

Hi all,
This is my first post here. I searched the forum but did not find anything about this topic.
I use Aperture as my main workflow for processing and organizing my photographs. I use Fuji S3pro and S5pro, the S3 exclusively jpg, but S5 largely Raw (RAF-files). As you might know, Fuji RAW files are quite different due the the s- and r-pixels of the SuperCCD. Many RAW converters had initial problems with those files. I started using aperture in May last year (Aperture 2.0).
Everything was fine, actually I was surprised. I found Aperture conversions not to be any worse than ACR. The only nag is that 2 of the sliders do not work, but I could live with that. At some stage end of last year I installed an Aperture software update (don't remember which number it was). After that, most imported Raws from the S5 turn medium to heavily underexposed. In the import window the pics look fine, just as on the camera screen. Once imported, during the thumbnail creation process, most of the pics turn underexposed. I can often correct it by shifting the exposure slider to max, but this always leads to increased noise levels. Opening the same file in ACR/CS3, no problem, the files are fine.
So I think something in that software update messed up the RAF file conversion. Interestingly, files imported before the update remained fine. My workaround has been to open the problematic files in CS3, convert them to TIFF (or JPG) and then re-import them to Aperture. This is however no solution on the long term. I use Aperture because I like the smoothness and speed of the workflow (I shoot wedddings and events and have to process large bulk of files in short time). The wedding season is now ahead, and I am a bit worried. I do not want to shift to Lightroom because of that.
There have been newer software updates for Aperture, but none of them was a remedy for that problem.
Has anybody who uses Fuji DSLRS (or any brand) experienced similar problems, or does anybody know any remedy for this issue?
Any input is highly appreciated
Cheers
Gilbert

Gilbert
Many thanks for bringing this matter up and apologies for not getting back to you sooner on your first post here.
Just out of interest I took some test images on my S5 to see if I could assist you.
I took RAW images (RAF) with the dynamic range set to 100% at 100, 200, 400, 800, 1600 and 3200 ASA.
I then repeated the above, but with the Dynamic Range set to 400%
I was able to reproduce your problem.
So - I did a further test to narrow it down and find that the moment you go over 1000 ASA (i.e. from 1250 ASA and above) AND as soon as you use anything other than a Dynamic Range of 100% - then the images will be underexposed in Aperture.
But - if you stay under 1250 ASA, irrespective of the Dynamic Range - all is OK
Or - use JPEG rather than RAF as the issue does not appear
Not a solution - more a workaround
Hope this helps
Brian

Lightroom's poor conversion of Fuji RAW files

I am on the verge of switching to Capture One due to Lightroom's poor RAW conversion capabilities of Fuji RAW files. Before I do jump boat, I thought I'd ask whether anyone had actually heard as to whether Adobe were going to do something about this. i am not impressed by Adobe lack of performance & communication.

Mark Alan Thomas,
You see only half of the story. The Problem with JPGs is that this file format applies a "lossy" compression, and with each <save> "unnecessary" pixel information is deleted and lost irretrievably. And this happens each time the JPG is re-saved. So after a few saves the JPG is of very poor quality.
Even with LR that saves edits in the catalog and not in the pixels, you cannot avoid multiple <saves> of a JPG., for instance by exporting.
Also, how many quality settings for JPGs do you have in your camera? I have three: fine - normal - basic. And I have no way of knowing if "fine" corresponds to 100%, 80%, or 75%, or even less. I have practically no control over the quality of your JPG but maybe your camera gives you more control?
IMHO JPGs should only be used for
- e-mail;
- web-use;
- delivery of Lo-res for layout purposes.
The only scenario where I can see a pro shooting JPG is this: You cover a sports event for a sports magazine. The game is on a Sunday and starts at 3 PM and ends at 5 PM. The deadline for the magazine is at 5:30 PM. There is no time to edit Raw images. The photographer has to shoot JPGs and send them off to the magazine right after the game has ended. Maybe there are a few other scenarios that would justify shooting JPGs.
But if you value quality - forget JPPGs.
I use JPGs for the above stated three purposes. But I create them in Lr only when I need them. And I delete them regularly after a while.

Nikon D3 Raw Conversion difference between ACR4.4 and CaptureNX

Digital Photography Review has just published an in depth review of the D3. In it they compare raw conversions by ACR 4.4, ViewNX 1.0.3 (Capture NX), and Capture One 4.0.1. The ViewNX conversion mirrors the camera's jpg standard; but there are significant differences - to my eye at least - between that and the colours in the GretagMacbeth chart of the ACR result.
Is this sort of thing common knowledge among the LR community?
I would have thought this a rather fundamental issue; but would welcome any thoughts from those more familiar with this level of colour expertise.
Anyone interested can see the dpr result on page 17 of the review at
www.dpreview.com/reviews/NikonD3/page17.asp

It's not unique to a D3. Check out http://www.damianharty.com/Purple.html for my take on it all - including a step-by-step guide to the calibration process Michael mentions.
Others get very uptight about the fact that this isn't a "proper" calibration and I'm sure that technically they're right, but life is short and this route works well for me. It also ends up as an LR preset and is super-fast to apply.
If "accuracy" was the only consideration, the camera wouldn't have "vivid" and "portrait" and all those other settings in it. We also wouldn't have had, in days gone by, the choice between Fuji Velvia and Kodak Portra - see http://www.damianharty.com/Film.html for my take on all that, too.
Both my articles are typically short-attention span things that appear on the net. Try "Real World Color Management" for a genuine guide through it all.
Or else don't worry about it.
Damian
PS I'm sure I used to be able to format links more nicely than that. Where did that go?

Fuji RAW

Well, as happy as I am for the D200 folks(and myself) the 10.4.6 does not add support for Fuji S3 Pro RAF files. That makes Aperture useless as far as I am concerned. Yes I knew 1.0 did not support it, but c'mon get real. The S3 is a highly popular camera among wedding photographers and even Lightroom BETA 1 supported it. Aperture as a baseline app may be evolving into a "pro" app, but Apple's "window dressing" support is far from "professional". This is the only Apple product that I utterly and completely regret wasting my money on.

<...>
This won't keep me from using Aperture, and I don't
feel like it's a waste (it just could be A LOT
better) but it puts a serious kink in what could
otherwise be a very elegant workflow. I either have
to shoot JPG, or load everything with ACR, then save
as Tiff, and then import those into Aperture. That
sort of defeats the purpose of it being an "All in
one workflow solution" or whatever their tagline is.
Even then either format isn't really ideal.
<...>
I use Aperture in exactly this way today - generate 16-bit TIFF files in batch and then import those into Aperture.
There are some side benefits to this process. One is that you can edit that base TIFF for some alterations after you have already done other adjustments in Aperture - so for example if you think an image needs a noise ninja pass you can edit the master TIFF and all of the versions you have created from it will automatically pick up the reduced noise base for crops and color corrections and so on.
Have you Fuji owners looked at Bibble yet? I think it supports the S3, and it comes now with noise ninja and lens correction tools. That might make a good starting point before the images come into Aperture. If you can't use Aperture for RAW conversion them embrace that as an opporunity to use the very best raw conversion software you can find, like Bibble or C1. RAW conversion is such a small part of what makes Aperture great that I really don't feel it's very limiting to do without if something else can do that well.
Until the day FUji RAW files are supported in Aperture you might try dropping Fuji a note asking them to work with Apple to get support included. I'm sure we'll see support for other cameras eventually but I don't think you can fault them for focusing on Nikon and Canon users first. I don't have either make of camera myself but I cannot logically say that any others should have come first in priority.

Fujifilm x pro 1 raw conversion

Dear Apple Aperture,
In the Fujifilm X Pro 1, you have one of the most exciting and in-demand cameras of 2012, and in my view, since the Nikon D90. But still we have no plugin for working with it's disruptive raw format within Aperture 3.x. While this capablity delays, I am forced to edit raws outside of Aperture making for a clumsy workflow, as I first have to edit and convert images in Silkypix. I know you are busy, but is this because of Fuji, or are iPxxx's the only important products these days...
I love you Apple, but please get us x pro 1 raw conversion soon!
g2

Apple is officially not here. We are a user-to-user forum, hosted on Apple's servers.
The Apple-approved method for making suggestions and feature requests for Aperture is via the feedback form: "Aperture→Provide Aperture Feedback".

I have an A77 and see that DxO RAW conversions look different

Several RAW conversion comparisons on the web amongst A77 users are pointing to markedly better conversions and noise handling currently within new DxO 7 eg. http://forums.dpreview.com/forums/readflat.asp?forum=1037&thread=39970661
I know that Sony's RAW have historically taken a while to arrive at optimal conversions from previous experinece with my A350. When Lightroom 3 came along it was like getting new cameras for most Sony Alpha users with from RAW performance at last matching Nikon from effectively the same sensors.
Can you let me know the likely time lag till ACR and Lightroom will have an update to this initial default to really match the DxO performance. Otherwise, to be honest, despite being a Lightroom user since the original Beta stages and a passionate supporter and advocate, I may have to consider jumping ship. Working exclusively in RAW I do need to be using the very best conversions possible to make the best out of my investment in my camera equipment.
I don't know if this lag with ARW conversions is because Sony don't co-operate with Adobe early enough or whether because Sony is only number three in DSLR share it gets less priority within Adobe than Canon and Nikon, but some timeline on a revised version of Lightroom to address this for the new Sony Alphas would be great.
Many thanks from a long time advocate who really hopes I can stick with Lightroom,
Cheers,
Paul

Hi Hal,
Many thanks...I’ll give it a try. Not trying to cause trouble as I genuinely am a fan of LR, but if they always lag on getting to grips with Sony RAWs it’s a major drawback for Sony users.
Cheers,
Paul

Lightroom vs. Photoshop Raw conversion

I have noticed that the Lightroom RAW conversion looks about 1/3 to 1/2 stop brighter compared to Photoshop on the same image with the same settings (I'm using LR 2.4 and Photoshop CS4). Anybody else notice this or have any thoughts? I'm assuming they use the same RAW conversion engine.

Thanks for the response. Well, when I export from LR to a JPEG and do the same from Photoshop (viewing them in photoshop), I get two slightly different toned images (I mistakenly said the LR images are brighter...they're actually darker). Viewing them this way should remove any monitor discrepencies (I'm working on a calibrated Lacie 724 monitor with 120% Adobe 1998 gamut so that should not be an issue).

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)

"Unable to save the raw conversion settings. There was a write permission error."

I just built a new workstation for processing photos using PS CS5. I use external drives to store my images as I find it easier for backing up as well as for when I want use my laptop for sorting, etc.. I copied over all my old "Collection" files, and of course, had to "fix" them once on the new machine. Once pointed in the right direction, the collections all fill out correctly.
When I go to process a collection though, I encounter an odd problem I can't seem to sort out. I can delete files, rename files, copy/paste to the external drives, etc.. What I can't seem to do is add Labels, Ratings, or modify RAW settings. I mean, I can use ACR to make adjustments, I just can't seem to save them.
The system just ignores label, rating commands completely. When I try to save an ACR adjustment I get this error. "Unable to save the raw conversion settings. There was a write permission error."
The files are NOT write protected. I'm set up as the owner of my workstation, with complete control of the system. I can't seem to find any useful information about this error because the "write permission error" seems to only be happening on installs, so that's all I can find help for.
My system:
Intel Core i7 970@ 3.20GHZ
24.0 GB RAM
64-bit OS - Windows 7 Pro
DX58S02 Motherboard
NVIDIA GeForce GTX 580

Thanks for replying. I've been going crazy trying to fix this.
To answer your first question; I use sidecar XMP files. If everything from my archive was shot in RAW I'd try converting to DNG and see if embedding the changes directly in a file worked. Unfortunately, a lot of my old stuff was shot in JPG, so sidecars seems to be the best choice.
When I add labels, ratings, as well as change RAW settings on files I place on my workstations HD everything works. It's only when I try to do these things with the same files on removable drives that I run into trouble. The drives I use are Transcend 640GB StoreJet 25ms connected via USB.
I don't think it's a UAC problem. At least, to my understanding, doesn't that control how your machine alerts you to program changes? I looked into how to change ownership, and did so, but that didn't work. Here's a link to what I mean: http://www.addictivetips.com/windows-tips/windows-7-access-denied-permission-ownership/
I'm stumped. I also hate the idea that I'll have to go through various folders to find images from already created collections, copy them to a new folder on my HD and then work on them. Then I'll have to put them all back... ugghhhh

Exported Raw Conversion Image Resolution and Assigning a Color Profile, etc

In Aperture 1.1, although I set the exported Raw conversion image resolution to 300 dpi in the preferences, it continues to come out at 72 dpi which is something of an inconvenience. Also, is it possible to assign a color profile to the "exported version" so that it is congruent to my PS CS2 color workspace (if that is what its called). Is this program capable of carrying out a conversion as a background operation? Finally, can the layout windows be configured so that they remember how they have been used in the past? Thanks.

Iatrogenic huh! Cool!
Anyway, I'm not real clear on what it is you are trying to accomplish. Despite your obvious vocabulary skills, there seems to be some disconnect relative to what you are trying to accomplish. You are right that "exporting a version" in Aperture is roughly equivalent to what happens in ACR when you "Open" a RAW image into Photoshop. In both cases you have, hopefully, already done the adjusting of parameters you want prior to "exporting", or "opening". When you "open" or "export" you wind up with an "image" composed of pixels, whereas in the RAW adjustment phase you are just working with a temporary thumbnail and a set of mathematical instructions. Big difference, I suppose is that when you "open" and image from ACR into CS2, the resulting image is truly just pixels and has not had a "file type" applied to the file yet, until you "save" it, while in Aperture, if you "export" a file to CS2, or to the desktop, you end up with the file type already applied. Presuming you "export" a 16 bit TIFF or PSD, there is no operational difference.
I could be wrong, but with the new Bayer Demosaicing algorithms in Aperture 1.1, and the Camera RAW adjustments, you should be able to come up with an adjusted image that is VERY close if not identical to one done in ACR, with the possible exception of lens abberation adjustment. I was very critical of the RAW adjustments in 1.0.1, but I am very happy with the capabilites in 1.1. That said, I think there is still some room for improvement in user friendliness of some of the adjustments such as Levels.

Numeric or value error: hex to raw conversion error , pls help

I am having problem with a sproc which accepts a Raw parameter.
I have a table called Profile:
CREATE TABLE PROFILES
PROFILEID INTEGER NOT NULL,
USERID INTEGER NOT NULL,
PROFILE RAW(255)
and a sproc named addprofile
CREATE OR REPLACE PROCEDURE addprofile
profile IN RAW,
userName IN VARCHAR2
AS
userId INT;
BEGIN
GetUserIdByName( userName, userId);
INSERT INTO Profiles
( ProfileID,userId , profile )
VALUES ( Profiles_ProfileID_SEQ.NEXTVAL,AddProfile.userId ,
AddProfile.profile );
END;
I am calling the Ent Library's Insert profile method which is part of DbProfileProvider.cs (Security App block). It is trying to persist a serialized profile object into the database.
private void InsertProfile(string userName, byte[] serializedProfile,
Data.Database securityDb, IDbTransaction transaction)
DBCommandWrapper cmd = securityDb.GetStoredProcCommandWrapper
(SPAddProfile);
cmd.AddInParameter("userName", DbType.String, userName);
cmd.AddInParameter("profile", DbType.Binary, serializedProfile);
securityDb.ExecuteNonQuery(cmd, transaction);
I get the following error:
Any suggestion on what needs to be changed to get this working? thanks!
Exception Details: Oracle.DataAccess.Client.OracleException: ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error ORA-06512: at line 1
Stack trace:
[OracleException: ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error
ORA-06512: at line 1]
Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure)
Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src)
Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery()
Microsoft.Practices.EnterpriseLibrary.Data.Database.DoExecuteNonQuery(DBCommandWrapper command)
Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteNonQuery(DBCommandWrapper command, IDbTransaction transaction)
Microsoft.Practices.EnterpriseLibrary.Security.Database.DbProfileProvider.InsertProfile(String userName, Byte[] serializedProfile, Database securityDb, IDbTransaction transaction)
Microsoft.Practices.EnterpriseLibrary.Security.Database.DbProfileProvider.SetProfile(IIdentity identity, Object profile)
[InvalidOperationException: Error saving the profile for the following user 'test'.]
Microsoft.Practices.EnterpriseLibrary.Security.Database.DbProfileProvider.SetProfile(IIdentity identity, Object profile)
EntLibSecuritySample.DFO.Security.SecurityHelper.SetUserProfile(IIdentity identity, Object Profile) in C:\DFO\Sample\Security\EntLibSecuritySample\SecurityHelper.vb:285
[ApplicationException: An error has occurred saving profile object to Datastore. See stack trace for further information]
EntLibSecuritySample.DFO.Security.SecurityHelper.SetUserProfile(IIdentity identity, Object Profile) in C:\DFO\Sample\Security\EntLibSecuritySample\SecurityHelper.vb:287
EntLibSecuritySample.ProfilePage.cmdSaveProfile_Click(Object sender, EventArgs e) in C:\DFO\Sample\Security\EntLibSecuritySample\profile.aspx.vb:59
System.Web.UI.WebControls.Button.OnClick(EventArgs e)
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
System.Web.UI.Page.ProcessRequestMain() +1292

Harsh,
I am not a user of the Enterprise Library so I can not speak to the specifics of that. However, here is a short sample that is based on the information you've provided. Perhaps it will be useful.
Database:
create table profiles
profileid integer not null,
userid    integer not null,
profile   raw(255)
create or replace procedure addprofile
p_profileid in integer,
p_userid    in integer,
p_profile   in raw
as
begin
insert into
    profiles (profileid, userid, profile)
    values (p_profileid, p_userid, p_profile);
end;
/C# code:
using System;
using System.Data;
using System.Text;
using Oracle.DataAccess.Client;
using Oracle.DataAccess.Types;
namespace HarshTest
/// <summary>
/// Summary description for Class1.
/// </summary>
class Class1
    /// <summary>
    /// The main entry point for the application.
    /// </summary>
    [STAThread]
    static void Main(string[] args)
      // connect to local db using o/s authentication
      OracleConnection con = new OracleConnection("User ID=/; Pooling=False");
      con.Open();
      // create command object and set properties
      OracleCommand cmd = new OracleCommand();
      cmd.Connection = con;
      cmd.CommandText = "ADDPROFILE";
      cmd.CommandType = CommandType.StoredProcedure;
      // parameter object for profileid
      OracleParameter p_profileid = new OracleParameter();
      p_profileid.OracleDbType = OracleDbType.Int32;
      p_profileid.Value = 1;
      p_profileid.Direction = ParameterDirection.Input;
      // parameter object for userid
      OracleParameter p_userid = new OracleParameter();
      p_userid.OracleDbType = OracleDbType.Int32;
      p_userid.Value = 1;
      p_userid.Direction = ParameterDirection.Input;
      // create a byte array for the raw value
      ASCIIEncoding encoder = new ASCIIEncoding();
      byte[] byteArray = encoder.GetBytes("TestProfile");
      // parameter object for profile
      OracleParameter p_profile = new OracleParameter();
      p_profile.OracleDbType = OracleDbType.Raw;
      p_profile.Value = byteArray;
      p_profile.Direction = ParameterDirection.Input;
      // add parameters to collection
      cmd.Parameters.Add(p_profileid);
      cmd.Parameters.Add(p_userid);
      cmd.Parameters.Add(p_profile);
      // execute the stored procedure
      try
        cmd.ExecuteNonQuery();
      catch (OracleException ex)
        Console.WriteLine(ex.Message);
      // clean up objects
      p_profile.Dispose();
      p_userid.Dispose();
      p_profileid.Dispose();
      cmd.Dispose();
      con.Dispose();
}Maybe the part about creating the byte array is what you are missing...
- Mark

Fuji raw conversion

Similar Messages

Maybe you are looking for