Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: Schewe on May 17, 2013, 03:28:40 am
-
From the horses mouth, Tom has clarified some of the info relating to LR and CC, check out the Lightroom Journal post (http://blogs.adobe.com/lightroomjournal/2013/05/lightroom-and-the-creative-cloud.html).
See, they really don't have subscription on in mind for LR...
-
Georg, better to start a separate thread rather than hijack Jeff's?
-
Georg, better to start a separate thread rather than hijack Jeff's?
Huh? I was asking his and others opinion and perhaps insights on this point concerning CC. Wasn't aware of hijacking a thread.
Mea culpa
Question on pricing difference EU-ÚS
http://www.luminous-landscape.com/forum/index.php?topic=78452.0 (http://www.luminous-landscape.com/forum/index.php?topic=78452.0)
-
Georg, better to start a separate thread rather than hijack Jeff's?
Ok...now I'm confused...ho said what, when?
:~)
-
Ok...now I'm confused...ho said what, when?
:~)
;D I reposted it here:
Was a question on pricing difference US-EU
http://www.luminous-landscape.com/forum/index.php?topic=78452.0 (http://www.luminous-landscape.com/forum/index.php?topic=78452.0)
-
Was a question on pricing difference US-EU
Ah, ok...above my pay grade...(and I agree that regional price differences beyond currency differences sucks when everything is subscription downloads).
-
It's all very well posting "Don't worry it's all going to OK" posts, but the damage to Adobe's reputation has been well and well done now.
I don't think many people will believe that the product managers have the sort of power to dictate how products are sold, they can be over ridden by those higher up in the company.
Adobe's real problem now is how to re-establish trust with it's client base before they loose too many customers. U turns in policy will only further erode trust.
Frankly the best policy right now is to stop making statements no one will believe and get back to designing some products that people really want to buy and are prepared to pay for.
-
Ah, ok...above my pay grade...(and I agree that regional price differences beyond currency differences sucks when everything is subscription downloads).
Thanks Jeff, I was reasonably confident you would share my view on this point.
From an investor's perspective this pricing model is bad for business. The shit storm that is currently happening would have been much reduced by a coherent international pricing model that reflects the economic reality of cloud business / subscription downloads.
-
It's all very well posting "Don't worry it's all going to OK" posts, but the damage to Adobe's reputation has been well and well done now.
I don't think many people will believe that the product managers have the sort of power to dictate how products are sold, they can be over ridden by those higher up in the company.
So, are you calling Tom a liar?
What Tom said was a clarification to let people know that LR is a non subscription product.
-
So, are you calling Tom a liar?
No, I'm just pointing out that if someone above him chooses to make all Adobe products subscription only it'll happen regardless of what he's said.
If the cloud approach generates extra revenue, as it probably will overall, do you really think they'll stick with the current model for other products just because one person posted a comment the previous year ? You're not that dumb Jeff.
-
You can't have it both ways - at one time there was reassurance that CS would continue. Now that turned out to be not true, and people say "well, you can never say 'always', business is business, the world changes, etc etc etc ". Now there is reassurance that LR will continue to be available by licence, you can't claim that it is over-reaction for people to be skeptical.
-
The best plans of mice and men.....
http://www.luminous-landscape.com/forum/index.php?topic=78085.msg630159#msg630159
From your linked Adobe press release announcing CC in Oct. 2011.
"Pricing and Availability
Pricing details regarding Adobe Creative Cloud and its expanded capabilities around applications, services and community will be announced in November 2011. For more information, visit http://www.adobe.com/go/creativecloud. Adobe will continue to offer all its creative products as standalone offerings, including Adobe Creative Suite editions and flagship individual products such as Photoshop, Illustrator, InDesign and Dreamweaver."
-
Was thinking this morning that nobody has yet (to my knowledge), asked, "So, what happens to CC in six months or a year from now if PS/CS
sales subscriptions plummet and someone at Adobe says, "Well, that didn't work."
Mike.
-
As it's already been running for over 12 months and they've had a bigger take up than expected, I doubt that will happen.
-
Was thinking this morning that nobody has yet (to my knowledge), asked, "So, what happens to CC in six months or a year from now if PS/CS sales subscriptions plummet and someone at Adobe says, "Well, that didn't work."
Hi Mike,
A typical reaction, driven by revenue only, would be to raise the price to compensate for the losses ...
And those who have not prepared a plan B. by then can do nothing to prevent it.
Cheers,
Bart
-
Equally typical, in these days, would be to go for volume and drop the price or offer "first 6 months free" deals.
-
Equally typical, in these days, would be to go for volume and drop the price or offer "first 6 months free" deals.
Isn't that exactly what they're doing now ? by offering the first year at a discount rate.
-
From the fact that Adobe felt able to force the move to subscrition it is clear that the revenue came in alright.
What Adobe failed to see was that the many customers who use only a small part of the suite cn still make a lot of noise.
What those customers fail to see is that they bring in only a small part of Adobe'revenue.
Sort of a mexican stand-off
-
Isn't that exactly what they're doing now ? by offering the first year at a discount rate.
Sure, though I'm saying that in the situation we're discussing ("So, what happens to CC in six months or a year from now if PS/CS sales subscriptions plummet and someone at Adobe says, "Well, that didn't work."), I doubt the response will be, as Bart says, to push up the unit revenues. I'm not sure there's much scope to raise prices with weak economies and the rise of app store cheap-but-volume models, and this move to SAAS will also cause them to adopt strategies familiar to services (eg phones, cable and satellite TV, power) such as more of these read-the-small-print introductory offers.
-
Isn't that exactly what they're doing now ? by offering the first year at a discount rate.
Hi,
That would of course be only available for first time subscribers, wouldn't it?
Still scr€wing the users that got Adobe to where they are now ...
Still unknown is what happens when users unsubscribe for a (couple of) month(s),
and re-subscribe only when required, using CS6 for the interim period ...
Cheers,
Bart
-
That would of course be only available for first time subscribers, wouldn't it?
The price shown for Creative Cloud "Single app" (https://creative.adobe.com/plans?plan=single) is $19.99/mo for "annual commitment", $29.99/mo for "Cancel at any time" and $9.99/mo for "Requires CS3+ purchase".
Still scr€wing the users that got Adobe to where they are now ...
Did Adobe get those users to where they are now?
-
The best plans of mice and men...
Let's re-state the obvious - Adobe did continue to offer... blah blah - and do continue to offer... "While Adobe Creative Suite® 6 products will continue to be supported and available for purchase (http://www.adobe.com/aboutadobe/pressroom/pressreleases/201305/050613AdobeAcceleratesShifttotheCloud.html)..."
The recent announcement was that -- "... the company has no plans for future releases of Creative Suite or other CS products".
-
The price shown for Creative Cloud "Single app" (https://creative.adobe.com/plans?plan=single) is $19.99/mo for "annual commitment", $29.99/mo for "Cancel at any time" and $9.99/mo for "Requires CS3+ purchase".
Hi Isaac,
You seem to have some difficulty with the concept of 'future pricing' ("So, what happens to CC in six months or a year from now if PS/CS sales subscriptions plummet") ... Or are you suggesting that the introductory discount is also available for existing customers at a later stage, and the increased pricing will not change in the future? On what authority (or even credibility) would you be prepared to claim that?
Or are you indeed only reacting (without respecting context) to what you perceive as semantic issues (seemingly without grasping them) without adding real information to the thread???
Regurgitating 'Adobe speak' or 'fan-boyish' one-liners, doesn't picture an independent mind, capable of valuing the 'intricate' balance of "Pro's and Con's".
Did Adobe get those users to where they are now?
Since you're asking, NO. Sorry about having to put the emphasis on NO for the slower members, but judging from your (unavoidable, BTW not meant as an encouragement, but apparently/unfortunately a required clarification) earlier posts you seem to be incapable of understanding that in successful interactivity (between supplier and consumer) there is an implied synergetic interaction between both parties, in fact it is usually encouraged by the more clever suppliers.
Now, back on topic of the "Clarifications" ...
Anything remotely meaningful you would like to add for posterity?
Cheers,
Bart
-
Let's re-state the obvious - Adobe did continue to offer... blah blah - and do continue to offer... "While Adobe Creative Suite® 6 products will continue to be supported and available for purchase (http://www.adobe.com/aboutadobe/pressroom/pressreleases/201305/050613AdobeAcceleratesShifttotheCloud.html)..."
The recent announcement was that -- "... the company has no plans for future releases of Creative Suite or other CS products".
I thought the subject of this thread was LR and CC....and Jeff's reference to the LR Journal posting
I cannot comprehend what your post is trying to communicate.
-
You seem to have some difficulty with ...
No :-)
Or are you indeed only reacting (without respecting context) to ...
I'm reacting to your snark and misinformation ;-)
Regurgitating 'Adobe speak' or 'fan-boyish' one-liners, doesn't picture an independent mind, capable of valuing the 'intricate' balance of "Pro's and Con's".
Regurgitating 'anti-Adobe hate-speak' or 'anything but Adobe fan-boyish' one-liners, doesn't picture an independent mind, capable of valuing the 'intricate' balance of "Pro's and Con's".
-
I am currently a user of LR5 and Photoshop CS6. I have read every thread here about CC issues and questions, but I am still not sure about the relationship of Photoshop CC and LR5, and I am also not sure of which tread would be most appropriate to deal with my question, so I am putting it here:
I have been a long-time Photoshop user who recently came to love LR for its non-destructive processing and ease of the Development module, and have also finally begun to manage my images using LR. I am also fond of RAW editing in LR and editing further in Photoshop CS6, and am really comfortable with the ins & outs of this process.
I am considering (reluctantly) getting a single-application subscription to Photoshop CC, and I do understand that LR will continue to be upgraded for some time by Adobe. I cannot afford the full CC subscription just to get LR in the cloud. My concern is this: As Photoshop CC gets new features (and presumably its Camera Raw features change), will I be able to continue to use LR as I have up to now to manage files and do RAW nondestructive edits, then send images to Photoshop CC where I would have access to the new features, and have them come back to LR after editing, just as I do now? Or would the new features in Photoshop CC sort of push me into using Bridge to manage my images because of growing differences between eternal LR and Photoshop CC?
-
Hi walter.sk,
Yes, you will continue to be able to round-trip image editing between Photoshop CC and Lr. Furthermore, image rendering compatibility will be maintained between Camera Raw for Photoshop CC and Lightroom (assuming matching versions) in the same way that we've done in the past.
To make this concrete with examples:
Using a current example, Lightroom 5.0 has image rendering compatibility with Camera Raw 8.1: so, raw files edited in Camera Raw 8.1 (under Ps CC or CS6) will look the same when opened in Lr 5.0, and similarly raw files edited in Lr 5.0 will look the same when edited under Camera Raw 8.1.
Moreover, using standard round-trip editing workflows (e.g., begin adjusting images in Lightroom, use Edit-in-Photoshop or pano-merging or HDR-merging, finish edits in Photoshop, bring back image (as TIFF/PSD) into Lightroom for presentation, export, printing, etc.) will all continue to work.
Going forward, we have every intention of preserving interoperability between ACR, Lr, and Ps.
-
Thanks for the quick reply and the explanation. I guess I'll try the cloud!
Hi walter.sk,
Yes, you will continue to be able to round-trip image editing between Photoshop CC and Lr. Furthermore, image rendering compatibility will be maintained between Camera Raw for Photoshop CC and Lightroom (assuming matching versions) in the same way that we've done in the past.
To make this concrete with examples:
Using a current example, Lightroom 5.0 has image rendering compatibility with Camera Raw 8.1: so, raw files edited in Camera Raw 8.1 (under Ps CC or CS6) will look the same when opened in Lr 5.0, and similarly raw files edited in Lr 5.0 will look the same when edited under Camera Raw 8.1.
Moreover, using standard round-trip editing workflows (e.g., begin adjusting images in Lightroom, use Edit-in-Photoshop or pano-merging or HDR-merging, finish edits in Photoshop, bring back image (as TIFF/PSD) into Lightroom for presentation, export, printing, etc.) will all continue to work.
Going forward, we have every intention of preserving interoperability between ACR, Lr, and Ps.
-
Going forward, we have every intention of preserving interoperability between ACR, Lr, and Ps.
Will tiffs & jpeg LR edited previews reflected in their embedded (instead of sidecar) xmp edits and opened in future updates/upgrades to Photoshop change because of dissimilar Raw engines?
I've been dealing with how this works in LR4 over how it works in Bridge with regard to sidecars and I'm a bit perplexed on how embedded xmp edits to tiffs and jpegs would be handled in a round trip scenario between a newer ACR and older LR raw engine.
Been reading these two threads on how LR deals with LR edited tiffs here and how it stores them to the catalog and/or xmp sidecar...
http://forums.adobe.com/thread/838473
After reading up on this...
http://help.adobe.com/en_US/lightroom/using/WS638E3AC9-A04C-4445-A0D3-F7D8BA5CDE37.html
I'm just bewildered how complicated this has become after recently attempting to migrate out of CS3 Bridge/ACR4.6 into a LR4 workflow and noticing how convolutely different LR deals with these file management driven preview scenarios.
How would CC updates to Photoshop and ACR deal with LR's older Raw engine and how it deals with xmp edits and catalog system? I guess you'ld have to keep upgrading LR to keep up.
I really don't understand what the implications of LR's embedding xmp sidecar edits in tiffs & jpegs presents in future upgrades to Photoshop.
-
Tim,
Don't look for complications where there need not be any. Despite the noise in that thread, Adobe has never given any indication that they have any intention to start creating sidecars for files other than proprietary raw , and I'd suggest they're unlikely to change that view.
Once you are using LR as the hub of your workflow, you need never think about sidecar files. Back up your catalogue and the originals, and you're 100% covered in terms of disaster recovery, and you don't need to have sidecar files to send files to/from Photoshop. When you send files to Photoshop, there's a message if the ACR and LR versions don't match. It gives you the choice to render with LR. Only if the ACR version is more recent than LR might you want to save the sidecar from LR, open in Bridge, update the raw rendering in ACR, then open the file in Photoshop.
John
-
The Australian Government held a Senate enquiry a few months into what is locally called here the, "Australia Tax", imposed by companies such as Adobe, Microsoft, and Apple on both physical and electronic downloads.
This is one of their recommendations released yesterday.
http://www.abc.net.au/news/2013-07-29/geo-blocking-mps-committee-price-report-apple-adobe-microsoft/4850484
-
Tim,
Don't look for complications where there need not be any. Despite the noise in that thread, Adobe has never given any indication that they have any intention to start creating sidecars for files other than proprietary raw , and I'd suggest they're unlikely to change that view.
Once you are using LR as the hub of your workflow, you need never think about sidecar files. Back up your catalogue and the originals, and you're 100% covered in terms of disaster recovery, and you don't need to have sidecar files to send files to/from Photoshop. When you send files to Photoshop, there's a message if the ACR and LR versions don't match. It gives you the choice to render with LR. Only if the ACR version is more recent than LR might you want to save the sidecar from LR, open in Bridge, update the raw rendering in ACR, then open the file in Photoshop.
John
Telling me not to be concerned about sidecars doesn't answer my question, John, but I appreciate your attempts at reassuring me about adopting a completely different preview driven workflow with LR than I have in CS3 Bridge/ACR4.6.
Non-destructive Xmp sidecar edits in CS3 Bridge are applied to all files regardless of format, at least that's how it's working for me. I know it doesn't work that way with LR regarding tiffs, jpegs and PSDs which embeds the sidecar edits inside the file.
What I want to know is what is going on with these file format previews that have this embedded xmp data? An xmp sidecar with a Raw file is just instructions on how to render the preview for Adobe apps that can read it without altering the original Raw data.
Does it work the same when it's embedded in tiffs, jpegs and PSD's in LR?
And as for not looking for complications working with LR it seems quite unavoidable seeing LR4's pdf User's Manual is 205 pages long for what basically is an image preview editor. To do the simplest task of adding one photo to a folder by dragging and dropping in the Finder's OS interface (or doing it in Bridge) won't automatically update and show up in LR's imported folder catalog unless you rummage around within a slew of listed menu options and look for the "Synchronize Folder..." command (now there's intuitive nomenclature for ya') where you're given another dialog box to check and uncheck more options.
Who the hell designed the interface to work this way for this freakin' app?! It certainly wasn't from the POV of a photographer.
-
Yes, Lightroom does often involve changing the way you may have worked - at least if you want to make the most of it. And I'm not sure loose analogies like the PDF's size justify looking for complications in specific areas such as this.
You probably need to investigate the origin of the sidecars you seem to have for the tiffs, jpegs and PSDs. I don't see how they were produced by Adobe software, and while you can force Bridge to create sidecars for DNGs by making the DNG files read-only, that's an exception and Bridge/ACR has always embedded the metadata in those file formats. Maybe, if you can explain how they were created, the question may make more sense?
-
You probably need to investigate the origin of the sidecars you seem to have for the tiffs, jpegs and PSDs. I don't see how they were produced by Adobe software, and while you can force Bridge to create sidecars for DNGs by making the DNG files read-only, that's an exception and Bridge/ACR has always embedded the metadata in those file formats. Maybe, if you can explain how they were created, the question may make more sense?
Your dry, droll and dismissive responses tell me you really don't have an understanding or an answer to what I clearly put forth. I didn't mention DNGs so I have no idea why you brought it up. And who else creates sidecars but Adobe software in both Bridge and Lightroom? It says it in the links I provided.
The only portion of metadata I'm referring to are the edits recorded into (non-destructive) xmp data by both ACR/LR which allow a catalog or sidecar approach to latching it onto the image irregardless of format. Since Adobe Raw converter engines are the only software that can read such sidecar/xmp edit data that alters the original image's preview whether embedded/sidecared/cataloged, it stands to reason Adobe created it and put it there.
For the third time I'll ask it again, when LR embeds sidecar/xmp data EDITS (not IPTC, EXIF, etc.) into tiffs & jpegs, which Raw engine driven adjustments that form the previews does it go by when the engines aren't the same between LR & Photoshop's ACR?
And the very fact I'm having to ask such questions is confirmation of the complexities of the underpinnings of this software and why daisy chaining one or a set of software through a CC subscription that updates in increments but doesn't address OTHER WORKFLOW compatibilities to other NON-CC apps like LR is of major concern.
-
Your dry, droll and dismissive responses tell me you really don't have an understanding or an answer to what I clearly put forth. I didn't mention DNGs so I have no idea why you brought it up. And who else creates sidecars but Adobe software in both Bridge and Lightroom? It says it in the links I provided.
The only portion of metadata I'm referring to are the edits recorded into (non-destructive) xmp data by both ACR/LR which allow a catalog or sidecar approach to latching it onto the image irregardless of format. Since Adobe Raw converter engines are the only software that can read such sidecar/xmp edit data that alters the original image's preview whether embedded/sidecared/cataloged, it stands to reason Adobe created it and put it there.
For the third time I'll ask it again, when LR embeds sidecar/xmp data EDITS (not IPTC, EXIF, etc.) into tiffs & jpegs, which Raw engine driven adjustments that form the previews does it go by when the engines aren't the same between LR & Photoshop's ACR?
And the very fact I'm having to ask such questions is confirmation of the complexities of the underpinnings of this software and why daisy chaining one or a set of software through a CC subscription that updates in increments but doesn't address OTHER WORKFLOW compatibilities to other NON-CC apps like LR is of major concern.
Tim, I think this is pretty simple....and a bigger issue that you are making it to be.
My understanding is that a newer version of Camera Raw (CR), whether ACR or LR, will understand the commands from the older version. Not so the other way around.
Interchangeably using different levels of CR is asking for trouble as you can never be sure if the new command will be just ignored or interpreted as something else.
Your best bet is to either keep the versions in sync or decide to use one or the other.
-
My response certainly indicates I can't make much sense of your problem! If you don't read what I wrote, you'll have no idea why I mentioned read-only DNGs there. And for your information, lots of other programs can create xmp files - Media Pro in its various guises, Capture One, Photomechanic....
Anyway, if the PS/ACR version is more recent than the version of the LR editing instructions in the tif/jpeg, PS will apply those LR instructions when it opens the file. If not, it discards any specific instructions it doesn't understand.
-
As far as I'm aware, ACR/Lr will continue to deal with reading image settings (e.g., in XMP sidecars, embedded XMP metadata, etc.) in the same way as they have for several years: Namely, they will be able to correctly read settings from current and earlier versions, but may not be able to read settings from later versions.
Example: ACR 8.1 can read image settings created from ACR 8.1 and earlier (ACR 8.0, ACR 7.4, ACR 4.5, ACR 3.7, etc.) but not necessarily later versions like 8.2.
For instance, ACR 8.2 introduces a new Color Smoothness slider and a Feather control for spot adjustments. If you use these controls in ACR 8.2 to edit an image and save your settings (click Done in ACR), the settings will be written into XMP metadata. However, if you then try to process the same image in an older ACR version (8.1, 4.5, 2.4, etc.) they won't read those new Spot Feather and Color Smoothness settings correctly, obviously, because those older versions don't support the new controls.
-
As far as I'm aware, ACR/Lr will continue to deal with reading image settings (e.g., in XMP sidecars, embedded XMP metadata, etc.) in the same way as they have for several years: Namely, they will be able to correctly read settings from current and earlier versions, but may not be able to read settings from later versions.
The embedded xmp edits in jpegs/tiffs created in LR will be rendered differently if the ACR plugin version (hog tied to Photoshop) is not the same as LR's, correct?
I take it then the non-destructive xmp edits embedded in jpeg/tiffs don't alter the image's internal pixels, just how the preview is rendered when it appears in Photoshop, upon which, if PS's/ACR Raw engine version is newer with newer settings/features than LR's, it will alter the intended preview.
This connection between the way LR integrates with Photoshop requires both Raw engines/features/settings be on parity with each other which means when you update/upgrade Photoshop now through the CC subscription in the future, LR will have to be upgraded as well or else the user has to turn their non-destructive xmp edits embedded in jpegs/tiffs into finished/altered pixels in the form of a copy>(jpeg/tiff). Correct?
-
The embedded xmp edits in jpegs/tiffs created in LR will be rendered differently if the ACR plugin version (hog tied to Photoshop) is not the same as LR's, correct?
Doh...it's as Eric explained, the most recent version of ACR/LR wins. If your ACR version is behind LR, yes, those features not found in that version of ACR will be ignored. If the most recent version is LR, then you want LR to do the rendering, not ACR. This is the way it's been since the beginning of ACR/LR versioning. Since you are new to this, it's up to you to learn this stuff.
-
Doh...it's as Eric explained, the most recent version of ACR/LR wins. If your ACR version is behind LR, yes, those features not found in that version of ACR will be ignored. If the most recent version is LR, then you want LR to do the rendering, not ACR. This is the way it's been since the beginning of ACR/LR versioning. Since you are new to this, it's up to you to learn this stuff.
My being new to this isn't relevant concerning the fact I'm only mentioning this as part of the "Clarification" relating to this topic of what happens when signing up CC subscription apps (Photoshop) that are closely tied to other workflows using NON-CC subscription apps such as LR that require updates/upgrades that follow different time schedules.
Glossing over with the broad statement that LR will continue to be updated to work with CC Photoshop doesn't add enough clarification on what this means to real world workflow habits for a broad range of LR users new and old who may or may not be aware of all the snags and gotcha's that may arise depending on various ways customers use these apps which are understood to function as "NON-DESTRUCTIVE" image editing apps that are becoming more complicated with each upgrade as they are made to integrate with each other.
The only thing that is most likely to be destroyed with this setup are previews which Adobe software engineers decide when it's parametric or pixel driven depending if the edits are done with a plug-in (ACR) or a standalone (LR) both do the same thing to the image with the customer paying double for it. When the "PREVIEW" is viewed in Photoshop it's deemed a pixel based image whether it came from a plug-in or a standalone parametric editor. One is on a CC subscription update/upgrade timeline and the other isn't. MORE COMPLEXITY!
All the customers are paying for is the improved PREVIEW and don't want complexity (deciding when the image is at a parametric or pixel editing stage) to change these previews because they don't keep two parametric editing apps on the same upgrade/update timeline.
Why does this crap have to be setup so damn complicated when all we want is the preview, the preview...THE PREVIEW!
-
My being new to this isn't relevant concerning the fact I'm only mentioning this as part of the "Clarification" relating to this topic of what happens when signing up CC subscription apps (Photoshop) that are closely tied to other workflows using NON-CC subscription apps such as LR that require updates/upgrades that follow different time schedules.
ACR and LR have and, probably, will be kept in sync....regardless of the release of the actual products.
You may want to note the recent announcement of the release candidates.
You have the choice of upgrading or not. If you do not, you are advised to follow the workflow as Jeff, and others, have suggested.
-
ACR and LR have and, probably, will be kept in sync....regardless of the release of the actual products.
You may want to note the recent announcement of the release candidates.
You have the choice of upgrading or not. If you do not, you are advised to follow the workflow as Jeff, and others, have suggested.
I didn't ask for workflow advise. Just making some clarifications.
How about thoroughly reading what I posted? Now there some advise for ya'.
-
I didn't ask for workflow advise. Just making some clarifications.
How about thoroughly reading what I posted? Now there some advise for ya'.
Thanks...yer sweet :-)
-
How about thoroughly reading what I posted? Now there some advise for ya'.
Funny, I said exactly that to you. ;)
-
...but I bet you spelled "advice" correctly, John.
;)
It always dulls the poignancy of someone's sarky post when they reveal a lack of eduction.
.
-
...but I bet you spelled "advice" correctly, John.
;)
It always dulls the poignancy of someone's sarky post when they reveal a lack of eduction.
.
You really shouldn't disparage Jeff Schewe's online writing style, though he does have editors when writing his books to help him avoid some of the grammar and misspelling yips most our age encounter.
But if this is your only come back you can drum up to my responses here, I'll take my education over yours any day and I didn't even have to go in debt to get it.
Snarky enough for ya'?