On 04/28/2016 05:18 PM, Simon Budig wrote:
>No there isn't but there will. This is work-in-progress. We'll
>probably end up with the plug-in having to specify "I am a raw
>importer", and a page in prefs to pick one of the installed
>importers.
An alternate idea might be to en/disable the file-pl
On 28/04/16 21:07, Carmelo DrRaw wrote:
Hi!
I’m not sure to understand what you mean by "if these could save to
high-bit-depth XCF directly, that would be even nicer”, but what I can say is that
photoflow works as a “native” plug-in, in the sense that it does not call an
external program, and
Michael Natterer (mi...@gimp.org) wrote:
> On Thu, 2016-04-28 at 15:43 -0400, Elle Stone wrote:
> > On 04/28/2016 03:40 PM, Elle Stone wrote:
> > >
> > > Delete the following text from pluginrc after you uninstall
> > > darktable,
> > > and you can use a different raw plug-in:
> > Is there an "ord
On Thu, 2016-04-28 at 15:43 -0400, Elle Stone wrote:
> On 04/28/2016 03:40 PM, Elle Stone wrote:
> >
> > Delete the following text from pluginrc after you uninstall
> > darktable,
> > and you can use a different raw plug-in:
> Is there an "order of preference" in the pluginrc file such that if
> a
On 04/28/2016 03:40 PM, Elle Stone wrote:
Delete the following text from pluginrc after you uninstall darktable,
and you can use a different raw plug-in:
Is there an "order of preference" in the pluginrc file such that if a
user installs a raw plugin, the installed raw plugin would take
prece
On 04/28/2016 01:09 PM, Ofnuts wrote:
Uninstalling darktable does allow the user to use the PhotoFlow raw
plug-in. But this doesn't seem like a very user-friendly way to
proceed. Also, it only seems to work if GIMP is recompiled and
reinstalled *after* darktable has been uninstalled. Or at least
Hi!
I’m not sure to understand what you mean by "if these could save to
high-bit-depth XCF directly, that would be even nicer”, but what I can say is
that photoflow works as a “native” plug-in, in the sense that it does not call
an external program, and it copies the output into the GEGL buffer
On 28/04/16 12:31, Elle Stone wrote:
On 04/27/2016 12:11 PM, Elle Stone wrote:
Hmm, now that I have darktable properly installed using Lua, and GIMP
opening 32f raw files processed with darktable, I can't figure out how
to open a raw file from GIMP using the PhotoFlow plug-in.
What's the proce
On 04/27/2016 12:11 PM, Elle Stone wrote:
Hmm, now that I have darktable properly installed using Lua, and GIMP
opening 32f raw files processed with darktable, I can't figure out how
to open a raw file from GIMP using the PhotoFlow plug-in.
What's the procedure for bypassing the darktable plug-
On 04/24/2016 09:54 AM, Elle Stone wrote:
On Wed, Apr 20, 2016 at 6:46 AM, Sven Claussner
wrote:
Hi,
sorry if I'm asking the wrong question but I feel I have to.
Since 18.04.2016 there is a raw importer plug-in in GIMP master
that calls darktable to do its job. With the same commit
the GEGL NE
On 04/26/2016 12:13 PM, johannes hanika wrote:
that version looks like it's from a git-archive snapshot.. maybe the
silly tar.gz that github provides as auto-generated tarball [0]? that
doesn't work. either use git clone or the .tar.xz we provide with the
releases.
-jo
[0]https://github.com/dar
that version looks like it's from a git-archive snapshot.. maybe the
silly tar.gz that github provides as auto-generated tarball [0]? that
doesn't work. either use git clone or the .tar.xz we provide with the
releases.
-jo
[0] https://github.com/darktable-org/darktable/releases
``as always, pleas
On Tue, 2016-04-26 at 09:37 -0400, Elle Stone wrote:
> OK, so I downloaded the source code from the darktable website and
> build
> darktable from source:
>
> $ darktable --version
> this is darktable archive-c2f7fdb1fce2d1206cb6b86d19a2de03f71e2448
That version string won't be parsed by the GIM
OK, so I downloaded the source code from the darktable website and build
darktable from source:
$ darktable --version
this is darktable archive-c2f7fdb1fce2d1206cb6b86d19a2de03f71e2448
copyright (c) 2009-2015 johannes hanika
darktable-...@lists.darktable.org
compile options:
normal build
Op
Having spent the last 45 minutes reinstalling Lua and and then darktable
through Gentoo portage, here's which version of Lua Gentoo says I'm using:
equery list lua
[IP-] [ ] dev-lang/lua-5.2.3-r1:5.2
$ eselect lua list
[1] 5.2 *
The little * means that's the selected version of Lua that a
Am Dienstag, 26. April 2016, 07:16:50 schrieb Elle Stone:
> On 04/25/2016 07:12 PM, Tobias Ellinghaus wrote:
> > Am Montag, 25. April 2016, 17:16:03 schrieb Elle Stone:
> >
> > [...]
> >
> >> Raw files opened from GIMP still aren't being opened in darktable.
> >> Instead it looks like the embedde
On 04/25/2016 07:12 PM, Tobias Ellinghaus wrote:
Am Montag, 25. April 2016, 17:16:03 schrieb Elle Stone:
[...]
Raw files opened from GIMP still aren't being opened in darktable.
Instead it looks like the embedded jpeg is opened in GIMP. I'm clueless
what I might be doing wrong but I'll try aga
Am Montag, 25. April 2016, 17:16:03 schrieb Elle Stone:
[...]
> Raw files opened from GIMP still aren't being opened in darktable.
> Instead it looks like the embedded jpeg is opened in GIMP. I'm clueless
> what I might be doing wrong but I'll try again tomorrow with a
> completely fresh build.
On 04/25/2016 09:21 AM, Tobias Ellinghaus wrote:
>Maybe I don't understand what you mean by "select the Canon or Nikon
>format in the open dialog"? If it matters, the sample raw file I'm
>trying to open is a Canon CR2 file.
There is a way to specify how to open an image in the lower left hand co
On Mon, 2016-04-25 at 06:52 -0400, Elle Stone wrote:
> On 04/24/2016 12:30 PM, Tobias Ellinghaus wrote:
> >
> > Am Sonntag, 24. April 2016, 09:54:25 schrieb Elle Stone:
> >
> > [...]
> >
> > >
> > > Speaking specifically of the GIMP-darktable code, it seems the
> > > GIMP-darktable code opens a
Am Montag, 25. April 2016, 06:52:45 schrieb Elle Stone:
> On 04/24/2016 12:30 PM, Tobias Ellinghaus wrote:
> > Am Sonntag, 24. April 2016, 09:54:25 schrieb Elle Stone:
> >
> > [...]
> >
> >> Speaking specifically of the GIMP-darktable code, it seems the
> >> GIMP-darktable code opens an already-p
On 04/25/2016 06:52 AM, Elle Stone wrote:
But opening the Canon CR2 file still results in an 8-bit jpeg,
accompanied by various terminal and popup errors and warnings.
Looking more closely at the resulting jpeg, GIMP seems to just be
opening the embedded jpeg.
Elle
__
On 04/24/2016 12:30 PM, Tobias Ellinghaus wrote:
Am Sonntag, 24. April 2016, 09:54:25 schrieb Elle Stone:
[...]
Speaking specifically of the GIMP-darktable code, it seems the
GIMP-darktable code opens an already-processed 8-bit jpeg. It doesn't
open the darktable raw processor interface and al
Am Sonntag, 24. April 2016, 09:54:25 schrieb Elle Stone:
[...]
> Speaking specifically of the GIMP-darktable code, it seems the
> GIMP-darktable code opens an already-processed 8-bit jpeg. It doesn't
> open the darktable raw processor interface and allow the user to choose
> the processing parame
On Wed, Apr 20, 2016 at 6:46 AM, Sven Claussner wrote:
Hi,
sorry if I'm asking the wrong question but I feel I have to.
Since 18.04.2016 there is a raw importer plug-in in GIMP master
that calls darktable to do its job. With the same commit
the GEGL NEF importer was disabled which is a quite cl
hi all,
let me try to answer some details from the dt side:
On Wed, Apr 20, 2016 at 6:46 AM, Sven Claussner wrote:
> Hi,
>
> sorry if I'm asking the wrong question but I feel I have to.
> Since 18.04.2016 there is a raw importer plug-in in GIMP master
> that calls darktable to do its job. With t
26 matches
Mail list logo