I just changed up the new single preference page for Pd-extended 0.43, hopefully its for the better. First off, there is no more "Startup" prefs, which allowed you to globally load libraries. Now, use [import] in your patch to load libraries. The "Startup flags" and "Real-time scheduling" are now added to the new preference panel.
The OK and Apply buttons only apply the settings for the current session of Pd. In order to save them for the next time you start Pd, there is the "Save All Settings" button. But now that I look at that, the "Save All Settings" button might actually be redundant, and OK actually saves everything...
Setting global paths should no longer be used for externals, instead you should use the standard install locations for your OS: http://puredata.info/docs/faq/how-do-i-install-externals-and-help-files
Or you can set the path in your patch. Either use the new [path] object or [declare -path] to set a relative path in your patch.
"Making boring techno music is really easy with modern tools, but with live coding, boring techno is much harder." - Chris McCormick
Hi list,
How are you ? Fine ? So am I
Any Ideas, why pdext is very slow when I click on "audio computer" with some patches ?
Hey,
Turning on DSP aka 'compute audio' will turn on the processing of audio. If that patch is doing a lot of things with audio, that can require a lot of CPU power. So turning on DSP will start all that processing, and make things slow.
That's my guess, if you provide more info, then we can make better guesses :)
.hc
On Apr 18, 2012, at 10:33 AM, prince ba wrote:
Hi list,
How are you ? Fine ? So am I
Any Ideas, why pdext is very slow when I click on "audio computer" with some patches ?
--
Combien de gens ne sont abstraits que pour paraître profond
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin
But I haven t got this problem with pd vanilla... So I Think the problem is not this. Is there a sort of "demux" on pd vanilla ? Le 18 avr. 2012 16:58, "Hans-Christoph Steiner" hans@at.or.at a écrit :
Hey,
Turning on DSP aka 'compute audio' will turn on the processing of audio. If that patch is doing a lot of things with audio, that can require a lot of CPU power. So turning on DSP will start all that processing, and make things slow.
That's my guess, if you provide more info, then we can make better guesses :)
.hc
On Apr 18, 2012, at 10:33 AM, prince ba wrote:
Hi list,
How are you ? Fine ? So am I
Any Ideas, why pdext is very slow when I click on "audio computer" with some patches ?
-- http://caracteriel.wordpress.com/
Combien de gens ne sont abstraits que pour paraître profond
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin
Can you post the patch? Without more info, you won't get an helpful answer because no one can tell what is happening.
.hc
On Apr 18, 2012, at 11:54 AM, prince ba wrote:
But I haven t got this problem with pd vanilla... So I Think the problem is not this. Is there a sort of "demux" on pd vanilla ?
Le 18 avr. 2012 16:58, "Hans-Christoph Steiner" hans@at.or.at a écrit :
Hey,
Turning on DSP aka 'compute audio' will turn on the processing of audio. If that patch is doing a lot of things with audio, that can require a lot of CPU power. So turning on DSP will start all that processing, and make things slow.
That's my guess, if you provide more info, then we can make better guesses :)
.hc
On Apr 18, 2012, at 10:33 AM, prince ba wrote:
Hi list,
How are you ? Fine ? So am I
Any Ideas, why pdext is very slow when I click on "audio computer" with some patches ?
--
Combien de gens ne sont abstraits que pour paraître profond
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin
Programs should be written for people to read, and only incidentally for machines to execute.