When all images selected for batch processing - only one is being processed
Hello to all,
does anyone know why suddenly, when trying to export my RAW files via JPG process recipe which work without any issues up to now, only one image is being processed, no matter if I have all selected? I have tried restart C1, restart PC without any impact on this.
Is the process recipe corrupted or what? Or some bug which occured?
What works is when using "Export" button from the above hadder, but then I have to fill in again all intended - properties, metadata, exif, destination, naming etc and then the process is not seeing in batch process righ down the window.
Well, this is the next bug after another two ones I have encountered after seamless using of 14 months. Seems to me like intentional or delibarate way how to get me off the C1. Upgrading is not the way how to get rid of this I guess. Reinstalling the same. Patience is gone.
Thank you
-
Stanley,
Do you have warning messages turned off?
It sounds like you have the "Edit all selected" toggle option set to Off and you need to change it to On.
If it is not that then you have found something I have never seen.
0 -
SFA,
thank you, probably that was it, but still don´t know why that was turned to "off" without my intervention.
Interesting is, I turned it to on as a first thing and then nothing had happend. After three C1 restarts I switched off HW acceleration, then process reciping worked. Now HW acc is back to on and all works.
Interesting.
Sorry for such an unpleasant end of my topic, but C1 is last time really suprising me.
0 -
Stanley,
There are some settings that are held in dynamic files and are maintained as you make use of the system so that the "latest state" of you settings does not have to be regenerated every tome you open C1.
This is usually recorded for each recently opened catalog or session although sometime may be a Universal setting.
It is just possible that there is something unexpected happening in that area of functionality. I suspect that Windows also loses track of its temporary work files from time to time (they can certainly end up orphaned in the system) and that may, once in a while, result in unexpected connection between a problematic file and a running process.
Multiple setting changes and application restarts sort of hints at something like that.
I would be tempted to take an early opportunity to restart the PC as well. Maybe run the restart 2 or 3 times without firing up any applications (other than those that are automatically started.)
Windows, as far as I can tell, will attempt some "clean up" activity on start up but may get best results, if there are a series of dependent files that need to be cleaned up, by being run more than once.
0 -
That make sence and personally I see it similary. That´s why I am a litlle bit scared of what new Win 10 updates, new GC updates will bring to C1 in terms of connectivity:-;
0 -
I have avoided Win 10 for exactly the same reasons. However I am aware that an 8 years old notebook offers some potential for advancing unreliability perhaps issues about obtaining parts (at a sensible price).
So I decided it was time to investigate the world of Win 10.
One interesting aspect is that my very old but still functioning printer does not work with WIn10 due an apparent lack of driver support. I'm fairly sure that some of the older software I have but rarely use will also not work on Win 10. Hence the idea of replacing the Win7 machine for the bulk of day to day activities before it fails. I need to keep those old options running for a while longer if possible!
So far I have found the Win10 experience acceptable. Some good things. Some that are OK but maybe not especially advantageous except for power users and admins in large corporations. Some that suggest there may be some flakiness not too far under the surface.
We will see ...
0 -
Well,
somehow I have feeling, when taking into an account when C1 was released for the first time, that all this small or bigger bugs (like heal one), that all must tend to a complete overhaul from the scratch. Not only new features are kinds of benefit, but 100% reliability would add more to a Pro concept, as C1 is supposed to be.
Cheers
0 -
Stanley,
The problem with suggesting 100% reliability is that the developers are battling so very many moving targets and outside influences.
Some years ago I worked for a company that developed some niche software for business applications. This was back inthe days when, pre-internet, one had the concept of total control over a release and things were much more stable. But potentially very laborious. Certainly not very "agile" as we understand the and expect in the modern era.
As the owner of the company was very "quality" focussed at a certain point in the products suite's development, with functionality modules maturing and technology bases expanding the decision was made to deliver a new release that accumulated all of the development threads, eliminated any legacy inconsistencies of design or methods, and was tested to be 100% bug free at the time of release.
At great risk to the business cycle cash flow pertaining to existing customers and their upgrade expectations a lengthy gestation period was extended by 6 months of additional testing and a few tricky developments but, finally, a 100% no known bugs product was delivered.
The customers shrugged. It meant nothing to them.
The probable effect on cash flow for upgrades and new business order placement seemed to be significant and the business went into administration. It was run successfully by the administrators until a new owner was found. And then for a further 6 years or so (to my knowledge) while the new owner set about converting the client base to their own similar (but less comprehensive) offering. In the end the new owners moved to a completely different business model and both of the original products and the market they catered for were dropped.
There is often a world of difference between what people claim they want or will do and what they actually want or do.
Delivering 100% can be very expensive (money and time) and not as successful as one might hope and expect. That applies from both supplier and consumer point of view.
0 -
The problem with suggesting 100% reliability is that the developers are battling so very many moving targets and outside influences.
Some years ago I worked for a company that developed some niche software for business applications. This was back inthe days when, pre-internet, one had the concept of total control over a release and things were much more stable. But potentially very laborious. Certainly not very "agile" as we understand the and expect in the modern era.
As the owner of the company was very "quality" focussed at a certain point in the products suite's development, with functionality modules maturing and technology bases expanding the decision was made to deliver a new release that accumulated all of the development threads, eliminated any legacy inconsistencies of design or methods, and was tested to be 100% bug free at the time of release.
At great meilleur crédit to the business cycle cash flow pertaining to existing customers and their upgrade expectations a lengthy gestation period was extended by 6 months of additional testing and a few tricky developments but, finally, a 100% no known bugs product was delivered.
The customers shrugged. It meant nothing to them.
The probable effect on cash flow for upgrades and new business order placement seemed to be significant and the business went into administration. It was run successfully by the administrators until a new owner was found. And then for a further 6 years or so (to my knowledge) while the new owner set about converting the client base to their own similar (but less comprehensive) offering. In the end the new owners moved to a completely different business model and both of the original products and the market they catered for were dropped.
There is often a world of difference between what people claim they want or will do and what they actually want or do.
Delivering 100% can be very expensive (money and time) and not as successful as one might hope and expect. That applies from both supplier and consumer point of view.
Hi, how sure are you that the business owner was very 'quality' oriented?-1
投稿コメントは受け付けていません。
コメント
8件のコメント