Hi,

When I run  (as linked in the cpumeter opcode doc page) in :

The Canonical Csound Reference Manual

Version 5.19.0

Author: John ffitch

May 2011

New in Csound version 5.14, for Linux/Unix and OSX only

I get the following results:


mam15:~ markmillikan$ csound64 /Applications/csound\
extras/examples/cpumeter.csd
Csound version 5.19.02 (double samples) Jan 20 2013
UnifiedCSD: /Applications/csound extras/examples/cpumeter.csd
Creating options
Creating orchestra
Creating score
graph init
using callback interface
Parsing successful!
Elapsed time at end of orchestra compile: real: 0.002s, CPU: 0.002s
Sorting score
Elapsed time at end of score sort: real: 0.003s, CPU: 0.003s
0dBFS level = 1.0
orch now loaded
audio buffered in 1024 sample-frame blocks
PortAudio V19-devel (built Oct  3 2012 09:31:53)
PortAudio: available output devices:
   0: Built-in Output
PortAudio: selected output device 'Built-in Output'
writing 1024 sample blks of 64-bit floats to dac
SECTION 1:
ftable 1:
new alloc for instr 1:
INIT ERROR in instr 1: Failed to open /proc/stat: No such file or
directory    <<<<<<<<<<<<<<<<<<<
k0	cpumeter	0.1	
Csound tidy up: Segmentation fault
inactive allocs returned to freespace
end of score.		   overall amps:  0.00000
	   overall samples out of range:        0
0 errors in performance
Elapsed time at end of performance: real: 0.409s, CPU: 0.080s
0 1024 sample blks of 64-bit floats written to dac
mam15:~ markmillikan$

1. Why is it trying to call procfs on osx?
2. Many (most?) of the simple example files / tutorials I've tried
appear to heavily load the cpu(s) in my macbook pro.
    It gets very warm and activity monitor shows one core pegged and
the others with significant activity.
    Any suggested documentation to look at for pointers on (hardware)
performance tips?

thx