--
v8: vkd3d-shader/spirv: Avoid invalid bool-to-bool conversion in spirv_compiler_emit_movc().
vkd3d-shader/dxil: Implement the DXIL VSELECT instruction.
tests/shader-runner: Add tests for 64-bit casts.
vkd3d-shader/spirv: Return an error if an invalid handler is encountered.
tests/shader-runner: Add a test for float comparisons.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/459
Rémi Bernon (@rbernon) commented about dlls/dmsynth/synth.c:
> struct wave *wave;
> };
>
> +struct fixup
> +{
> + struct list entry;
> + int dst;
> + int src;
> + int flags;
> +
> + int fixup_dst;
> + float amount;
> +};
> +
Instead of a dynamic list, could we have just a simple structure like:
```c
struct gen_increments
{
float env_hold;
float env_decay;
float vol_hold;
float vol_decay;
};
```
Which we would pass around down to `add_mod_from_connection` which would set the needed adjustments (it's actually only needed there, `set_gen_from_connection` won't have to add increments), and then after the loops we would call `fluid_voice_gen_incr` for each of these?
Or do we need the generic version for more fixups that are not in this MR?
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4375#note_52124
--
v5: dmime: Implement segment state repeat and looping.
dmime: Split segment_state_play_chunk helper.
dmsynth: Reset synthesizer defaults on MIDI_SYSTEM_RESET.
dmime: Send MIDI_SYSTEM_RESET message on performance reset.
dmime: Clear all pending messages in IDirectMusicPerformance_Stop.
dmime/tests: Test that IDirectMusicPerformance_Stop clears messages.
dmime/tests: Avoid discarding old notifications in test.
https://gitlab.winehq.org/wine/wine/-/merge_requests/4358
Although they look fine, 20ab5954 (and ec219ce1 even more) cut some notes early in FF VIII intro.
Haven't really looked into the details but 0ff26da7 feels a bit complicated, I'm wondering if there's a better way to do this.
Regarding 2e226c26, is this what native does?
Fwiw I'm thinking that if we want to have a much more robust SF2 / DLS2 mapping, it may be a good thing to have more dmsynth tests. I already added one that does basic sample rendering without checking the output, but maybe we should extend it to compare the rendered samples with various input.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4375#note_52119
On Mon Nov 13 10:09:34 2023 +0000, Yuxuan Shui wrote:
> What errors are you getting?
> I don't think it needs special build instructions? I link it with
> mfplat, mf, ole32 and combase.
First thing is that it's not supported in current mingw-w64. And I'm not sure if building cpp stuff with it will work at all on windows.
The "hit race" condition is not really a race, isn't it? It means callback was called after item was cancelled. That could mean that cancellation does not work, but it's not a problem in call order I think. Regarding managing TP objects, does our rtworkq work correctly on Windows? Maybe we need to fix something on threadpool side.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4243#note_52107