No sound after stop problem
Hello all, I’m quite new to MAX.
I have installed MAX/MSP on my laptop, but I have a problem:
Whenever a "stop" message is sent (both with "stop" or toggle on a dac~) all sound goes dead… nothing in the audio tester, no way to get sound with "start" "startwindow". These work only once, but if a stop message is sent it all goes dead. Only solution is to close MAX and open it again.
My cnfiguration is:
Windows XP Home with service pack 2 (ver.5.1.2600)
fast processorm, 1 GB RAM.
MAX/MSP 4.5 and 4.6 (tried both…).
Latest Quicktime installed
I have an internal AC’97 and external USB soundcard and the problem happens with both. Have unsuccessfully tried:
- changing (playing with..) "driver" and "output" settings in the DSP window
- The problem happens both with MAX/MSP version 4.5 and 4.6
- Getting the latest DirectX drivers…
Please any experienced user or anybody with same problem who managed to find a solution please help
thanks a lot
I don’t know if it suits your situation or not but I remember seeing the cause of this problem as a "trial software limitation" on this board. It was pointed out that this was the behaviour of the trial version of max/msp.
I really do not know if this is the case for you, or not.
> I really do not know if this is the case for you, or not.
Not really; in fact I have a regulary registered and authorised copy.
Thanks the same for your help
Thanks for suggesting ej
Actually no… works fine in Runtime :-|
Guess I’ll have to contact support. I wonder how that could be?
On 13 nov. 06, at 11:19, lorenzo wrote:
> Thanks for suggesting ej
> Actually no… works fine in Runtime :-|
That confirm the authorisation problem.
Actually the copy is authorised….
anyway as you suggested I contacted support.
On 13 nov. 06, at 12:43, lorenzo wrote:
> Actually the copy is authorised….
I didn’t say the invert… It’s just there’s some problem related to
PACE authorisation on your machine.
I see. I emailed support, hoping they might have a solution. Thanks again for your help.
In the end it looks like it was a response problem. Seems to work now.