| I see your point, but unfortunately, for the majority of users, installing Csound without a GUI is
confusing. Some of the CsoundQT issues sometime turn out to be Csound issues in that
it’s Csound not exiting from a user error cleanly, or something of the kind, which is not
apparent in the command-line because the frontend is not on an event loop. I think we
have to work with these issues, which will benefit all frontends in the end.
========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952
> On 29 Oct 2016, at 09:15, Rory Walsh wrote:
>
> As long as we ship frontends with Csound people will assume when something doesn't work it is Csound's fault. You won't believe how often people have said to me, I tried Csound, but it didn't work. I really think this is detrimental to the sterling work being done on Csound by a small handful of extremely dedicated developers. So with that, it's time again for my once yearly plea for Csound to be packaged as a compiler only. Btw, I've never heard a user of Cabbage say they tried Csound and it didn't work. They simple say, "I tried Cabbage and it crashes, it's total crap". But thankfully Cabbage takes the brunt of their frustration, not the wonderful project that is Csound ;)
>
> On 29 October 2016 at 08:39, Victor Lazzarini wrote:
> Try opening preferences and selecting different audio output modules in the drop down list.
>
> It is a CsoundQT problem, so you might ask in their list as well.
>
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> > On 29 Oct 2016, at 04:28, Richard Holmes wrote:
> >
> > I'm returning to Csound after several years away. I installed it using brew on my Mac (running OS X 10.11.6), started up CsoundQt (version 0.9.2.1, Using Csound version:6070 Precision:double (64-bit)), and started running examples from the "Get Started" page. It all worked fine, for half an hour or so. Then, right after I experimented with creating a button widget, it stopped making sound.
> >
> > I'm using examples cut and pasted from http://csound.github.io/documentation.html . I pasted one below.
> >
> > I see one error in the CsoundQt output console: "WARNING: Buffer overrun in real-time audio input". Other than that the output looks reasonable. It ends with:
> >
> > Score finished in csoundPerformKsmps().
> > inactive allocs returned to freespace
> > end of score. overall amps: 1.2
> > overall samples out of range: 0
> > 0 errors in performance
> > Elapsed time at end of performance: real: 4.320s, CPU: 0.385s
> > closing device
> > 130 1024 sample blks of 64-bit floats written to dac
> >
> > I have verified the Mac's sound is on. I have verified the sound control panel settings look reasonable. I have verified other applications can produce sound. I have restarted the Mac and the problem persists.
> >
> > Any suggestions?
> >
> > Score:
> >
> >
> >
> >
> > instr 1
> > aOut vco2 1, p4
> > out aOut
> > endin
> >
> >
> >
> > i1 0 1 100
> > i1 1 1 200
> > i1 2 1 300
> >
> >
> >
> > Csound mailing list
> > Csound@listserv.heanet.ie
> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> > Send bugs reports to
> > https://github.com/csound/csound/issues
> > Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
> https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
|