[Csnd] Automatic printing
Date | 2010-11-05 12:23 |
From | Marco Stroppa |
Subject | [Csnd] Automatic printing |
Dear Csounders, I wonder whether somebody knows, if and how it is possible to deactivate the automatic printing of the seed of a random generator when it is taken from the system clock, something like: Seeding from current time 1717844963 Seeding from current time 1717845041 Seeding from current time 1717845070 Seeding from current time 1717845156 Seeding from current time 1717845355 Seeding from current time 1717845424 When using many instances of randi in the instrument, and many instruments, this printing slows down the whole process in a sizeable fashion. I tried with the flag -m0, but nothing happened. I'm using csound 5.11 on a MacIntel. Thanks a lot in advance. Marco Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
Date | 2010-11-05 12:58 |
From | Rory Walsh |
Subject | [Csnd] Re: Automatic printing |
How about -m0d? On 5 November 2010 12:23, Marco Stroppa |
Date | 2010-11-05 13:12 |
From | jpff@cs.bath.ac.uk |
Subject | [Csnd] Re: Re: Automatic printing |
Sounds like a debugging line left in. WIll check == JPff > How about -m0d? > > On 5 November 2010 12:23, Marco Stroppa |
Date | 2010-11-05 17:00 |
From | Louis Cohen |
Subject | [Csnd] Re: Automatic printing |
I've also seen this printout and it then dawned on my that I probably didn't need to seed over and over again. I just moved the seed opcode to a place where it gets executed once. Of course I still get the message (but only once.) -Lou On Nov 5, 2010, at 8:23 AM, Marco Stroppa wrote: > Dear Csounders, > > I wonder whether somebody knows, if and how it is possible to > deactivate the > automatic printing of the seed of a random generator when it is > taken from the > system clock, something like: > > Seeding from current time 1717844963 > Seeding from current time 1717845041 > Seeding from current time 1717845070 > Seeding from current time 1717845156 > Seeding from current time 1717845355 > Seeding from current time 1717845424 > > > When using many instances of randi in the instrument, and many > instruments, this > printing slows down the whole process in a sizeable fashion. I tried > with the > flag -m0, but nothing happened. I'm using csound 5.11 on a MacIntel. > > Thanks a lot in advance. > > > Marco > > > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body > "unsubscribe csound" > Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
Date | 2010-11-06 09:41 |
From | Enrico Francioni |
Subject | [Csnd] Re: Automatic printing |
…to me the same thing happens with SOLO_MV; Here we employ the random opcode e -- View this message in context: http://csound.1045644.n5.nabble.com/Automatic-printing-tp3251724p3252929.html Sent from the Csound - General mailing list archive at Nabble.com. Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
Date | 2010-11-06 09:58 |
From | Enrico Francioni |
Subject | [Csnd] Re: Automatic printing |
...for now my remedy was to suppress messages in the gui display of MacCsound 1.5. e |
Date | 2010-11-10 13:34 |
From | ben hackbarth |
Subject | [Csnd] Re: Re: Automatic printing |
hello all, on the topic of printing, i'd really like to see csound have more robust user control over stdout messages. console outputs are currently very long (for me at least) and i would love to disable all printing of messages regarding lib loading and orchestra/score processing (i.e. versions, macros, LABELS, GOTOS, udos, ftables, etc...). perhaps some control over these messages already exists and i'm unaware? currently i'm catching stdout with python and filtering printed messages with a Popen pipe, but i'd rather have better control over csound itself. regards & thanks, — ben On Sat, Nov 6, 2010 at 10:58 AM, Enrico Francioni |
Date | 2010-11-10 13:36 |
From | jpff@cs.bath.ac.uk |
Subject | [Csnd] Re: Re: Re: Automatic printing |
Examples? Details? hello all, > > on the topic of printing, i'd really like to see csound have more > robust user control over stdout messages. console outputs are > currently very long (for me at least) and i would love to disable all > printing of messages regarding lib loading and orchestra/score > processing (i.e. versions, macros, LABELS, GOTOS, udos, ftables, > etc...). perhaps some control over these messages already exists and > i'm unaware? > > currently i'm catching stdout with python and filtering printed > messages with a Popen pipe, but i'd rather have better control over > csound itself. > > regards & thanks, > ben > > > > On Sat, Nov 6, 2010 at 10:58 AM, Enrico Francioni > |
Date | 2010-11-12 10:48 |
From | Enrico Francioni |
Subject | [Csnd] Re: Automatic printing |
I do not understand what you mean I can have an explanation? thanks e |
Date | 2010-11-13 00:45 |
From | ben hackbarth |
Subject | [Csnd] Re: Re: Re: Re: Automatic printing |
as to the OT, there seem to be several opcodes which, like seed, print information to stdout even with -m0. schedule and pconvolve come to mind, but i know i've encountered this situation with others too. @john csound outputs the following messages when loading the orc/sco, even with -m0. a way to avoid printing this would be most helpful. --- time resolution is 1000.000 ns 0dBFS level = 32768.0 Csound version 5.12 beta (float samples) Aug 13 2010 libsndfile-1.0.21 orchname: /tmp/orch.orc scorename: /tmp/ngenOutput Loading command-line libraries: /Users/ben/composition/particle-wave/includes/pvsExtend.dylib Macro definition for omacro:NGEN=-1 orch compiler: 3172 (3173) lines read extending Floating pool to 512 opcode frqShift a akk opcode ExpEnv k iiii opcode aExpEnv a iiii opcode ExpBreakPoint k iiii opcode aExpBreakPoint a iiii opcode globalAmpChecker a ai opcode iProcessToggler iiiiiiiiii i opcode idbtorms i i opcode kdbtorms k k opcode iCpsToMidi i i opcode kCpsToMidi k k opcode aFormantFilter a akii opcode aDiskinVariablePlayStereo aa iiki opcode aDiskinVariablePlayMono aa iiki opcode iquantize i ii opcode kquantize k ki opcode iMakePianoNote 0 iiiiiiiiiiii opcode kMakePianoNote 0 kkkkkkkkkkkk opcode iVerbosePrint 0 0 opcode iPercentToSecond i iSii opcode iGetTransposition i iii opcode iAttackLikeDur i ii opcode iFileSegToPvsBuf iiki iiii instr 99 instr 100 instr 50 instr 52 instr 98 instr 200 instr 201 LABELS list is full...extending to 10 LABELS list is full...extending to 15 LABELS list is full...extending to 20 LABELS list is full...extending to 25 LABELS list is full...extending to 30 GOTOS list is full..extending to 80 LABELS list is full...extending to 35 LABELS list is full...extending to 40 LABELS list is full...extending to 45 LABELS list is full...extending to 50 LABELS list is full...extending to 55 LABELS list is full...extending to 60 GOTOS list is full..extending to 120 LABELS list is full...extending to 65 LABELS list is full...extending to 70 LABELS list is full...extending to 75 LABELS list is full...extending to 80 LABELS list is full...extending to 85 GOTOS list is full..extending to 160 LABELS list is full...extending to 90 LABELS list is full...extending to 95 LABELS list is full...extending to 100 LABELS list is full...extending to 105 LABELS list is full...extending to 110 LABELS list is full...extending to 115 LABELS list is full...extending to 120 GOTOS list is full..extending to 200 LABELS list is full...extending to 125 LABELS list is full...extending to 130 LABELS list is full...extending to 135 sorting score ... Clockbase = 0.000000 ... done Csound version 5.12 beta (float samples) Aug 13 2010 displays suppressed 0dBFS level = 1.0 ftable 1000: ftable 1001: ftable 1002: ftable 1003: ftable 1004: ftable 1005: ftable 1006: ftable 1007: ftable 1008: ftable 1009: ftable 1010: ftable 1011: ftable 1012: ftable 1013: ftable 1014: ftable 1015: ftable 1016: ftable 1017: ftable 1018: ftable 2000: ftable 2001: orch now loaded audio buffered in 1024 sample-frame blocks writing 6144-byte blks of 24bit ints to /tmp/test.wav (WAV) SECTION 1: On Wed, Nov 10, 2010 at 2:36 PM, |
Date | 2010-11-13 10:04 |
From | Enrico Francioni |
Subject | [Csnd] Re: Automatic printing |
excuse ben, but I still do not understand what your remedy to prevent the automatic printing… e -- View this message in context: http://csound.1045644.n5.nabble.com/Automatic-printing-tp3251724p3263410.html Sent from the Csound - General mailing list archive at Nabble.com. Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
Date | 2010-11-13 14:06 |
From | joachim heintz |
Subject | [Csnd] Re: Re: Automatic printing |
i think there is no remedy because even -m0 prints something. there is the -O flag (http://www.csounds.com/manual/html/CommandFlags.html#FlagsMinusUpperO ). when used as -O null it should suppress all printing. for me, it just works when it is set explicitely in the command line, like csound -O null bla.csd but it has no effect when it's written in the CsOptions part of a csd file. i don't know whether this must be, or is a small bug. joachim Am 13.11.2010 um 11:04 schrieb Enrico Francioni: > > > > excuse ben, > but I still do not understand what your remedy to prevent the > automatic > printing… > > e > -- > View this message in context: http://csound.1045644.n5.nabble.com/Automatic-printing-tp3251724p3263410.html > Sent from the Csound - General mailing list archive at Nabble.com. > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body > "unsubscribe csound" > > Send bugs reports to the Sourceforge bug tracker https://sourceforge.net/tracker/?group_id=81968&atid=564599 Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
Date | 2010-11-13 21:21 |
From | Marco Stroppa |
Subject | [Csnd] AW: Re: Re: Automatic printing |
If I may express my opinion, I'd sayt that the information that is printed at the beginning of a synthesis process is not so "problematic", since it happens only once. It is the information printed at every allocation of the instrument that may slow the synthesis down considerably if there are thousands or more instances. By me (csound 5.12 on a Macintel), the -O flag does not seem to work properly: flag defaults: csound -s -otest -b1024 -B4096 -m135 Csound Command ERROR:no log file signalflowgraph: CsoundModuleDestroy(0xdc000) But perhaps it's my problem. In any case, a flag suppressing all the graphics (or as much as possible of them) would be helpful, especially when running Csound from another program. All the best to all the Csounders! Marco ----- Ursprüngliche Mail ---- > Von: joachim heintz |
Date | 2010-11-14 19:50 |
From | ben hackbarth |
Subject | [Csnd] Re: AW: Re: Re: Automatic printing |
fair enough, marco. my message was only to note that csound's stdout would be much more useful if the user could configure, more robustly, what information they want to see and suppress that which they do not. the -m flag is a start, but the options still leave something to be desired, IMO. i'd love to have a setting which suppresses all printing except for note amplitudes and samples out-of-range (besides user-specified printing, of course). meaning no configuration information (like i noted above) and no verbose debugging messages (like the one that you've noted). cheers, — ben On Sat, Nov 13, 2010 at 10:21 PM, Marco Stroppa |
Date | 2010-11-16 08:40 |
From | Marco Stroppa |
Subject | [Csnd] AW: Re: AW: Re: Re: Automatic printing |
Dear Ben, I do agree with you, it would be great if one could configure the structure of the printout more robustly, but I simply do not know how thorny it might be to go through the code and set it up in this way. In the meantime, perhaps, being able to suppress at least the messages that seem to slow down the synthesis would already be a big step forward. Ciao! Marco ----- Ursprüngliche Mail ---- > Von: ben hackbarth |
Date | 2010-11-16 13:57 |
From | Enrico Francioni |
Subject | [Csnd] Re: Automatic printing |
Ciao Marco, but what use frontend for csound 5.11? and |
Date | 2010-11-16 18:24 |
From | Marco Stroppa |
Subject | [Csnd] AW: Re: Automatic printing |
Hello, Enrico! I'm calling csound from a program in Lisp, and am not using any frontends. Frontends are very practical for me when testing, but risk being too cumbersome when one has hundreds of files to synthesize. Cheers! Marco ----- Ursprüngliche Mail ---- > Von: Enrico Francioni |
Date | 2010-11-16 18:33 |
From | Michael Gogins |
Subject | [Csnd] Re: AW: Re: Automatic printing |
Just out of curiosity, do you shell out from Lisp to exec Csound, or do you use the CFFI interface and call the Csound shared library directly? Regards, Mike On Tue, Nov 16, 2010 at 1:24 PM, Marco Stroppa |
Date | 2010-11-16 20:50 |
From | Marco Stroppa |
Subject | [Csnd] AW: Re: AW: Re: Automatic printing |
J'm shelling out from Lisp to exec Csound, since this allows me to call Csound (usually from a Terminal window) with the score and orc files that were automatically generated, in case I need to find out some details of the synthesis, and modify or correct them (even if the files are pretty big...!). Cheers. Marco ----- Ursprüngliche Mail ---- > Von: Michael Gogins |
Date | 2010-11-19 00:27 |
From | ben hackbarth |
Subject | [Csnd] Re: AW: Re: AW: Re: Automatic printing |
dear marco, just a thought: are you compiling csound from source? if so, you could comment out the offending line (in ugens4.c, i think) and recompile. regards, — ben On Tue, Nov 16, 2010 at 9:50 PM, Marco Stroppa |