> On 26/05/21 15:09, Lars Knoll wrote:
> > The hope is that we can change that for Qt 6. To make this possible, we
> > have changed not only parts of the public API, but completely redone its
> > internal architecture, especially how multimedia connects to the platform
> > specific backends. Apa
On 28/05/21 11:09, Lars Knoll wrote:
> Before we go into the topics below, can we take a step back, please? I’d
> first like to know *why* you were developing and maintaining your own
> multimedia backend.
In short, because of lifecycle. In Ubuntu Touch, applications are
stopped when in the back
> On 28 May 2021, at 11:31, Tor Arne Vestbø wrote:
>
>
> Cheers,
> Tor Arne
>
>> On 28 May 2021, at 10:54, Samuel Gaist via Development
>> wrote:
>>
>>>
>>> On 28 May 2021, at 10:37, Lars Knoll wrote:
>>>
>>> How have you implemented those? If you implemented a gstreamer element for
>>>
Cheers,
Tor Arne
On 28 May 2021, at 10:54, Samuel Gaist via Development
mailto:development@qt-project.org>> wrote:
On 28 May 2021, at 10:37, Lars Knoll
mailto:lars.kn...@qt.io>> wrote:
How have you implemented those? If you implemented a gstreamer element for
those cameras, and gst-device-m
> On 28 May 2021, at 10:37, Lars Knoll wrote:
>
>> On 28 May 2021, at 10:27, Samuel Gaist wrote:
>>
>>
>>> On 28 May 2021, at 10:09, Lars Knoll wrote:
>>>
On 28 May 2021, at 09:15, Alberto Mardegan
wrote:
Hi Lars,
On 26/05/21 15:09, Lars Knoll wrote:
>
> On 28 May 2021, at 10:27, Samuel Gaist wrote:
>
>
>> On 28 May 2021, at 10:09, Lars Knoll wrote:
>>
>>> On 28 May 2021, at 09:15, Alberto Mardegan
>>> wrote:
>>>
>>> Hi Lars,
>>>
>>> On 26/05/21 15:09, Lars Knoll wrote:
The hope is that we can change that for Qt 6. To make this poss
> On 28 May 2021, at 10:09, Lars Knoll wrote:
>
>> On 28 May 2021, at 09:15, Alberto Mardegan
>> wrote:
>>
>> Hi Lars,
>>
>> On 26/05/21 15:09, Lars Knoll wrote:
>>> The hope is that we can change that for Qt 6. To make this possible, we
>>> have changed not only parts of the public API, bu
> On 28 May 2021, at 09:15, Alberto Mardegan
> wrote:
>
> Hi Lars,
>
> On 26/05/21 15:09, Lars Knoll wrote:
>> The hope is that we can change that for Qt 6. To make this possible, we have
>> changed not only parts of the public API, but completely redone its internal
>> architecture, especial
Hi Lars,
On 26/05/21 15:09, Lars Knoll wrote:
> The hope is that we can change that for Qt 6. To make this possible, we have
> changed not only parts of the public API, but completely redone its internal
> architecture, especially how multimedia connects to the platform specific
> backends. Apa
> > If it matters: I disclaim any copyright for the attached
> > files.
>
> Thanks for the snippet. I think this should be perfectly doable. Connect to
> the signal, then map the QVideoFrame and copy out the Y channel.
One ask that may not be captured anywhere: currently, it is impossible to h
On 27 May 2021, at 16:18, Lars Knoll
mailto:lars.kn...@qt.io>> wrote:
On 27 May 2021, at 15:34, Eike Hein mailto:h...@kde.org>> wrote:
May 27, 2021 2:51 PM, "Samuel Gaist"
mailto:samuel.ga...@idiap.ch>> wrote:
I think one of the main use case I have seen for custom GStreamer pipelines is
to b
> On 27 May 2021, at 15:34, Eike Hein wrote:
>
> May 27, 2021 2:51 PM, "Samuel Gaist" wrote:
>> I think one of the main use case I have seen for custom GStreamer pipelines
>> is to be able to get
>> rtsp or other network streams in Qt applications.
>
> This is my personal use case as well.
On 27 May 2021, at 15:25, Rodrigo Gonçalves de Oliveira
wrote:
Also, this is how I define and change different audio devices ("gst-pipeline:
... audio_sink=\"alsasink device=%1\") on demand.
Are there plans to have an easy way to change the output audio device? Think on
an embedded system,
May 27, 2021 2:51 PM, "Samuel Gaist" wrote:
> I think one of the main use case I have seen for custom GStreamer pipelines
> is to be able to get
> rtsp or other network streams in Qt applications.
This is my personal use case as well. With the addition that I also have
some pipelines where I nee
Also, this is how I define and change different audio devices
("gst-pipeline: ... audio_sink=\"alsasink device=%1\") on demand.
Are there plans to have an easy way to change the output audio device?
Think on an embedded system, within a media app and multiple audio devices,
where the user want to c
> On 27 May 2021, at 14:35, Lars Knoll wrote:
>
>> On 27 May 2021, at 14:25, Eike Hein wrote:
>>
>> May 27, 2021 8:14 AM, "Lars Knoll" wrote:
>>> The one thing I want to avoid is what we had in Qt 5, where you could force
>>> Qt MM to use a
>>> different/custom gstreamer pipeline based on en
> On 27 May 2021, at 14:25, Eike Hein wrote:
>
> May 27, 2021 8:14 AM, "Lars Knoll" wrote:
>> The one thing I want to avoid is what we had in Qt 5, where you could force
>> Qt MM to use a
>> different/custom gstreamer pipeline based on environment variables. That
>> part made maintaining the
>
May 27, 2021 8:14 AM, "Lars Knoll" wrote:
> The one thing I want to avoid is what we had in Qt 5, where you could force
> Qt MM to use a
> different/custom gstreamer pipeline based on environment variables. That part
> made maintaining the
> code base extremely hard. Other than that I’m of cours
> On 26 May 2021, at 17:30, Eike Hein wrote:
>
> Exciting!
>
> Are there any plans to officially support the GStreamer backend on Android
> down the line (with building GStreamer as an acceptable exercise left to the
> user) or would work in that direction be appreciated by the module mainta
On 26 May 2021, at 21:00, Arnaud Vrac
mailto:raw...@gmail.com>> wrote:
Le mer. 26 mai 2021 à 14:11, Lars Knoll
mailto:lars.kn...@qt.io>> a écrit :
[snip]
Hi Lars,
Thanks for the updates. One feature that I've always waited for is the
possibility to list and select audio/subtitle tracks from q
> On 26 May 2021, at 18:14, Jason H wrote:
>
>>> 4. On the removal of QAbstractVideoFilter AND QVideoProbe: Disappointed to
>>> hear this. I previously used this for read-only frames for analysis, i.e.
>>> Barcode reading and object detection. How do we do that now?
>>
>> You can get full acc
Thanks for simplifying that API!
On 26/5/21 10:09 PM, Lars Knoll wrote:
NX support is missing right now, and is planned after 6.2.
As well, a webassembly backend is being contributed based on openAL, for
6.3...
https://codereview.qt-project.org/c/qt/qtmultimedia/+/349515
--
Lorn Potter
F
Le mer. 26 mai 2021 à 14:11, Lars Knoll a écrit :
>
> Hi all,
>
> After 5 months of work, I am now preparing to merge the new API and
> implementation for Qt Multimedia back into the development branch.
>
> You can find the first iteration of a merge commit here:
> https://codereview.qt-project.
> > 4. On the removal of QAbstractVideoFilter AND QVideoProbe: Disappointed to
> > hear this. I previously used this for read-only frames for analysis, i.e.
> > Barcode reading and object detection. How do we do that now?
>
> You can get full access to the video data from a QVideoSink through th
Exciting!
Are there any plans to officially support the GStreamer backend on Android down
the line (with building GStreamer as an acceptable exercise left to the user)
or would work in that direction be appreciated by the module maintainer?
At KDE, we have a couple of apps that use GStreamer AP
> On 26 May 2021, at 16:47, Alexander Akulich
> wrote:
>
> On Wed, May 26, 2021 at 5:25 PM Jason H wrote:
>>
>> 4. On the removal of QAbstractVideoFilter AND QVideoProbe: Disappointed to
>> hear this. I previously used this for read-only frames for analysis, i.e.
>> Barcode reading and obje
> On 26 May 2021, at 16:24, Jason H wrote:
>
>> There are still open issues and gaps in the implementation that need fixing,
>> but the code is now in a decent enough shape to merge it back to dev and
>> continue on that branch. We will however now have everything ready in Qt
>> Multimedia fo
On Wed, May 26, 2021 at 5:25 PM Jason H wrote:
>
> 4. On the removal of QAbstractVideoFilter AND QVideoProbe: Disappointed to
> hear this. I previously used this for read-only frames for analysis, i.e.
> Barcode reading and object detection. How do we do that now?
I second that. QAbstractVideoF
> There are still open issues and gaps in the implementation that need fixing,
> but the code is now in a decent enough shape to merge it back to dev and
> continue on that branch. We will however now have everything ready in Qt
> Multimedia for the 6.2 feature freeze, and will be working with a
> On 26 May 2021, at 14:09, Lars Knoll wrote:
[snip]
> There are still open issues and gaps in the implementation that need fixing,
> but the code is now in a decent enough shape to merge it back to dev and
> continue on that branch. We will however now have everything ready in Qt
> Multimedia
Hi all,
After 5 months of work, I am now preparing to merge the new API and
implementation for Qt Multimedia back into the development branch.
You can find the first iteration of a merge commit here:
https://codereview.qt-project.org/c/qt/qtmultimedia/+/351108
With this, Qt Multimedia is proba
31 matches
Mail list logo
