How close are we to a reasonable stopping point?

I have made most of the changes I had developed, and there are only a
couple of things outstanding.  I feel that it might be a little tight
for 1 Oct, but what do people think?
  As a strawman, how about tagging on Monday, with actual release on
Wed or Thursday?

==John ffitch

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I would guess that manual entries for cpsmidinn and friends still need to be
done as I have not written them.  I will probably not be able to do that
until Monday at this point (sorry) but I have no plans to make any more
changes to the code base.

Anthony

> On 9/27/07, jpff  wrote:
>> How close are we to a reasonable stopping point?
>> 
>> I have made most of the changes I had developed, and there are only a
>> couple of things outstanding.  I feel that it might be a little tight
>> for 1 Oct, but what do people think?
>> As a strawman, how about tagging on Monday, with actual release on
>> Wed or Thursday?


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Anthony,
When do you think you can prepare the manual entries? I think the manual 
should wait until this is ready since it's one of the new features in 
this version. If you're too tied up, I can help you format the entries, 
just send them as plain text.

Cheers,
Andrés

Anthony Kozar escribió:
> I would guess that manual entries for cpsmidinn and friends still need to be
> done as I have not written them.  I will probably not be able to do that
> until Monday at this point (sorry) but I have no plans to make any more
> changes to the code base.
>
> Anthony
>
>   
>> On 9/27/07, jpff  wrote:
>>     
>>> How close are we to a reasonable stopping point?
>>>
>>> I have made most of the changes I had developed, and there are only a
>>> couple of things outstanding.  I feel that it might be a little tight
>>> for 1 Oct, but what do people think?
>>> As a strawman, how about tagging on Monday, with actual release on
>>> Wed or Thursday?
>>>       
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Andrés, 

Sorry but I forgot that I had some commitments today for most of the
afternoon and evening.  But the changes are pretty straightforward as I have
been looking at what needs to be done.  I will just copy from the cpspch,
etc. pages and list the *midinn opcodes on each of those pages as well.

I will get started on it tonight and should be able to commit sometime
tomorrow.

Anthony

PS.  On another topic, I am getting a compilation error in sfont.c at line
213 due to variable declarations after other code:

    char temp_string[24];
    int j;

I will just work around this for the release so that it does not need to be
retagged.

Andres Cabrera wrote on 9/30/07 1:56 PM:

> Hi Anthony,
> When do you think you can prepare the manual entries? I think the manual
> should wait until this is ready since it's one of the new features in
> this version. If you're too tied up, I can help you format the entries,
> just send them as plain text.
> 
> Cheers,
> Andrés
> 
> Anthony Kozar escribió:
>> I would guess that manual entries for cpsmidinn and friends still need to be
>> done as I have not written them.  I will probably not be able to do that
>> until Monday at this point (sorry) but I have no plans to make any more
>> changes to the code base.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks Anthony.

Anthony Kozar escribió:
> Hi Andrés, 
>
> Sorry but I forgot that I had some commitments today for most of the
> afternoon and evening.  But the changes are pretty straightforward as I have
> been looking at what needs to be done.  I will just copy from the cpspch,
> etc. pages and list the *midinn opcodes on each of those pages as well.
>
> I will get started on it tonight and should be able to commit sometime
> tomorrow.
>
> Anthony
>
> PS.  On another topic, I am getting a compilation error in sfont.c at line
> 213 due to variable declarations after other code:
>
>     char temp_string[24];
>     int j;
>
> I will just work around this for the release so that it does not need to be
> retagged.
>
> Andres Cabrera wrote on 9/30/07 1:56 PM:
>
>   
>> Hi Anthony,
>> When do you think you can prepare the manual entries? I think the manual
>> should wait until this is ready since it's one of the new features in
>> this version. If you're too tied up, I can help you format the entries,
>> just send them as plain text.
>>
>> Cheers,
>> Andrés
>>
>> Anthony Kozar escribió:
>>     
>>> I would guess that manual entries for cpsmidinn and friends still need to be
>>> done as I have not written them.  I will probably not be able to do that
>>> until Monday at this point (sorry) but I have no plans to make any more
>>> changes to the code base.
>>>       
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

The Linux installer is text driven, so moving from /usr/local/bin to
/usr/local is a simple change in the file def.ins in the tar file
==John ffitch

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

There's no real need to install. Just point OPCODEDIR to your source 
directory and run csound from there.

Cheers,
Andres


Vircy Parker escribió:
>
>
>     There is little work left for the package. However, I'm not hurrying
>     to finish it because current scons is broken in debian unstable[1],
>     which makes it kind of pointless to make an upload.
>
>
>     [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444204
>     
>     --
>
>             Felipe Sateler
>
>
> Hello, anyway really thanks for your work. While the deb package came, 
> what do you advice for to use csound5 in debian?. I dont like the 
> csound actual installer because is not reversible, there is not 
> uninstallation. Too, after to install it, I have errors of 
> localization of libraries and folders. The recourse of 
> /usr/local/bin/bin  is weird in common debian style, etc.  do you know 
> a  clean  way for csound5 installation ?
>
> How do you install last csound in your debian distro?
>
> Thanks, best
>
>
>
>
>  
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>   

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi All,

I'm on intel OSX 10.4.10
I downloaded the 5.07 intelOSX binaries and installed using the  
default Csound5.mpkg

on CLI instantiation I get the following errors

> Localisation of messages is disabled, using default language.
> Error opening plugin directory '/usr/local/lib/csound/plugins': No  
> such file or directory
>

-----
Also to report:
Winsound.app works (no graphics output)
csoundSGUI.app works
MacCsound won't instantiate - (confirming  Ma++'s note about same)
The MacCsound (PPC version) Csound5.mpkg from his link (over the top  
of the Intel version) works via his GUI.
However CLI aborts,  with same error as above (can't find plugins)

two questions:
1. should I have installed the plugins beforehand - if so, from  
where? and is there reference to the need to do this?
2. is there are "standard" way people have both MacCsound and the CLI  
version (.dmg, CVS source build etc) installed?

Thanks, as always,

David




_________________________________________________
experimental polymedia:	www.avatar.com.au
Sonic Communications Research Group,
University of Canberra:	 creative.canberra.edu.au/scrg/


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net