Plzzz help help… DSP won't start
I had compiled an application of a patch I wrote, everything was working till couple of weeks ago, now when I start it up for some reason I can not get the dsp started.
just can’t turn it on, anyone knows why?
see image attached and please help me if you can, I would really rather not have to go back and recompile the patch !!
All those error messages complaining about the absence of adstatus don’t
look at all good, and will make whatever the DSP status window says
entirely fictional, AFAIK.
Have you tried reintsalling the runtime? Does the patch still work
> Hey guys, I had compiled an application of a patch I wrote,
> everything was working till couple of weeks ago, now when I start it
> up for some reason I can not get the dsp started. just can’t turn it
> on, anyone knows why?
> see image attached and please help me if you can, I would really
> rather not have to go back and recompile the patch !! thank you David
Thanks for the quick response,
yeah I have reinstalled the environment, I also can’t check now if the patch works in max, but I had programmed it in the latest version of max and everything was working fine, so I’m not sure what happened !!
If you don’t use externals, try to just open the original patch (not the
application) with Max 5 or Max 5 Runtime. Let us know if that works.
> Thanks for the quick response,
> yeah I have reinstalled the environment, I also can’t check now if the patch
> works in max, but I had programmed it in the latest version of max and
> everything was working fine, so I’m not sure what happened !!
I’ll try it when I get home and let you know.
yeah I am using externals
> I’ll try it when I get home and let you know.
> yeah I am using externals
Then, you may need updated versions of your externals (UI externals for
sure, the others may work even if they were intended for Max 4).
Try maxobjects . com for updates.
Jan 28th update: Audio Freeze – From Melody to Harmony
thanks for the help, but I don’t think that’s the issue, you see I did include all the externals and indeed they were working perfectly for max 5.
Also, the application itself was working perfectly until about 2 weeks ago !!
I will try including the dsp abstraction.
one thing is that I had originally programmed it and compiled the application while I had my firewire sound card connected, although it did work after that without that sound card, I suspect that there is a problem there.
I will try your suggestions and then let you know of the outcome.
i have had this happen a couple of times.
do you use the standalone-object?
do you create a preference file with a name specific to that
that usually helped me sort this kind of trouble.
Am 31.01.2009 um 01:23 schrieb David:
> thanks for the help, but I don’t think that’s the issue, you see I
> did include all the externals and indeed they were working perfectly
> for max 5.
> Also, the application itself was working perfectly until about 2
> weeks ago !!
> I will try including the dsp abstraction.
> one thing is that I had originally programmed it and compiled the
> application while I had my firewire sound card connected, although
> it did work after that without that sound card, I suspect that there
> is a problem there.
> I will try your suggestions and then let you know of the outcome.
> thanks again
I have experienced what *might* be a related problem, though I am not sure that it would explain why an app you generated would work ok for some time then stop working unless there was a system interaction involved.
In any case, starting the dac automatically (ie via loadbang) on load does not appear to work. I can not get a patch to start audio with a loadbang without additionally stopping audio and starting it (via delays), or, delaying the start message.
Illustration attached. Interested if anyone else can reproduce or explain. This may be system related so for the benefit this is with 5.0.5 (36470) running on a early 2008 MacBook pro with 10.5.5.
----------begin_max5_patcher---------- 823.3oc0X00aaBCE84jeEV7xjlxh3hs4i8xz9cLUM4.tDuQrivF0lU09aefA ZSRaZnPf19Bj6013y83qO95b27YNqT2x0Nnui9EZ1r6lOal0UkiYM1yb1vtM NioscyYCWqYobmE0sY32Zr9gVOxhMBYF2X6t2SNUElVuPiWQhcnpU+4aQsC+ ZkzHYa31V9Ytfk01R8GvraKuFuNNnqZZZKyDuVHS+cNO1T2JD5szcAxy0u5E 1aIcQouktONlpIRK9m8iAvRZDEBCpZ594yqdrniDRFO4QDJiUYp7F.TMutK8 CBIXn5WD.B7qPwdf3.xB5JYEbRJQHMuJqfIV5.hn0jS6SzUeNhbx.h7vJXQC u.AdrZyFd47c7dfs77307e3z8Pz84gHb9cBuP34QhrgDXWX88eJ9tvo6R9Mk n7YgdBOisqbFccGlN.tG5.qXxzWcsmVmz6isbSvmUtweD4FfLxbyo1yrpvft QI+hAUTxHZMRXzHSQtjmfTRDSV955qQrTlP1N3LgjGqJjlinudrai1ucaXKc ATqNBDZEUv3oKkJSwRrKsCSMEFuLJO7gxsWbl4TEhnMpsCaeFDLREi.T6KbS VyDRJCr5L3xWdluMyHLZjqN6TxNk0tfRUbcoFyBDqHQnP50phrDToZT9eQZS NKcsAwtgsaDjc75mrCX0mipyehHSspyWenrXNugkJ4E1iTIsHUV17qVeGTW. Tfs5SbzTeHe7t3L9CkUdMvC48hFW9gXSg7ISM+bIxcvjwga.R8cECnuq4NDx PKdlNt7CEdexcRXwO7FXlWPuEG0OAW25ymHt8LvsczdvwQ+IK1Iqx+grgVUj G2txzdxK5o4KgqMBIyHTx85D4f9rVjjvk6SDaDIaUkWPtACm3NucERUUMdVH cDtOKl7oUk.DTeYjffViABU+tfzf9fTfTeCfH3QqAh0ivwKCVbzjtT2oru2J lZVdAu56F.1WGZ4ggVKZi0.ijJowyGIS6FoiltKD6RsYjX2f8XPq0.QaUgac CsP2QK1Kbez5iuXnsKYtGERi85cWTive7jx8m1MEc.Q85rEOW7dJ1VqAB0nO dB1cARAC.QkF2O++lns9d. -----------end_max5_patcher-----------
maybe this could help?
----------begin_max5_patcher---------- 376.3ocuT1sTCBCDE95vSQlbM1gDLzp24ygiiSJDaiCjzgDlVsSe2Mr.8G0V SsZufvr6df8rejv5HDYpYkzRv2ieDiPqiPHHUaBTeLhTIVkWJrfLhVtzL8UR bWImbkCRWaZbRrU5Fp3iKkN2aKjcucBI1egepu7BgKetRO64ZYtqSQZ1njXL e7tUVxnjsOgp.Zju42PyF5xKFsSKpfdPdnVIJGpnapTZuC.WS2StU8NHmx7s Xq1N6BhYsI2DE0tDGHUpjVqXl7KXgdbb7ynfRgaorQbevjumEiOSTvNGTP+E n3HaPrxRbxQowTgdVfaPlvAnjcpMH7+Snv96fhnv5DtFK1tT4G2Sd1QocAPm zj106RO4wmqEcflSJU5O+KFv9s4ODYVSSc9vL2u4FuaDJjVmRKbJidOMzCzL WUTHgxC1qRUrv3gWuEtkCml3.mX.mNL.vXuprV.9setCcBngLAYm2HboVJK. OwupVhGfiFeANxGrI5C.E.Lk.B -----------end_max5_patcher-----------
Thanks Jakob, it *should* help, but no, it doesn’t.
Yes, the DSP status window indicates that DSP is on – something I meant to add in my previous post – but no audio is produced. To illustrate this I added a oscillator and meter to your patch and it should show some signal but there is none. See the pic attached
I didn’t mean to hijack this thread either but troubled by this…
ok, this keeps getting more weird,
I opened my original patch just a patch and it worked fine, but then when I compiled the application again, it still doesn’t work !! any ideas?
It works !!!!
ok, so I replaed the dac~ object, then added the adstatus driver object, in fact I added the subpatch p driver-options from the ads help files and recompiled and it all seems to work now !!
thanks for all your help, if you have a reason why this works and can explain it to me, please do so.
also, how to include a preference file for all your settings with a patch that you build into an application?
I can store settings and read them, I can also create an xml file of the settings and load it in, but I’m not sure how to always store the settings to the same file by default, so that it always works, and so that if I give the app to someone else they get all the settings etc…