Hello Bernhard
I will double check, I must say for convenience I am using a Packman /
Suse rpm.
Therefore they may use a release version rather than a CVS one.
I am probably missing on that one.
Hopefully yes, because it will mean that my question was already
obsolete when I asked it :-[
Cheer
Hallo
>> No - The heaviest hitting process is causing the bottle neck. Look at
>> optimising this process to better utilise your machine, multithreading
>> may help. There is no point optimising the low %CPU processes if
>> this is the case.
>>
>
> This is the case.
> It seems to be yuvdenoise
> Are both your CPU cores loaded?
>
Well one is 20 % the other 65 % (or so) and then swap from time to time.
cheers
E
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise de
Are both your CPU cores loaded?
yuvdenoise is a bit of a complicated beast I don't think it'd be easy
to optimise.
A simple multithreaded optimisation technique is to use slices (less
than full height sections of the frame, each section is given to a
CPU) However yuvdenoise uses spatial ga
Thanks Mark
> No - The heaviest hitting process is causing the bottle neck. Look at
> optimising this process to better utilise your machine, multithreading
> may help. There is no point optimising the low %CPU processes if
> this is the case.
>
This is the case.
It seems to be yuvden
The simple solution to worrying about the need to optimise the code
for your cpu is to look at the output from top.
(I am actually interested in seeing the %CPU each of your processes
take up.)
Are both your CPUs fully loaded?
Yes - multi threading is not needed but you could always optimise
Le 14 nov. 2010 à 21:04, E Chalaron a écrit :
> Hello Bernhard
> Thanks for the reply.
>> That is a normal behaviour both programms use only one CPU/Core and are
>> not multithreaded.
>>
>
> Ok so if I understand properly does it mean that y4munsharp will get 1
> core and the yuvdenoise the oh
Hello Bernhard
Thanks for the reply.
> That is a normal behaviour both programms use only one CPU/Core and are
> not multithreaded.
>
Ok so if I understand properly does it mean that y4munsharp will get 1
core and the yuvdenoise the oher one ? or both on 1 core that will
alternate from time to
Hallo
E Chalaron wrote:
> Hello all
> Just a quick question : using mjpegtools through ffmpeg piping.
> are they (or not) multi threaded ?
>
> ffmpeg -threads 2 -y -i - -f yuv4mpegpipe - | \
> yuvdenoise -t 2,8,8 -m 2,8,8 |
> y4munsharp |\
> ffmpeg -y -threads 2 -i - -b 22k -vcodec dnxhd -thre
Hello all
Just a quick question : using mjpegtools through ffmpeg piping.
are they (or not) multi threaded ?
ffmpeg -threads 2 -y -i - -f yuv4mpegpipe - | \
yuvdenoise -t 2,8,8 -m 2,8,8 |
y4munsharp |\
ffmpeg -y -threads 2 -i - -b 22k -vcodec dnxhd -threads 2 $fichier
On (for say) a dual core
Hi,
The yuvdenoise manpage says:
|As it is self-adapting to the noise-situation found in the stream
|you normally just can go without any options set:
I would just like to have a confirmation that this assertion is
not outdated ;-)
c
--
\black\trash movie _COWBOY CANOE COMA_
Am Mittwoch, 12. Juli 2006 10:18 schrieb stefan:
> stefan schrieb:
> > Steven M. Schultz schrieb:
> >
> >> On Wed, 5 Jul 2006, Michael Hanke wrote:
> >>
> >>> Hmmm... Please excuse my dumb question. Here are you puzzling me a
little bit.
[snip]
Hi Steven and Stefan,
being back from my va
stefan schrieb:
> Steven M. Schultz schrieb:
>
>> On Wed, 5 Jul 2006, Michael Hanke wrote:
>>
>>> Hmmm... Please excuse my dumb question. Here are you puzzling me a little
>>> bit.
>>>
>>>
>> It is not dumb at all! You raise some very interesting points that
>> people should b
On Wed, 5 Jul 2006, Michael Hanke wrote:
> Hmmm... Please excuse my dumb question. Here are you puzzling me a little bit.
It is not dumb at all! You raise some very interesting points that
people should be aware of.
> My model of thinking with respect to interlacing/deinterlaci
Am Mittwoch, 5. Juli 2006 00:03 schrieb stefan:
> Steven M. Schultz schrieb:
> > I'm on vacation at the moment and a lengthy discussion is not possible
> > (about to wander out and do some sight seeing) but my suggestion
> > is omit the deinterlace step
> >
>
> clearly depends on what he trie
On Sun, 9 Oct 2005, Frank Albrecht wrote:
> > The other thing that can be done is find where streamer is calling
> > 'quicktime_set_audio' and find out if it is setting things up
> > correctly for what libquicktime is expecting.
>
> I inspected the sources of 0.9.7 and 0.9.2 and it d
On Oct 04,13:36, Steven M. Schultz wrote:
[...Segmentation fault with sttreamer and libquicktime...]
> ./configure --enable-debug
I've done that. See below...
> > I woldn't have expected it's an audio related problem. It' the
> > same with rpm package and self-compiled.
> Ok -
Hi -
> On Thu, 6 Oct 2005, Dave Dodge wrote:
>
> > One option for NTSC might be the JVC SR-V101US. This is an S-VHS deck
> > from their pro line, has Y/C output and a built-in TBC. It can be
I've the JVC HRS-9911 ($319) that also lists a TBC as a feature (in
addition to DNR [Di
On Tue, Oct 04, 2005 at 01:30:03PM -0700, Steven M. Schultz wrote:
> Is this from a VHS tape deck? Maybe a signal stabilizer would help,
> something like:
>
> http://www.kramerelectronics.com/indexes/item.asp?desc=98
>
> or a TBC but that's probably more money than you want to
On Oct 02,09:33, Steven M. Schultz wrote:
> On Sun, 2 Oct 2005, Frank Albrecht wrote:
> > > What does a gdb backtrace look show? Perhaps knowing where the
> > > fault is happening will provide an idea what area to investigate.
> > Puh, I don't know how to do that.
[...manual for dummies
On Oct 04,18:28, Joe Friedrichsen wrote:
Thank you all for your suggestions.
[...]
> >Mplayer and ffmpeg can both produce a yuv4mpeg stream which works
> >nicely with mjpeg tools.
> >ffmpeg -i input_file.ext -f yuv4mpegpipe outfile.yuv
> >mplayer -vo yuv4mpeg input_file.ext
> mplayer -
On Wed, 5 Oct 2005, E.Chalaron wrote:
> Unless you are familiar with electronics :
>
> http://www.astro.uu.se/~marcus/private/newvidproc.html
Nice looking unit - wonder how much he would charge to build one?
(soldering irons and I do not get along ;))
I noticed it was d
On Wednesday 05 Oct 2005 09:30, Steven M. Schultz wrote:
> or a TBC but that's probably more money than you want to spend ;)
Unless you are familiar with electronics :
http://www.astro.uu.se/~marcus/private/newvidproc.html
---
This SF.Net em
On Tue, 4 Oct 2005, Frank Albrecht wrote:
> > > > What does a gdb backtrace look show?...
>
> [...manual for dummies such as me...]
> Thank you.
You're welcome.
Oh, I forgot to mention "chapter 2" in the manual ;)
When you configure libquicktime add the "--ena
On Tue, 4 Oct 2005, Frank Albrecht wrote:
It might be a better idea to reply to this list (especially with
lavrec or V4L problems - I abandoned the Bt878 card several years
some time ago).
> > Perhaps others who capture to mjpeg can help with some ideas - but
> >
Hi!
Mark Heath wrote:
On 02/10/2005, at 6:35 PM, Frank Albrecht wrote:
Is it possible to use mencoder or ffmpeg for capturing for
mjpegtools? I couldn't figure out how to create an input
satifying lav2yuv/mpeg2.
Hopefully this is will answer what you are asking.
Mplayer and ffmpeg can b
On 02/10/2005, at 6:35 PM, Frank Albrecht wrote:
Is it possible to use mencoder or ffmpeg for capturing for
mjpegtools? I couldn't figure out how to create an input
satifying lav2yuv/mpeg2.
Hopefully this is will answer what you are asking.
Mplayer and ffmpeg can both produce a yuv4mpeg str
On Sep 28,08:51, Steven M. Schultz wrote:
>
> On Wed, 28 Sep 2005, Frank Albrecht wrote:
>
> > It doesn't work. Segmentation fault with libquicktime, with
> > all versions of streamer, self-compiled or not.
> What does a gdb backtrace look show? Perhaps knowing where the
> fault is
On Sun, 2 Oct 2005, Frank Albrecht wrote:
> > What does a gdb backtrace look show? Perhaps knowing where the
> > fault is happening will provide an idea what area to investigate.
>
> Puh, I don't know how to do that.
gdb yourprogram
run program_args
when the fa
On Wed, 28 Sep 2005, Frank Albrecht wrote:
> It doesn't work. Segmentation fault with libquicktime, with
> all versions of streamer, self-compiled or not.
Sigh :(
What does a gdb backtrace look show? Perhaps knowing where the
fault is happening will provide an idea what
On Sep 27,04:45, Frank Albrecht wrote:
> On Sep 26,10:19, Steven M. Schultz wrote:
>
> > 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:
>
> > > Usi
On Sep 26,10:19, Steven M. Schultz wrote:
> 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 Ge
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
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, 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
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, Luca Bonissi wrote:
> Make attenction: by default, the new yuvdenoise has a gaussian filter
> and a spatial filter on...
>
> I usually disable the spatial and gaussian filter (-s 0,0,0 -g 0,0,0).
> Maybe you can keep the gaussian filter for chroma only (-g 0,255,255).
Frank Albrecht, on 25/09/2005 05:42 you wrote:
> I use yuvdenoise for a long time with the options -S and -b.
> Are these gone in mjpegtools 1.8.x?
Make attenction: by default, the new yuvdenoise has a gaussian filter
and a spatial filter on. The motion compensation was also removed (it
was very u
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 almost 2 years ;)).
> I don't see an equivalence in othe
Hi,
I use yuvdenoise for a long time with the options -S and -b.
Are these gone in mjpegtools 1.8.x?
I don't see an equivalence in other yuv-tools.
How can I(little) sharpen the video?
How can I set a black border for the overscan area?
For a PAL-VHS i used, for example:
lav2yuv $5|yuvdenoise
Steven M. Schultz wrote:
> On Wed, 10 Aug 2005, CPM wrote:
>An easier way to get the set of options that yuvdenoise accepts would
>be with
>
> yuvdenoise -h
Good solution it is. :-)
>> So, my question: where is the problem?
>
>The problem is in the yuvdenoise manpage ;) yuvd
On Wed, 10 Aug 2005, Steven M. Schultz wrote:
> DVD (and to a slightly lesser extent) encoding parameters have been
(and to a slightly lesser extent SVCD) - left out a word there.
Much has been written about encoding with mpeg2enc - I think you'll
find much useful i
On Thu, 11 Aug 2005, CPM wrote:
> In Kino, they use yuvdenoise like this:
>
> ...|yuvdenoise -F -f | yuvscaler -v 0 -O VCD -n p | mpeg2enc -v 0 -f 1
> -I 0 -n p -a 2 -o 'cliptestc'.mpv'
>
> or like this:
>
> ...|yuvdenoise -F | yuvscaler -v 0 -O VCD -n p | mpeg2enc -v 0 -f 1 -I 0
> -n p -
In Kino, they use yuvdenoise like that:
...|yuvdenoise -F -f | yuvscaler -v 0 -O VCD -n p | mpeg2enc -v 0 -f 1
-I 0 -n p -a 2 -o 'cliptestc'.mpv'
or like that:
...|yuvdenoise -F | yuvscaler -v 0 -O VCD -n p | mpeg2enc -v 0 -f 1 -I 0
-n p -a 2 -o 'cliptestc'.mpv'
As mjpeg has changed
Steven M. Schultz wrote:
> On Wed, 10 Aug 2005, CPM wrote:
> An easier way to get the set of options that yuvdenoise accepts would
> be with
>
>yuvdenoise -h
Good solution it is. :-)
>> So, my question: where is the problem?
>
> The problem is in the yuvdenoise manpage ;)
On Wed, 10 Aug 2005, CPM wrote:
> I have a problem with Kino when it using yuvdenoise because
> yuvdenoise doesn't accept the -F option. In the manpage, this
> option is available but read error message below:
The manpage is outdated. When yuvdenoise went thru a couple
rewrit
Hello,
I have a problem with Kino when it using yuvdenoise because
yuvdenoise doesn't accept the -F option. In the manpage, this
option is available but read error message below:
[EMAIL PROTECTED] (15:23:24) ~ 1 > echo "fo" | yuvdenoise
INFO: [yuvdenoise] yuvdenoise version 1.6.3-r
Hello,
I get the main.c ( 1.42 ) and the makefile.am ( 1.24 ) of /yuvdenoise and
compile another time. Now everything is fine. Thanks for help
> De: "Odile Planquelle" <[EMAIL PROTECTED]>
> A: "Bernhard Praschinger" <[EMAIL PROTECTED]>
> Objet
h the pb. I can send if you want.
> De: Bernhard Praschinger <[EMAIL PROTECTED]>
> A: Odile Planquelle <[EMAIL PROTECTED]>
> Objet: Re: [Mjpeg-users] yuvdenoise
> Date: Wed, 03 Aug 2005 18:15:24 +0200
> Hallo
>
> > I think I run the last version of the tool ;
> &
Hallo
> I think I run the last version of the tool ;
>INFO: [lt-yuvdenoise] yuvdenoise version 1.6.3-rc1
> I've got it from yum ( I'm running fedora core 4 )
Was that package compiled for a special architecture ? Intel AMD MAC ?
There is a known problem with MAC running Fedora core 4, which se
der version of yuvdenoise ?
Regards
> De: Bernhard Praschinger <[EMAIL PROTECTED]>
> A: Odile Planquelle <[EMAIL PROTECTED]>
> Objet: Re: [Mjpeg-users] yuvdenoise
> Date: Wed, 03 Aug 2005 07:11:01 +0200
> Odile Planquelle wrote:
> >
> > Hello, I'm trying to use
Odile Planquelle wrote:
>
> Hello, I'm trying to use yuvdenoise with files created wiyh kino :
>
> smil2yuv input.dv | yuvdenoise | mpeg2enc -f8 -o test01.mv2
> the mpeg2enc end at frame 90 with informtaion :
> INFO: [mpeg2enc] Frame8787 P q=8.00 sum act=4086.08653
> INFO: [mpeg2enc]
From: "Odile Planquelle" <[EMAIL PROTECTED]>
--=_NextPart_Lycos_307751847992422_ID
Content-Type: text/html; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
body{font:12px Arial;margin:3px;over=
flow-y:auto;overflow-x:auto}p{margin:0px;}blockquote, ol, ul{margin-top:0=
px;margin
Hello, I'm trying to use yuvdenoise with files created wiyh kino :
smil2yuv input.dv | yuvdenoise | mpeg2enc -f8 -o test01.mv2
the mpeg2enc end at frame 90 with informtaion :
INFO: [mpeg2enc] Frame 87 87 P q=8.00 sum act=4086.08653
INFO: [mpeg2enc] Signaling last frame = 90
INFO:
When yuvdenoise was first re-written I was really sad because I liked the
original yuvdenoise so much. The newer one was slow and did not seem to get
rid of anywhere near the noise the original did. I decided to give it another
chance using the latest from CVS and noticed it is now only 2X as
Thanks Steven ...
That may save me some time actually to put it at the end.. Instead of
conforming the big frames at the beginning.
Cheers
E
---
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How
On Fri, 10 Jun 2005, E.Chalaron wrote:
> Was wondering in yuvdenoise :
>
> -Y 2 -U 5 -V 1 -y 2 -u 5 -v 1
> Is it considered as agressive filtering ?
I think that is moderate to mild filtering. I think the '-V' and
'-v' could be safely increased to 2 but that's not critical.
Was wondering in yuvdenoise :
-Y 2 -U 5 -V 1 -y 2 -u 5 -v 1
Is it considered as agressive filtering ?
and if yuvcorrect -Y CONFORM should be placed before or after ?
Can't make my mind, results seems really close and the more opinion the better
Cheers
E
-
On Wed, 23 Jun 2004, Jonathan Woithe wrote:
> I have encountered something rather odd about yuvdenoise from mjpegtools
> 1.6.2 and the way it works on two different machines. In short, I encoded
> a video in two 90 minute sections using the same command line - one was on a
> (PII-vintage) Celero
Hi all
I have encountered something rather odd about yuvdenoise from mjpegtools
1.6.2 and the way it works on two different machines. In short, I encoded a
video in two 90 minute sections using the same command line - one was on a
(PII-vintage) Celeron 466 and one on a 3.0GHz P4 with hyperthreadi
On Thu, 12 Feb 2004, Bernhard Praschinger wrote:
> I have a strange effect, using when I don't use yuvdenoise, I get smaller
> files than when I use yuvdenoise -f. Using only yuvdenoise makes smaller
> file than without the usage of yuvdenoise.
Hmmm, is it possible that when you use "yuv
Hallo
I have a strange effect, using when I don't use yuvdenoise, I get smaler
files than when I use yuvdenoise -f. Using only yuvdenoise makes smaler
file than without the usage of yuvdenoise.
The source (Digital Sat) is recorded by the BUZ. And looks rather good.
The command I use lookes like
Greetings,
yuvdenoise 1.6.1.90 seems to introduce an artifact into its filtered output.
The artifact is at the top left corner of the picture, has the
appearance resembling a translucent frame, and seems to have a size of
256x256 pixels.
I have created demonstration material and testcases, and
Can yuvdenoise cope with an interlaced source (VHS tape) and keep it
interlaced. Only it says:
"and then into the filter. (Well, the other way would work, too,
except that the filter doesn't do interlaced MC yet and doesn't do a
good job on interlaced
Hi -
>From: "Scott Waye" <[EMAIL PROTECTED]>
>
>Can yuvdenoise cope with an interlaced source (VHS tape) and keep it
>interlaced. Only it says:
Yes indeed. I've lost count of the VHS & 8mm tapes I've converted
to DVD/SVCD.
Cheers,
Steven Schultz
-
Can yuvdenoise cope with an interlaced source (VHS tape) and keep it
interlaced. Only it says:
"and then into the filter. (Well, the other way would work, too,
except that the filter doesn't do interlaced MC yet and doesn't do a
good job on interlaced frames that way... I'll fix that!)"
--
--- Ronald Bultje <[EMAIL PROTECTED]> wrote:
> Hey Richard,
>
> On Fri, 2003-03-07 at 14:13, Richard Ellis wrote:
> > Note, w/h appear to be the result of subtracting two from unsigned
> > int's that were initialized to zero, instead of being initialized to
> > the incoming frame width/height from
Hey Richard,
On Fri, 2003-03-07 at 14:13, Richard Ellis wrote:
> Note, w/h appear to be the result of subtracting two from unsigned int's
> that were initialized to zero, instead of being initialized to the
> incoming frame width/height from the yuv4mpeg header.
Yup, they're uint16_t's (see yuvde
While we are on the subject of parameter handling bugs in the yuv* tools,
this one also exists:
Call yuvdenoise with this parameter: -b 2,2,-2,-2 which according to the
man page should do this:
"Sometimes it may be usefull to have relative coordinates like this:
yuvdenoise -b 16,16,-16,-16
Hi Robert
> > Hi all,
> > What the -l stands for in yuvdenoise ?
>
> low-pass threshold. See "yuvdenoise --help".
Thanks,
I was not really sure if I can understand that as antialiasing, my question
was not to the point. Is it the case ?
Edouard
On Wed, 12 Feb 2003, Edouard Chalaron wrote:
>
> Hi all,
> What the -l stands for in yuvdenoise ?
low-pass threshold. See "yuvdenoise --help".
--
Robert Kesterson
[EMAIL PROTECTED]
---
This SF.NET email is sponsored by:
SourceForge Ente
Hi all,
What the -l stands for in yuvdenoise ?
Thanks
Edouard
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
M
72 matches
Mail list logo
