Want to retouch your photos? we can help you.
Deep etching or masking for your photos, or even adding clipping path.
Retouching also if needed.
Hopefully to start something for you soon.
Thanks,
Grace
Bremerhdaven
Wunsdtorf
Want to retouch your photos? we can help you.
Deep etching or masking for your photos, or even adding clipping path.
Retouching also if needed.
Hopefully to start something for you soon.
Thanks,
Grace
Redmscheid
Pirna
We are an imaging team who can process 300+ images daily.
If you need any image editing service, please contact us today.
We do mainly images cut out and clipping path, masking.
Such as for your ecommerce photos, jewelry photos retouching, also it is
for beauty portraits and skin images
and
We are an imaging team who can process 300+ images daily.
If you need any image editing service, please contact us today.
We do mainly images cut out and clipping path, masking.
Such as for your ecommerce photos, jewelry photos retouching, also it is
for beauty portraits and skin images
and
We are an imaging team who can process 300+ images daily.
If you need any image editing service, please contact us today.
We do mainly images cut out and clipping path, masking.
Such as for your ecommerce photos, jewelry photos retouching, also it is
for beauty portraits and skin images
and
We are an imaging team who can process 300+ images daily.
If you need any image editing service, please contact us today.
We do mainly images cut out and clipping path, masking.
Such as for your ecommerce photos, jewelry photos retouching, also it is
for beauty portraits and skin images
and
We are an imaging team who can process 300+ images daily.
If you need any image editing service, please contact us today.
We do mainly images cut out and clipping path, masking.
Such as for your ecommerce photos, jewelry photos retouching, also it is
for beauty portraits and skin images
and
We are an imaging team who can process 300+ images daily.
If you need any image editing service, please contact us today.
We do mainly images cut out and clipping path, masking.
Such as for your ecommerce photos, jewelry photos retouching, also it is
for beauty portraits and skin images
and
We are an image team who can process 400+ images each day.
If you need any image editing service, please let us know.
Image cut out and clipping path, masking.
Such as for ecommerce photos, jewelry photos retouching, beauty and skin
images
and wedding photos.
We give test editing for your
Have photos for cutting out or retouching?
We are one image team and we do editing for your the e-commerce photos,
industry photos or portrait photo.
If you need test editing then let me know.
Waiting for your reply and the photo work.
Thanks,
Joanna
Have photos for cutting out or retouching?
We are one image team and we do editing for your the e-commerce photos,
industry photos or portrait photo.
If you need test editing then let me know.
Waiting for your reply and the photo work.
Thanks,
Joanna
Have photos for cutting out or retouching?
We are one image team and we do editing for your the e-commerce photos,
industry photos or portrait photo.
If you need test editing then let me know.
Waiting for your reply and the photo work.
Thanks,
Joanna
Hi,
I would like to take the chance to speak with the person who handle your
images in your company?
Our ability of imaging editing.
Cutting out for your images
Clipping path for your images
Masking for your images
Retouching for your images
Retouching for the Portraits images
We have 17 photo
Hi,
I would like to take the chance to speak with the person who handle your
images in your company?
Our ability of imaging editing.
Cutting out for your images
Clipping path for your images
Masking for your images
Retouching for your images
Retouching for the Portraits images
We have 17 photo
your photos
Retouching for the Beauty Model and Portraits.
We have 20 staffs in house and daily basis 1000 images can be processed.
We give testing for your photos.
Thanks,
Jimmy Wilson
Do you have photos for editing?
We are image team and we can process 500+ images each day.
We edit ecommerce photo, jewelry photos, and beauty model photos.
also wedding photos.
We do cut out and clipping path for photos, also retouching.
You may send us a test photo to check our quality
We have got a team of professional to do image editing service for you.
We have 20 image editors and on daily basis 2000 images can be processed.
If you want to check our quality of work please send us a photo with
instruction and we will work on it.
Our Services:
Photo cut out, masking
We have got a team of professional to do image editing service for you.
We have 20 image editors and on daily basis 2000 images can be processed.
If you want to check our quality of work please send us a photo with
instruction and we will work on it.
Our Services:
Photo cut out, masking
We can process 400+ images per day.
If you need any image editing, please let us know.
Photos cut out;
Photos clipping path;
Photos masking;
Photo shadow creation;
Photos retouching;
Beauty Model retouching on skin, face, body;
Glamour retouching;
Products retouching.
We can give you testing
ures.
> > >
> > > No, but there are some ascii art images inside some txt/rst files
> > > and inside some kernel-doc comments. We could either use the above
> > > extension for them or to convert into some image. The ascii art
> > > images I saw seem t
> > > and I know Paul has run into these issues with the RCU docs as
> > > well. Might there be a tool or an extension out there that would
> > > allow us to express these diagrams in a text-friendly, editable
> > > form?
> > >
> > > With som
On Mon, 21 Nov 2016, Johannes Berg wrote:
> I had a hack elsewhere that would embed the fixed-width text if the
> plugin isn't present, which seemed like a decent compromise, but nobody
> is willing to let plugins be used in general to start with, it seems :)
FWIW I'm all for doing this stuff in
> > > You had pointed me to this plugin before
> > > https://pythonhosted.org/sphinxcontrib-aafig/
> > >
> > > but I don't think it can actually represent any of the pictures.
> >
> > No, but there are some ascii art images inside some txt/
Em Mon, 21 Nov 2016 11:39:41 +0100
Johannes Berg escreveu:
> On Sat, 2016-11-19 at 10:15 -0700, Jonathan Corbet wrote:
> >
> > I don't know what the ultimate source of these images is (Mauro,
> > perhaps you could shed some light there?).
>
> I'd arg
On Sat, 2016-11-19 at 10:15 -0700, Jonathan Corbet wrote:
>
> I don't know what the ultimate source of these images is (Mauro,
> perhaps you could shed some light there?).
I'd argue that it probably no longer matters. Whether it's xfig, svg,
graphviz originally etc. - the
Em Sat, 19 Nov 2016 22:59:01 -
"David Woodhouse" escreveu:
> > I think that graphviz and svg are the reasonable modern formats. Let's
> > try to avoid bitmaps in today's world, except perhaps as intermediate
> > generated things for what we can't a
> On Sat, Nov 19, 2016 at 9:55 AM, David Woodhouse
> wrote:
>>
>> I know it's unfashionable these days, but TeX always used to be bloody
>> good at that kind of thing.
>
> You must have used a different TeX than I did.
>
> TeX is a horrible example. The moment you needed to insert anything
> that
On Sat, Nov 19, 2016 at 12:54 PM, Mauro Carvalho Chehab
wrote:
>
> I did some research on Friday trying to identify where those images
> came. It turns that, for the oldest images (before I took the media
> maintainership), PDF were actually their "source", as far as I could
rly need to
> engage more with sphinx upstream in general. But I guess I still haven't
> figured out what "fixing sphinx" means in this case.
>
> I don't know what the ultimate source of these images is (Mauro, perhaps
> you could shed some light there?). Perhap
On Sat, Nov 19, 2016 at 9:55 AM, David Woodhouse wrote:
>
> I know it's unfashionable these days, but TeX always used to be bloody
> good at that kind of thing.
You must have used a different TeX than I did.
TeX is a horrible example. The moment you needed to insert anything
that TeX didn't know
On 11/19/16 09:15, Jonathan Corbet wrote:
> Might there be a tool or an extension out there that would allow us
> to express these diagrams in a text-friendly, editable form?
How about using the graphviz languages for generating diagrams that can
be described easily in one of the graphviz langua
On Sat, 2016-11-19 at 10:15 -0700, Jonathan Corbet wrote:
> Might there be a tool or an extension out there that
> would allow us to express these diagrams in a text-friendly, editable
> form?
I know it's unfashionable these days, but TeX always used to be bloody
good at that kind of thing.
--
d
> Rather than beating our heads against the wall trying to convert between
> various image formats, maybe we need to take a step back. We're trying
> to build better documentation, and there is certainly a place for
> diagrams and such in that documentation. Johannes was asking about it
> for the
in.
>
> But what we *should* worry about is having the kernel source tree
> contain source.
I would be happy to take a shot at fixing sphinx; we clearly need to
engage more with sphinx upstream in general. But I guess I still haven't
figured out what "fixing sphinx" means in
On Fri, Nov 18, 2016 at 11:15:09AM +0200, Jani Nikula wrote:
> On Thu, 17 Nov 2016, Linus Torvalds wrote:
> > We have makefiles, but more importantly, few enough people actually
> > *generate* the documentation, that I think if it's an option to just
> > fix sphinx, we should do that instead. If i
On Thu, 17 Nov 2016, Linus Torvalds wrote:
> We have makefiles, but more importantly, few enough people actually
> *generate* the documentation, that I think if it's an option to just
> fix sphinx, we should do that instead. If it means that you have to
> have some development version of sphinx, s
On Thu, Nov 17, 2016 at 3:07 AM, Arnd Bergmann wrote:
>
> [adding Linus for clarification]
>
> I understood the concern as being about binary files that you cannot
> modify with classic 'patch', which is a separate issue.
No. That is how I *noticed* the issue. Those stupid pdf binary files
have b
conf and different macro libraries that might be installed on
> > the
> > system. So this isn't a hard and fast rule by any means (although
> > Linus may be more strict than I on that issue).
> >
> > I don't understand why it's so terrible to have
On Thu, Nov 17, 2016 at 12:07:15PM +0100, Arnd Bergmann wrote:
> [adding Linus for clarification]
>
> I understood the concern as being about binary files that you cannot
> modify with classic 'patch', which is a separate issue.
I think the other complaint is that the image files aren't "source"
> So, the problem that remains is for those images whose source
> is a bitmap. If we want to stick with the Sphinx supported formats,
> we have only two options for bitmaps: jpg or png. We could eventually
> use uuencode or base64 to make sure that the patches won't use
ible to have generate the image
> file from the .svg file in a Makefile rule, and then copy it somewhere
> else if Sphinx is too dumb to fetch it from the normal location?
The images whose source are in .svg are now generated via Makefile
for the PDF output (after my patches, already applied to
and pdf. For reference, those are the formats it supports
for images:
http://www.sphinx-doc.org/en/1.4.8/builders.html
There are just two formats supported for the output types we use:
PNG and JPEG.
> [adding Linus for clarification]
>
> I understood the concern as being about
e, a PNG file
> >> is OK, as it is editable.
Btw, Sphinx is indeed supporting PNG without external conversions, for
both html and pdf. For reference, those are the formats it supports
for images:
http://www.sphinx-doc.org/en/1.4.8/builders.html
There are just two formats supported fo
On Thu, Nov 17, 2016 at 8:02 AM, Linus Torvalds
wrote:
>
> No. That is how I *noticed* the issue. Those stupid pdf binary files
> have been around forever, I just didn't notice until the Fedora people
> started complaining about the patches.
Side note: my release patches these days enable both "-
files
>> > though, as they have the same problem as the .pdf files.
>>
>> Actually, my last patch series removed all *.pdf images and converted
>> all .gif files under Documentation/media to PNG[1]. I also replaced some
>> images by .svg, but the remainin
ot; tool for all png and
> > > pdf files currently at the documentation (they're all at media,
> > > ATM).
> >
> > It looks like we still need to find a way to address the .gif files
> > though, as they have the same problem as the .pdf files.
>
>
're all at media,
> > ATM).
>
> It looks like we still need to find a way to address the .gif files
> though, as they have the same problem as the .pdf files.
Actually, my last patch series removed all *.pdf images and converted
all .gif files under Documentation/media to PNG[1].
On Tuesday, November 8, 2016 8:50:36 AM CET Mauro Carvalho Chehab wrote:
> > [...]
> > > And it may even require "--shell-escape" to be passed at the xelatex
> > > call if inkscape is not in the path, with seems to be a strong
> > > indication that SVG support is not native to texlive, but, instead
\unskip}\relax \unskip}
> >\relax \\
> > ?
> >
> > This patch fixes the issue:
> >
> > https://git.linuxtv.org/mchehab/experimental.git/commit/?h=dirty-pdf&id=b709de415f34d77cc121cad95bece9c7ef4d12fd
> >
>
r specified via O= directive) and generate the *.pdf there,
> >and produce those converted images via Makefile.;
> >
> > 2) add an Sphinx extension that would internally call ImageMagick and/or
> >inkscape to convert the bitmap;
> >
> > 3) if possible, a
linuxtv.org/mchehab/experimental.git/commit/?h=dirty-pdf&id=b709de415f34d77cc121cad95bece9c7ef4d12fd
>
> That means that Sphinx is not generating the right LaTeX output even for
> (some?) PNG images.
So I'm seriously confused.
I can get that particular message - TeX is complai
On Mon, 7 Nov 2016 07:55:24 -0200
Mauro Carvalho Chehab wrote:
> So, we have a few alternatives:
>
> 1) copy (or symlink) all rst files to Documentation/output (or to the
>build dir specified via O= directive) and generate the *.pdf there,
>and produce those conve
Am 11.11.2016 um 12:22 schrieb Jani Nikula :
> On Thu, 10 Nov 2016, Jani Nikula wrote:
>> On Thu, 10 Nov 2016, Markus Heiser wrote:
>>> Could this POC persuade you, if so, I send a more elaborate RFC,
>>> what do you think about?
>>
>> Sorry, I do not wish to be part of this.
>
> That was unc
On Thu, 10 Nov 2016, Jani Nikula wrote:
> On Thu, 10 Nov 2016, Markus Heiser wrote:
>> Could this POC persuade you, if so, I send a more elaborate RFC,
>> what do you think about?
>
> Sorry, I do not wish to be part of this.
That was uncalled for, apologies.
Like I said, I don't think this is t
tput (or to the
> >>>> build dir specified via O= directive) and generate the *.pdf there,
> >>>> and produce those converted images via Makefile.;
> >>
> >> We're supposed to solve problems, not create new ones.
> >
> >
On Thu, 10 Nov 2016, Markus Heiser wrote:
> Could this POC persuade you, if so, I send a more elaborate RFC,
> what do you think about?
Sorry, I do not wish to be part of this.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubs
>> build dir specified via O= directive) and generate the *.pdf there,
>>>>> and produce those converted images via Makefile.;
>>>
>>> We're supposed to solve problems, not create new ones.
>>
>> ... new ones? ...
>
> Handle in-tree build
Em Mon, 07 Nov 2016 12:53:55 +0200
Jani Nikula escreveu:
> On Mon, 07 Nov 2016, Mauro Carvalho Chehab wrote:
> > Hi Jon,
> >
> > I'm trying to sort out the next steps to do after KS, with regards to
> > images included on RST files.
> >
> > The issue
*.pdf there,
>>>> and produce those converted images via Makefile.;
>>
>> We're supposed to solve problems, not create new ones.
>
> ... new ones? ...
Handle in-tree builds without copying.
Make dependency analysis with source rst and "intermediate" rst
f there,
>> >> and produce those converted images via Makefile.;
>>
>> We're supposed to solve problems, not create new ones.
>
> So, what's your proposal?
Second message in the thread,
http://lkml.kernel.org/r/87wpgf8ssc@intel.com
>
> Thanks,
>
Em Wed, 09 Nov 2016 13:16:55 +0200
Jani Nikula escreveu:
> >> 1) copy (or symlink) all rst files to Documentation/output (or to the
> >> build dir specified via O= directive) and generate the *.pdf there,
> >> and produce those converted images via Makefile.;
&
Am 09.11.2016 um 12:16 schrieb Jani Nikula :
>> So I vote for :
>>
>>> 1) copy (or symlink) all rst files to Documentation/output (or to the
>>> build dir specified via O= directive) and generate the *.pdf there,
>>> and produce those converted images via
onvert the bitmap;
>>
>> This seems sensible; Sphinx should directly handle the source format we
>> want to use for images/diagrams.
>>
>>> 3) if possible, add an extension to trick Sphinx for it to consider the
>>> output dir as a source dir too.
>
d directly handle the source format we
> want to use for images/diagrams.
>
>> 3) if possible, add an extension to trick Sphinx for it to consider the
>> output dir as a source dir too.
>
> Or to provide an additional source path and point that at the output
> direc
\endtemplate
> >
> > l.21429 \unskip}\relax \unskip}
> >\relax \\
> > ?
> >
> > This patch fixes the issue:
> >
> > https://git.linuxtv.org/mchehab/experimental.git/commit/?h=dirty-p
On Mon, Nov 07, 2016 at 07:55:24AM -0200, Mauro Carvalho Chehab wrote:
> 2) add an Sphinx extension that would internally call ImageMagick and/or
>inkscape to convert the bitmap;
This seems sensible; Sphinx should directly handle the source format we
want to use for images/diagrams.
&
xes the issue:
>
> https://git.linuxtv.org/mchehab/experimental.git/commit/?h=dirty-pdf&id=b709de415f34d77cc121cad95bece9c7ef4d12fd
>
> That means that Sphinx is not generating the right LaTeX output even for
> (some?) PNG images.
\includegraphics normally works just fine for
Em Mon, 07 Nov 2016 12:53:55 +0200
Jani Nikula escreveu:
> On Mon, 07 Nov 2016, Mauro Carvalho Chehab wrote:
> > Hi Jon,
> >
> > I'm trying to sort out the next steps to do after KS, with regards to
> > images included on RST files.
> >
> > The issue
On Mon, 07 Nov 2016, Mauro Carvalho Chehab wrote:
> Hi Jon,
>
> I'm trying to sort out the next steps to do after KS, with regards to
> images included on RST files.
>
> The issue is that Sphinx image support highly depends on the output
> format. Also, despite TexLi
Hi Jon,
I'm trying to sort out the next steps to do after KS, with regards to
images included on RST files.
The issue is that Sphinx image support highly depends on the output
format. Also, despite TexLive support for svg and png images[1], Sphinx
doesn't produce the right LaTeX comma
Le vendredi 28 octobre 2016 à 14:14 +0200, Michael Haardt a écrit :
> I am currently developing a new image v4l2 sensor driver to acquire
> sequences of still images and wonder how to interface that to the
> v4l2 API.
>
> Currently, cameras are assumed to deliver an endless s
I am currently developing a new image v4l2 sensor driver to acquire
sequences of still images and wonder how to interface that to the
v4l2 API.
Currently, cameras are assumed to deliver an endless stream of images
after being triggered internally with VIDIOC_STREAMON. If supported by
the driver
On 2016-09-14 23:00:33 +0300, Laurent Pinchart wrote:
> Hi Niklas,
>
> On Wednesday 14 Sep 2016 21:27:33 Niklas Söderlund wrote:
> > On 2016-09-14 02:17:04 +0300, Laurent Pinchart wrote:
> > > From: Kieran Bingham
> > >
> > > The partition algorithm needs to determine the capabilities of each
>
Hi Niklas,
On Wednesday 14 Sep 2016 21:27:33 Niklas Söderlund wrote:
> On 2016-09-14 02:17:04 +0300, Laurent Pinchart wrote:
> > From: Kieran Bingham
> >
> > The partition algorithm needs to determine the capabilities of each
> > entity in the pipeline to identify the correct maximum partition w
On 2016-09-14 02:17:04 +0300, Laurent Pinchart wrote:
> From: Kieran Bingham
>
> The partition algorithm needs to determine the capabilities of each
> entity in the pipeline to identify the correct maximum partition width.
>
> Extend the vsp1 entity operations to provide a max_width operation an
From: Kieran Bingham
The partition algorithm needs to determine the capabilities of each
entity in the pipeline to identify the correct maximum partition width.
Extend the vsp1 entity operations to provide a max_width operation and
use this call to calculate the number of partitions that will be
Just like on dvb-raw-vbi.rst, the LaTeX output doesn't work
well with cell spans. Also, this is actually a note, so, move
it to a footnote.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/media/uapi/v4l/dev-sliced-vbi.rst | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff -
Hi Oliver,
On Thursday 19 March 2015 20:31:43 Oliver Lehmann wrote:
> Hi Laurent,
>
> I took the first option ;)
>
> http://pastebin.com/7YUgS2Zt
I have good news and bad news.
The good news is that the camera seems to support capturing video in 1920x1080
natively, which is higher than the 72
Hi Laurent,
I took the first option ;)
http://pastebin.com/7YUgS2Zt
Regards, Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Oliver,
On Thursday 19 March 2015 19:17:48 Oliver Lehmann wrote:
> Hi Laurent,
>
> Laurent Pinchart wrote:
> > Could you please post the output of "lsusb -v" for your camera (running as
> > root if possible) ?
>
> No lsusb on FreeBSD but usbconfig - I hope the results are similar or are at
>
Hi Laurent,
Laurent Pinchart wrote:
Could you please post the output of "lsusb -v" for your camera (running as
root if possible) ?
No lsusb on FreeBSD but usbconfig - I hope the results are similar or are at
least close to what you are seeking for.
http://pastebin.com/s3ndu63h
Regards, Oli
is? Looking at the
> Microsoft so vry "technical" data sheet it says, it is compatible with
> Android. So, it hints at it being a UVC camera.
>
> As for the actual question, I have no idea how they implement still
> images: the UVC standard defines two methods for high
Hi Oliver,
On Thursday 19 March 2015 06:57:24 Oliver Lehmann wrote:
> Hi Guennadi,
>
> Guennadi Liakhovetski wrote:
> > As for the actual question, I have no idea how they implement still
> > images: the UVC standard defines two methods for higher-resolution still
>
Hi Guennadi,
Guennadi Liakhovetski wrote:
As for the actual question, I have no idea how they implement still
images: the UVC standard defines two methods for higher-resolution still
image capture: either using the "still image trigger control" or a
dedicated bulk pipeline (and
in either case I'd be interested to know details of this camera. Can you
find out what driver is serving it, what standard it is? Looking at the
Microsoft so vry "technical" data sheet it says, it is compatible with
Android. So, it hints at it being a UVC camera.
As for the
is only available for snapshot pictures. The highest resolution
supported for videos is 720p.
All I want is recording snapshot images and I do not need the video
capability at all.
I wonder how I can capture those big 8MP images? With mplayer I'm
only able toe capture 720p at max. I guess because m
the cameras to 15fps using VIDIOC_S_PARM. This reduces the
> frequency of corrupt images.
> I zero fill any structs before using ioctl with the #define CLEAR(x)
> memset(&(x), 0, sizeof(x)) macro.
> I use select() before VIDIOC_DQBUF.
> I copy the buffer and create the resulting
Hello Alaganraj,
thank you very much for your reply and your tips. I tried to improve my
code as you suggested and also implemented several other things, which
should improve the result.
I set the cameras to 15fps using VIDIOC_S_PARM. This reduces the
frequency of corrupt images.
I zero fill any
l(fd, VIDIOC_S_FMT, &fmt);
if (ret < 0)
printf("VIDIOC_S_FMT failed: %d\n", ret);
Please find comments in-line.
On Tuesday 02 September 2014 05:36 PM, Mácha, Karel wrote:
> Hello,
>
> I would like to grab images from multiple cameras under using the V4L2
>
Hello,
I would like to grab images from multiple cameras under using the V4L2
API. I followed the presentation under found on
http://linuxtv.org/downloads/presentations/summit_jun_2010/20100206-fosdem.pdf
used the code and adapted it sightly for my purpose. It works very well
for 1 camera
On Apr 25, Steve Cookson wrote:
[..]
>
> If the DVC100 and ImpactVCB-e had had the same love and attention that
> Ezequial has shown the EasyCap would they outperform it?
>
I really appreciate the kind words and I'm happy to see the driver is being
used and works well.
However, to be fair, the
n Toth wrote:
>> On Fri, Apr 25, 2014 at 8:19 AM, Steve Cookson wrote:
>>>
>>> Hi Guys,
>>>
>>
>> Hello again.
>>
>>>
>>> (I'm copying Ezequial on this because of the work he has done on the
>>> stk1160).
>&
has done on the
>> stk1160).
>>
>> My colleague (a Doctor) had this to say on the medical images I posted
>> earlier (see below):
>>
>> > The impactVCB-e image is redder and less clear. The dvc100 and easycap
>> > seem similar to me and both of t
Hi Guys,
(I'm copying Ezequial on this because of the work he has done on the
stk1160).
My colleague (a Doctor) had this to say on the medical images I posted
earlier (see below):
> The impactVCB-e image is redder and less clear. The dvc100 and
easycap seem similar to me and both
Hi Guys,
I would be interested in your views of the comparisons of these images.
The still is the image of a duodenum taken during an endoscopy and
recorded to a DVD player (via an s-video or composite cable). Although
the endoscope is an HD endoscope, the DVD recorder isn't an
The minimum width and height for VPE input/output was kept as 128 pixels. VPE
doesn't have a constraint on the image height, it requires the image width to
be at least 16 bytes.
Change the minimum supported dimensions to 32x32. This allows us to de-interlace
qcif content. A smaller image size than
On 03/11/14 09:33, Archit Taneja wrote:
> The minimum width and height for VPE input/output was kept as 128 pixels. VPE
> doesn't have a constraint on the image height, it requires the image width to
> be at least 16 bytes.
>
> Change the minimum supported dimensions to 32x32. This allows us to
>
The minimum width and height for VPE input/output was kept as 128 pixels. VPE
doesn't have a constraint on the image height, it requires the image width to
be at least 16 bytes.
Change the minimum supported dimensions to 32x32. This allows us to de-interlace
qcif content. A smaller image size than
The minimum width and height for VPE input/output was kept as 128 pixels. VPE
doesn't have a constraint on the image height, it requires the image width to
be at least 16 bytes.
Change the minimum supported dimensions to 32x32. This allows us to de-interlace
qcif content. A smaller image size than
s
the image width to be atleast 16 bytes.
"16 bytes" - shouldn't it be pixels? (also "at least" :) )
I can correct it when applying the patch if the above is the case.
VPDMA IP requires the line stride of the input/output images to be at
least 16 bytes in total.
This
1 - 100 of 146 matches
Mail list logo
