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

raichea

Members
  • Posts

    18
  • Joined

  • Last visited

Recent Profile Visitors

694 profile views
  1. Fair comment. I hadn't noticed that the support was only in the beta. I should have been more thorough in my research.
  2. I've read this entire thread and have to conclude that Affinity have dropped the ball on the OM-1. Assuming statements made here are correct, and Affinity Photo (AP) does use LibRaw, it is indefensible that OM-1 support is not yet included in AP. There is obviously always a chance that a camera is released a short time before a new version of a software package is released and thus you have to get the new version of the software to get support for the camera. However, a camera that was announced over 6 months ago and available for at least 5 months should have an update to support it by now. There are no excuses.
  3. Thanks for the reply. I understand the reasoning behind the Presets. My question was to ask how the selected settings (eg. Colour space, Bleed) can be changed after the initial creation of the document. I've done some more exploration of the user interface and now figured out that this can be changed in File>Document Setup... What is the Type field in the Spread Properties dialogue for? The presence of this field led me down a blind alley. Although it appears to offer the ability to change these settings, it doesn't actually seem to do anything. Possibly even worse, after you've changed the Colour Space and Bleed in the Document Setup dialogue, the Type field still reflects the selection made when the document was created (ie. it still says Print even if you've changed settings to match Press Ready settings), so could lead to user error.
  4. I have the Affinity Suite (1.9.2.1035) and have some experience with DTP but just beginning to dig in with Publisher. I've run into one issue, though, concerning the Type of document setting. Assume I create a document that is initially intended for publication as a PDF, so I select Print (A4, say) in the New Document dialogue and create the new document. Some time later, I decide that, actually, I'd like to print it so want to change the Type to Press Ready. Having created a document, I find that I'm unable to change the type of spread in the Master pages (eg Print to Press Ready). If I create a document from one of the standard presets (eg Print A4), the Type field in the spread properties only offers Print and Presets but selecting either leaves it at Print. If, instead, I create a "My Preset" of Print A4, and use that for the new document, the Type field in Spread Properties now shows a full list (Print, Press Ready etc) but, again, selecting any of them and clicking OK has no effect on the document. In short, it doesn't seem possible to change the type of document - even though the dialogue appears to offer that option (if you use My Presets). Am I missing something, or is this a restriction that cannot be circumvented?
  5. If load time has to be significant, it would be helpful if the splash screen had some kind of progress indicator while the software is loading. Applications such as Lightroom and CorelDraw have a status line saying things like, "Building GUI" or "Loading palettes" - I just made those up, but you get the idea.
  6. I'm seeing similar start up times on Win7 (64-bit) quad-core i7, 16GB RAM - AP 1.6.1.93
  7. Hmm.. for both drivers, my display show DDI 10.1... which apparently may be how v11 is displayed in Win7. Still confused but I don't get the message so I won't worry about it. Thanks for your help
  8. Thanks for the pointer to the new driver, which I've now installed... I obviously hadn't checked for updates for a while! The DirectX error message doesn't appear now. However, it had stopped appearing with the older driver too, as I mentioned previously. The dxdiag output for the older driver did say DirectX11 was running so why would the message have appeared the first few runs?
  9. Thanks for the reply. Please see the attached dxdiag.txt file. DxDiag.txt
  10. I installed AP today and initially got a message about needing DirectX 10 but that AP had fallen back to some other graphics level. This message appeared the first two or three times I ran the software. I started investigating. My system has quite an old graphics card (NVidia GeForce 310) but according to dxdiag is running DirectX11 although the driver is version 9.18.xx - does this mean I'm actually using DirectX9? While investigating, I restarted the software a few times. Now the program starts without any message. How do I figure out exactly what it is doing or needs wrt graphics hardware? Thanks.
  11. Not a big deal... just a thought. I tried the Preferences setting you mentioned.... I think I prefer the default behaviour. Thanks.
  12. The lock aspect ratio (AR) function works fine if you type numbers into the W: and H: boxes... whichever you change, the other changes to maintain the AR. However, dragging a handle on the object itself does not maintain the AR - pressing Shift does lock the AR as expected. If I've locked the AR, I don't want it to change without my taking a direct action to do so. I think it would make more sense to lock the AR when dragging if the AR lock is set and flip the sense of the Shift key to allow distorted changes. Another entry on the forum describes how the Shift key function operates in this "flipped" mode "natural AR" objects such as bitmaps, so this wouldn't be out of step. Steve
  13. Ah... could be... I did try both Alt keys before finding that Ctrl brought up the measuring guides. <pause> Yes.. that's the problem, Ctrl-Z works fine if AltGr isn't pressed. AltGr didn't seem to cause a problem with a single press, but some combination of AtlGr presses eventually messes up Ctrl-Z undo. Thanks.
×
×
  • 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.