Jump to content
You must now use your email address to sign in [click for more info] ×

william7

Members
  • Posts

    195
  • Joined

  • Last visited

Posts posted by william7

  1. My knowledge about this is limited. As I understand the issue, a single processor can handle all the operations, which might include recording user input, performing calculations to accomplish tasks, send and receive  data from GPUs, write to memory, etc. That single core can only perform 1 operation per clock cycle. If the stream of tasks can be separated, and performed on another core, each core will perform a sub task at the same speed as the primary. 

     

    An analogy. In a kitchen, the chef receives the order, and hands off the different portions to dedicated cooks. Then inspects the results, and instructs the server to deliver. The chef could do it all, but for some meals, it would be very hard to have everything ready at once.

    Thanks for the explanation, but I already knew that :P (I am a computer engineer). Maybe my question wasnt clear enough. How many threads can affinity run in parallel? are there enough for 8 or 12 core machines? More? at what point does affinity cease to benefit from more cores?

  2. Edit: This article explains a lot of the problems I'm having with RAW files: http://loewald.com/blog/2015/07/affinity-photo-no-good-for-photography/

     

    Im curious about the devs thoughts on this, I currently use my iphone as my camera and thus do not currently shoot in raw although with ios 10 I will, and in a year or so will be buying my first dslr which I will also shoot in raw. This article is pretty scathing of the raw engine in AP, are there planned improvements for it? why is it that even with noise reduction all the way the image is still noisier than the apple raw engine? if I select the apple raw engine will apples noise reduction be applied or no?

     

    I want to clarify that I love AP and want to see it succeed thus my concern for this. If this is a problem I would love to see steps taken to correct it. Thanks guys.

  3. After I finish editing my photo in AP in the photo persona I switch to export to export it however when I do the photo loses some detail. Switching back to the photo persona brings it back, I am assuming that this has something to do with my default export option (jpg High) but even when I switch to highest or Tiff 16bit I can't seem to get the detail back? How can I export with all the detail exactly as it appears in photo persona?

  4.  

     

    First off, I have seen the posts confirming that the affinity team will be working on a DAM which excites me very much! (can I pre-order?  ;)) anyways I'm assuming that the project is in the early stages if started at all, but I wanted to ask for these now so that they could be considered in the core of the design. My requests are founded on my reading of this article: http://www.cambridge...hoto-backup.htm

     

    Things I would like to see specifically in the Affinity DAM (and which I think are a must for a truly PRO DAM):

    • Strong Compatibility with different file types and the ability to convert between them losslessly (is that a word?) as different formats eventually go extinct
    • Support for creating and tracking multiple copies of the library for redundancy purposes - Ideally I'd like to have multiple external hard drives with no special connection like raid and put copies on each
    • The ability to split a library across multiple storage pieces (ie split a 300 gb library accross 50 gb blu ray discs and then the merging of the library back to one volume)
    • Strong Checksum Support for error detection
    • Parity/Recovery Files to recover from an error (and in extreme cases this is where redundancy matters most)
    • Finally a way to access the files in case ( I hope it never happens ) Affinity goes away.

    Thanks! 

     

    This is the first post from a thread I started months ago, that noone responded to so im reposting it here. As I look back at it the other thing I would add as part of the data recovery is the built in ability to use backups to fix errors in the main copy and to use them as a form of error checking.

     

    As someone who currently works on NAND flash the idea that no major software platforms are performing bit checks on my data scares the crap out of me. in NAND flash (which is used in all SSDs today) bits will be wrong on almost every single write, there is hardware error correction which makes up for it but I want another check in the software level because if there is an error with the write (one that ECC cant fix) you wont know until you try to read it later however if you catch it while the data is still in ram you can rewrite it.

     

    Edit: link to original thread in the off chance anyone cares: https://forum.affinity.serif.com/index.php?/topic/14942-dam-features/

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.