It can be done; but you have to rewrite the feedback loop - which scrambles your code. I have a nested allpass somewhere with an output tap from the inner loop. Is that what you mean? I resorted to viewing the output of the nested structure und understand that. I sometimes write test routines containing simplified versions of the nested structures. Functional programming is limited in this regard. -- Urban Schlemmer - Diplomtonmeister -\\ - Formation supérieure aux métiers du son (FSMS) -\\ http://chiselapp.com/user/jcage/repository/rdk/doc/www/www/revdev.html
Gesendet: Freitag, 01. Februar 2019 um 10:42 Uhr Von: "Dario Sanfilippo" <sanfilippo.da...@gmail.com> An: "Faust users" <faudiostream-users@lists.sourceforge.net> Betreff: [Faudiostream-users] Routing signals to output Hello. I searched the archives and there's an email from 24/07/2017 (Debugging "peripheral" values that are not the main signal path) but it didn't get an answer, at least not publicly. I'm having the same problem so I'm bringing it back. I have a network with several modules and nested feedback loops. I need to inspect some of the signals which are not part of the main output to make sure that their behaviour is correct. When those signals are within the feedback paths, it seems less straightforward to route them to the output so that they can be inspected with faust2plot. A send2output function would be great but I don't that there's something like that. Do you have some procedure to send any signals to the output without changing most parts of the process? Thanks, Dario_______________________________________________ Faudiostream-users mailing list Faudiostream-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-users _______________________________________________ Faudiostream-users mailing list Faudiostream-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-users
