Patchsets that need review by experienced Wine Developers
most at museresearch.com
Fri Jan 4 14:38:59 CST 2013
We at Muse Research are happy help move our patches from custom one-offs
to the main fork. Background info below...
>>> The original patches/sources (that i have based my version on, are
>>> found here: http://www.museresearch.com/support/receptor-faq.php
>>> ...at the bottom of the page / last link:
>> I looked over them briefly.
>> Not sure why this is needed?
> I'm not sure why either, but i am guessing it improves things in a
> linux-rt/VST setting (in fact, removing it causes regressions on my
> L_pa systems - so i am keeping it.
This is a really old patch. IIRC there were different long filenames
that were being converted to the same 8.3 filename. I don't have more
>> a user32.EnableWindow 2008 patch ... is it still needed for you,
>> as quite some enhancements have happened...
>> Would need review (likely from julliard or other user32 guru)
>> and testcases.
> Seems to be, yeah.
This fixed a problem where FM8's 'save' window would get stuck. Once you
opened and cancelled it, any mouse click would open it again.
>> A new synchronization method using UNIX pipe(2)s.
>> This is definitely not going in as is...
> Figured as much :) (that was pretty obvious lol.)
>> It would be interesting to know what deficit in regular Wine is
>> fixed by it. wineserver overhead?
> Yeah, Wineserver is probably the number one thing that slows down
> when, when you are looking for low-latency / high-performance. (ext4
> is also terrible on stock settings).
This removes key synchronization calls from the wineserver and keeps
them on the app side. Without it realtime performance is impossible. We
developed this with Codeweavers, and they were pretty sure it wasn't
general enough for the main fork.
>> Remove the MUSE specific fixmes and use the same FIXME() style
>> for stub parameters as in the other FIXME()s. Then
>> its ready for wine-patches I would say.
> Awesome :) I must have missed that ~ you will notice that i removed
> them from the new variables used by L_ (didn't want any
> hassles/trademark issues with Muse).
Don't worry, no problem with us! This was helpful in getting Pace CDRM
ilok support to work.
>> Use same FIXME() style as used for other stub functions, then
>> ready for submission.
>> Good for submission as-is.
> Great. :)
Ditto from 0023.
>> Not submittable as-is ...
>> It would be good to know the reason and/or what MUSE expects.
> You can contact them. They don't seem to get the idea of FOSS - by
> having our help, they could have _Less_ of a delta they are keeping.
> But as far as this patch is concerned, i am not sure. (this is why i
> got in touch with you guys).
This is internal and not generally useful.
>> Smells like the wrong place to do it. Perhaps mountmgr.sys,
>> but perhaps different.
>> Also unclear if Alexandre likes it.
> I think for their purposes it probably is though, so i have kept it as
> well (for now, unless told that i shouldn't for good reason).
This one is internal too.
>> Looks already good for submission to me.
> Yeah, it fixes BIG hassles for N.I users like myself.
>> Needs design and discussion... So far a RT solution
>> was not accepted for Wine yet.
> Yeah - that is in fact, one of the most important patches for us
> (linuxaudio folks). The FSThost developer (wraps wineVSTs, single
> hosted) said it is the 'holy grail' for fixing his software to
> properly handle windows VSTs and it does so very well :) ~ windows
> VSTs are highly performant, synchronized and run like normal
> Jack_cleints without wineserver getting in the way.
Same as above, moving sync calls out of the wineserver is the only way
to use Wine for realtime audio applications. Especially with more
complicated plugins like Kontakt.
This fixed a compiler problem when cross compiling a 32bit winelib
application on a 64bit system. The messages were:
> /usr/include/wine/windows/rpcndr.h:176:16: error: ‘_MIDL_STUB_MESSAGE’ has a
> field ‘_MIDL_STUB_MESSAGE::SavedContextHandles’ whose type uses the anonymous
> namespace [-Werror]
> /usr/include/wine/windows/rpcndr.h:479:16: error: ‘_SCONTEXT_QUEUE’ has a field
> ‘_SCONTEXT_QUEUE::ArrayOfObjects’ whose type uses the anonymous namespace
>> local hacks
Yep. One-offs for us.
>> Seems like a mistaken patch that was needed as we had
>> the old DIB sections.
>> gdb would have accepted "continue" here.
>> Should not be necessary anymore these days with the
> Okay, i will try reverting it locally and make sure everything is good.
Yes to all of that. I just hated having to hit CONTINUE all the time.
And, right, my understanding is that the DIBENGINE no longer uses the
same tricks with memory that it used to.
>> Might be submittable as-is.
>> Might need autoconf checks for non-Linux.
> good. but i am not the guy to do this ~ i have a _ton_ of work right
> now, both professionally and for my own projects. I just wanted to
> make sure anything that _should_ be in wine goes into Wine to improve
> the experience for everyone.
Ditto that on the "busy" thing. ;)
>> Alexandre usually does not like override files
>> like this unless necessary.
>> What is actually expected? you mentioned rendering issues?
> I am not sure about this one. it needs investigating but i have it
> applied. As far as rendering issues, yes upstream wine causes ugly
The drive geometry from a disk wasn't being reported correctly or
consistently. It caused problems with SampleTank from IK Multimedia.
> flickering in some apps/VSTs, while L_pa-Wine does not (at all, ever).
>> Hmm, needs user32 windowing guru review.
The 'prefs' menu from SampleTank wasn't opening with Metacity.
Old bugzilla notes say "It comes down to the WS_DLGFRAME|WS_THICKFRAME
flags. If they are both present then the window is not visible. Turn on
or the other off in the example and the window shows up.
The second window must have a parent and have the WS_OVERLAPPED style as
Hope that helps.
-- Michael Ost
Muse Research and Development
More information about the wine-devel