Hi all,
I'm back here to ask you for a help to solve a issue I've faced on Xubuntu
using CsoundQT v.0.8.0.
I have to say I'm about a beginner in Linux environment: infact I started
using it only some months ago when I decided to install a really light
distro of Ubuntu on VirtualBox running on Windows. Then some weeks ago, I
decided to start to install the last version of Csound (6.00.1) and the
front-end CsoundQT (0.8.0, as I already written). I think, also following
your guides on Sourceforge, I installed both packages in the right way,
because no errors appeared on the terminal but, anyway, I've faced, and I
still face this issue: each time I run a project on CsoundQT, it
inexplicably freezes and I'm forced to terminate its process from Task
Manager.
So, anyone can please help me to understand the nature of this issue and
then to solve it?

Thanks.
Greetings.



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009.html
Sent from the Csound - General mailing list archive at Nabble.com.

laurence wrote
> I think I have encountered "inexplicable" freezes before here when
> "portmidi" was
> chosen as the "RT Midi Module" in the configuration.

Thanks for suggestion; I'll try to disable PortMIDI.



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729016.html
Sent from the Csound - General mailing list archive at Nabble.com.

Unfortunately, the issue persists also disabling MIDI Module (or even
enabling a module different from PortMIDI).

I'd also like to point that Csound works fine if it is run from terminal:
that is because I think the issue regards only CsoundQT.



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729017.html
Sent from the Csound - General mailing list archive at Nabble.com.

Does the project freeze before it plays any sound?
On 2 Nov 2013, at 12:45, Rodolfo Cangiotti wrote:

> Unfortunately, the issue persists also disabling MIDI Module (or even
> enabling a module different from PortMIDI).
> 
> I'd also like to point that Csound works fine if it is run from terminal:
> that is because I think the issue regards only CsoundQT.
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729017.html
> Sent from the Csound - General mailing list archive at Nabble.com.
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

Victor Lazzarini wrote
> Does the project freeze before it plays any sound?

Yes, as soon as I click on Run.


I don't know if this is useful to isolate the cause of this issue but, as
you can see in this screenshot, the Run button seems to be already pressed
each time I start CsoundQT. Does the same thing happen to you too? 

 




--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729024.html
Sent from the Csound - General mailing list archive at Nabble.com.

i think that might be related to the Rt Audio configuration.

can you try to open the Configuration panel, and then look at the Rt 
Audio Module:
try selecting Alsa, and adc for input device, dac for output device.
try selecting "none" for Rt MIDI Module.

then run Examples > Getting Started > Basics > Hello World.

hope this helps, all best -

	joachim


Am 02.11.2013 15:38, schrieb Rodolfo Cangiotti:
> Victor Lazzarini wrote
>> Does the project freeze before it plays any sound?
>
> Yes, as soon as I click on Run.
>
>
> I don't know if this is useful to isolate the cause of this issue but, as
> you can see in this screenshot, the Run button seems to be already pressed
> each time I start CsoundQT. Does the same thing happen to you too?
>
> 
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729024.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>

Although I set:
- RT Audio: ALSA (adc, dac)
- RT MIDI: none (blank)
CsoundQT still freezes, also running "Hello World" example.

Sincerely, it seems this issue isn't easy to solve and I don't know what to
do unless trying to re-install it. What about it?



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729078.html
Sent from the Csound - General mailing list archive at Nabble.com.

Hi Rodolfo,

I didn't catch if you mentioned it, but did you compile csound and
csoundQT?  If so, there may have been fixes since 6.00.1 for csound
(we're on 6.01.0 now).  Also, CsoundQT has had a number of fixes too
since 0.8.0.  If you're compiling you might want to try getting the
latest from git for both of those.

steven

On Sun, Nov 3, 2013 at 10:05 AM, Rodolfo Cangiotti  wrote:
> Although I set:
> - RT Audio: ALSA (adc, dac)
> - RT MIDI: none (blank)
> CsoundQT still freezes, also running "Hello World" example.
>
> Sincerely, it seems this issue isn't easy to solve and I don't know what to
> do unless trying to re-install it. What about it?
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729078.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

Steven Yi wrote
> Hi Rodolfo,
> 
> I didn't catch if you mentioned it, but did you compile csound and
> csoundQT?  If so, there may have been fixes since 6.00.1 for csound
> (we're on 6.01.0 now).  Also, CsoundQT has had a number of fixes too
> since 0.8.0.  If you're compiling you might want to try getting the
> latest from git for both of those.
> 
> steven

Ah, ok. So I'll try to update both.
Is it enough to overwrite the current installation or should I uninstall the
current version and install the new one? And, in the second case, how to
uninstall it?



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729083.html
Sent from the Csound - General mailing list archive at Nabble.com.

I don't know regarding CsoundQT, but with Csound, if you used cmake
and ran "make install", you should be able to do "make uninstall" in
the folder you built in.  I imagine if you built from Git that the
changes since 6.00.1 wouldn't affect artifacts built, so an install
would just overwrite everything.

On Sun, Nov 3, 2013 at 11:00 AM, Rodolfo Cangiotti  wrote:
> Steven Yi wrote
>> Hi Rodolfo,
>>
>> I didn't catch if you mentioned it, but did you compile csound and
>> csoundQT?  If so, there may have been fixes since 6.00.1 for csound
>> (we're on 6.01.0 now).  Also, CsoundQT has had a number of fixes too
>> since 0.8.0.  If you're compiling you might want to try getting the
>> latest from git for both of those.
>>
>> steven
>
> Ah, ok. So I'll try to update both.
> Is it enough to overwrite the current installation or should I uninstall the
> current version and install the new one? And, in the second case, how to
> uninstall it?
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729083.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

Hi,

CsoundQt is just one binary file, that should be in the bin directory of your 
build source (named CsoundQt-d-cs6-py or something like that).
If you wish, you can just delete it.

If you rebuild, I suggest you clean also leftovers from previous build
make clean
make

Please let know, how it goes! Perhaps embedded linux or linux on a virtual 
machin within windows can be on possible way to get the lates CsoundQt for 
windos users.

best!
tarmo 


On Sunday 03 November 2013 11:06:52 Steven Yi wrote:
> I don't know regarding CsoundQT, but with Csound, if you used cmake
> and ran "make install", you should be able to do "make uninstall" in
> the folder you built in.  I imagine if you built from Git that the
> changes since 6.00.1 wouldn't affect artifacts built, so an install
> would just overwrite everything.
> 
> On Sun, Nov 3, 2013 at 11:00 AM, Rodolfo Cangiotti  
wrote:
> > Steven Yi wrote
> > 
> >> Hi Rodolfo,
> >> 
> >> I didn't catch if you mentioned it, but did you compile csound and
> >> csoundQT?  If so, there may have been fixes since 6.00.1 for csound
> >> (we're on 6.01.0 now).  Also, CsoundQT has had a number of fixes too
> >> since 0.8.0.  If you're compiling you might want to try getting the
> >> latest from git for both of those.
> >> 
> >> steven
> > 
> > Ah, ok. So I'll try to update both.
> > Is it enough to overwrite the current installation or should I uninstall
> > the current version and install the new one? And, in the second case, how
> > to uninstall it?
> > 
> > 
> > 
> > --
> > View this message in context:
> > http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-t
> > p5729009p5729083.html Sent from the Csound - General mailing list archive
> > at Nabble.com.
> > 
> > 
> > Send bugs reports to the Sourceforge bug trackers
> > 
> > csound6:
> >             https://sourceforge.net/p/csound/tickets/
> > 
> > csound5:
> >             https://sourceforge.net/p/csound/bugs/
> > 
> > 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 trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"

Well, to make all easier, I restored a disk image on VirtualBox created
before installing the previous version of Csound. Then, I followed your
guide on Sourceforge.net to install the latest Csound release by GIT: during
the "make" phase, on terminal some warnings, that I hope they didn't
influence the next installation phase, appeared.
Afterall, I created a simple Hello World file and I ran it on terminal; it
works but two suspected errors appears.

This is the .csd file I ran

>  
> 
> 
> 
> 
> sr		= 44100
> ksmps	= 512
> nchnls	= 1
> 0dbfs	= 1
> 
> instr 1
> prints "\\nHello World!\\n\\n"
> endin
> 
> 
> i 1 0 -1
> e
> 
> 

And these are the errors appeard on terminal:

> Error: define environment variable RAWWAVE_PATH
> (points to rawwaves directory) to use STK opcodes.

I have to say that, trying to solve this error, I also followed your
previous guide to edit etc\environment file. Maybe, is the RAWWAVE_PATH I
added to environment file not correct?



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729099.html
Sent from the Csound - General mailing list archive at Nabble.com.

I think  that is not an error, just a warning. It only affects the stk opcodes.  Sounds like your installation is generally good.
On 4 Nov 2013, at 00:24, Rodolfo Cangiotti wrote:

> Well, to make all easier, I restored a disk image on VirtualBox created
> before installing the previous version of Csound. Then, I followed your
> guide on Sourceforge.net to install the latest Csound release by GIT: during
> the "make" phase, on terminal some warnings, that I hope they didn't
> influence the next installation phase, appeared.
> Afterall, I created a simple Hello World file and I ran it on terminal; it
> works but two suspected errors appears.
> 
> This is the .csd file I ran
> 
>> 
>> 
>> 
>> 
>> 
>> sr		= 44100
>> ksmps	= 512
>> nchnls	= 1
>> 0dbfs	= 1
>> 
>> instr 1
>> prints "\\nHello World!\\n\\n"
>> endin
>> 
>> 
>> i 1 0 -1
>> e
>> 
>> 
> 
> And these are the errors appeard on terminal:
> 
>> Error: define environment variable RAWWAVE_PATH
>> (points to rawwaves directory) to use STK opcodes.
> 
> I have to say that, trying to solve this error, I also followed your
> previous guide to edit etc\environment file. Maybe, is the RAWWAVE_PATH I
> added to environment file not correct?
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729099.html
> Sent from the Csound - General mailing list archive at Nabble.com.
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

Ok, so this morning I started CsoundQT's installation with RT Midi. I ran: 
> sudo qmake qcs.pro LIBSNDFILE_LIBRARY_DIR=/usr/lib/i386-linux-gnu
> CSOUND_LIBRARY_DIR=/usr/local/lib/
> CSOUND_INCLUDE_DIR=/usr/local/include/csound CONFIG+=rtmidi
> RTMIDI_DIR=/home/rodolfo/Risorse_Csound/qutecsound/rtmidi-2.0.1

Paths seem correct; but the "make" phase stops with: 
>  make: *** [build/doubles/obj/csoundengine.o] Errore 1 

I tried defining CSOUND_INTERFACES_INCLUDE_DIR with
/usr/local/include/csound/interfaces but the error still occurs.

Sincerely, I thought that a Linux OS use was easier than it really is! :)




--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729116.html
Sent from the Csound - General mailing list archive at Nabble.com.

i think we forgot to update the install instructions after andrés did a 
change which simplifies a lot for people who build from source (as you do).
can you try only to specify CSOUND_SOURCE_TREE instead of 
CSOUND_INTERFACES_INCLUDE_DIR etc?
this is my command now, which you certainly can apply to your paths:

qmake qcs.pro CONFIG+=csound6 
LIBSNDFILE_LIBRARY_DIR=/usr/lib/x86_64-linux-gnu CONFIG+=rtmidi 
RTMIDI_DIR=../rtmidi-2.0.1 CONFIG+=pythonqt 
PYTHONQT_SRC_DIR=../PythonQt2.1_Qt4.8 
CSOUND_SOURCE_TREE=/home/jh/src/csound6-git

please let us know if it works; i should not forget then to update the 
instructions.
best -
	joachim


Am 04.11.2013 15:30, schrieb Rodolfo Cangiotti:
> Ok, so this morning I started CsoundQT's installation with RT Midi. I ran:
>> sudo qmake qcs.pro LIBSNDFILE_LIBRARY_DIR=/usr/lib/i386-linux-gnu
>> CSOUND_LIBRARY_DIR=/usr/local/lib/
>> CSOUND_INCLUDE_DIR=/usr/local/include/csound CONFIG+=rtmidi
>> RTMIDI_DIR=/home/rodolfo/Risorse_Csound/qutecsound/rtmidi-2.0.1
>
> Paths seem correct; but the "make" phase stops with:
>>   make: *** [build/doubles/obj/csoundengine.o] Errore 1
>
> I tried defining CSOUND_INTERFACES_INCLUDE_DIR with
> /usr/local/include/csound/interfaces but the error still occurs.
>
> Sincerely, I thought that a Linux OS use was easier than it really is! :)
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729116.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>

Hi!

Don't give up! Sure there is a way to make it work!

Can you also forward, what is the output of you qmake command,

also I noted that you ran qmake withs sudo , that runs the command as root - 
the administrator - and all files created by that command belong to root and 
maybe the make command could not use some of them. Usually for building, sudo 
is not necessary,

try 
qmake qcs.pro etc 

(and have a look to the e-mail from Joachim about possible settings of the 
qmake options)

and make without sudo, only if you need to install something, use
sudo install (then you get access to system folders)

if you get errors, please forward, what was the output and which command 
caused it.

best!
tarmo



On Monday 04 November 2013 06:30:36 Rodolfo Cangiotti wrote:
> Ok, so this morning I started CsoundQT's installation with RT Midi. I ran:
> > sudo qmake qcs.pro LIBSNDFILE_LIBRARY_DIR=/usr/lib/i386-linux-gnu
> > CSOUND_LIBRARY_DIR=/usr/local/lib/
> > CSOUND_INCLUDE_DIR=/usr/local/include/csound CONFIG+=rtmidi
> > RTMIDI_DIR=/home/rodolfo/Risorse_Csound/qutecsound/rtmidi-2.0.1
> 
> Paths seem correct; but the "make" phase stops with:
> >  make: *** [build/doubles/obj/csoundengine.o] Errore 1
> 
> I tried defining CSOUND_INTERFACES_INCLUDE_DIR with
> /usr/local/include/csound/interfaces but the error still occurs.
> 
> Sincerely, I thought that a Linux OS use was easier than it really is! :)
> 
> 
> 
> 
> --
> View this message in context:
> http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5
> 729009p5729116.html Sent from the Csound - General mailing list archive at
> Nabble.com.
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"

Guys, I'm following the tips by Joachim and Tarmo; so I ran : 
> qmake qcs.pro CONFIG=+rtmidi
> LIBSNDFILE_LIBRARY_DIR=/usr/lib/i386-linux-gnu
> RT_MIDI_DIR=/home/rodolfo/Risorse_Csound/qutecsound-code/rtmidi-2.0.1
> CSOUND_SOURCE_TREE=/home/rodolfo/Risorse_Csound/cs6make

(as you can see, without sudo command).
And the output from terminal is:

> Project MESSAGE: 
> Project MESSAGE: Building CsoundQt for Unix-based system.
> Project MESSAGE: 
> Project MESSAGE: Building CsoundQt for the double precision version of
> Csound.
> Project MESSAGE: 
> Project MESSAGE: CONFIG ...
> Project MESSAGE: + +rtmidi
> Project MESSAGE: + build64
> Project MESSAGE: + thread
> Project MESSAGE: + warn_on
> Project MESSAGE: 
> Project MESSAGE: libsndfile include directory not specified.
> Project MESSAGE: ... searching in /usr/include
> Project MESSAGE: LIBSNDFILE_INCLUDE_DIR set to /usr/include
> Project MESSAGE: 
> Project MESSAGE: Csound API include directory is
> /home/rodolfo/Risorse_Csound/cs6make/include
> Project MESSAGE: Csound interfaces include directory is
> /home/rodolfo/Risorse_Csound/cs6make/interfaces
> Project MESSAGE: Csound library directory is
> /home/rodolfo/Risorse_Csound/cs6make
> Project MESSAGE: libsndfile include directory is /usr/include
> Project MESSAGE: libsndfile library directory is /usr/lib/i386-linux-gnu
> Project MESSAGE: 
> Project ERROR: csound.h not found

If I search csound.h file, it's in GIT folder, that is: 
> /home/rodolfo/Risorse_Csound/csound6

Should I add this path with CSOUND_INCLUDE_DIR command, shouldn't I?



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729169.html
Sent from the Csound - General mailing list archive at Nabble.com.

i think you should set
CSOUND_SOURCE_TREE=/home/rodolfo/Risorse_Csound/csound6
instead of
CSOUND_SOURCE_TREE=/home/rodolfo/Risorse_Csound/cs6make
because this has to point to the sources, not the build.

hope this gets you there ...
all best -
	joachim

Am 05.11.2013 16:10, schrieb Rodolfo Cangiotti:
> Guys, I'm following the tips by Joachim and Tarmo; so I ran :
>> qmake qcs.pro CONFIG=+rtmidi
>> LIBSNDFILE_LIBRARY_DIR=/usr/lib/i386-linux-gnu
>> RT_MIDI_DIR=/home/rodolfo/Risorse_Csound/qutecsound-code/rtmidi-2.0.1
>> CSOUND_SOURCE_TREE=/home/rodolfo/Risorse_Csound/cs6make
>
> (as you can see, without sudo command).
> And the output from terminal is:
>
>> Project MESSAGE:
>> Project MESSAGE: Building CsoundQt for Unix-based system.
>> Project MESSAGE:
>> Project MESSAGE: Building CsoundQt for the double precision version of
>> Csound.
>> Project MESSAGE:
>> Project MESSAGE: CONFIG ...
>> Project MESSAGE: + +rtmidi
>> Project MESSAGE: + build64
>> Project MESSAGE: + thread
>> Project MESSAGE: + warn_on
>> Project MESSAGE:
>> Project MESSAGE: libsndfile include directory not specified.
>> Project MESSAGE: ... searching in /usr/include
>> Project MESSAGE: LIBSNDFILE_INCLUDE_DIR set to /usr/include
>> Project MESSAGE:
>> Project MESSAGE: Csound API include directory is
>> /home/rodolfo/Risorse_Csound/cs6make/include
>> Project MESSAGE: Csound interfaces include directory is
>> /home/rodolfo/Risorse_Csound/cs6make/interfaces
>> Project MESSAGE: Csound library directory is
>> /home/rodolfo/Risorse_Csound/cs6make
>> Project MESSAGE: libsndfile include directory is /usr/include
>> Project MESSAGE: libsndfile library directory is /usr/lib/i386-linux-gnu
>> Project MESSAGE:
>> Project ERROR: csound.h not found
>
> If I search csound.h file, it's in GIT folder, that is:
>> /home/rodolfo/Risorse_Csound/csound6
>
> Should I add this path with CSOUND_INCLUDE_DIR command, shouldn't I?
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729169.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>

I know what you mean but if I run this command:

> qmake qcs.pro CONFIG=+rtmidi LIBSNDFILE_LIBRARY=/usr/lib/i386-linux-gnu
> CSOUND_SOURCE_TREE=/home/rodolfo/Risorse_Csound/csound6
> RT_MIDI_DIR=/home/rodolfo/Risorse_Csound/qutecsound-code/rtmidi-2.0.1

The output is:

> Project MESSAGE: 
> Project MESSAGE: Building CsoundQt for Unix-based system.
> Project MESSAGE: 
> Project MESSAGE: Building CsoundQt for the double precision version of
> Csound.
> Project MESSAGE: 
> Project MESSAGE: CONFIG ...
> Project MESSAGE: + +rtmidi
> Project MESSAGE: + build64
> Project MESSAGE: + thread
> Project MESSAGE: + warn_on
> Project MESSAGE: 
> Project ERROR: A valid csound library was not found.

Despite libsndfile.a *.so *.so.1 *.so.1.0.15 are in the directory I set in
"qmake" command.



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729171.html
Sent from the Csound - General mailing list archive at Nabble.com.

Damn, if I set CSOUND_SOURCE_TREE and CSOUND_LIBRARY_DIR, I'm able to
complete "qmake" phase but the error I already mentioned occurs during
"make".
Here is the output from terminal:

> In file included from src/csoundengine.h:30:0,
>                  from src/csoundengine.cpp:37:
> ../csound6/include/csound.hpp:159:16: warning: unused parameter ‘type’
> [-Wunused-parameter]
> src/csoundengine.cpp: In static member function ‘static void
> CsoundEngine::inputValueCallback(CSOUND*, const char*, double*)’:
> src/csoundengine.cpp:181:50: error: ‘csoundGetStrVarMaxLen’ was not
> declared in this scope
> src/csoundengine.cpp: At global scope:
> src/csoundengine.cpp:375:5: warning: unused parameter ‘type’
> [-Wunused-parameter]
> src/csoundengine.cpp:759:6: warning: unused parameter ‘delay’
> [-Wunused-parameter]
> src/csoundengine.cpp: In member function ‘int CsoundEngine::runCsound()’:
> src/csoundengine.cpp:821:29: error: ‘csoundPreCompile’ was not declared in
> this scope
> src/csoundengine.cpp:860:73: error: ‘csoundSetCallback’ was not declared
> in this scope
> src/csoundengine.cpp: In member function ‘void
> CsoundEngine::cleanupCsound()’:
> src/csoundengine.cpp:948:40: error: ‘csoundRemoveCallback’ was not
> declared in this scope
> src/csoundengine.cpp: In member function ‘void
> CsoundEngine::setupChannels()’:
> src/csoundengine.cpp:976:75: error: ‘csoundSetInputValueCallback’ was not
> declared in this scope
> src/csoundengine.cpp:977:77: error: ‘csoundSetOutputValueCallback’ was not
> declared in this scope
> src/csoundengine.cpp:984:2: error: ‘CsoundChannelListEntry’ was not
> declared in this scope
> src/csoundengine.cpp:984:26: error: ‘channelList’ was not declared in this
> scope
> src/csoundengine.cpp:986:26: error: ‘entry’ was not declared in this scope
> make: *** [build/doubles/obj/csoundengine.o] Errore 1

I rely to your knowledge for this kind of issues because I really don't know
what to do, now.



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729186.html
Sent from the Csound - General mailing list archive at Nabble.com.

Finally I have been able to build CsoundQT! I think the error was due to,
besides the lack of CONFIG+=csound6 as Andreas pointed out to me, a really
stupid typing error: I always wrote LIBSNDFILE_LIBRARY instead of
LIBSNDFILE_LIBRARY_DIR.
Anyway, the "qmake" phase reported some warnings but I think they are
neglectable.
Now, I have a last question: how can I set the RAWWAVE_PATH to work with
JACK module and STK Opcodes on CsoundQT?




--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729204.html
Sent from the Csound - General mailing list archive at Nabble.com.

Dear Rodolfo,
Congratulations!
You can add extra csound command line options in csoundqt in Configure->Run tab.
Unfortunately I don't know about STK opcodes....
Otherwise, does CsounQt work? Can you run some example csd and hear the sound?
Tarmo

Andres Cabrera wrote
> You can set the variable with:
> export RAWWAVE_PATH=/your/path
> and then run CsoundQt in that terminal.

Ok, fantastic. 
To make it permanent, I added the same path to /etc/environment and it seems
it works very well (I'm able to run all of the STK examples).
Regarding Jack, I'll be back soon to this subject because no hardware
appears in the Configuration tab under Jack.

Anyway, thanks again and again for your huge help.




--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729234.html
Sent from the Csound - General mailing list archive at Nabble.com.

Hi,

Jack has to be running for devices to appear.

Cheers,
Andres

... and then set in the Configure panel:
for Input device:  adc:system:capture_
and Output device:  dac:system:playback_

thanks to tarmo for this tip; it has saved me a lot of time; no need to 
manually connect anything in qjackctl. only make sure that you ksmps is 
an integer division of the jack buffer size.

best -
	joachim


Am 07.11.2013 02:10, schrieb Andres Cabrera:
> Hi,
>
> Jack has to be running for devices to appear.
>
> Cheers,
> Andres
>
> On Nov 6, 2013 5:08 PM, "Rodolfo Cangiotti"  > wrote:
>
>     Andres Cabrera wrote
>      > You can set the variable with:
>      > export RAWWAVE_PATH=/your/path
>      > and then run CsoundQt in that terminal.
>
>     Ok, fantastic.
>     To make it permanent, I added the same path to /etc/environment and
>     it seems
>     it works very well (I'm able to run all of the STK examples).
>     Regarding Jack, I'll be back soon to this subject because no hardware
>     appears in the Configuration tab under Jack.
>
>     Anyway, thanks again and again for your huge help.
>
>
>
>
>     --
>     View this message in context:
>     http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729234.html
>     Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>     Send bugs reports to the Sourceforge bug trackers
>     csound6:
>     https://sourceforge.net/p/csound/tickets/
>     csound5:
>     https://sourceforge.net/p/csound/bugs/
>     Discussions of bugs and features can be posted here
>     To unsubscribe, send email sympa@lists.bath.ac.uk
>      with body "unsubscribe csound"
>
>

Hi,

you can add line
export RAWWAVE_PATH=/your/path

to file .bashrc in your home directory, the variable gets loaded every time 
you log in (thus logout-login to make effect) and then you can run csound with 
the RAWWAVE_PATH from anywhere. I have included also the other audio varaibles 
in the basrc file:

export OPCODEDIR64=/usr/local/lib/csound/plugins64
export OPCODE6DIR64=/home/tarmo/src/cs6/lib/csound/plugins64-6.0 
export CSSTRNGS=/usr/local/share/locale
export LV2_PATH=/usr/lib64/lv2 # ardourile lv2 pluginad
export LADSPA_PATH=/home/tarmo/src/csLADSPA/

Is csound running fine? Do you have any perfomrance issues? Was it embedded 
linux or linux in a virtual machine? Would be good to suggest to other users, 
too. if it works fine.
take care!
tarmo





On Wednesday 06 November 2013 17:08:34 Rodolfo Cangiotti wrote:
> Andres Cabrera wrote
> 
> > You can set the variable with:
> > export RAWWAVE_PATH=/your/path
> > and then run CsoundQt in that terminal.
> 
> Ok, fantastic.
> To make it permanent, I added the same path to /etc/environment and it seems
> it works very well (I'm able to run all of the STK examples).
> Regarding Jack, I'll be back soon to this subject because no hardware
> appears in the Configuration tab under Jack.
> 
> Anyway, thanks again and again for your huge help.
> 
> 
> 
> 
> --
> View this message in context:
> http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5
> 729009p5729234.html Sent from the Csound - General mailing list archive at
> Nabble.com.
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"

So, I gather that /etc/environment and /home//.bashrc are different
only in loading time: I mean /etc/environment variables are loaded during
boot while /home//.bashrc variables are loaded when you log in,
aren't they?



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729253.html
Sent from the Csound - General mailing list archive at Nabble.com.

Regarding Jack, I sincerely don't know if it is already installed or not. How
should I do to discover this? Using the search function, appears a lot of
files that I suppose are library files but no executable file are found.



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729263.html
Sent from the Csound - General mailing list archive at Nabble.com.

Ok, I was interested in Jack and its settings because I read it performs
audio with a really low latency but, if you think that ALSA is enough for
CsoundQT, I'll deepen this subject in a second stage.



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729295.html
Sent from the Csound - General mailing list archive at Nabble.com.

Ah ok, so I will probably install it. I'm sorry but I thought that, when you
mentioned qjackctl as a front-end, you meant a programming environment with
its own programming language, for ex. like CsoundQT.



--
View this message in context: http://csound.1045644.n5.nabble.com/CsoundQT-v-0-8-0-freezes-on-Xubuntu-tp5729009p5729456.html
Sent from the Csound - General mailing list archive at Nabble.com.