- Oct 18, 2019
-
-
Marvin Scholz authored
DOLT (provides doltlibtool and doltcompile to make compilation faster by not always running full libtool) does not handle --with-pic at all, so even when PIC is requested, it won't use it. As a workaround manually add it to X86ASMDEFS.
-
Marvin Scholz authored
This reverts commit 508e3db7.
-
Marvin Scholz authored
This fixes meson build issues when cross-compiling for iOS.
-
Marvin Scholz authored
The libtool in extras/tools has additional patches that are needed to build with llvm-mingw.
-
Steve Lhomme authored
We need to keep a local copy of the pool configuration now. + rename DestroyVideoDecoder to ReleasePoolSurfaces
-
Steve Lhomme authored
-
Steve Lhomme authored
Only D3D11 was using it and it doesn't make sense in push.
-
Steve Lhomme authored
va_surface is always set in picture context reindent after external pool removal
-
Steve Lhomme authored
We can push pictures to the display with zero copy as this is the same device.
-
Steve Lhomme authored
vout_device_configuration_t is for device configuration vout_configuration_t is for display configuration
-
Steve Lhomme authored
We don't need a full vout_configuration_t for that, only the vout object and the video_format_t to initialize the window size.
-
Steve Lhomme authored
instead of the decoder device
-
Steve Lhomme authored
We might store a reference to the VA module so the destructor of the module is not called while the video context is used.
-
Steve Lhomme authored
-
Steve Lhomme authored
-
Steve Lhomme authored
-
Steve Lhomme authored
-
Steve Lhomme authored
-
Steve Lhomme authored
For now they don't create one.
-
Steve Lhomme authored
-
Steve Lhomme authored
Each video context can store extra objects, like the IDirect3DDevice9* for D3D9, which is not found in the decoder device.
-
Steve Lhomme authored
It's kept in the input resources and will come embedded in the video context.
-
Steve Lhomme authored
Decoders that don't use a decoder device don't need to create one in the first place.
-
Steve Lhomme authored
-
Steve Lhomme authored
-
Steve Lhomme authored
The pictures are similar to the ones created in the OpenGL converter.
-
Steve Lhomme authored
-
Steve Lhomme authored
And remove the locally held decoder device that used to come from the picture_sys_t.
-
Steve Lhomme authored
rather than the picture_sys
-
Steve Lhomme authored
rather than the picture_sys
-
Steve Lhomme authored
This is used to initialize the VA instead of the picture_sys_t from the external decoder pool.
-
Steve Lhomme authored
Only call decoder_GetDecoderDevice() in lavc_UpdateVideoFormat(). The decoder_UpdateVideoOutput() is done afterwards. After the call to lavc_UpdateVideoFormat() the received decoder device holds an extra reference that needs to be released after the VA is created. decoder_NewPicture() cannot be used until decoder_UpdateVideoOutput() is called. So this patch temporarily breaks va modules relying on the picture_sys_t data that used to be passed. It will be via the decoder device we just got.
-
Steve Lhomme authored
This is how the VA's will be probed when multiple outputs are possible.
-
Steve Lhomme authored
The video context will be passed to various modules up to the display where it will be ultimately released when the last associated picture will be released. It needs to be refcounted and we need a destructor to do this final release. By default the video context holds a reference to the matching decoder device. This reference is released with the video context.
-
Steve Lhomme authored
-
Steve Lhomme authored
Rather than telling the resource storage if the vout needs to be stopped in some way. Incidentally the vout_Cancel is not needed anymore since the vout_StopDisplay, which is now used, destroys the picture pool.
-
Steve Lhomme authored
First handle the resources needed by the get_device() call, then the format_update() which creates the display. The on_vout_started is only notified when the vout is really started. Rename vout_thread_added to vout_thread_started.
-
Steve Lhomme authored
It may not work, in which case a new display/thread should be created to handle the new format. No functional changes.
-
Steve Lhomme authored
This is the real event the player is looking for. It doesn't care if a vout has been created but is dormant. No functional changes.
-
Steve Lhomme authored
To create the vout and decoder device we don't need to know the DPB. For now the display still holds the picture pool so the display still needs the DBP size.
-