[Cs-dev] gen23 again
| Date | 2014-10-05 19:22 |
| From | john ffitch |
| Subject | [Cs-dev] gen23 again |
There is a problem in gen23 in that it fiddles with the guard bit and reduces the size of the f-table by one. I have changed it in git again but I want to know if it breaks anything. I think gen23 was worked over recently so this might be a new problem. ==John ffitch ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
| Date | 2014-10-09 10:58 |
| From | menno |
| Subject | Re: [Cs-dev] gen23 again |
after the latest repair from John i can use the scan opcodes again, but not xscan etc. Output from the examples from the manual of xscans and xscansmap: file /home/menno/Csound_manual6.03/examples/128,8-cylinderX (3035 bytes) loaded into memory WARNING: rtjack: xrun in real time audio B 0.000 .. 10.000 T 10.000 TT 10.000 M: 0.99555 0.99555 end of section 1 sect peak amps: 0.99555 0.99555 *** Error in `/usr/local/bin/csound': double free or corruption (out): 0x0000000000fe42c0 *** Csound tidy up: Aborted Csound tidy up: Quit It plays one note, after which it stops. xscanu does not work at all, ftables are not displayed and CPU = 100% Same goes when i run the example from the manual gen23.csd: writing 512 sample blks of 64-bit floats to dac:system:playback_ SECTION 1: ftable 1: ftable 2: new alloc for instr 1: new alloc for instr 10: new alloc for instr 10: new alloc for instr 10: new alloc for instr 10: new alloc for instr 10: ............. ........... until i manually quit: Csound tidy up: Quit CPU = 94,7% I use KXStudio14.04, jack2 and Csound build 5 October -- View this message in context: http://csound.1045644.n5.nabble.com/gen23-again-tp5737811p5737848.html Sent from the Csound - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
| Date | 2014-10-09 14:28 |
| From | jpff |
| Subject | Re: [Cs-dev] gen23 again |
OK; another one for me to investigate ==John ff On Thu, 9 Oct 2014, menno wrote: > after the latest repair from John i can use the scan opcodes again, but not > xscan etc. > > Output from the examples from the manual of xscans and xscansmap: > > file /home/menno/Csound_manual6.03/examples/128,8-cylinderX (3035 bytes) > loaded into memory > WARNING: rtjack: xrun in real time audio > B 0.000 .. 10.000 T 10.000 TT 10.000 M: 0.99555 0.99555 > end of section 1 sect peak amps: 0.99555 0.99555 > *** Error in `/usr/local/bin/csound': double free or corruption (out): > 0x0000000000fe42c0 *** > Csound tidy up: Aborted > Csound tidy up: Quit > > It plays one note, after which it stops. > > xscanu does not work at all, ftables are not displayed and CPU = 100% > > Same goes when i run the example from the manual gen23.csd: > > writing 512 sample blks of 64-bit floats to dac:system:playback_ > SECTION 1: > ftable 1: > ftable 2: > new alloc for instr 1: > new alloc for instr 10: > new alloc for instr 10: > new alloc for instr 10: > new alloc for instr 10: > new alloc for instr 10: > ............. > ........... > > until i manually quit: > Csound tidy up: Quit > > CPU = 94,7% > > I use KXStudio14.04, jack2 and Csound build 5 October > > > > > -- > View this message in context: http://csound.1045644.n5.nabble.com/gen23-again-tp5737811p5737848.html > Sent from the Csound - Dev mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |
| Date | 2014-10-10 19:15 |
| From | jpff |
| Subject | Re: [Cs-dev] gen23 again |
The example xscanu.csd in the manual is wrong. It attempts to load 128-stringX with gen23, but it is not the right format. The files rhat start |
| Date | 2014-10-12 11:45 |
| From | jpff |
| Subject | Re: [Cs-dev] gen23 again |
I have made adjustments to (x)scanu which had a howler which caused the hammer to overwrite unknown areas of memory. In my tests it runs but not sure if it is right. In git now Also changed gen23 to ignore XML tags as if they were comment. There are warnings in the manual example whic are true as the input files are too long. ==John ff On Thu, 9 Oct 2014, menno wrote: > after the latest repair from John i can use the scan opcodes again, but not > xscan etc. > > Output from the examples from the manual of xscans and xscansmap: > > file /home/menno/Csound_manual6.03/examples/128,8-cylinderX (3035 bytes) > loaded into memory > WARNING: rtjack: xrun in real time audio > B 0.000 .. 10.000 T 10.000 TT 10.000 M: 0.99555 0.99555 > end of section 1 sect peak amps: 0.99555 0.99555 > *** Error in `/usr/local/bin/csound': double free or corruption (out): > 0x0000000000fe42c0 *** > Csound tidy up: Aborted > Csound tidy up: Quit > > It plays one note, after which it stops. > > xscanu does not work at all, ftables are not displayed and CPU = 100% > > Same goes when i run the example from the manual gen23.csd: > > writing 512 sample blks of 64-bit floats to dac:system:playback_ > SECTION 1: > ftable 1: > ftable 2: > new alloc for instr 1: > new alloc for instr 10: > new alloc for instr 10: > new alloc for instr 10: > new alloc for instr 10: > new alloc for instr 10: > ............. > ........... > > until i manually quit: > Csound tidy up: Quit > > CPU = 94,7% > > I use KXStudio14.04, jack2 and Csound build 5 October > > > > > -- > View this message in context: http://csound.1045644.n5.nabble.com/gen23-again-tp5737811p5737848.html > Sent from the Csound - Dev mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net |