Re: [PD] problem with mixer project
I think I found the problem: if ALSA audio is selected the problem shows up, but if I select OSS the patch works perfectly well. Could somebody tell me why does that happen? Is there anyway to set automaticly audio to OSS and midi to ALSA inserting some code inside the patch or will I have to set this manually or with flags each time I load the patch? ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
Asunto: Re: [PD] problem with mixer project De: IOhannes m zmölnig Fecha: Sat, 07 May 2011 16:12:45 +0200 Para: pd-list@iem.at Para: pd-list@iem.at -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/07/2011 12:58 PM, Fernando Gadea wrote: Asunto: Re: [PD] problem with mixer project De: Jose Luis Santorcuato Fecha: ot, you got weird reply-settings. It's manual editing. I receive the list as digests but I try to simplify to gain legibility (I hope it works) As Iohannes lets think, I use xfce for its lightness and minimalistic user interface. I hope there is not a problem in the interaction between puredata and xubuntu's xfce environment. there is definitely no problem with xfce4 and Pd. i use it all the time. Try mixer~ objetct Thank you, I will substitute the before-master audio mixing with this object and see if the problem solves, at least as an alternative try. i still believe that you have a problem in your patch (which will go away if you don't use the patch; however it would probably be more interesting on the long run to find out what caused your problem) yes, that's my aim too, but it will be another possible test (I will do it tonight) to find out if the problem is really in the mixing channels. I deffinetly would like to stick to the original project and see where the problem is. Reading my mail I realized that I did not explain it all: the latency problem starts when the dac~ is computing audio. As you can see in the i still have no clue what you mean by "latency". please clarify. It is midi latency I guess (I have no degree in electronic music. just an amateur that started with puredata some years ago). After switching audio on, even in the primal midi patch that translates my controller to control data the numbers start to show really late. Is that midi latency? you probably should have a closer look at [delay] and what it does if you send it a number. Thank you, I have just found it out: it changes the delay time instead of giving a bang after the already setted delay time. I'll change it now. ah, btw, you could simplify the following [expr $f1; if ($f1 == 0, 0, 1] | ++ | [change] | [select 1 0] | [;pd dsp 0( [;pd dsp 1( to this [!= 0] (actually this should be [> 0] | [change] | [;pd dsp $1( Thank you, I will implement this one. Really simple. gdsft IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3FVi8ACgkQkX2Xpv6ydvQu4QCglguloZgIt7TIKiomT1QV/Nhe uxYAoJH7wkFP3IlWgpaWa2QRXiPmci4J =DHWR -END PGP SIGNATURE- ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/07/2011 04:13 PM, IOhannes m zmölnig wrote: > i still have no clue what you mean by "latency". please clarify. you probably should have a closer look at [delay] and what it does if you send it a number. ah, btw, you could simplify the following [expr $f1; if ($f1 == 0, 0, 1] | ++ | [change] | [select 1 0] | [;pd dsp 0( [;pd dsp 1( to this [!= 0] (actually this should be [> 0] | [change] | [;pd dsp $1( gdsft IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3FVi8ACgkQkX2Xpv6ydvQu4QCglguloZgIt7TIKiomT1QV/Nhe uxYAoJH7wkFP3IlWgpaWa2QRXiPmci4J =DHWR -END PGP SIGNATURE- ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/07/2011 12:58 PM, Fernando Gadea wrote: >> Reading my mail I realized that I did not explain it all: the latency >> problem starts when the dac~ is computing audio. As you can see in the i still have no clue what you mean by "latency". please clarify. fgasmdr IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3FU6IACgkQkX2Xpv6ydvQKigCeOXeqjIKUMC6oSl+B+jlQ5ePt gNIAn0brIpG/I77hl+rNg/UDHsmlKq+y =KeQa -END PGP SIGNATURE- ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/07/2011 12:58 PM, Fernando Gadea wrote: >> >> Asunto: >> Re: [PD] problem with mixer project >> De: >> Jose Luis Santorcuato >> Fecha: ot, you got weird reply-settings. > As Iohannes lets think, I use xfce for its lightness and minimalistic > user interface. I hope there is not a problem in the interaction between > puredata and xubuntu's xfce environment. there is definitely no problem with xfce4 and Pd. i use it all the time. >> Try mixer~ objetct > Thank you, I will substitute the before-master audio mixing with this > object and see if the problem solves, at least as an alternative try. i still believe that you have a problem in your patch (which will go away if you don't use the patch; however it would probably be more interesting on the long run to find out what caused your problem) fg,asd IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3FU10ACgkQkX2Xpv6ydvT2jACg5OKwcNInqvw5J7YCpJsypVX8 Li8AoIexnlelbtWvA9ZFPd+9lg60mZKA =tjJC -END PGP SIGNATURE- ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
Asunto: Re: [PD] problem with mixer project De: Jose Luis Santorcuato Fecha: Fri, 6 May 2011 23:14:57 -0400 Para: Fernando Gadea Para: Fernando Gadea CC: pd-list@iem.at Hi...¿Kernel? ... probablemente debas compilar un kernel de baja latencia...tiene poca ram y un procesador pequeño, igual debería funcionar... I am not really a power user, but I haven' t had latency problems before, so maybe this is not the central problem (but I understand that you may be right and I could improve performance with a kernel change, only that, if I can solve this latency problem in an easyer inside-puredata way, I will leave it for a later macro-system optimizing stage) Maybe you could compile a low latency kernel... your processor is slow, but must go on... check the latency... Why you use Xubuntu??? try Ubuntu... i worked with open cv, pidip and other in a little cpu... As Iohannes lets think, I use xfce for its lightness and minimalistic user interface. I hope there is not a problem in the interaction between puredata and xubuntu's xfce environment. Try mixer~ objetct Thank you, I will substitute the before-master audio mixing with this object and see if the problem solves, at least as an alternative try. Gracias, y mejores deseos Fernando Best regards José El 6 de mayo de 2011 15:45, Fernando Gadea <mailto:fga...@gmail.com>> escribió: Hi list! I am trying to design a mixer with integrated effects on each channel. The effects part is not started yet, and I have a particular problem with the mixer itself: If I move any slider in my controller to raise the volume of any channel, it works perfectly well, but if I move the master level the latency starts to get crazy and the resulting values come really slowly, and then if I move any other volume slider (of the mixing channels of any other values in the master patch, being instrument values or sequencer values) the latency still is really big. I tryed deleting all the mixing channels and moving the master level slider and there is no problem then, so I guess the problem is in the mixing channels. I also tryed deleting all the instruments and it didn't solve the problem neither. As you see the mixing channels are all abstractions (canalmezcla n), and the master itself is one of these abstractions. I am running puredata Extended 0.41.4 in Xubuntu in an HP Pavilion dv 1680us 1.83 Ghz + 1 Gb ram. I believe the hardware is not the problem, and the rest of the patch works fine. Thanks for any tip! Fernando ___ Pd-list@iem.at <mailto:Pd-list@iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list -- http://arselectronicachile.blogspot.com http://comunicacionnativa.blogspot.com/ http://www.myspace.com/santorcuato ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
Asunto: Re: [PD] problem with mixer project De: IOhannes m zmölnig Fecha: Sat, 07 May 2011 11:33:03 +0200 Para: pd-list@iem.at Para: pd-list@iem.at -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/06/2011 08:45 PM, Fernando Gadea wrote: Hi list! If I move any slider in my controller to raise the volume of any channel, it works perfectly well, but if I move the master level the latency starts to get crazy and the resulting values come really slowly, Pd is designed to have a constant latency. so Pd's (and the system's) latency will never when moving a slider (well, unless you control a delay with the slider or do some other explicit latency fuddling, but that's a different story) or maybe you are referring to GUI latency? e.g the slider starts to visually respond very slowly (it seems like in CM-talk, "latency" mostly refers to audio latency). without having looked at your patch, a good chance is that you have created some control feedback. Reading my mail I realized that I did not explain it all: the latency problem starts when the dac~ is computing audio. As you can see in the mixer, when I rise the master volume audio computation starts, meanwhile if I set master volume to zero it ends. It is while computing audio that the latency problem exists, so I guess the control side is not the problem (am I in the right logic?) Nevertheless I have done what I believe is an extensive control check in my patch, before and after finding that deleting the mixer channels the problem ended. After that I did another control check on the mixer part of the patch and found no control feedback (my checks are visual, following line after line, so, as human, I might be wrong, but I cannot find my error if I did one). It seems that the latency is present not only in GUI. I send the values to a symbol in the main patch to see what I am doing, so I am preety sure I also hear the audio consecuences with the same latency (the audio rises just when the mixer volume rises, about a second after moving the slider if dac~ is on). Anyway, I will look for some other posibilities of control feedback. Thank you for your advice fgmasdrt IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3FEc8ACgkQkX2Xpv6ydvR1fQCdEGsRD4QqEaMLxhJpEr3MblTO kpcAoPTP2Rf14/nCN+GI3IOhBTP9B4xV =Oh4I -END PGP SIGNATURE- ___ Pd-list mailing list Pd-list@iem.at to manage your subscription (including un-subscription) see http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
Ubuntu, xubuntu, kubuntu are all the same distro with just a different flavor for the window manager system (X). On May 7, 2011 9:34 AM, "IOhannes m zmölnig" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 05/06/2011 08:45 PM, Fernando Gadea wrote: >> Hi list! >> If I move any slider in my controller to raise the volume of any >> channel, it works perfectly well, but if I move the master level the >> latency starts to get crazy and the resulting values come really slowly, > > Pd is designed to have a constant latency. > > so Pd's (and the system's) latency will never when moving a slider > (well, unless you control a delay with the slider or do some other > explicit latency fuddling, but that's a different story) > > or maybe you are referring to GUI latency? e.g the slider starts to > visually respond very slowly (it seems like in CM-talk, "latency" mostly > refers to audio latency). > without having looked at your patch, a good chance is that you have > created some control feedback. > > fgmasdrt > IOhannes > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk3FEc8ACgkQkX2Xpv6ydvR1fQCdEGsRD4QqEaMLxhJpEr3MblTO > kpcAoPTP2Rf14/nCN+GI3IOhBTP9B4xV > =Oh4I > -END PGP SIGNATURE- > > ___ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/06/2011 08:45 PM, Fernando Gadea wrote: > Hi list! > If I move any slider in my controller to raise the volume of any > channel, it works perfectly well, but if I move the master level the > latency starts to get crazy and the resulting values come really slowly, Pd is designed to have a constant latency. so Pd's (and the system's) latency will never when moving a slider (well, unless you control a delay with the slider or do some other explicit latency fuddling, but that's a different story) or maybe you are referring to GUI latency? e.g the slider starts to visually respond very slowly (it seems like in CM-talk, "latency" mostly refers to audio latency). without having looked at your patch, a good chance is that you have created some control feedback. fgmasdrt IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3FEc8ACgkQkX2Xpv6ydvR1fQCdEGsRD4QqEaMLxhJpEr3MblTO kpcAoPTP2Rf14/nCN+GI3IOhBTP9B4xV =Oh4I -END PGP SIGNATURE- ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/07/2011 05:14 AM, Jose Luis Santorcuato wrote: > > Why you use Xubuntu??? try Ubuntu... i worked with open cv, pidip and other maybe because xfce is lighter and cooler than gnome? apart from the different desktop environment, there is no difference between xubuntu and ubuntu (afaik) fgas IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3FELkACgkQkX2Xpv6ydvS0ogCggcqq/k6qxFnKp6D9P8ddzlen 3nIAn2ftavjW4nvHDWk95G23QzHYEAgv =bN8K -END PGP SIGNATURE- ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Re: [PD] problem with mixer project
Hi...¿Kernel? ... probablemente debas compilar un kernel de baja latencia...tiene poca ram y un procesador pequeño, igual debería funcionar... Maybe you could compile a low latency kernel... your processor is slow, but must go on... check the latency... Why you use Xubuntu??? try Ubuntu... i worked with open cv, pidip and other in a little cpu... Try mixer~ objetct Best regards José El 6 de mayo de 2011 15:45, Fernando Gadea escribió: > Hi list! > I am trying to design a mixer with integrated effects on each channel. The > effects part is not started yet, and I have a particular problem with the > mixer itself: > > If I move any slider in my controller to raise the volume of any channel, > it works perfectly well, but if I move the master level the latency starts > to get crazy and the resulting values come really slowly, and then if I move > any other volume slider (of the mixing channels of any other values in the > master patch, being instrument values or sequencer values) the latency still > is really big. > > I tryed deleting all the mixing channels and moving the master level slider > and there is no problem then, so I guess the problem is in the mixing > channels. > I also tryed deleting all the instruments and it didn't solve the problem > neither. > As you see the mixing channels are all abstractions (canalmezcla n), and > the master itself is one of these abstractions. > > I am running puredata Extended 0.41.4 in Xubuntu in an HP Pavilion dv > 1680us 1.83 Ghz + 1 Gb ram. I believe the hardware is not the problem, and > the rest of the patch works fine. > > Thanks for any tip! > > Fernando > > ___ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > > -- http://arselectronicachile.blogspot.com http://comunicacionnativa.blogspot.com/ http://www.myspace.com/santorcuato ___ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
[PD] problem with mixer project
Hi list! I am trying to design a mixer with integrated effects on each channel. The effects part is not started yet, and I have a particular problem with the mixer itself: If I move any slider in my controller to raise the volume of any channel, it works perfectly well, but if I move the master level the latency starts to get crazy and the resulting values come really slowly, and then if I move any other volume slider (of the mixing channels of any other values in the master patch, being instrument values or sequencer values) the latency still is really big. I tryed deleting all the mixing channels and moving the master level slider and there is no problem then, so I guess the problem is in the mixing channels. I also tryed deleting all the instruments and it didn't solve the problem neither. As you see the mixing channels are all abstractions (canalmezcla n), and the master itself is one of these abstractions. I am running puredata Extended 0.41.4 in Xubuntu in an HP Pavilion dv 1680us 1.83 Ghz + 1 Gb ram. I believe the hardware is not the problem, and the rest of the patch works fine. Thanks for any tip! Fernando #N canvas 365 85 318 547 10; #X obj -67 71 inlet~; #X msg 30 79 1; #X msg 64 79 0; #X obj 55 509 *~; #X obj 92 509 *~; #X obj -33 94 inlet~; #X obj 54 99 f; #X obj 30 57 select \$1; #X obj 148 437 * 0.01; #X obj 148 20 inlet; #X msg 158 464 50; #X floatatom 155 90 5 0 0 0 - - -; #X obj 148 68 f \$0; #X obj 148 42 b; #X obj 86 16 loadbang; #X obj 86 37 f \$1; #X obj 30 28 r n-inst; #X obj 23 525 outlet~; #X obj 93 525 outlet~; #N canvas 214 262 715 300 resampleo 0; #X obj 78 48 inlet~; #X obj 133 49 inlet~; #X obj 78 255 outlet~; #X obj 320 255 outlet~; #X text 12 163 acá va un buffer que me permite jugar con la velocidad y otros parámetros del audio que provenga de cualquier fuente y tenga ya filtrado de algunos efectos; #X obj 437 24 r \$0-fx; #X obj 437 184 f; #X obj 463 183 f; #X obj 437 45 route comienzo final veloc; #X obj 490 183 f; #X text 493 200 veloc; #X text 460 200 final; #X text 435 200 com; #X obj 463 91 r final; #X obj 437 68 r comienzo; #X obj 490 113 r veloc; #X obj 437 114 contin; #X obj 463 136 contin; #X obj 490 158 contin; #X obj 523 68 inlet; #X connect 0 0 2 0; #X connect 1 0 3 0; #X connect 5 0 8 0; #X connect 8 0 6 0; #X connect 8 1 7 0; #X connect 8 2 9 0; #X connect 13 0 17 0; #X connect 14 0 16 0; #X connect 15 0 18 0; #X connect 16 0 6 0; #X connect 17 0 7 0; #X connect 18 0 9 0; #X connect 19 0 16 1; #X connect 19 0 17 1; #X connect 19 0 18 1; #X restore -66 133 pd resampleo; #N canvas 226 190 783 300 notch 0; #X obj 78 48 inlet~; #X obj 133 49 inlet~; #X obj 78 255 outlet~; #X obj 320 255 outlet~; #X text 106 106 acá va un buffer que me permite jugar con la velocidad y otros parámetros del audio que provenga de cualquier fuente y tenga ya filtrado de algunos efectos; #X obj 522 28 r \$0-fx; #X obj 522 136 f; #X obj 571 136 f; #X obj 621 136 f; #X obj 522 50 route centro ancho dureza; #X text 519 149 centro; #X text 569 150 ancho; #X text 618 149 dureza; #X obj 621 93 r dureza; #X obj 522 71 r centro; #X obj 571 92 r ancho; #X obj 522 115 contin; #X obj 571 115 contin; #X obj 621 115 contin; #X obj 682 98 f; #X obj 682 28 inlet; #X connect 0 0 2 0; #X connect 1 0 3 0; #X connect 5 0 9 0; #X connect 9 0 6 0; #X connect 9 1 7 0; #X connect 9 2 8 0; #X connect 13 0 18 0; #X connect 14 0 16 0; #X connect 15 0 17 0; #X connect 16 0 6 0; #X connect 17 0 7 0; #X connect 18 0 8 0; #X connect 19 0 16 1; #X connect 19 0 17 1; #X connect 19 0 18 1; #X connect 20 0 19 0; #X restore -65 224 pd notch; #X obj 17 116 f; #X obj 17 207 f; #X obj 96 240 inlet; #X obj 96 262 s \$0-fx; #X obj 106 132 symbol; #X obj 106 152 s nomcont; #X obj 95 59 f; #X obj 95 194 symbol; #X obj 95 214 s nominst; #X obj 95 174 makefilename %d; #X obj 106 111 makefilename Vol-%d; #N canvas 223 60 338 503 reverb 0; #X obj -8 441 inlet~; #X obj -8 482 outlet~; #X obj 44 441 inlet~; #X obj 44 482 outlet~; #X obj -10 5 r \$0-fx; #X obj -8 462 freeverb~; #X msg -8 259 roomsize \$1; #X msg -8 338 damping \$1; #X msg -8 378 width \$1; #X msg -8 197 wet \$1; #X msg -8 219 dry \$1; #X msg -8 416 freeze \$1; #X msg 55 462 bypass \$1; #N canvas 480 33 101 119 crossfader 0; #X msg 22 27 1; #X obj 7 48 -; #X obj 7 69 * -1; #X obj 7 7 inlet; #X obj 7 89 outlet; #X connect 0 0 1 1; #X connect 1 0 2 0; #X connect 2 0 4 0; #X connect 3 0 0 0; #X connect 3 0 1 0; #X restore -8 177 pd crossfader; #X obj -7 160 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -41615 -1 -1 0 1; #X obj -5 241 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -41615 -1 -1 0 1; #X obj -4 281 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -41615 -1 -1 0 1; #X obj -5 360 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -41615 -1 -1 0 1; #X obj -5 399 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -41615 -1 -1 0 1; #X obj 122 464 hsl 128 15 0 1 0 0 empty empty empty -2 -8 0 10 -41615 -1 -1 12700 1; #X obj -10 124 f; #X obj -10
