Is there a list of acknowledged bugs from PhaseOne?
In the short amount of time I've had with C1 I have encountered many bugs with no fix or way to bypass them.
I opened a case for two of them and support told me they were acknowledged as bugs and sent to the R&D team. Awesome!
Later that day I searched online and found someone on a forum with the same issue as me who said support acknowledged it as a bug too... in January 2016. A bug as been sitting as acknowledged with no fix for 2 years? I don't think I need to tell you that I don't put a lot of hope in the ticket I opened.
Now, C1 is a top tier RAW processor and with high quality usually comes high price. I'm fine with that. But it'd be nice if there was a page to share the tracking of bugs with the userbase or the new features that are coming.
Examples of bugs
I'm torn. I really prefer C1 over LR but the rough start I'm having is pushing me back to LR. Then I look at the images I processed with C1 and I want to go back but then I remember that I can't. Some bugs are too annoying to work with on an daily basis. Another is a showstopper. Then I recall that one my bugs as been acknowledged 2 years ago.
Sorry for venting. ☹️
I opened a case for two of them and support told me they were acknowledged as bugs and sent to the R&D team. Awesome!
Later that day I searched online and found someone on a forum with the same issue as me who said support acknowledged it as a bug too... in January 2016. A bug as been sitting as acknowledged with no fix for 2 years? I don't think I need to tell you that I don't put a lot of hope in the ticket I opened.
Now, C1 is a top tier RAW processor and with high quality usually comes high price. I'm fine with that. But it'd be nice if there was a page to share the tracking of bugs with the userbase or the new features that are coming.
Examples of bugs
- Keywords reappearing after being deleted from keyword library upon application restart. Keyword is not applied to any image in the catalog. This literally prevents me from keywording anything in my library.
C1 does not remember view options such as Filmstrip or Grid mode. You put it on filmstrip mode and it comes back to grid mode. App also does not remember which option groups are expanded or collapsed. Let's say I have a 5 level deep folder structure. I leave a couple ones open that I work on. Upon restarting the application they are all collapsed! Same with the "date" filter. It insists on expanding it so I ended up removing the option from the filter panel.
Application keeps generating thumbnails for images upon application restart (orange pie at the top and photos gradually start appearing in the viewer.) When you have 7,000 photos it takes a while and it's annoying to say the least.
Folder view is not recursive. Not a bug but I've seen that feature request years ago and it's still not there. Super simple to add. Is there really no plan on adding it?
I'm torn. I really prefer C1 over LR but the rough start I'm having is pushing me back to LR. Then I look at the images I processed with C1 and I want to go back but then I remember that I can't. Some bugs are too annoying to work with on an daily basis. Another is a showstopper. Then I recall that one my bugs as been acknowledged 2 years ago.
Sorry for venting. ☹️
0
-
Another bug ghat comes to mind, and that has been around for a long time, is when you are in browser view, and you delete a variant, the selected image after deleting the variant will not be the original image or another variant of the same image, but an image somewhere (it seems at random) in the filmstrip of the active collection. If you are dealing with a large collection, that can be véry inconvenient, having to browse all the way back to the image of which you have just deleted a variant.
In fact, I think I will open a support case for this bug, that has been around for a long while.
Chris0 -
[quote="xplatinum" wrote:
C1 does not remember view options such as Filmstrip or Grid mode. You put it on filmstrip mode and it comes back to grid mode.
Can't replicate this, can't be a bug.. (Selected List mode, closed, opened. still in List mode.. Selected filmstrip, closed, opened. Still in Filmstrip)
Your other problem seem to be catalogue related, I've always used sessions and pointed C1 toward a folder I want to work on..0 -
[quote="xplatinum" wrote:
Application keeps generating thumbnails for images upon application restart (orange pie at the top and photos gradually start appearing in the viewer.) When you have 7,000 photos it takes a while and it's annoying to say the least.
Can't replicate this. This is only if you use Session not not with catalog.
But it is true - Catalog on Windows is after C1 start and click on "all photos" very very long time unusable ☹️ - here 30 Minutes. My catalog has ~45000 pictures0 -
[quote="RobiWan" wrote:
Can't replicate this. This is only if you use Session not not with catalog.
But it is true - Catalog on Windows is after C1 start and click on "all photos" very very long time unusable ☹️ - here 30 Minutes. My catalog has ~45000 pictures
Yes that is correct, I'm experiencing this with a catalog. Is this normal behavior? Why can't the application use the existing thumbnails like it does for previews?!0 -
[quote="xplatinum" wrote:
[quote="RobiWan" wrote:
Is this normal behavior? Why can't the application use the existing thumbnails like it does for previews?!
The first one - its a BUG only under Windows. OSX version don't have this problem.
But the second think - C1 use the old thumbnails and previews. There is no new generation. C1 is scanning "anything" (I can't tell you what).
I send it to P1 about 2 years ago. And they tell me always "we will fix it in the next version" but nothing happens. I think it is so because the primary platform for C1 is OSX.
Now I'm searching how I can switch from C1 catalog to different Software (maybe PhotoSupreme or iMach).
If your installation really generates always new thumbnails then I think your Previews and Thumbnails are corrupt. You can try delete all previews and thumbnails on the disk and start C1 new. Then give them long time to generate all previews and thumbnails.0 -
They really are being regenerated or at least that's what I'm suspecting based on the following image. When I start C1 new .cot files are generated but I don't end up with ~6,200 .cot files so go figure...
https://i.imgur.com/elAV3gS.png0 -
[quote="xplatinum" wrote:
They really are being regenerated or at least that's what I'm suspecting based on the following image. When I start C1 new .cot files are generated but I don't end up with ~6,200 .cot files so go figure...
https://i.imgur.com/elAV3gS.png
I think with your catalog is wrong.
My recommendation would be - close C1 but before close click on "trash" and then close, don't stay on any user collection or "all photos"!, then remove all files from C1 Catalog/Cache directory.
Then you can start C1, then select "verify/ repair catalog or session" and select your opened catalog. After you catalog is repaired, you can click on "all photos". Previews/ Thumbnails generating can be up to 3-4 Sec per Picture!!!. Also really long time0 -
I did what you said but that was not the issue.
I figured it out. C1 only generates thumbnails for images you saw in the viewer/browser. So I held the down arrow and scrolled down all 6,210 images. Now I have 6,210 thumbnail files in \cache\thumbnails.
Nothing resolved but at least I better understand how it works.0 -
To my knowledge, the preview generation bug was introduced in version 10.1
If you join the beta program you might be able to squeeze some insight with the latest build, but I would advise rolling back to the good old (buggy too) 10.0.2 instead. If your camera is supported of course.0 -
[quote="xplatinum" wrote:
I did what you said but that was not the issue.
I figured it out. C1 only generates thumbnails for images you saw in the viewer/browser. So I held the down arrow and scrolled down all 6,210 images. Now I have 6,210 thumbnail files in \cache\thumbnails.
Nothing resolved but at least I better understand how it works.
I have last days some things tested here. I found under Windows same issue, but Phase One Support tell me he can't reproduce this.
The solution I found was export old catalog and import it in a new one. For me works it. But catalog on Windows is much slower then under OSX ☹️
Here a example what happens after I start small catalog with ~1200 pictures0 -
I think that's an inherent property of the SQL database system CO uses.
As you may know SQL databases have amazing organisation properties, but you need seriously beefy hardware to parse tens of thousands of entries in a user-acceptable amount of time.
My rule of thumb for working with a large catalog in anything shy of a high-end workstation, is to never click the "All Images".
(and also to not use Smart Albums after a few thousand images)0 -
But there is a big difference between Win and OSX version. The same operation on the same machine but under OSX El Capitan need 1Sec. And of corse - same catalog and same settings.
Never click the "All Images" is not a option, because without it can C1 not acceptable search at smart albums (under Windows)0 -
[quote="gusferlizi" wrote:
My rule of thumb for working with a large catalog in anything shy of a high-end workstation, is to never click the "All Images".
I have an i7 7700, a Samsung EVO 850 SSD, 16GB of RAM (plenty left) and a GTX 1080 GPU. This setup should breeze through C1.
I will try exporting in a brand new catalog and see what happens.0 -
[quote="xplatinum" wrote:
How can Support not acknowledge this if there's more than 1 client with the same issue?
There is a big difference -
1. my and your issue (you wrote) was - really generating on each start Thumbnails for all/most or some Images. This exist if catalog is corrupt but C1 can't see who and why (I can't tell you how this happens)
- After export into a new catalog and generating all Thumbnails and Previews I can no more reproduce this
BUT
the problem with the orange bar is still here and Phase One has confirmed that they have it too!!!
I have done today some tests and I mean C1 is always searching and if possible reading metadata (XMP) files although it should not do that (XMP Sync is off)
Phase One promised me to work on the problem. I hope they will do it now and quickly find the cause and a solution.
In other case I will switch to LR or if it really should work PhotoSupreme as DAM and C1 use only in Session mode.0 -
Good to know that the orange progress circle has been acknowledged. It's really annoying.
Thanks for your feedback.0 -
Well I watched the other video now.
I know that 10.1.x or higher, introduced a preview regeneration thing for catalogs (does not seem to happen in sessions).
When I open a catalog from 10.0.2 in anything newer, it will start regenerating previews, and does take longer than on 10.0.2 to generate. Since I haven't had the cojones to wait for that, perhaps I haven't encountered that massive amount of time to load the orange pie.
In 10.0.2 I get a couple minutes at most to parse 18K images, indexed in a WD Black hard drive.
My database comment was partly intrinsic and partly sarcastic, alluding to the enterprise server 50 core multi gpu $10k hardware that is implied to give you vast improvement in performance.0 -
[quote="xplatinum" wrote:
[quote="gusferlizi" wrote:
My rule of thumb for working with a large catalog in anything shy of a high-end workstation, is to never click the "All Images".
I have an i7 7700, a Samsung EVO 850 SSD, 16GB of RAM (plenty left) and a GTX 1080 GPU. This setup should breeze through C1.
I will try exporting in a brand new catalog and see what happens.
I couldn't agree more.0 -
[quote="xplatinum" wrote:
Good to know that the orange progress circle has been acknowledged. It's really annoying.
Thanks for your feedback.
Uninstalled 10.2.1 and installed 10.0.2 and the orange pie is indeed still there. I'm not gonna try other major versions but I'm starting to wonder if this as always been present.
Only other application I've tried is LR and I have never seen anything like this. So what's the problem? Why can't C1 load whatever's already cached? Why does it absolutely have to go through so many images on every startup? It puzzles me.
Always thought LR (pre 7.0) was slow but god damn, this is ridiculous.0
Post is closed for comments.
Comments
19 comments