Hi,
Can someone please help me out here? I've searched the forum and list
archives and understand that the following is the construction for
including a simple vu meter in a patch:
[env~] | [-100] | [vu]
So I used it like this:
[number box] | [osc~] | [env~] | [-100] | [vu]
but this produces no sound. (The connectors from [env~] and [-100]
are message connectors, not audio.)
Thanks, Peter
Peter O'Doherty http://www.peterodoherty.net http://www.myspace.com/peterodoherty
Are you expecting [vu] to output sound? Use the [dac~] object for that. I guess you mean that the [vu] doesn't register any levels...
[env~] sends a message stream of numbers, not audio. And I assume you mean [- 100] here? It won't work without the space. [- ] is the name of the object and "100" is the creation argument. Could that be the problem?
best, d.
Peter O'Doherty wrote:
Hi, Can someone please help me out here? I've searched the forum and list archives and understand that the following is the construction for including a simple vu meter in a patch:
[env~] | [-100] | [vu]
So I used it like this:
[number box] | [osc~] | [env~] | [-100] | [vu]
but this produces no sound. (The connectors from [env~] and [-100] are message connectors, not audio.)
Thanks, Peter
Peter O'Doherty http://www.peterodoherty.net http://www.myspace.com/peterodoherty
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Thanks for your reply.
I was expecting [vu] simply to show some levels.
How would I slot [vu] into a very basis chain like the following
which would allow me to keep an eye on levels, or am I missing the
point of [vu]? (Perhaps these's a better way to do it.)
[number box] | [osc~] | [*~ 0] ----- [number box]
| [dac~]
Thanks, Peter
On 5 Aug 2008, at 18:18, Derek Holzer wrote:
Are you expecting [vu] to output sound? Use the [dac~] object for
that. I guess you mean that the [vu] doesn't register any levels...[env~] sends a message stream of numbers, not audio. And I assume
you mean [- 100] here? It won't work without the space. [- ] is the
name of the object and "100" is the creation argument. Could that
be the problem?best, d.
Peter O'Doherty wrote:
Hi, Can someone please help me out here? I've searched the forum and
list archives and understand that the following is the
construction for including a simple vu meter in a patch: [env~] | [-100] | [vu] So I used it like this: [number box] | [osc~] | [env~] | [-100] | [vu] but this produces no sound. (The connectors from [env~] and [-100]
are message connectors, not audio.) Thanks, Peter ---- Peter O'Doherty http://www.peterodoherty.net http://www.myspace.com/peterodoherty
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
-- derek holzer ::: http://www.umatic.nl ::: http://blog.myspace.com/ macumbista ---Oblique Strategy # 36: "Consult other sources -promising -unpromising"
You were close, you just didn't include a space in an object name:
[number box] | [osc~] | [env~] | [- 100] | [vu]
But keep in mind that quickly refreshing graphics in the patch will dramatically affect overall audio performance. If you just need to know if you are close to peaking, this could work too:
["some sound source~"] | [env~] | [> 0.90] | ["graphical bang"]
Or this:
["some sound source~"] | [env~] | ["number box with very slow refresh rate set in properties"]
good luck! d.
Peter O'Doherty wrote:
Thanks for your reply.
I was expecting [vu] simply to show some levels.
How would I slot [vu] into a very basis chain like the following which would allow me to keep an eye on levels, or am I missing the point of [vu]? (Perhaps these's a better way to do it.)
[number box] | [osc~] | [*~ 0] ----- [number box]
| [dac~]
Thanks, Peter
On 5 Aug 2008, at 18:18, Derek Holzer wrote:
Are you expecting [vu] to output sound? Use the [dac~] object for that. I guess you mean that the [vu] doesn't register any levels...
[env~] sends a message stream of numbers, not audio. And I assume you mean [- 100] here? It won't work without the space. [- ] is the name of the object and "100" is the creation argument. Could that be the problem?
best, d.
Peter O'Doherty wrote:
Hi, Can someone please help me out here? I've searched the forum and list archives and understand that the following is the construction for including a simple vu meter in a patch: [env~] | [-100] | [vu] So I used it like this: [number box] | [osc~] | [env~] | [-100] | [vu] but this produces no sound. (The connectors from [env~] and [-100] are message connectors, not audio.) Thanks, Peter ---- Peter O'Doherty http://www.peterodoherty.net http://www.myspace.com/peterodoherty
Pd-list@iem.at mailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- derek holzer ::: http://www.umatic.nl ::: http://blog.myspace.com/macumbista ---Oblique Strategy # 36: "Consult other sources -promising -unpromising"
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I meant:
["some sound source~"] | [env~] | [> 90] ...or 92 or 96 or however close you want to get... | ["graphical bang"]
Derek Holzer wrote:
You were close, you just didn't include a space in an object name:
[number box] | [osc~] | [env~] | [- 100] | [vu]
But keep in mind that quickly refreshing graphics in the patch will dramatically affect overall audio performance. If you just need to know if you are close to peaking, this could work too:
["some sound source~"] | [env~] | [> 0.90] | ["graphical bang"]
Or this:
["some sound source~"] | [env~] | ["number box with very slow refresh rate set in properties"]
good luck! d.
Peter O'Doherty wrote:
Thanks for your reply.
I was expecting [vu] simply to show some levels.
How would I slot [vu] into a very basis chain like the following which would allow me to keep an eye on levels, or am I missing the point of [vu]? (Perhaps these's a better way to do it.)
[number box] | [osc~] | [*~ 0] ----- [number box]
| [dac~]
Thanks, Peter
On 5 Aug 2008, at 18:18, Derek Holzer wrote:
Are you expecting [vu] to output sound? Use the [dac~] object for that. I guess you mean that the [vu] doesn't register any levels...
[env~] sends a message stream of numbers, not audio. And I assume you mean [- 100] here? It won't work without the space. [- ] is the name of the object and "100" is the creation argument. Could that be the problem?
best, d.
Peter O'Doherty wrote:
Hi, Can someone please help me out here? I've searched the forum and list archives and understand that the following is the construction for including a simple vu meter in a patch: [env~] | [-100] | [vu] So I used it like this: [number box] | [osc~] | [env~] | [-100] | [vu] but this produces no sound. (The connectors from [env~] and [-100] are message connectors, not audio.) Thanks, Peter ---- Peter O'Doherty http://www.peterodoherty.net http://www.myspace.com/peterodoherty
Pd-list@iem.at mailto:Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- derek holzer ::: http://www.umatic.nl ::: http://blog.myspace.com/macumbista ---Oblique Strategy # 36: "Consult other sources -promising -unpromising"
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
yes yes, thanks frank! in too much of a hurry over here ;-)
d.
Frank Barknecht wrote:
Hallo, Derek Holzer hat gesagt: // Derek Holzer wrote:
I meant:
["some sound source~"] | [env~] | [> 90] ...or 92 or 96 or however close you want to get... |
| [select 1] ;) |
["graphical bang"]
Ciao
Hallo, Derek Holzer hat gesagt: // Derek Holzer wrote:
yes yes, thanks frank! in too much of a hurry over here ;-)
I cannot count the times that I stumbled over a forgotten [select 1] after a logical comparison myself. Happens to me at least once every month, and can take very long to find ...
Frank Barknecht _ ______footils.org__
Hallo, Peter O'Doherty hat gesagt: // Peter O'Doherty wrote:
Thanks for your reply.
I was expecting [vu] simply to show some levels.
How would I slot [vu] into a very basis chain like the following
which would allow me to keep an eye on levels, or am I missing the
point of [vu]? (Perhaps these's a better way to do it.)[number box] | [osc~] | [*~ 0] ----- [number box]
| [dac~]
For example as in the attachment.
Frank Barknecht _ ______footils.org__
Frank Barknecht wrote:
For example as in the attachment.
Interesting playing with that...If you give the osc~ a gain of 100dB, which dbtorms translates to a gain of 1, then [env~] outputs 96.99dB and the vu meter -3dB. To get 0dB on the meter you need to give 103dB to the osc~, a gain of 1.413. My onboard soundcard starts clipping with the vu meter at -3dB, so a gain of 1 on an osc~ is the maximum the hardware can handle. That is, maximum gain allowed by the hardware is 100dB ("sound pressure level"), 1 ("full scale"), or -3dB (why not 0dB?). Why does env~ give an output that is 3dB less than, or 1/2 of, its input?
Martin
Maybe the difference between RMS and peak-to-peak dB levels?
d.
Martin Peach wrote:
Frank Barknecht wrote:
For example as in the attachment.
Interesting playing with that...If you give the osc~ a gain of 100dB, which dbtorms translates to a gain of 1, then [env~] outputs 96.99dB and the vu meter -3dB. To get 0dB on the meter you need to give 103dB to the osc~, a gain of 1.413. My onboard soundcard starts clipping with the vu meter at -3dB, so a gain of 1 on an osc~ is the maximum the hardware can handle. That is, maximum gain allowed by the hardware is 100dB ("sound pressure level"), 1 ("full scale"), or -3dB (why not 0dB?). Why does env~ give an output that is 3dB less than, or 1/2 of, its input?
Martin
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Tue, 2008-08-05 at 14:19 -0400, Martin Peach wrote:
Frank Barknecht wrote:
For example as in the attachment.
Interesting playing with that...If you give the osc~ a gain of 100dB, which dbtorms translates to a gain of 1, then [env~] outputs 96.99dB and the vu meter -3dB. To get 0dB on the meter you need to give 103dB to the osc~, a gain of 1.413. My onboard soundcard starts clipping with the vu meter at -3dB, so a gain of 1 on an osc~ is the maximum the hardware can handle. That is, maximum gain allowed by the hardware is 100dB ("sound pressure level"), 1 ("full scale"), or -3dB (why not 0dB?). Why does env~ give an output that is 3dB less than, or 1/2 of, its input?
i think (correct me, if i am wrong) this is dependent on the crest factor of the signal:
http://en.wikipedia.org/wiki/Crest_factor
altough, the peak of the sine is 1, -1 respectively, the average (that is what [env~] gives you) is lower, 3dB to be exactly. try the same with a square wave and the result should pretty much be 0dB, respectively 100dB.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Roman Haefeli wrote:
On Tue, 2008-08-05 at 14:19 -0400, Martin Peach wrote:
Frank Barknecht wrote:
For example as in the attachment.
Interesting playing with that...If you give the osc~ a gain of 100dB, which dbtorms translates to a gain of 1, then [env~] outputs 96.99dB and the vu meter -3dB. To get 0dB on the meter you need to give 103dB to the osc~, a gain of 1.413. My onboard soundcard starts clipping with the vu meter at -3dB, so a gain of 1 on an osc~ is the maximum the hardware can handle. That is, maximum gain allowed by the hardware is 100dB ("sound pressure level"), 1 ("full scale"), or -3dB (why not 0dB?). Why does env~ give an output that is 3dB less than, or 1/2 of, its input?
i think (correct me, if i am wrong) this is dependent on the crest factor of the signal:
http://en.wikipedia.org/wiki/Crest_factor
altough, the peak of the sine is 1, -1 respectively, the average (that is what [env~] gives you) is lower, 3dB to be exactly. try the same with a square wave and the result should pretty much be 0dB, respectively 100dB.
Yes, that makes sense. That's why in analog equipment you try to stay around -3dB instead of 0dB because the peaks are at 0dB. In analog you can go above 0dB with progressively reduced gain, but in digital equipment you get hard clipping at exactly 0dB, so it's nice to know when it's happening. [env~] will give different output depending on the waveform it's measuring, so it's not too useful for determining if overload is occurring. Maybe [peak~] from flib is appropriate for that, but it seems to involve doing an fft so it may be computationally heavy. I'm still not able to instantiate [>~] from zexy...
Martin
On Tue, 2008-08-05 at 15:23 -0400, Martin Peach wrote:
Roman Haefeli wrote:
On Tue, 2008-08-05 at 14:19 -0400, Martin Peach wrote:
Frank Barknecht wrote:
For example as in the attachment.
Interesting playing with that...If you give the osc~ a gain of 100dB, which dbtorms translates to a gain of 1, then [env~] outputs 96.99dB and the vu meter -3dB. To get 0dB on the meter you need to give 103dB to the osc~, a gain of 1.413. My onboard soundcard starts clipping with the vu meter at -3dB, so a gain of 1 on an osc~ is the maximum the hardware can handle. That is, maximum gain allowed by the hardware is 100dB ("sound pressure level"), 1 ("full scale"), or -3dB (why not 0dB?). Why does env~ give an output that is 3dB less than, or 1/2 of, its input?
i think (correct me, if i am wrong) this is dependent on the crest factor of the signal:
http://en.wikipedia.org/wiki/Crest_factor
altough, the peak of the sine is 1, -1 respectively, the average (that is what [env~] gives you) is lower, 3dB to be exactly. try the same with a square wave and the result should pretty much be 0dB, respectively 100dB.
Yes, that makes sense. That's why in analog equipment you try to stay around -3dB instead of 0dB because the peaks are at 0dB. In analog you can go above 0dB with progressively reduced gain, but in digital equipment you get hard clipping at exactly 0dB, so it's nice to know when it's happening. [env~] will give different output depending on the waveform it's measuring, so it's not too useful for determining if overload is occurring. Maybe [peak~] from flib is appropriate for that, but it seems to involve doing an fft so it may be computationally heavy. I'm still not able to instantiate [>~] from zexy...
on extended? which version? from what i heard, extended-0.40-rc4 doesn't suffer anymore from this problem. [>~] from the multiclass library should work well, no matter what version.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Thanks a million Derek and Frank. Those suggestions and the basic- metering patch work beautifully. Regards, Peter
Peter O'Doherty http://www.peterodoherty.net http://www.myspace.com/peterodoherty
On 5 Aug 2008, at 19:41, Frank Barknecht wrote:
Hallo, Peter O'Doherty hat gesagt: // Peter O'Doherty wrote:
Thanks for your reply.
I was expecting [vu] simply to show some levels.
How would I slot [vu] into a very basis chain like the following which would allow me to keep an eye on levels, or am I missing the point of [vu]? (Perhaps these's a better way to do it.)
[number box] | [osc~] | [*~ 0] ----- [number box]
| [dac~]
For example as in the attachment.
Ciao
Frank Barknecht _
______footils.org__<basic- metering.pd>_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list