90% of Custom Presets still not recognized/won't load!

[stefanhodgden]

I gave this a shot and hoped fro the best but it is still failing and I don't now why.

Why would some .lrtemplate preset's configure and other's not? If you look at the scroll bar, you can see that sorted by date and time of presets that have been correctly adjusted. The other's have not. Why would adobe release this kind of update in a 0.0.1 fashion if it's not going to work? I have presets that I have custom made that I use everyday that I can't use. I guess I'm going to have to downgrade AGAIN!

Please address this issue. We're all paying for this and we're not offered a standalone anymore.

Yes The larger tone curve box, main window preset preview, dehaze, and profiles are a huge thing but why couldn't they put this in a standalone?

[JohanElzenga]

If these presets were custom made, then I suggest you contact the author. He/she will have to take a look at them, and check why conversion to xmp does not work. If he/she wants to remain in this business, that is.

[stefanhodgden]

I made them

[JohanElzenga]

So did you do anything special? Like including a special camera profile, or editing the preset with a text editor?

[stefanhodgden]

I don't think you're going to fix what the entire Adobe team hasn't fixed by narrowing down through me; my issues. This is Adobe's bug and as a customer, they should have ran through benchmarks on their own. Not make us expose the problems one by one. Have you spent time debugging it? If you're a part of the Adobe team, I don't understand why we are facing this issue. It shouldn't matter what I've done or what other preset suppliers have done prior to the errors, it need's to be fixed from within Adobe, not on the endusers time, or unless Adobe want's to keep THIER jobs.

To answer your question, No, I only used what Camera Raw profiles were already there and I did not use a text editor for anything.

[Bob Somrak]

Post a couple of the presets on Dropbox so others can see if they will load.

[stefanhodgden]

Presets

[Ian Lyons]

Your presets converted to XMP without issue on my Mac OS system.

Some customers have reported that one of the causes for failure is the folders containing the original 'lrtemplate' and the folder to which the converted XMP preset is to be stored in need to have their permissions updated. I've not found this to be the case myself but still worth checking.

[Joe Foe Toe]

They loaded fine to custom presets on my Win10 system.

[JohanElzenga]

I just noticed they seem to have a colon in their name. I think I remember that somebody reported a problem with certain characters in the name of the preset, or the folder.

[Bob Somrak]

There was a problem with some characters.on 7.3 but it is supposedly fixed in 7.3.1.  Coming from old DOS days I avoid any special characters in file names to avoid such problems.  They might work on one system/program and break on another.  See here for info

Lightroom Classic CC 7.3 not converting all the develop presets (.lrtemplate) to XMP

[stefanhodgden]

It's still not working after the update. That's why I'm posting this.

[Bob Somrak]

Take the colon out of one of the names and see if it loads.

[Rob_Cullen]

https://forums.adobe.com/people/Bob+Somrak  wrote

Take the colon out of one of the names and see if it loads.

And I suggest also the forward slashes [ / ].

[stefanhodgden]

I'm still not happy. Nobody should have to do anything to fix their presets. I have thousands of presets that are categorized.

If I have to text edit every single one that will take me over a month and times wasted I could be spending with my family.

[JohanElzenga]

Try it with one first. If that works, it should probably be possible to fix this with a text editor that can do it in batch.

[stefanhodgden]

If you have a video on how to do this  it would help/

[JohanElzenga]

No, I don’t have a video. It should not be too difficult to find a text editor that can batch edit text files, and then read the manual on how to do that.

[Rob_Cullen]

Curious about your problem- I have tried importing your presets. (Windows-10  Classic v7.3.1)

One file { Kodak Tech Pan-BW400CN--.lrtemplate} gave me the following error, and because it was first of a multi selection the error stopped all four from importing.- The other three presets imported OK if selected singly.

When I opened this file in Windows Notepad I noticed that the dash '-' after the word Pan in the filename appears as a '/' in the .lrtemplate file-

When I edit the file in Notepad and replace the / with a dash -   in both "Internal Name" and "Title" I can import this preset successfully.

So I can only conclude it is the odd (LR- "illegal") characters internally in the preset files (NOT the OS filename) that are causing the import errors.

I do not know of a 'batch' way to edit many files easily. And "thousands of files" to edit will be an impossible task! I hope for you that Adobe comes up quickly with a patch that will allow you to import your presets.

[Bob Somrak]

Great sleuthing WobertC