Csound Csound-dev Csound-tekno Search About

[Csnd] QuteCsound, some question

Date2009-01-25 09:26
FromFederico Vanni
Subject[Csnd] QuteCsound, some question
i'm trying qutecsound, an interesting front ends for csound
on mac... thanks to andres cabrera...
i have some question about it:

1. the names of the opened fles remains in the toolbar,
it seems to be not possible to delete them. so the window
became more and more large... until to fill the whole
monitor.

2. by the preset "play" run the csound 5.08, not the
latest version i installed... (which runs by the preset
"play in terminal")... is it possible to change the version
of csound? by the "play" button the sound is segmented...
i change the buffer but nothing appens...

3. in regard to exsternal programs, i put the following
path: /Applications/Soundtrack Pro.app...
when i use "ext editor" or "ext player" this strange message
apper: "the document "deskop" cound not be opened"

do you have some suggestions?
thanks
fv







  

Date2009-01-25 22:34
FromAndres Cabrera
Subject[Csnd] Re: QuteCsound, some question
Hi,

On Sun, Jan 25, 2009 at 4:26 AM, Federico Vanni  wrote:
>
> i'm trying qutecsound, an interesting front ends for csound
> on mac... thanks to andres cabrera...
> i have some question about it:
>
> 1. the names of the opened fles remains in the toolbar,
> it seems to be not possible to delete them. so the window
> became more and more large... until to fill the whole
> monitor.
>

These are actually tabs, the documents are still open. You can close
documents with file->close or with command+W.

> 2. by the preset "play" run the csound 5.08, not the
> latest version i installed... (which runs by the preset
> "play in terminal")... is it possible to change the version
> of csound? by the "play" button the sound is segmented...
> i change the buffer but nothing appens...
>

QuteCsound currently uses the 5.08 API, even if 5.10 is installed.
This will be fixed in the next release. If sound is choppy usually the
problem is you need to run in a separate thread.


> 3. in regard to exsternal programs, i put the following
> path: /Applications/Soundtrack Pro.app...
> when i use "ext editor" or "ext player" this strange message
> apper: "the document "deskop" cound not be opened"
>

I suspect Soundtrack can't open audio files directly. Can you try
something like Audacity.


Cheers,
Andrés


> do you have some suggestions?
> thanks
> fv
>
>
>
>
>
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>



-- 


Andrés


Date2009-01-26 14:26
FromFederico Vanni
Subject[Csnd] Re: Re: QuteCsound, some question
Il giorno 25/gen/09, alle ore 23:34, Andres Cabrera ha scritto:



3. in regard to exsternal programs, i put the following

path: /Applications/Soundtrack Pro.app...

when i use "ext editor" or "ext player" this strange message

apper: "the document "deskop" cound not be opened"



I suspect Soundtrack can't open audio files directly. Can you try

something like Audacity.



Cheers,

Andrés



hi andreas, thank you for your reply.

i tried audacity, but qutecsound can't open
the file! i get a message that it can't open 
the folder of the file. 

if these few problems will be solved, 
qutecsound could be a great solution
for many mac users. thank you very much...
i have wished an easy front end like that.

moreover, it would be nice if we have 
the choice to put the csound version we
want.

best
fv 


   


Date2009-01-26 14:45
Frompeiman khosravi
Subject[Csnd] Re: Re: Re: QuteCsound, some question
Hi,

soundtrack pro opens audio directly so that's not the problem. I have the same issue with audacity on osx.

Best
Peiman

2009/1/26 Federico Vanni <fvanni84@gmail.com>
Il giorno 25/gen/09, alle ore 23:34, Andres Cabrera ha scritto:



3. in regard to exsternal programs, i put the following

path: /Applications/Soundtrack Pro.app...

when i use "ext editor" or "ext player" this strange message

apper: "the document "deskop" cound not be opened"



I suspect Soundtrack can't open audio files directly. Can you try

something like Audacity.



Cheers,

Andrés



hi andreas, thank you for your reply.

i tried audacity, but qutecsound can't open
the file! i get a message that it can't open 
the folder of the file. 

if these few problems will be solved, 
qutecsound could be a great solution
for many mac users. thank you very much...
i have wished an easy front end like that.

moreover, it would be nice if we have 
the choice to put the csound version we
want.

best
fv 


   



Date2009-01-26 14:50
From"Ryan"
Subject[Csnd] Re: Re: Re: QuteCsound, some question
I've actually been experiencing this exact same thing with Csound GUI for Windows since 5.08. I figure it has something to do with spaces in paths but putting the path in quotations doesn't help either. Anyone know a fix? It's kind of vexing to not be able to launch a different editor directly from the GUI.
 
Thanks,
Ryan
----- Original Message -----
Sent: Monday, January 26, 2009 8:26 AM
Subject: [Csnd] Re: Re: QuteCsound, some question

Il giorno 25/gen/09, alle ore 23:34, Andres Cabrera ha scritto:



3. in regard to exsternal programs, i put the following

path: /Applications/Soundtrack Pro.app...

when i use "ext editor" or "ext player" this strange message

apper: "the document "deskop" cound not be opened"



I suspect Soundtrack can't open audio files directly. Can you try

something like Audacity.



Cheers,

Andrés



hi andreas, thank you for your reply.

i tried audacity, but qutecsound can't open
the file! i get a message that it can't open 
the folder of the file. 

if these few problems will be solved, 
qutecsound could be a great solution
for many mac users. thank you very much...
i have wished an easy front end like that.

moreover, it would be nice if we have 
the choice to put the csound version we
want.

best
fv 


   


Date2009-01-26 15:24
Frompeiman khosravi
Subject[Csnd] Re: Re: Re: Re: QuteCsound, some question
yes csound gui never worked properly for me on os x. The terminal command for opening a sound file with an application is:

open -a audacity soundfile.aif

Where audacity can be replaced by any application installed in the applications folder.   

2009/1/26 Ryan <mediaahrecords@gmail.com>
I've actually been experiencing this exact same thing with Csound GUI for Windows since 5.08. I figure it has something to do with spaces in paths but putting the path in quotations doesn't help either. Anyone know a fix? It's kind of vexing to not be able to launch a different editor directly from the GUI.
 
Thanks,
Ryan
----- Original Message -----
Sent: Monday, January 26, 2009 8:26 AM
Subject: [Csnd] Re: Re: QuteCsound, some question

Il giorno 25/gen/09, alle ore 23:34, Andres Cabrera ha scritto:



3. in regard to exsternal programs, i put the following

path: /Applications/Soundtrack Pro.app...

when i use "ext editor" or "ext player" this strange message

apper: "the document "deskop" cound not be opened"



I suspect Soundtrack can't open audio files directly. Can you try

something like Audacity.



Cheers,

Andrés



hi andreas, thank you for your reply.

i tried audacity, but qutecsound can't open
the file! i get a message that it can't open 
the folder of the file. 

if these few problems will be solved, 
qutecsound could be a great solution
for many mac users. thank you very much...
i have wished an easy front end like that.

moreover, it would be nice if we have 
the choice to put the csound version we
want.

best
fv 


   



Date2009-01-27 12:25
From"Ryan Olejnik"
Subject[Csnd] Csound 5 GUI Paths
For those of you on Windows using Csound 5 GUI who wish to be able to edit their files in an external editor, you're going to have to edit your paths that have spaces (path to editor and file) to use the short names. These are easy to find using dir /x in cmd. The naming convention is typically the first six characters of the folder or file ending with ~1 or a successive number for each file or folder which is similiarly named.
 
EXAMPLES:
 
(C:\Program Files\This Is a Test.txt) =
C:\PROGRA~1\THISIS~1.TXT
 
(C:\Program Files\This Is a Test2.txt) =
C:\PROGRA~1\THISIS~2.TXT
 
Could getting the short name automatically from the file dialog be hacked into the code?
 
Ryan
 
----- Original Message -----
From: Ryan
Sent: Monday, January 26, 2009 8:50 AM
Subject: Re: [Csnd] Re: Re: QuteCsound, some question

I've actually been experiencing this exact same thing with Csound GUI for Windows since 5.08. I figure it has something to do with spaces in paths but putting the path in quotations doesn't help either. Anyone know a fix? It's kind of vexing to not be able to launch a different editor directly from the GUI.
 
Thanks,
Ryan
----- Original Message -----
Sent: Monday, January 26, 2009 8:26 AM
Subject: [Csnd] Re: Re: QuteCsound, some question

Il giorno 25/gen/09, alle ore 23:34, Andres Cabrera ha scritto:



3. in regard to exsternal programs, i put the following

path: /Applications/Soundtrack Pro.app...

when i use "ext editor" or "ext player" this strange message

apper: "the document "deskop" cound not be opened"



I suspect Soundtrack can't open audio files directly. Can you try

something like Audacity.



Cheers,

Andrés



hi andreas, thank you for your reply.

i tried audacity, but qutecsound can't open
the file! i get a message that it can't open 
the folder of the file. 

if these few problems will be solved, 
qutecsound could be a great solution
for many mac users. thank you very much...
i have wished an easy front end like that.

moreover, it would be nice if we have 
the choice to put the csound version we
want.

best
fv 


   


Date2009-01-27 16:06
From"Ryan Olejnik"
Subject[Csnd] Re: Csound 5 GUI Paths
Okay, I'm sort of a Sunday programmer here but I took a look at the code. So, basically, Csound GUI is using FLTK's NativeFileChooser class and methods for a portable common dialog box... I'm guessing you would need to alter the FLTK code in order to pass the OFN_NOLONGNAMES flag to the OPENFILENAME struct? I apologize if this inquiry seems rather silly but I've only begun to embark on the Win32 API and have no knowledge of FLTK. And I'm just trying to understand what's going on here because having to manually edit the paths to short names or not being able to simply click edit is a real inconvenience.
 
Thanks,
Ryan 
----- Original Message -----
Sent: Tuesday, January 27, 2009 6:25 AM
Subject: Csound 5 GUI Paths

For those of you on Windows using Csound 5 GUI who wish to be able to edit their files in an external editor, you're going to have to edit your paths that have spaces (path to editor and file) to use the short names. These are easy to find using dir /x in cmd. The naming convention is typically the first six characters of the folder or file ending with ~1 or a successive number for each file or folder which is similiarly named.
 
EXAMPLES:
 
(C:\Program Files\This Is a Test.txt) =
C:\PROGRA~1\THISIS~1.TXT
 
(C:\Program Files\This Is a Test2.txt) =
C:\PROGRA~1\THISIS~2.TXT
 
Could getting the short name automatically from the file dialog be hacked into the code?
 
Ryan
 
----- Original Message -----
From: Ryan
Sent: Monday, January 26, 2009 8:50 AM
Subject: Re: [Csnd] Re: Re: QuteCsound, some question

I've actually been experiencing this exact same thing with Csound GUI for Windows since 5.08. I figure it has something to do with spaces in paths but putting the path in quotations doesn't help either. Anyone know a fix? It's kind of vexing to not be able to launch a different editor directly from the GUI.
 
Thanks,
Ryan
----- Original Message -----
Sent: Monday, January 26, 2009 8:26 AM
Subject: [Csnd] Re: Re: QuteCsound, some question

Il giorno 25/gen/09, alle ore 23:34, Andres Cabrera ha scritto:



3. in regard to exsternal programs, i put the following

path: /Applications/Soundtrack Pro.app...

when i use "ext editor" or "ext player" this strange message

apper: "the document "deskop" cound not be opened"



I suspect Soundtrack can't open audio files directly. Can you try

something like Audacity.



Cheers,

Andrés



hi andreas, thank you for your reply.

i tried audacity, but qutecsound can't open
the file! i get a message that it can't open 
the folder of the file. 

if these few problems will be solved, 
qutecsound could be a great solution
for many mac users. thank you very much...
i have wished an easy front end like that.

moreover, it would be nice if we have 
the choice to put the csound version we
want.

best
fv 


   


Date2009-01-28 00:40
FromAndres Cabrera
Subject[Csnd] Re: Re: Csound 5 GUI Paths
Hi Ryan,

Csound5GUI is abandoned right now, and quite buggy... I suggest you
try something like QuteCsound.

Cheers,
Andrés

On Tue, Jan 27, 2009 at 11:06 AM, Ryan Olejnik  wrote:
> Okay, I'm sort of a Sunday programmer here but I took a look at the code.
> So, basically, Csound GUI is using FLTK's NativeFileChooser class and
> methods for a portable common dialog box... I'm guessing you would need to
> alter the FLTK code in order to pass the OFN_NOLONGNAMES flag to the
> OPENFILENAME struct? I apologize if this inquiry seems rather silly but I've
> only begun to embark on the Win32 API and have no knowledge of FLTK. And I'm
> just trying to understand what's going on here because having to manually
> edit the paths to short names or not being able to simply click edit is a
> real inconvenience.
>
> Thanks,
> Ryan
>
> ----- Original Message -----
> From: Ryan Olejnik
> To: csound@lists.bath.ac.uk
> Sent: Tuesday, January 27, 2009 6:25 AM
> Subject: Csound 5 GUI Paths
> For those of you on Windows using Csound 5 GUI who wish to be able to edit
> their files in an external editor, you're going to have to edit your paths
> that have spaces (path to editor and file) to use the short names. These are
> easy to find using dir /x in cmd. The naming convention is typically the
> first six characters of the folder or file ending with ~1 or a
> successive number for each file or folder which is similiarly named.
>
> EXAMPLES:
>
> (C:\Program Files\This Is a Test.txt) =
> C:\PROGRA~1\THISIS~1.TXT
>
> (C:\Program Files\This Is a Test2.txt) =
> C:\PROGRA~1\THISIS~2.TXT
>
> Could getting the short name automatically from the file dialog be hacked
> into the code?
>
> Ryan
>
> ----- Original Message -----
>
> From: Ryan
> To: csound@lists.bath.ac.uk
> Sent: Monday, January 26, 2009 8:50 AM
> Subject: Re: [Csnd] Re: Re: QuteCsound, some question
> I've actually been experiencing this exact same thing with Csound GUI for
> Windows since 5.08. I figure it has something to do with spaces in paths but
> putting the path in quotations doesn't help either. Anyone know a fix? It's
> kind of vexing to not be able to launch a different editor directly from
> the GUI.
>
> Thanks,
> Ryan
>
> ----- Original Message -----
> From: Federico Vanni
> To: csound@lists.bath.ac.uk
> Sent: Monday, January 26, 2009 8:26 AM
> Subject: [Csnd] Re: Re: QuteCsound, some question
> Il giorno 25/gen/09, alle ore 23:34, Andres Cabrera ha scritto:
>
>
> 3. in regard to exsternal programs, i put the following
>
> path: /Applications/Soundtrack Pro.app...
>
> when i use "ext editor" or "ext player" this strange message
>
> apper: "the document "deskop" cound not be opened"
>
> I suspect Soundtrack can't open audio files directly. Can you try
>
> something like Audacity.
>
> Cheers,
>
> Andrés
>
> hi andreas, thank you for your reply.
> i tried audacity, but qutecsound can't open
> the file! i get a message that it can't open
> the folder of the file.
> if these few problems will be solved,
> qutecsound could be a great solution
> for many mac users. thank you very much...
> i have wished an easy front end like that.
> moreover, it would be nice if we have
> the choice to put the csound version we
> want.
> best
> fv
>
>
>



-- 


Andrés