Title: Nachricht
Good morning
users,
sorry for my
english, but I hope your understand me. I have a problem with the version 1.8.0
in combination with the newest digikam-plugin (kipi-plugin for generate a mpg
file for a images archiv).
I see the error from
ppmto4yuv that "Error: maxval==255.
On Mon, 26 Sep 2005 [EMAIL PROTECTED] wrote:
> I have a problem with the version 1.8.0 in combination with the newest
> digikam-plugin (kipi-plugin for generate a mpg file for a images archiv).
I think something in the newest digikam-plugin is causing the
problem.
> I see the
On Sep 24,21:36, Steven M. Schultz wrote:
> On Sun, 25 Sep 2005, Frank Albrecht wrote:
> > I use yuvdenoise for a long time with the options -S and
> > -b. Are these gone in mjpegtools 1.8.x?
>
> Yes, they are gone in 1.8 (actually they have been
> gone in the cvs version for almo
On Mon, 26 Sep 2005, Frank Albrecht wrote:
> I had to use mjpegtools 1.6.x because of several quicktime
> issues. I wasn't successfull in using streamer with libquicktime-0.9.4:
> "Speicherzugriffsfehler"
...error but my German is not good enough to translate Speicherzugriffs
Hallo
> > I had to use mjpegtools 1.6.x because of several quicktime
> > issues. I wasn't successfull in using streamer with libquicktime-0.9.4:
>
> > "Speicherzugriffsfehler"
> ...error but my German is not good enough to translate
> Speicherzugriffs
Error is close, actually it is trans
On Mon, 26 Sep 2005, Bernhard Praschinger wrote:
> > > "Speicherzugriffsfehler"
> > ...error but my German is not good enough to translate
> > Speicherzugriffs
> Error is close, actually it is translated with segmentation fault.
Ah, thank you! I knew I'd seen that before but c
On Monday 26 Sep 2005 17:02, Steven M. Schultz wrote:
> On Mon, 26 Sep 2005 [EMAIL PROTECTED] wrote:
> > I have a problem with the version 1.8.0 in combination with the
> > newest digikam-plugin (kipi-plugin for generate a mpg file for a
> > images archiv).
>
> I think something in the newest
On Mon, 26 Sep 2005, Anne Wilson wrote:
> I passed these two messages to one of the kipi developers. He replied:
> Can you check if the problem is related to this:
> http://qa.mandriva.com/show_bug.cgi?id=18748 ?
That is the 2nd part of the problem. Not sure things have gotten
