Well, I hope that somebody more competent than myself stumbles across this issue: EVERY style that I have downloaded from github.com/jade-nl/dt.styles/releases/tag/V1.7, in the dt.black.white.zip, dt.alt.personal.zip and dt.fuji.zip collections fails to load in either dt 3.6.1 (Win) or 3.9.0-git6.c6e8ed5447-1 (Linux) and in neither case give any diagnostic information when dt is started from the commend line.
That’s a lot of ‘defective’ styles!
You can’t be bothered to do the work to improve things but you hope someone will? Come on, that’s extremely unfair.
You can play up this “omg I don’t know how this works” thing all you want, but that’s literally how almost everyone started.
Just had a look at dt.styles: They work when using darktable 3.6.,1 they do not when using darktable3.9.0. This error is thrown:
12.563882 [styles] file /data/Images/Shared/Styles/Colour/Fuji/3510 constlclip.dtstyle is malformed style file
I checked this on Linux. I do not have access to Windows or MacOS based systems.
Just to let you know: The styles I collected and made accessible are rather old and are not scene-referred “safe” at their base. At the moment I do not know why these do not work in 3.9.0. I need to think about what I want to do about a solution (if anything…).
Based on your observable history in this forum, I know your comment is well meant and is, In principle, justified, but, specifically in my context, it’s not applicable; it is very much NOT a case of ‘I can’t be bothered’, but rather a case of how do I allocate my limited time.
I’m not only old, but I’m well beyond my life expectancy (according to this consultant report here…) and I still have 15 boxes (200 slides per box) of slides, a couple of hundred 35mm film negative strips, a few hundred seriously fading 100 to 120 year old prints and about 50,000 digital images to (variously) scan, tag, restore and then edit with dt. It’s about 3 to 4 hours per slide on average, for me. You do the math. And that’s not my primary duty, which involves far more serious matters. So at some stage I have to say ‘sorry, I just can’t do that’. Given my current age-limited ability to acquire new knowledge, especially if it is not widely applicable, means that mastering the secret signs and incantations to become a member of the August github club takes me to that stage.
Sorry, that’s life.
Thanks for taking a look at this. As reported elsewhere, I have tried a good selection of them in 3.6.1 under Win 10: they do not import; no error message is displayed when dt is started from the command line. And, as stated elsewhere, I confirm that every one of the sample dtstyles I have tried do not import under 3.9.0 under Linux.
Thanks for the advice that they are not ‘scene-referred’ safe - I hadn’t thought of that. I was more attracted to the X-Trans II versions on the assumption they would be more suitable for adjusting the images taken with my earlier Fuji cameras.
So we help you through your problems and even tolerate your cheap shots at our work (your user manual thread), but when you’re asked to do one notch above nothing (go to github, click new issue, copy what you have written here and include a link to the style repo), you can’t do it. OK, understood, “that’s life.”
As confirmed by @elstoc and me: This is probably/might be a darktable parsing bug. So these are not defective styles (turns out that my collection are the only ones that show this issue).
As mentioned by elstoc: File a detailed bug report on GitHub about this.
I get a “404” error on the link you gave, the “v” must be lowercase…
After solving that, no trouble importing styles from the dt.black.white.zip under linux, dt 3.6.1. So at least those are not defective in the archive. (and opening them in a text editor does not show any empty lines).
@paperdigits: at one point, everyone starts from not knowing how x works. After that, it’s mostly a matter of time and backtracking when you realise you missed a concept.
@LateJunction You do realise that 3.9.0 is the current development version? Which means it has a higher probablility of containing bugs (which you are then supposed to help solve…). Perhaps not the best choice if you have trouble with the stable versions.
Well, indeed you do, without question; and that help is gratefully received. But you should not tolerate ‘cheap shots’ - that is not my intent and it would be a churlish attitude for me to adopt. As I have observed elsewhere, this forum is the most benign I have experienced, so if some of my rantings are making you, personally, or any over contributor here, feel uncomfortable, please make it very clear to me.
I had thought (based on analysing a previous issue) that ‘raising an issue’ an issue on github involved considerably more rigour and collection of supporting ‘evidence’, and the use of tools, technology and vocabulary which are foreign to me. If it is a straightforward as you suggest, I will look into it further.
Hmm, point well taken. I think I was assuming that functions like importing of styles were well established by now, very unlikely to be changed in the ‘next’ release and, so, unlikely to be the source of a logic error. In fact it never occurred to me that this might be a bug.
More importantly I don’t want to lose sight of the fact that this ‘anomaly’ happens in dt 3.6.1 under Windows 10 - and that is a stable release version, is it not?
Right now 3.9.0 and 3.8.0 are virtually identical, though this will change soon.
darktable -d all returns:
22,676848 [styles] file /tmp/dt.styles-master/Fuji/XTrans III Velvia.dtstyle is malformed style file
it seems dt doesn’t like line breaks and blanks between tags in styles
more precise: between <darktable_style version=“1.0”> and <info> tag
issue reported: https://github.com/darktable-org/darktable/issues/10664
Darkroom is just to apply the style not import functionality there that I am aware of…
Not uncomfortable, but some of your last posts seem like they try to add comedic value with their verbosity, but the verbosity only clouds your question and at times seems mocking of both yourself (which is your prerogative) and the project.
If you have a question, just ask it. I don’t want to read six paragraphs to get to a one sentence queation, especially when it is a technical question.
Mica, be a little more understanding. It must be tiresome to deal with the same kinds of questions and complaints over and over again, but it’s very true that learning how to deal with a Linux-based program is a very difficult experience for many of us who don’t have a background in Linux and programming. Linux is not user friendly at all, and the error messages it throws are mostly very opaque and non-informative to those of us who are Windows users (and probably Mac users also). It’s not an issue of being too lazy to learn something new, it’s FRUSTRATION.
I have been more than understanding, you’re free to peruse the post history. However, there is a bit of an unwritten social contract here, and that is, you get the application for free, the source code for free, the support for free, but when you find an issue you need to report it. This social contract is what was violated, along with the last several posts getting more and more unclear due to their verbosity. Support is a limited resource, so making people guess as to what you need is unkind.
I totally understand and agree with you. I think almost all users of darktable greatly appreciate the time and sacrifice that the developers and support folks are selflessly donating to keep this great software one of the very best of its kind. The intellect at work here is mind-boggling!
Unfortunately Unix is a tool of the devil, and that tool is used here.
Most of us (devs) think that about Micro$oft Window$
Yeah, point well made. Change of style required.
Accepted: message noted and lesson learned.