October 2023 - wine-gitlab

Re: [PATCH v2 0/2] MR4108: Improve DMI tables under Linux.
by eric pouech (＠epo) 20 Oct '23

20 Oct '23

On Thu Oct 19 14:52:17 2023 +0000, Hans Leidekker wrote: > sd_id128_get_machine_app_specific() requires cooperation from the app. > That's not something we can expect from Windows apps. Windows apps > should treat this information with confidentiality just like Linux apps. > The game whose name I forgot collected several more or less unique IDs > and calculated a hash over those values. I'm referring to Unix apps. was the game Project Kunai? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4108#note_49382

1 0

[PATCH v2 0/3] MR4073: msxml3: Stop possible typelib out of bounds access (Coverity)
by Alistair Leslie-Hughes (＠alesliehughes) 20 Oct '23

20 Oct '23

typelib has an array size of 2 (eg LibXml_Last), so a lookup of IID_NULL will result in a lookup of the third index. -- v2: msxml3: Free IBindCtx on error paths (Coverity) msxml3: Move tid_NULL out of possible enum values. msxml3: Dont call qsort if we have no data (Coverity). https://gitlab.winehq.org/wine/wine/-/merge_requests/4073

2 3

[PATCH 0/1] MR4148: advapi32/tests: Add ReadEventLogW tests for direction.
by Daniel Lehman (＠dlehman25) 20 Oct '23

20 Oct '23

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/4148

2 1

[PATCH v4 0/5] MR408: vkd3d-shader/dxil: Implement constant buffer loads.
by Conor McCarthy (＠cmccarthy) 20 Oct '23

20 Oct '23

-- v4: vkd3d-shader/dxil: Implement the DXIL EXTRACTVAL instruction. vkd3d-shader/spirv: Support scalar swizzle of vector SSA registers. vkd3d-shader/dxil: Implement DX instruction CBufferLoadLegacy. vkd3d-shader/dxil: Implement DX instruction CreateHandle. vkd3d-shader/dxil: Replace register_address_init() with register_index_address_init(). https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/408

2 6

Re: [PATCH v13 0/7] MR3938: winegstreamer: Implement CLSID_CMpegVideoCodec
by Alfred Agrell (＠Alcaro) 20 Oct '23

20 Oct '23

On Mon Oct 16 23:45:47 2023 +0000, Zebediah Figura wrote: > This may be correct (although I'm curious if it actually matters here?) > but should be a separate patch. It does matter, gst_pad_push returns GST_FLOW_NOT_NEGOTIATED if I omit it. Separate commit, sure, if you say so. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3938#note_49357

1 0

Re: [PATCH v13 0/7] MR3938: winegstreamer: Implement CLSID_CMpegVideoCodec
by Alfred Agrell (＠Alcaro) 20 Oct '23

20 Oct '23

On Fri Oct 20 01:24:23 2023 +0000, Zebediah Figura wrote: > Hi, really sorry about the very late review on this one (I was out for a > while, and then spent a lot of time catching up on review while I was > out, and then trying to get some more important Wine work done...) > 2/7, seeking parts aside, is broadly doing the right thing (from my > perspective) but I would like to see it arranged differently. What I > would like to see is something like the following, in a series of > individual patches: > * Introduce a wg_parser_create option to use the encoded format; this > should end up being translated to "chain_decodebins" basically as you > have it. I would also rename that to something like "output_compressed" > (with inverted meaning). > Note that in this case autoplug-continue already does what we want, > you shouldn't need to set the "caps" property on top of that. > * Use this property, plus WG_PARSER_DECODEBIN, in the existing frontend > instead of WG_PARSER_MPEGAUDIOPARSE. Delete WG_PARSER_MPEGAUDIOPARSE. > * Ideally patch 1/7 should be moved from the beginning of the series to here. > * Add MPEG-1 system stream support to the quartz frontend. Yes, IRL stuff is always in the way (from us internet folks' perspective), and code review isn't the most exciting task. I don't understand the point of that autoplug-continue handler. It looks like it says "yep, I want this" for certain formats, then it turns around and says "no, I don't want this after all, decode it again" in the pad-added signal. I'm sure that complexity exists for some reason, otherwise someone would've deleted it long ago, but... But I don't need to understand it, as long as someone does. This took me longer to implement than I expected, didn't expect you to be this thorough. Sure helps to have a pair of fresh eyes on it. Worth the wait (though it would've helped to have known how long it'd take). I think I fixed everything (except those with follow-up questions), but some changes are pretty big and/or not exactly what you were thinking of, so I suspect you'll have another set of remarks. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3938#note_49356

1 0

Re: [PATCH v13 0/7] MR3938: winegstreamer: Implement CLSID_CMpegVideoCodec
by Alfred Agrell (＠Alcaro) 20 Oct '23

20 Oct '23

On Mon Oct 16 23:46:02 2023 +0000, Zebediah Figura wrote: > Can you please also check (at least the return value of) > IMediaSample::GetMediaType()? I'm rather curious if it's updated or not. It just returns S_FALSE every frame (which means unchanged since previous sample). Sure, let's test it, no reason not to. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3938#note_49355

1 0

Re: [PATCH v13 0/7] MR3938: winegstreamer: Implement CLSID_CMpegVideoCodec
by Alfred Agrell (＠Alcaro) 20 Oct '23

20 Oct '23

On Mon Oct 16 23:46:01 2023 +0000, Zebediah Figura wrote: > Shouldn't we get an exact number of frames here? Or is that not > consistent somehow? Yes, it's inconsistent. Wine emits two frames; native only emits one, probably because the graph is paused. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3938#note_49354

1 0

Re: [PATCH v13 0/7] MR3938: winegstreamer: Implement CLSID_CMpegVideoCodec
by Alfred Agrell (＠Alcaro) 20 Oct '23

20 Oct '23

On Mon Oct 16 23:45:59 2023 +0000, Zebediah Figura wrote: > If Windows never sets the sample time for video samples after the first > then we should probably make this check more restrictive to explicitly > check that. It's Complicated™ (Apologies if you know some of this already, better too much information than too little.) The MPEG video format contains two layers of framing - the program stream tells which bytes are audio and which are video, but it's just arbitrarily arranged bytes, with no relation to video frame boundaries. Windows' MPEG splitter parses the program stream, reads the first few bytes of the video stream (the codec data) to determine image size, and emits that. Determining the frame boundaries is the video codec's job. GStreamer's mpegpsdemux doesn't read the codec data because why would it. To make the splitter's media type contain image size, I needed to put the mpegvideoparse on this side. Which means that, unlike Windows, each submitted packet is exactly one frame. ``` Windows video0 hr=00000000 len=1214 audio0 hr=00000000 len=2037 audio1 hr=00000000 len=2037 audio2 hr=00000000 len=2025 audio3 hr=00000000 len=2025 audio4 hr=80040249 len=653 Wine video0 hr=00000000 len=859 audio0 hr=00000000 len=1253 video1 hr=80040249 len=195 audio1 hr=00000000 len=1254 video2 hr=80040249 len=84 audio2 hr=00000000 len=1254 video3 hr=80040249 len=76 audio3 hr=00000000 len=1254 audio4 hr=00000000 len=1254 audio5 hr=00000000 len=1254 audio6 hr=00000000 len=1254 ``` Yes, it's messy, but I don't think we can do any better unless I move the mpegvideoparse into the codec object. Which would be more accurate to native, but it would require writing my own decoder for the codec data, would require reintroducing <https://gitlab.winehq.org/wine/wine/-/merge_requests/3938#note_46588>, and would improve nothing except our test suite. That said, the VFW_S_NO_STOP_TIME check catches nothing. I'll drop it. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3938#note_49353

1 0

Re: [PATCH v13 0/7] MR3938: winegstreamer: Implement CLSID_CMpegVideoCodec
by Alfred Agrell (＠Alcaro) 20 Oct '23

20 Oct '23

On Mon Oct 16 23:45:56 2023 +0000, Zebediah Figura wrote: > This probably needs to take the filter CS. Same for Info() for that matter. You sure? There's no reference to filter_cs in dlls/quartz/ or dlls/winegstreamer/, except in VMR; it's mostly used in libs/strmbase/. Is this specific interface different? Or maybe they're all buggy? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3938#note_49352

1 0

2025

2024

2023

2022

wine-gitlab October 2023