On 21/09/2010 22:31, Tom Cato Amundsen wrote:
> I've been quite busy, so I feel the release need some testing before a
> announce it more widely than solfege-devel. So please test this
> release, and give a short reply to the list saying if it was OK.
1. The MIDI output in Windows still doesn't work. The list of MIDI
devices is there, there's just no sound, neither via Test button or in
exercises, no matter which device is selected (not even Microsoft GS
Synth). I worked around it using Timidity, but it's still a bug, and
it's there since... well, forever ;-)
2. Starting GNU Solfege (debug) prints this and quits:
PYTHONHOME must not point to locally installed python, for example
C:\Python25 or D:\Python25
Current value:
PYTHONHOME=
Traceback (most recent call last):
File "C:\Program Files\GNU Solfege\bin\solfege", line 82, in <module>
import solfege.startup
File "C:\Program Files\GNU Solfege\share\solfege\solfege\startup.py",
line 64,
in <module>
from solfege.exercises import *
File "C:\Program Files\GNU
Solfege\share\solfege\solfege\exercises\tuner.py",
line 26, in <module>
import solfege.soundcard.solfege_c_midi
File "C:\Program Files\GNU
Solfege\share\solfege\solfege\soundcard\solfege_c_m
idi.py", line 28, in <module>
import _solfege_c_midi
ImportError: No module named _solfege_c_midi
Press any key to continue . . .
There is no binary called _solfege_c_midi.pyd or anything like that in
the installed Solfege tree.
3. There are some files in the distribution that probably aren't
necessary (*.lib, *.a etc)
Krzysztof
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Solfege-devel mailing list
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe", or visit
https://lists.sourceforge.net/lists/listinfo/solfege-devel
