http://bugs.winehq.org/show_bug.cgi?id=21589
Summary: MacOS error from MIDI SetVolume Product: Wine Version: 1.1.36 Platform: x86 OS/Version: Mac OS X 10.5 Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winmm&mci AssignedTo: wine-bugs@winehq.org ReportedBy: hoehle@users.sourceforge.net
Created an attachment (id=26043) --> (http://bugs.winehq.org/attachment.cgi?id=26043) console output during tests
Hi,
The midi tests now in git that will appear with wine-1.1.38 produce a strange error on MacOS: err:wave:AudioUnit_GetVolume AudioUnitGetParameter return an error "\xff\xff\xd5\x8e" Same error for SetVolume
a) Is dbg_fourcc() really the appropriate method for reporting error codes there? It rather looks like a small negative number: -10866 aka. kAudioUnitErr_InvalidScope
b) The same function succeeds when called from waveGetVolume in tests/wave.c on a wave handle instead of a MIDI one. Perhaps the MacOS MIDI SW-synth does not support volume settings after all?
Perhaps a more elaborate filter graph would be needed to support variable volumes? One would then question whether MIDICAPS_VOLUME need be reported at all in such a case and possibly drop support for Get/SetVolume in midi.c -- or implement said filter graph. This is just supposition. I'm not familiar with MacOS programming.
http://bugs.winehq.org/show_bug.cgi?id=21589
--- Comment #1 from Jörg Höhle hoehle@users.sourceforge.net 2010-09-24 06:39:25 CDT --- I found 2 interesting links on the topic of OSStatus as integer vs. fourcc:
http://zathras.de/angelweb/blog-carbon-for-the-cocoa-guy-oserror.htm "some CoreAudio developer didn't understand that error codes are supposed to be numbers, and actually used a FourCharCode for some errors." http://stackoverflow.com/questions/2196869/how-do-you-convert-an-iphone-osst...
as well as one function which may turn an OSStatus into text: CoreServices/CarbonCore/Debugging.h const char* GetMacOSStatusCommentString(OSStatus err);
http://bugs.winehq.org/show_bug.cgi?id=21589
--- Comment #2 from Jörg Höhle hoehle@users.sourceforge.net 2011-01-13 05:53:00 CST --- commit 2e54019391572d354d9a3295ee941df3cb536897 fixed a) the fourcc message
b) is about the typical tension between - be internally consistent: given no support for XYZ in Wine, e.g. volume, don't set the corresponding capabilities flag, e.g. MIDICAPS_VOLUME; (somehow figure out good error code to return)
- lying to the app and pretend volume is supported, presumably because that's always the case in native (or native always lies as well?) and apps behave badly when presented fewer flags; possibly add FIXME() + stub message
- going to extra hoop to match both sides, e.g. add a volume filter into the MIDI audio chain (which only makes sense with a SW synth). This would be superfluous with PulseAudio which already provides easy per app volume control, but I've not seen that for MacOS' SW-synth.
BTW, the native MIDI volume setting is tied to the audio/mixer control panel in system preferences when the SW synthesizer is in use.
http://bugs.winehq.org/show_bug.cgi?id=21589
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Mac OS X 10.5 |Mac OS X
http://bugs.winehq.org/show_bug.cgi?id=21589
--- Comment #3 from Austin English austinenglish@gmail.com 2013-11-13 16:50:32 CST --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.6 or newer) wine? If so, please attach the terminal output in 1.7.6 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=21589
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #4 from Austin English austinenglish@gmail.com --- Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=21589
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org