Why bother using capture one 7 pro
I'm just curios why you still prefer to use capture one 7 pro than acr/lr when capture one 7 pro gots lots of problems, such as instability, constant crashing/hanging, very slow to preview the Raw files or zooming in/out, tethered shooting crashes, cannot import images in a cf card attached inside dslr(d800 & d4), moire removal is horrible, you get black images on the browser, dynamic ranger slider isn't really that better than other competitors software. Lack of third party plug in such ad vsco and proper integration of nik softwares. So far my experience using capture one 7 pro are all inconviences. Using the catalog system is pain in the ass, because during importation of raw files into catalog it always crashes, very very slow to browse/view the images. Organising the images is worst/slow unlike in acr/Lr it's very easy to organise the files.
. I find using this software makes my workflow very slow because of the factors that I mentioned above.
Well the only thing good with capture one 7 pro is local Hsl and capture pilot(if it work properly)... Which all of us will probably prefer photoshop to handle those local Hsl, since its more intuitive and accurate than capture one 7 pro.
. I find using this software makes my workflow very slow because of the factors that I mentioned above.
Well the only thing good with capture one 7 pro is local Hsl and capture pilot(if it work properly)... Which all of us will probably prefer photoshop to handle those local Hsl, since its more intuitive and accurate than capture one 7 pro.
0
-
One of the main reasons I bought the paid version was to use Capture Pilot with my D300 as the DB version of C1 is all I need for my old H25. Seems I wasted my money as my D300 is not supported ☹️ although I'm sure it used to be ???????? but can't get a straight answer from support!
From what I'm reading here it seems C1-7 should come with a roll of sticky tape, some blue tack and a packet of safety pins for all the workrounds & fixes!!0 -
[quote="Saul G" wrote:
One of the main reasons I bought the paid version was to use Capture Pilot with my D300 as the DB version of C1 is all I need for my old H25. Seems I wasted my money as my D300 is not supported ☹️ although I'm sure it used to be ???????? but can't get a straight answer from support!
From what I'm reading here it seems C1-7 should come with a roll of sticky tape, some blue tack and a packet of safety pins for all the workrounds & fixes!!
It states clear under supported cameras that the D300 is not supported for tether in Capture One 7. Phase One didn't give you a straight answer because I did in this thread: viewtopic.php?f=46&t=14112
Support was kind enough to offer a workaround that isn't officially supported as well. There are reports of it working for some people though without the workaround, have you gone and made sure Canon is unchecked in Capture One Preferences > Capture > Providers before you connect your D300?
And to the OP: it sounds like you are having a lot of system related errors, have you created a support case with Phase One to get help with your issues and have an official response given to you on why plugins are not supported
(maybe you could ask VSCO to make some Capture One Styles of their popular styles) and why you think third party software is not properly integrated?
It's super easy if you haven't! http://www.phaseone.com/en/SupportMain.aspx 😲0 -
[quote="rave81" wrote:
I'm just curios why you still prefer to use capture one 7 pro than acr/lr when capture one 7 pro gots lots of problems, such as instability, constant crashing/hanging, very slow to preview the Raw files or zooming in/out, tethered shooting crashes, cannot import images in a cf card attached inside dslr(d800 & d4), moire removal is horrible, you get black images on the browser, dynamic ranger slider isn't really that better than other competitors software. Lack of third party plug in such ad vsco and proper integration of nik softwares. So far my experience using capture one 7 pro are all inconviences. Using the catalog system is pain in the ass, because during importation of raw files into catalog it always crashes, very very slow to browse/view the images. Organising the images is worst/slow unlike in acr/Lr it's very easy to organise the files.
. I find using this software makes my workflow very slow because of the factors that I mentioned above.
Well the only thing good with capture one 7 pro is local Hsl and capture pilot(if it work properly)... Which all of us will probably prefer photoshop to handle those local Hsl, since its more intuitive and accurate than capture one 7 pro.[quote="rave81" wrote:
I'm just curios why you still prefer to use capture one 7 pro than acr/lr when capture one 7 pro gots lots of problems, such as instability, constant crashing/hanging, very slow to preview the Raw files or zooming in/out, tethered shooting crashes, cannot import images in a cf card attached inside dslr(d800 & d4), moire removal is horrible, you get black images on the browser, dynamic ranger slider isn't really that better than other competitors software. Lack of third party plug in such ad vsco and proper integration of nik softwares. So far my experience using capture one 7 pro are all inconviences. Using the catalog system is pain in the ass, because during importation of raw files into catalog it always crashes, very very slow to browse/view the images. Organising the images is worst/slow unlike in acr/Lr it's very easy to organise the files.
. I find using this software makes my workflow very slow because of the factors that I mentioned above.
Well the only thing good with capture one 7 pro is local Hsl and capture pilot(if it work properly)... Which all of us will probably prefer photoshop to handle those local Hsl, since its more intuitive and accurate than capture one 7 pro.
I logged several support cases to them but their response is not helpful, I've complaint to them several times about the slowness of previewing images, and most of the time under the browsers the small thumblines appears blank. "Their response We'll get back to you" That been almost a month now. I managed to resolve the blank thumblines, by unistalling it and reinstalling co 7 pro again However I have to do this in several times. C07 Pro always crashes every day, since it 1st version of co 7 pro was release, they said they will fix the problem, however until now they have not fix the problem. Lastly my complaints to them was something to do with exporting several images to ps for panoramic stitching, their response, well we have to update it soon, because it is only compatible with cs3,cs4 and cs5, which is unacceptable, since before they developed Co7 pro, CS6 has been out for several months....
I experience those problems constantly, which is pretty annoying and drastically slow my workflow.0 -
[quote="rave81" wrote:
[quote="rave81" wrote:
I'm just curios why you still prefer to use capture one 7 pro than acr/lr when capture one 7 pro gots lots of problems, such as instability, constant crashing/hanging, very slow to preview the Raw files or zooming in/out, tethered shooting crashes, cannot import images in a cf card attached inside dslr(d800 & d4), moire removal is horrible, you get black images on the browser, dynamic ranger slider isn't really that better than other competitors software. Lack of third party plug in such ad vsco and proper integration of nik softwares. So far my experience using capture one 7 pro are all inconviences. Using the catalog system is pain in the ass, because during importation of raw files into catalog it always crashes, very very slow to browse/view the images. Organising the images is worst/slow unlike in acr/Lr it's very easy to organise the files.
. I find using this software makes my workflow very slow because of the factors that I mentioned above.
Well the only thing good with capture one 7 pro is local Hsl and capture pilot(if it work properly)... Which all of us will probably prefer photoshop to handle those local Hsl, since its more intuitive and accurate than capture one 7 pro.[quote="rave81" wrote:
I'm just curios why you still prefer to use capture one 7 pro than acr/lr when capture one 7 pro gots lots of problems, such as instability, constant crashing/hanging, very slow to preview the Raw files or zooming in/out, tethered shooting crashes, cannot import images in a cf card attached inside dslr(d800 & d4), moire removal is horrible, you get black images on the browser, dynamic ranger slider isn't really that better than other competitors software. Lack of third party plug in such ad vsco and proper integration of nik softwares. So far my experience using capture one 7 pro are all inconviences. Using the catalog system is pain in the ass, because during importation of raw files into catalog it always crashes, very very slow to browse/view the images. Organising the images is worst/slow unlike in acr/Lr it's very easy to organise the files.
. I find using this software makes my workflow very slow because of the factors that I mentioned above.
Well the only thing good with capture one 7 pro is local Hsl and capture pilot(if it work properly)... Which all of us will probably prefer photoshop to handle those local Hsl, since its more intuitive and accurate than capture one 7 pro.
I logged several support cases to them but their response is not helpful, I've complaint to them several times about the slowness of previewing images, and most of the time under the browsers the small thumblines appears blank. "Their response We'll get back to you" That been almost a month now. I managed to resolve the blank thumblines, by unistalling it and reinstalling co 7 pro again However I have to do this in several times. C07 Pro always crashes every day, since it 1st version of co 7 pro was release, they said they will fix the problem, however until now they have not fix the problem. Lastly my complaints to them was something to do with exporting several images to ps for panoramic stitching, their response, well we have to update it soon, because it is only compatible with cs3,cs4 and cs5, which is unacceptable, since before they developed Co7 pro, CS6 has been out for several months....
I experience those problems constantly, which is pretty annoying and drastically slow my workflow.
Have you tried CO 7.1? If not, give it a spin. There's a lot of fixes in it.
http://www.phaseone.com/en/Downloads/Ca ... Pro-7.aspx0 -
[quote="Christian Gr" wrote:
[quote="rave81" wrote:
[quote="rave81" wrote:
I'm just curios why you still prefer to use capture one 7 pro than acr/lr when capture one 7 pro gots lots of problems, such as instability, constant crashing/hanging, very slow to preview the Raw files or zooming in/out, tethered shooting crashes, cannot import images in a cf card attached inside dslr(d800 & d4), moire removal is horrible, you get black images on the browser, dynamic ranger slider isn't really that better than other competitors software. Lack of third party plug in such ad vsco and proper integration of nik softwares. So far my experience using capture one 7 pro are all inconviences. Using the catalog system is pain in the ass, because during importation of raw files into catalog it always crashes, very very slow to browse/view the images. Organising the images is worst/slow unlike in acr/Lr it's very easy to organise the files.
. I find using this software makes my workflow very slow because of the factors that I mentioned above.
Well the only thing good with capture one 7 pro is local Hsl and capture pilot(if it work properly)... Which all of us will probably prefer photoshop to handle those local Hsl, since its more intuitive and accurate than capture one 7 pro.[quote="rave81" wrote:
I'm just curios why you still prefer to use capture one 7 pro than acr/lr when capture one 7 pro gots lots of problems, such as instability, constant crashing/hanging, very slow to preview the Raw files or zooming in/out, tethered shooting crashes, cannot import images in a cf card attached inside dslr(d800 & d4), moire removal is horrible, you get black images on the browser, dynamic ranger slider isn't really that better than other competitors software. Lack of third party plug in such ad vsco and proper integration of nik softwares. So far my experience using capture one 7 pro are all inconviences. Using the catalog system is pain in the ass, because during importation of raw files into catalog it always crashes, very very slow to browse/view the images. Organising the images is worst/slow unlike in acr/Lr it's very easy to organise the files.
. I find using this software makes my workflow very slow because of the factors that I mentioned above.
Well the only thing good with capture one 7 pro is local Hsl and capture pilot(if it work properly)... Which all of us will probably prefer photoshop to handle those local Hsl, since its more intuitive and accurate than capture one 7 pro.
I logged several support cases to them but their response is not helpful, I've complaint to them several times about the slowness of previewing images, and most of the time under the browsers the small thumblines appears blank. "Their response We'll get back to you" That been almost a month now. I managed to resolve the blank thumblines, by unistalling it and reinstalling co 7 pro again However I have to do this in several times. C07 Pro always crashes every day, since it 1st version of co 7 pro was release, they said they will fix the problem, however until now they have not fix the problem. Lastly my complaints to them was something to do with exporting several images to ps for panoramic stitching, their response, well we have to update it soon, because it is only compatible with cs3,cs4 and cs5, which is unacceptable, since before they developed Co7 pro, CS6 has been out for several months....
I experience those problems constantly, which is pretty annoying and drastically slow my workflow.
Have you tried CO 7.1? If not, give it a spin. There's a lot of fixes in it.
http://www.phaseone.com/en/Downloads/Ca ... Pro-7.aspx
I've freshly installed the CO 7.1 last night, there is not improvement at all... I still get the blank thumbnails, zooming in/out is much slower to properly view the image, it took between 8-10 secs, compared to 3-5 secs in 7.0.2. I also encountered incomplete importation of all images, I have 64,555 raw files. It only imported 7544 in the new catalog, however when I use sessions I could access the whole 64,555 raw images. I did not fix the issue of importing images from CF card attached inside of the camera, which I mentioned above.
I also noticed that C0 7.1 uses 98% of my RAM, which is 32GB...0 -
Hello everyone,
Just wanted to throw in a quick comment:
I totally have to agree with most of the statements made here. Except image preview being slow. On my Mid2010 MacBock Pro LR is unbearable slow with previews (D800 files are a real pain); BUT in CO they come up quickly and adjustment are show almost instantly.
For me CO really gives very inconsistent user experience. I am not sure why that is, taking into account the very limited array of hardware (Macs).
Greetings,
CT0 -
I use it because it is the best RAW converter you can get. I have always used LR next to C1 mostly for cases where C1 didn't support some cameras or lens correction and although LR4 is a really good RAW engine, it still has the odd horrible problems that I never encounter with C1. Furthermore, although the highlight & shadow recovery in LR4 is exceptionally good, it will often overdo it and you get some ugly noise. Something I haven't seen in C1.
On the other hand I fully agree that C1 is horrible buggy. I just remember when the first C1 v4 came out (after waiting like more than two years) and what horrible, almost useless crap it was. But it improved and C1 v6 was very stable and good. Now v7 seems to be a new bag of cats and the first version was bad, I had a lot of issues with it too (eg the thumbnails not rendering, etc), but it got better with 7.0.2. I still think the catalogue thing is something that is just a nice add on but completely useless. It should be like the LR4 catalogue (or like LR catalogue always was). I don't trust C1 catalogue and I just tried it on and off, but I see no real reason to use it at the moment (also see the bloat issue wheres LR catalogue pretty much is controllable small). Unless you have a tree of keywords, show all data from a parent folder (so all subfolders in there are shown) and it actually works I don't have issues with importing things several times and it never works, I really do not trust it. Plus it needs to maps module.
Yeah C1 is not perfect, but when it comes to quality of the output, it beats everything I have tried. That is why I use it and will continue using it. (remark, if you have Reid Review site subscription, just look into his recent comparison of X-trans sensor files in LR 4.3 and C1 7.0.2, I hope he makes an update soon as LR 4.4 has somewhat better X-trans support.)0 -
I use Capture One 7 Pro because, from my perspective, it produces the absolutely best output from RAW files. I shoot portraits with a Canon and now a X-Pro1, so skin tones are especially critical to me. Lightroom is easier and I spent a lot of time trying to get the same results using it, but I was never satisfied. I cannot easily define the difference, but the capture one results look more real, or maybe more film like. So, I put up with the occasional CO problems in order to get the results that I want. I use a session for each project rather than the catalog because sessions still seem far more stable. So far I'm also very pleased with the performance of 7.1, even thought I'm on an older macbook pro and my images are on a relatively slow external drive. I'm sorry you are not having the same experience. 0 -
[quote="gullevek" wrote:
I use it because it is the best RAW converter you can get. I have always used LR next to C1 mostly for cases where C1 didn't support some cameras or lens correction and although LR4 is a really good RAW engine, it still has the odd horrible problems that I never encounter with C1. Furthermore, although the highlight & shadow recovery in LR4 is exceptionally good, it will often overdo it and you get some ugly noise. Something I haven't seen in C1.
On the other hand I fully agree that C1 is horrible buggy. I just remember when the first C1 v4 came out (after waiting like more than two years) and what horrible, almost useless crap it was. But it improved and C1 v6 was very stable and good. Now v7 seems to be a new bag of cats and the first version was bad, I had a lot of issues with it too (eg the thumbnails not rendering, etc), but it got better with 7.0.2. I still think the catalogue thing is something that is just a nice add on but completely useless. It should be like the LR4 catalogue (or like LR catalogue always was). I don't trust C1 catalogue and I just tried it on and off, but I see no real reason to use it at the moment (also see the bloat issue wheres LR catalogue pretty much is controllable small). Unless you have a tree of keywords, show all data from a parent folder (so all subfolders in there are shown) and it actually works I don't have issues with importing things several times and it never works, I really do not trust it. Plus it needs to maps module.
Yeah C1 is not perfect, but when it comes to quality of the output, it beats everything I have tried. That is why I use it and will continue using it. (remark, if you have Reid Review site subscription, just look into his recent comparison of X-trans sensor files in LR 4.3 and C1 7.0.2, I hope he makes an update soon as LR 4.4 has somewhat better X-trans support.)
I try to use it because I like the processing engine and the intuitive way you can control the image.
That is: I would like to try it. But I can't. I can't get my images into a catalog, and what is not in a catalog can't be processed.
I have no other problems on my new system. I have one small catalog of 800 images of recent shoots. And even those few images are too much. When I go to folders, they aren't even arranged. They are topsy-turvy.
I have the impression that the image processing engine has been designed by great guys, and the catalog section by a horde of monkeys or devils, or both.
My question is: why did Phase One take away the file browser? If I had that, I could show the catalog a series of dirty hand gestures and continue working. All my folders have date and project name in its file name, and I can find things quickly.
It's good to hear that older versions of C1 were total junk, and they dug their way out of it.
I'm not sure how I will achieve it to use C1 7 when I can't get a catalog together... maybe magic or satanic rituals? Would this help?0 -
[quote="Hegel 59" wrote:
I try to use it because I like the processing engine and the intuitive way you can control the image.
That is: I would like to try it. But I can't. I can't get my images into a catalog, and what is not in a catalog can't be processed.
I have no other problems on my new system. I have one small catalog of 800 images of recent shoots. And even those few images are too much. When I go to folders, they aren't even arranged. They are topsy-turvy.
I have the impression that the image processing engine has been designed by great guys, and the catalog section by a horde of monkeys or devils, or both.
My question is: why did Phase One take away the file browser? If I had that, I could show the catalog a series of dirty hand gestures and continue working. All my folders have date and project name in its file name, and I can find things quickly.
It's good to hear that older versions of C1 were total junk, and they dug their way out of it.
I'm not sure how I will achieve it to use C1 7 when I can't get a catalog together... maybe magic or satanic rituals? Would this help?
There still is a file browser. You just have to be in session mode. This is how I currently use C1.0 -
I started to use C1 because I thought that Apple had given up on Aperture. There had not been a lot of updates since 3.x so I figured they were going to abandon it like they have several other Pro products.
I started with C1 around V5 and have stuck with it and am now a 7.1. I like the local adjustments and I think the raw processor is excellent. Also Aperture does not support my Mamiya 645 digital back.
However C1 is a hard program to use when you need to update and add to the Metadata. Aperture has a HUD where you can add keywords and they are across all projects and imports etc. You just select and drag them. You can rename then also.
I just wrote a support case about the fact you can not change the case of a keyword and some of the other Metadata fields. If you enter Nature and you want to change it to nature there is no way to do this. There are other major problems with the type-a-head methods.
Working on a major book where the client wanted to go through the photos and select them I had to Import them into Aperture so I could keyword them and add descriptions. When I open Aperture to import the images and add descriptions and keywords it was so simple and it was like reuniting with an old friend. I import the files into Aperture as referenced files so I can go back and process them in C1 if I want to.
Anyway PhaseOne needs to do something with the Metadata so you can change the case of a description and keyword and get away from this copy and pasting of keywords and data from one file to another.
I wasted my money on MediaOne but that is water under the bridge and I guess, look hard before you leap.0 -
The preview load becomes really "WARPY", if you decrease the size of the previews in the preferences sections from 2560 to 1280 - 1440.
Decreasing the size - regarding 35mm previews - to 1280 will speed up the loading process tremendously because this is around the size the previews are stored within NEF/CR2 files by camera default and they have just to be extracted from the raw-file,
Using a larger size than the ones that are stored within the mentioned RAW files by default causes every system to additional "heavy workload" because the amount has to doubled!
The reason AFAIK is that the size of 2560 in COne is the size of embedded previews stored within the MF files - remember that COne is primarily the renderer for POne MF camera systems.
Do some trials to elaborate the "best size" if you do not know at which size the previews are stored inside the raw file. The generic size of the previews can e.g be checked in MP within the EXIF section of the regarding type of raw.
saludos redondos -
tom0 -
[quote="Thomas248" wrote:
The preview load becomes really "WARPY", if you decrease the size of the previews in the preferences sections from 2560 to 1280 - 1440.
Decreasing the size - regarding 35mm previews - to 1280 will speed up the loading process tremendously because this is around the size the previews are stored within NEF/CR2 files by camera default and they have just to be extracted from the raw-file,
Using a larger size than the ones that are stored within the mentioned RAW files by default causes every system to additional "heavy workload" because the amount has to doubled!
The reason AFAIK is that the size of 2560 in COne is the size of embedded previews stored within the MF files - remember that COne is primarily the renderer for POne MF camera systems.
Do some trials to elaborate the "best size" if you do not know at which size the previews are stored inside the raw file. The generic size of the previews can e.g be checked in MP within the EXIF section of the regarding type of raw.
saludos redondos -
tom
Regarding previewsize, just to clear things up:
- If your screen resolution is very high, use high resolution previews
- If low, use low res previews
- The value indicate the longest side of a picture
- The default size of 2560 px is primarily to accommodate large displays (such as the Retina macs, 27" dells, and so on)
- I.e. if your screen is 1920 on the longest side, try setting the size 1 step lower than this value (unless you are using full screen a lot, then match the value)
- Nothing is stored inside the raw-file. CO will never write to the raw-file.
- Previews are generated from the full res raw.
- Preview can be regenerated from the "File" menu. A restart of CO is required after regeneration.
- Do not use very small preview sizes on a high res screen. This can lead to poor performance as well.0 -
I use it because the files look WAY better than what LR 4 can do. I know LR intimately, since its beta days and its quality for Nikon files (what I mostly shoot) has improved drastically. Still it's no match to C1, especially with skin tones.
I know all the LR profiles, I have built my own - never would it hold a candle against what I get from C1 out of the box.
Now with also owning and loving an Olympus OM-D it's even more pronounced. LR's version of the OM-D files look plain horrible! C1's are so much better.
Actually C1 v7.x works pretty well for me on a Mid 2010 Mac Pro with 16 GB RAM and an SSD. I am more plagued with LR's current sluggishness problems.0 -
[quote="Christian Gr" wrote:
- Nothing is stored inside the raw-file. CO will never write to the raw-file.
- Previews are generated from the full res raw.
Hi Christian,
never mentioned or assumed that COne writes previews to raw files - for sure the previews used in COne are stored in the .cop files. How else can changes after editing can be seen in the browser...
saludos redondos -
tom0
Post is closed for comments.
Comments
15 comments