[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-dev] [win32] discard SCSpawn?
I downloaded the new release but I am unable to start it...
The previous one was ok...
I think that now I should start Pycollider only or am I wrong ?
If I try to start the Scsynth alone, the same error appears...
When I do so I obtain:
Traceback (most recent call last):
File "Psycollider.py", line 62, in ?
File "PySCLang.pyo", line 9, in ?
File "PySCLang.pyo", line 7, in __load
ImportError: DLL load failed: Impossibile avviare l'applicazione specificata. La
configurazione dell'applicazione non Þ corretta. Una nuova installazione dell'a
pplicazione potrebbe risolvere il problema.
Sorry for the error description in Italian...
All the best
2005/12/13, Christopher Frauenberger <frauenberger@xxxxxx>:
here a patch that implements all changes involved for discarding
SCSpawn. The main issues here are:
* reading the ServerOptions for command line options for scsynth.exe
* the SC_PortAudioDriver now prints all available devices at startup
* the SC_PortAudioDriver reads ServerOption.device and sets input/
* scsynth allows -H option (deviceName) as parameter for windows
* all vc++ projectfiles were updated for use with VC++ Express
edition which is free
* minor changes to comply with the stricter compiler of VC++8
please test the patch against os x and linux.
I have also compiled a new package SC3-Complete with all these
changes and would like to ask people to test this with their hardware
and provide feedback on whether this way of specifying the devices is
practical. As usual available from http://sonenvir.at/downloads/sc3/
sc3-win/ This package should also solve the problems with PySCLang
that people reported back as I didnt use the bundle option for this.
SCSpawn is not needed any longer and you could specify all server
options in the startup.sc to select devices etc. A weak point is that
you need to specify a device name that would match (as substring)
with both, the input and output device as they are handled as
different devices by Port Audio. However, this does seems to work in
most cases well, for example:
at boot the driver tells you you have the following options:
- MME : Microsoft Soundmapper - Input (device #0 with 2 ins 0 outs)
- MME : Realtek AC97 Audio (device #1 with 2 ins 0 outs)
- MME : Microsoft Soundmapper - Output (device #2 with 0 ins 2
- MME : Realtek AC97 Audio (device #3 with 0 ins 2 outs)
and you specify:
s.options.device_("MME : Microsoft Soundmapper");
and it will match the Input and the Output...
PS: sorry zipping the patch, but its rather big mainly because the
conversion of the project files, and it would go through the list...