Aw: [darktable-dev] 3D LUT → segmentation fault
Hello I've checked the lut it at windows rc1 build and it happens to make the output window blank. The program works further and allows changing LUTs or making other actions. With respect, Alexander Rabtchevich > Gesendet: Mittwoch, 20. November 2019 um 07:29 Uhr > Von: "Timur Irikovich Davletshin" > An: darktable-dev@lists.darktable.org > Betreff: [darktable-dev] 3D LUT → segmentation fault > > Hi developers! > > Can anyone confirm dt master builds segmentation fault on loading big > HaldLUT file like this? Unlike other files from that source it is twice > bigger. > > File: > > https://drive.google.com/open?id=1WoPFoouBbJlbQa5VsWXiT2kPJMH5NREI > > File comes from: > > http://rawpedia.rawtherapee.com/Film_Simulation#RawTherapee_Film_Simulation_Collection > > Thanks in advance, > > Timur. > > ___ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org > > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] 3D LUT → segmentation fault
Hi developers! Can anyone confirm dt master builds segmentation fault on loading big HaldLUT file like this? Unlike other files from that source it is twice bigger. File: https://drive.google.com/open?id=1WoPFoouBbJlbQa5VsWXiT2kPJMH5NREI File comes from: http://rawpedia.rawtherapee.com/Film_Simulation#RawTherapee_Film_Simulation_Collection Thanks in advance, Timur. ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable 3.0 rc1 openCL
No luck with rocm either, but the message changes, see below I am not sure if the hsa module is correct... Why does it refer to /data/jenkins_workspace/ ??? This is not on my computer. Does anyone have darktable with openCL running on a Dell Precision 7700 series ??? If so which graphics card? Thanks Jozef Dassen rocminfo: ROCk module is loaded dassen is member of video group hsa api call failure at: /data/jenkins_workspace/compute-rocm-rel-2.9/rocminfo/rocminfo.cc:1102 Call returned HSA_STATUS_ERROR_OUT_OF_RESOURCES: The runtime failed to allocate the necessary resources. This error may also occur when the core runtime library needs to spawn threads or create internal OS-specific events. clinfo: Number of platforms: 1 Platform Profile: FULL_PROFILE Platform Version: OpenCL 2.1 AMD-APP (2982.0) Platform Name: AMD Accelerated Parallel Processing Platform Vendor: Advanced Micro Devices, Inc. Platform Extensions: cl_khr_icd cl_amd_event_callback cl_amd_offline_devices Platform Name: AMD Accelerated Parallel Processing ERROR: clGetDeviceIDs(-1) darktable-cltest: 0.038262 [opencl_init] opencl related configuration options: 0.038279 [opencl_init] 0.038281 [opencl_init] opencl: 1 0.038283 [opencl_init] opencl_library: '' 0.038285 [opencl_init] opencl_memory_requirement: 768 0.038287 [opencl_init] opencl_memory_headroom: 300 0.038289 [opencl_init] opencl_device_priority: '*/!0,*/*/*' 0.038291 [opencl_init] opencl_mandatory_timeout: 200 0.038292 [opencl_init] opencl_size_roundup: 16 0.038294 [opencl_init] opencl_async_pixelpipe: 0 0.038295 [opencl_init] opencl_synch_cache: active module 0.038297 [opencl_init] opencl_number_event_handles: 25 0.038299 [opencl_init] opencl_micro_nap: 1000 0.038300 [opencl_init] opencl_use_pinned_memory: 0 0.038302 [opencl_init] opencl_use_cpu_devices: 0 0.038303 [opencl_init] opencl_avoid_atomics: 0 0.038305 [opencl_init] 0.038443 [opencl_init] found opencl runtime library 'libOpenCL' 0.038460 [opencl_init] opencl library 'libOpenCL' found on your system and loaded 0.052124 [opencl_init] found 1 platform 0.052130 [opencl_init] could not get device id size: -1 0.052132 [opencl_init] found 0 device 0.052133 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. 0.052135 [opencl_init] initial status of opencl enabled flag is OFF. Sent: Tuesday, November 19, 2019 at 7:26 PM From: "Andreas Schneider" To: darktable-dev@lists.darktable.org Cc: "Jozef Dassen" Subject: Re: [darktable-dev] darktable 3.0 rc1 openCL On Tuesday, 19 November 2019 12:27:50 CET Jozef Dassen wrote: > After a lot of struggle I managed to install amdgpu drivers on my Ubuntu > 18.04. It did not work with kernel 5.0 but going back to kernel 4.15 worked > fine. Flawless installation of amdgpu 18.40. > Then I ran darktable-cltest (darktable 3.0 rc1) and got the following > result: > 0.037740 [opencl_init] opencl related configuration options: > 0.037752 [opencl_init] > 0.037755 [opencl_init] opencl: 1 > 0.037757 [opencl_init] opencl_library: '' > 0.037759 [opencl_init] opencl_memory_requirement: 500 > 0.037761 [opencl_init] opencl_memory_headroom: 0 > 0.037763 [opencl_init] opencl_device_priority: '*/!0,*/*/*' > 0.037784 [opencl_init] opencl_mandatory_timeout: 200 > 0.037786 [opencl_init] opencl_size_roundup: 16 > 0.037788 [opencl_init] opencl_async_pixelpipe: 0 > 0.037790 [opencl_init] opencl_synch_cache: active module > 0.037794 [opencl_init] opencl_number_event_handles: 25 > 0.037797 [opencl_init] opencl_micro_nap: 1000 > 0.037800 [opencl_init] opencl_use_pinned_memory: 0 > 0.037802 [opencl_init] opencl_use_cpu_devices: 0 > 0.037804 [opencl_init] opencl_avoid_atomics: 1 > 0.037806 [opencl_init] > 0.037962 [opencl_init] found opencl runtime library 'libOpenCL' > 0.037980 [opencl_init] opencl library 'libOpenCL' found on your system and > loaded 0.170870 [opencl_init] found 1 platform > 0.170885 [opencl_init] found 1 device > 0.170923 [opencl_init] device 0 `Capeverde' supports image sizes of 16384 x > 16384 0.170927 [opencl_init] device 0 `Capeverde' allows GPU memory > allocations of up to 1053MB [opencl_init] device 0: Capeverde > GLOBAL_MEM_SIZE: 1472MB > MAX_WORK_GROUP_SIZE: 256 > MAX_WORK_ITEM_DIMENSIONS: 3 > MAX_WORK_ITEM_SIZES: [ 1024 1024 1024 ] > DRIVER_VERSION: 2686.5 > DEVICE_VERSION: OpenCL 1.2 AMD-APP (2686.5) > 0.171329 [opencl_init] could not create command queue for device 0: -6 > 0.171373 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. > 0.171376 [opencl_init] initial status of opencl enabled flag is OFF. > > > my display is: > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83) (prog-if 00 [VGA > controller]) Subsystem: Dell Venus XTX [Radeon HD 8890M / R9 M275X/M375X] > Flags: bus master, fast devsel, latency 0, IRQ 128
Re: [darktable-dev] UI glitches
* Terry Duell [11-19-19 15:51]: > On Wed, 20 Nov 2019 01:11:27 +1100, Moritz Moeller > wrote: > > > > > > On a side note: What's exactly the problem with large file attachments > > in 2019 in the first world? > > > > Yes, it's a bad habit. Does it bother? :) > > My email client doesn't load attachments unless I tell it to. Most > > clients nowadays don't. > > Yes it does bother, not all mailers are selective about that. > It is a rather selfish indulgence to assume that all mail group users need > or want to have the attachment, so providing a link to the attachment is > simply good etiquette. thank you, my patience is gone :( -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] UI glitches
On Wed, 20 Nov 2019 01:11:27 +1100, Moritz Moeller wrote: On a side note: What's exactly the problem with large file attachments in 2019 in the first world? Yes, it's a bad habit. Does it bother? :) My email client doesn't load attachments unless I tell it to. Most clients nowadays don't. Yes it does bother, not all mailers are selective about that. It is a rather selfish indulgence to assume that all mail group users need or want to have the attachment, so providing a link to the attachment is simply good etiquette. Cheers, -- Regards, Terry Duell ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] UI glitches → Buttons and stuff
Good evening developers! Coming back to this topic. There is another harbor of buttons with wrong order I've discovered. Steps to reproduce: 1. Open lighttable mode → tagging module. 2. Create any tag if list of available tags is missing. 3. Right click on created tag: a) "delete tag" action opens confirmation window with reversed button order. Same for "delete branch". b) "create tag..." opens dialog window with reversed button order. Same for "edit tag...". Timur. On Mon, 2019-11-11 at 12:57 +0100, Nicolas Auffray wrote: > Hi, > At Timur, please test my PR here : > https://github.com/darktable-org/darktable/pull/3362 > sams96 replies this day that my PR fix this. I never had this issue > so that was not the purpose on start but if it helps ! > Have a good day > > Le 11/11/2019 à 03:57, Sam a écrit : > > Hey Timur, I opened an issue on github for this, but it seems like > > it's just you and I that see this so I was wondering what OS and > > maybe DE you're using? > > > > Thanks > > > > On Fri, 8 Nov 2019 at 02:49, Timur Irikovich Davletshin < > > timur.davlets...@gmail.com> wrote: > > > Buttons in following darkroom modules require fixing too: > > > > > > vignetting, rgb levels, levels, color mapping, basic adjustments. > > > > > > Timur. > > > > > > On Thu, 2019-11-07 at 15:09 +0800, Sam wrote: > > > > I've added fixes to a couple of these to my pull request here. > > > > > > > > > > > > > > ___ > > darktable developer mailing list to unsubscribe send a > > mail to darktable-dev+unsubscr...@lists.darktable.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] tone equalizer, filmic rgb → icon background
Thanks Aurélien for looking on that. That was what I have understood but do you think something could be improved here without quite easily to fix that or by this time, it's better to let that actually and maybe closed issue I posted ? Le 19/11/2019 à 14:46, Aurélien Pierre a écrit : Did look at that. The colour picker in levels and tone curve are GTK buttons. As such, they get hovering effects and stuff from CSS. The colour pickers next to sliders are bauhaus widgets, and their CSS support is very basic at this point (size and colour only). This is indeed a Cairo + GTK business to wire their state to user input, then their state to CSS rules. Le 15/11/2019 à 21:33, Aurélien Pierre a écrit : Will have a look in the next few days. Le 15/11/2019 à 21:10, Nicolas Auffray a écrit : Timur, see here for issue posted : https://github.com/darktable-org/darktable/issues/3445 I'm now waiting for someone with GTK/Cairo skills. Le 15/11/2019 à 20:55, Nicolas Auffray a écrit : I just look on that and color pickers with hover background are indeed buttons gtk items as color pickers in filmic rgb, exposer, color balance, tone equalizer (or some other modules) are not button widget ones but seems included in bauhaus-slider widget (or with). And these ones doesn't have specific CSS tag so I can't change that with CSS as it is without adding other glitches. So probably need a GTK code change to make all color pickers here have same behavior. I will post an issue on Github. Le 15/11/2019 à 20:12, Nicolas Auffray a écrit : Oups, sorry I just see that I was not on same color pickers than you. We recently update color pickers on levels modules and I don't know why, by answering you, I was thinking of that levels modules (so the black, grey and white pickers I was pointing) and not the curve rgb one... I've just edited an image and opening curve rgb (not level...) and I now understand what you point. Indeed, you're right, this pickers are the same as filmic, exposure or tones ones and not have the same behavior. Again, sorry for my last answers, not on purpose... I will see if I can fix that with CSS this week-end. Thanks for pointing that. Nicolas Le 15/11/2019 à 19:41, Timur Irikovich Davletshin a écrit : Nic, I'm just saying that this behavior looks a bit confusing from user standpoint. I'm sorry for not posting to github. MS decided that I cannot use it — https://help.github.com/en/github/site-policy/github-and-trade-controls and I'm too lazy to use VPN for that purpose. Timur. P.S. there is no need to reply both to personal email and mailing list. On Fri, 2019-11-15 at 19:32 +0100, Nicolas Auffray wrote: I have never say they are not pickers, just they are not same one... Just see how they renders and where they are on modules UI. Size is not the same, and also color. just see that they are visibly different... But remember that it's an open source software, so feel free to change that the way you want if you don't like that, for you or you could even propose a PR on Github... Hmm Color pickers on curve modules are here to apply black, grey and white parts of curve (so they are colored in... black, grey, white). If hover, that could only be on background. Other color pickers are not related to black, grey and white. So if we had a hover effect, it would be better to do that just on the picker (not the background but the picker himself). It's a possibility, but for me it's good as it is actually (and nobody else seems to have problem with that...). That's my view here ! Le 15/11/2019 à 18:40, Timur Irikovich Davletshin a écrit : If they are not pickers why use same icon? And if all other icons have hover action, why not these? Hmm... Timur. On Fri, 2019-11-15 at 18:25 +0100, Nicolas Auffray wrote: Hi Timur, It would really be better to post issues on Github (to let all know and follow that). Anyway, some answers on what I see : 1. Yes, this icon doesn't seems to have CSS editing possibility (maybe I make a mistake but on what I see with GTK inspector...). So posting on Github to let Aurélien see that (as it is his module work) would be better. 2 and 3. That's not issues. All color pickers like these ones (see exposure module for example) are displayed the same way. Color picker on rgb curve are not same color picker (colored one, black, grey and white and not on same place like others color picker ; so having a different way is not a problem as they are not totally the same). Not needed to have them have the exact same behavior. Nicolas Le 15/11/2019 à 18:09, Timur Irikovich Davletshin a écrit : Hi developers! 1. tone equalizer module → display exposure mask icon has no hover background lightening. Compare with display mask icon in drawn mask blending. 2. Same problem in tone equalizer module → masking tab → picker tool next to mask exposure compensation and mask contrast compensation. 3. filmic rgb module → scene tab → four picker
Re: [darktable-dev] UI glitches
On 19.11.19 14:54, Patrick Shanahan wrote: ah, when lacking a proper response, divert attention to something else which is also irrelevant. That's exactly what you were doing since attachment file sizes are not a topic of this thread. Maybe you meant /dev/troll? ;) The first ting I learned when running my own software company was that it doesn't matter what channel users try to reach you. If they reach out to you to let you know about something that is broken or could be better, be thankful. They mean well. They care about the software you make for them. What can be better testament to the work you do? Aka: No need to be rude. Tell them nicely about how to reach you better next time. You can prepare a nicely written response that outlines Red Mine account/ticket creation and procedure that you can C into a reply or point them to a website that does so. That takes 20 minutes. Obviously doing so will remove the opportunity to be rude to new people on this list forever to a large degree. Maybe the latter is more important to some people than solving the issue they purport to have here for once. On a side note: What's exactly the problem with large file attachments in 2019 in the first world? Yes, it's a bad habit. Does it bother? :) My email client doesn't load attachments unless I tell it to. Most clients nowadays don't. Beers, .mm ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] UI glitches
Man come on! The point is in the topic. I copy it for you: "UI glitches". It is not about your wishes. I told you already, once you manage to get your rules to official dt page people will be more likely to respect them: https://www.darktable.org/contact/#how-to-get-in-contact You just scarring off new users by your letters. You send it to EVERY user who sends attachments in letters. Hugs and kisses, Timur. On Tue, 2019-11-19 at 08:54 -0500, Patrick Shanahan wrote: > * Timur Irikovich Davletshin [11-19-19 > 08:41]: > > Perhaps rather than scaring off every new user on mailing list with > > your letters you will concentrate on something else. > > > > On Tue, 2019-11-19 at 08:30 -0500, Patrick Shanahan wrote: > > > * Timur Irikovich Davletshin [11-19- > > > 19 > > > 08:23]: > > > > Patrick, I believe we already discussed it. > > > > > > > > On Tue, 2019-11-19 at 08:02 -0500, Patrick Shanahan wrote: > > > > > please utilize a file-share service rather than uploading > > > > > large > > > > > files to everyone on the list > > > > > > I believe "discussed" is a bit of a stretch. Why don't you > > > create > > > issues and attach needed examples there and provide the dev's > > > with a > > > more singular place to watch instead of expecting them to react > > > to > > > bloated emails? > > > > > > ps: announced recently that the dev's are quite busy, perhaps > > > rather > > > minor nit-pics might be postponed until the major problems are > > > solved. > > > > > ah, when lacking a proper response, divert attention to something > else > which is also irrelevant. > > --> /dev/null ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] UI glitches
* Timur Irikovich Davletshin [11-19-19 08:41]: > Perhaps rather than scaring off every new user on mailing list with > your letters you will concentrate on something else. > > On Tue, 2019-11-19 at 08:30 -0500, Patrick Shanahan wrote: > > * Timur Irikovich Davletshin [11-19-19 > > 08:23]: > > > Patrick, I believe we already discussed it. > > > > > > On Tue, 2019-11-19 at 08:02 -0500, Patrick Shanahan wrote: > > > > please utilize a file-share service rather than uploading large > > > > files to everyone on the list > > > > I believe "discussed" is a bit of a stretch. Why don't you create > > issues and attach needed examples there and provide the dev's with a > > more singular place to watch instead of expecting them to react to > > bloated emails? > > > > ps: announced recently that the dev's are quite busy, perhaps rather > > minor nit-pics might be postponed until the major problems are solved. > > ah, when lacking a proper response, divert attention to something else which is also irrelevant. --> /dev/null -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] tone equalizer, filmic rgb → icon background
Did look at that. The colour picker in levels and tone curve are GTK buttons. As such, they get hovering effects and stuff from CSS. The colour pickers next to sliders are bauhaus widgets, and their CSS support is very basic at this point (size and colour only). This is indeed a Cairo + GTK business to wire their state to user input, then their state to CSS rules. Le 15/11/2019 à 21:33, Aurélien Pierre a écrit : > > Will have a look in the next few days. > > Le 15/11/2019 à 21:10, Nicolas Auffray a écrit : >> Timur, see here for issue posted : >> https://github.com/darktable-org/darktable/issues/3445 >> >> I'm now waiting for someone with GTK/Cairo skills. >> >> >> Le 15/11/2019 à 20:55, Nicolas Auffray a écrit : >>> I just look on that and color pickers with hover background are >>> indeed buttons gtk items as color pickers in filmic rgb, exposer, >>> color balance, tone equalizer (or some other modules) are not button >>> widget ones but seems included in bauhaus-slider widget (or with). >>> And these ones doesn't have specific CSS tag so I can't change that >>> with CSS as it is without adding other glitches. So probably need a >>> GTK code change to make all color pickers here have same behavior. I >>> will post an issue on Github. >>> >>> >>> Le 15/11/2019 à 20:12, Nicolas Auffray a écrit : Oups, sorry I just see that I was not on same color pickers than you. We recently update color pickers on levels modules and I don't know why, by answering you, I was thinking of that levels modules (so the black, grey and white pickers I was pointing) and not the curve rgb one... I've just edited an image and opening curve rgb (not level...) and I now understand what you point. Indeed, you're right, this pickers are the same as filmic, exposure or tones ones and not have the same behavior. Again, sorry for my last answers, not on purpose... I will see if I can fix that with CSS this week-end. Thanks for pointing that. Nicolas Le 15/11/2019 à 19:41, Timur Irikovich Davletshin a écrit : > Nic, I'm just saying that this behavior looks a bit confusing from > user > standpoint. > > I'm sorry for not posting to github. MS decided that I cannot use > it — > https://help.github.com/en/github/site-policy/github-and-trade-controls > > and I'm too lazy to use VPN for that purpose. > > Timur. > > P.S. there is no need to reply both to personal email and mailing > list. > > On Fri, 2019-11-15 at 19:32 +0100, Nicolas Auffray wrote: >> I have never say they are not pickers, just they are not same one... >> Just see how they renders and where they are on modules UI. Size is >> not >> the same, and also color. just see that they are visibly >> different... >> But remember that it's an open source software, so feel free to >> change >> that the way you want if you don't like that, for you or you could >> even >> propose a PR on Github... Hmm >> >> Color pickers on curve modules are here to apply black, grey and >> white >> parts of curve (so they are colored in... black, grey, white). If >> hover, >> that could only be on background. Other color pickers are not >> related >> to >> black, grey and white. So if we had a hover effect, it would be >> better >> to do that just on the picker (not the background but the picker >> himself). It's a possibility, but for me it's good as it is actually >> (and nobody else seems to have problem with that...). That's my view >> here ! >> >> >> Le 15/11/2019 à 18:40, Timur Irikovich Davletshin a écrit : >>> If they are not pickers why use same icon? And if all other icons >>> have >>> hover action, why not these? Hmm... >>> >>> Timur. >>> >>> On Fri, 2019-11-15 at 18:25 +0100, Nicolas Auffray wrote: Hi Timur, It would really be better to post issues on Github (to let all know and follow that). Anyway, some answers on what I see : 1. Yes, this icon doesn't seems to have CSS editing possibility (maybe I make a mistake but on what I see with GTK inspector...). So posting on Github to let Aurélien see that (as it is his module work) would be better. 2 and 3. That's not issues. All color pickers like these ones (see exposure module for example) are displayed the same way. Color picker on rgb curve are not same color picker (colored one, black, grey and white and not on same place like others color picker ; so having a different way is not a problem as they are not totally the same). Not needed to have them have the exact same behavior.
Re: [darktable-dev] UI glitches
Perhaps rather than scaring off every new user on mailing list with your letters you will concentrate on something else. On Tue, 2019-11-19 at 08:30 -0500, Patrick Shanahan wrote: > * Timur Irikovich Davletshin [11-19-19 > 08:23]: > > Patrick, I believe we already discussed it. > > > > On Tue, 2019-11-19 at 08:02 -0500, Patrick Shanahan wrote: > > > please utilize a file-share service rather than uploading large > > > files > > > to everyone on the list > > I believe "discussed" is a bit of a stretch. Why don't you create > issues > and attach needed examples there and provide the dev's with a more > singular place to watch instead of expecting them to react to bloated > emails? > > ps: announced recently that the dev's are quite busy, perhaps rather > minor > nit-pics might be postponed until the major problems are solved. > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] UI glitches
* Timur Irikovich Davletshin [11-19-19 08:23]: > Patrick, I believe we already discussed it. > > On Tue, 2019-11-19 at 08:02 -0500, Patrick Shanahan wrote: > > > > please utilize a file-share service rather than uploading large files > > to everyone on the list I believe "discussed" is a bit of a stretch. Why don't you create issues and attach needed examples there and provide the dev's with a more singular place to watch instead of expecting them to react to bloated emails? ps: announced recently that the dev's are quite busy, perhaps rather minor nit-pics might be postponed until the major problems are solved. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] UI glitches
* Timur Irikovich Davletshin [11-19-19 03:05]: > Hi developers! > > Couple of UI glitches which I find could impact user experience in > future dt 3.0. > > 1. Long lists (noscroll1.png) like the one in lens correction module > are not scrollable. Options down bellow are available to user. If your > lists are not long enough — try updating database via lensfun-update- > data. Probably the same issue will impact long lists in styles menu in > bottom left corner of the the image. > > 2. Tethering (width1.png) settings for some reason do not take full > width available in parent panel. Makes it hard to work with drop-down > menus. > > Thank you in advance, please utilize a file-share service rather than uploading large files to everyone on the list -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] darktable 3.0 rc1 openCL
On Tuesday, 19 November 2019 12:27:50 CET Jozef Dassen wrote: > After a lot of struggle I managed to install amdgpu drivers on my Ubuntu > 18.04. It did not work with kernel 5.0 but going back to kernel 4.15 worked > fine. Flawless installation of amdgpu 18.40. > Then I ran darktable-cltest (darktable 3.0 rc1) and got the following > result: > 0.037740 [opencl_init] opencl related configuration options: > 0.037752 [opencl_init] > 0.037755 [opencl_init] opencl: 1 > 0.037757 [opencl_init] opencl_library: '' > 0.037759 [opencl_init] opencl_memory_requirement: 500 > 0.037761 [opencl_init] opencl_memory_headroom: 0 > 0.037763 [opencl_init] opencl_device_priority: '*/!0,*/*/*' > 0.037784 [opencl_init] opencl_mandatory_timeout: 200 > 0.037786 [opencl_init] opencl_size_roundup: 16 > 0.037788 [opencl_init] opencl_async_pixelpipe: 0 > 0.037790 [opencl_init] opencl_synch_cache: active module > 0.037794 [opencl_init] opencl_number_event_handles: 25 > 0.037797 [opencl_init] opencl_micro_nap: 1000 > 0.037800 [opencl_init] opencl_use_pinned_memory: 0 > 0.037802 [opencl_init] opencl_use_cpu_devices: 0 > 0.037804 [opencl_init] opencl_avoid_atomics: 1 > 0.037806 [opencl_init] > 0.037962 [opencl_init] found opencl runtime library 'libOpenCL' > 0.037980 [opencl_init] opencl library 'libOpenCL' found on your system and > loaded 0.170870 [opencl_init] found 1 platform > 0.170885 [opencl_init] found 1 device > 0.170923 [opencl_init] device 0 `Capeverde' supports image sizes of 16384 x > 16384 0.170927 [opencl_init] device 0 `Capeverde' allows GPU memory > allocations of up to 1053MB [opencl_init] device 0: Capeverde > GLOBAL_MEM_SIZE: 1472MB > MAX_WORK_GROUP_SIZE: 256 > MAX_WORK_ITEM_DIMENSIONS: 3 > MAX_WORK_ITEM_SIZES: [ 1024 1024 1024 ] > DRIVER_VERSION: 2686.5 > DEVICE_VERSION: OpenCL 1.2 AMD-APP (2686.5) > 0.171329 [opencl_init] could not create command queue for device 0: -6 > 0.171373 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. > 0.171376 [opencl_init] initial status of opencl enabled flag is OFF. > > > my display is: > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83) (prog-if 00 [VGA > controller]) Subsystem: Dell Venus XTX [Radeon HD 8890M / R9 M275X/M375X] > Flags: bus master, fast devsel, latency 0, IRQ 128 > Memory at b000 (64-bit, prefetchable) [size=256M] > Memory at de30 (64-bit, non-prefetchable) [size=256K] > I/O ports at e000 [size=256] > Expansion ROM at 000c [disabled] [size=128K] > Capabilities: [48] Vendor Specific Information: Len=08 > Capabilities: [50] Power Management version 3 > Capabilities: [58] Express Legacy Endpoint, MSI 00 > Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 > Capabilities: [150] Advanced Error Reporting > Capabilities: [200] #15 > Capabilities: [270] #19 > Kernel driver in use: amdgpu > Kernel modules: radeon, amdgpu > > I have fresh Ubuntu 18.04-1 installation on a sytem with 64Gbyte RAM. Only > Firefox is running. So no resource problems. I have deferred all other > installations until I can get darktable with openCL running. This is a > sine-qua-non for me. > So no luck... Again > > Any ideas what could be the problem ?? > > darktablerc parameters: > opencl=true > opencl_async_pixelpipe=false > opencl_avoid_atomics=true > opencl_checksum= > opencl_device_priority=*/!0,*/*/* > opencl_disable_drivers_blacklist=false > opencl_library= > opencl_mandatory_timeout=200 > opencl_memory_headroom=0 > opencl_memory_requirement=500 > opencl_micro_nap=1000 > opencl_number_event_handles=25 > opencl_scheduling_profile=default > opencl_size_roundup=16 > opencl_synch_cache=active module > opencl_use_cpu_devices=false > opencl_use_pinned_memory=false I would suggest to just use the open source driver provided by the kernel and install ROCm for OpenCL. http://repo.radeon.com/rocm/apt/ Works just fine on Fedora and openSUSE. I can't help you with the proprietary driver. Andreas -- Andreas Schneider a...@cryptomilk.org GPG-ID: 8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] darktable 3.0 rc1 openCL
After a lot of struggle I managed to install amdgpu drivers on my Ubuntu 18.04. It did not work with kernel 5.0 but going back to kernel 4.15 worked fine. Flawless installation of amdgpu 18.40. Then I ran darktable-cltest (darktable 3.0 rc1) and got the following result: 0.037740 [opencl_init] opencl related configuration options: 0.037752 [opencl_init] 0.037755 [opencl_init] opencl: 1 0.037757 [opencl_init] opencl_library: '' 0.037759 [opencl_init] opencl_memory_requirement: 500 0.037761 [opencl_init] opencl_memory_headroom: 0 0.037763 [opencl_init] opencl_device_priority: '*/!0,*/*/*' 0.037784 [opencl_init] opencl_mandatory_timeout: 200 0.037786 [opencl_init] opencl_size_roundup: 16 0.037788 [opencl_init] opencl_async_pixelpipe: 0 0.037790 [opencl_init] opencl_synch_cache: active module 0.037794 [opencl_init] opencl_number_event_handles: 25 0.037797 [opencl_init] opencl_micro_nap: 1000 0.037800 [opencl_init] opencl_use_pinned_memory: 0 0.037802 [opencl_init] opencl_use_cpu_devices: 0 0.037804 [opencl_init] opencl_avoid_atomics: 1 0.037806 [opencl_init] 0.037962 [opencl_init] found opencl runtime library 'libOpenCL' 0.037980 [opencl_init] opencl library 'libOpenCL' found on your system and loaded 0.170870 [opencl_init] found 1 platform 0.170885 [opencl_init] found 1 device 0.170923 [opencl_init] device 0 `Capeverde' supports image sizes of 16384 x 16384 0.170927 [opencl_init] device 0 `Capeverde' allows GPU memory allocations of up to 1053MB [opencl_init] device 0: Capeverde GLOBAL_MEM_SIZE: 1472MB MAX_WORK_GROUP_SIZE: 256 MAX_WORK_ITEM_DIMENSIONS: 3 MAX_WORK_ITEM_SIZES: [ 1024 1024 1024 ] DRIVER_VERSION: 2686.5 DEVICE_VERSION: OpenCL 1.2 AMD-APP (2686.5) 0.171329 [opencl_init] could not create command queue for device 0: -6 0.171373 [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. 0.171376 [opencl_init] initial status of opencl enabled flag is OFF. my display is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus XTX [Radeon HD 8890M / R9 M275X/M375X] (rev 83) (prog-if 00 [VGA controller]) Subsystem: Dell Venus XTX [Radeon HD 8890M / R9 M275X/M375X] Flags: bus master, fast devsel, latency 0, IRQ 128 Memory at b000 (64-bit, prefetchable) [size=256M] Memory at de30 (64-bit, non-prefetchable) [size=256K] I/O ports at e000 [size=256] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Capabilities: [200] #15 Capabilities: [270] #19 Kernel driver in use: amdgpu Kernel modules: radeon, amdgpu I have fresh Ubuntu 18.04-1 installation on a sytem with 64Gbyte RAM. Only Firefox is running. So no resource problems. I have deferred all other installations until I can get darktable with openCL running. This is a sine-qua-non for me. So no luck... Again Any ideas what could be the problem ?? darktablerc parameters: opencl=true opencl_async_pixelpipe=false opencl_avoid_atomics=true opencl_checksum= opencl_device_priority=*/!0,*/*/* opencl_disable_drivers_blacklist=false opencl_library= opencl_mandatory_timeout=200 opencl_memory_headroom=0 opencl_memory_requirement=500 opencl_micro_nap=1000 opencl_number_event_handles=25 opencl_scheduling_profile=default opencl_size_roundup=16 opencl_synch_cache=active module opencl_use_cpu_devices=false opencl_use_pinned_memory=false Regards, Jozef Dassen ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] image information → export width/height
Hi dear developers! What is the point of "export width" and "export height" in "image information"? It seems to be straightforward but no matter what I do they remain just zeroes. Is it not working the way it was meant to be or I miss something? Thank you in advance, Timur. ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
