Subscribe: SourceForge.net: SF.net Project News: Sound Orgy
http://sourceforge.net/export/rss2_projnews.php?group_id=86185
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
basic  code  create  developers  language  make  modules  orgy  programming language  programming  project  sound orgy  sound  week 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: SourceForge.net: SF.net Project News: Sound Orgy

Recent changes to news



Recent changes to news



Last Build Date: Tue, 04 May 2004 00:54:34 -0000

 



Code imported to CVS.

Tue, 04 May 2004 00:54:34 -0000

I have performed the initial import into the CVS. This code includes the Sound Orgy library (lib directory) and three basic modules: soc (clock), soo (oscillator) and sod (debug helper). Sod outputs data to a file as the stream passes it. The format is human readable and works with gnuplot.

Compiling the code from CVS can be done from the root Sound Orgy directory by:

cd lib
./compile
cd ../modules
./compile

I will now work on adding compiler options for 64 bit capability and optimization for the AMD64 platform. I will add support for expressions for input values. Then I will create modules for mixing and sample type converse (so we can output to sox).

Once I have completed those tasks, Sound Orgy 0.1.0 will be released. I will then start creating more modules and adding more features.




Rethinking the project. Code Is on the way!

Tue, 06 Apr 2004 19:06:40 -0000

As promised in November, I have thought about the development of the project and new code will be up shortly.

The goals of this project are to allow users to manipulate waves with modules and allow developers to easily create new modules. Initially, I had planned to create a programming language. I was thinking that maybe we are making the solution more complicated than it had to be. As such, I have scrapped the idea of a new programming language. Instead we will focus on making simple interoperable command line modules.

There are many developers well versed in C. It will be much easier for them not to learn a new programming language. Instead we will provide C libraries to make it easier for them to focus on writing the code that manipulates the signals instead writing code to allow interoperability. We will also produce a C template which would work well in most situations and allow developers to not have to worry about some of the gory details going on behind the scenes.

Last week I rewrote the test code I had initially writen in August. Once I had some basic modules working, I was well versed in some of the problems that arise when coding the modules. So I rewrote the test code and the libraries again. Now the libraries provide a foundation for writing interoperable modules.

I expect to be doing the initial import into the CVS later this week. We've got the details of interoperability almost ironed out. Once that is done, we can focus on code that processes the signals.




It's quiet right now.

Sun, 16 Nov 2003 09:27:39 -0000

It seems quiet right now.

Tune in early next year for more developement of ideas. Implementation of code expected to begin in 2004.




Last Weekly Update: Sound Orgy to have programming language

Sun, 17 Aug 2003 05:15:02 -0000

I have decided to can the weekly updates and instead report news whenever their is a significant developement.

I have started designing a programming langauge for Sound Orgy called SOL (Sound Orgy Language). It is similar to C. I am using BNF to describe the language. A BNF document will be up later this week. I will try to make it work with BNF Parser Generator.

Their will be two ways to use the language. SOI will be an interpreter that acts as a module. SOC will be a compiler that will make c files and uss gcc to compile them into Sound Orgy modules. These tools and the language will be core to the project.




Weekly Update: Basic structure taking form

Sat, 09 Aug 2003 23:30:53 -0000

Ok, I am hacking away at the code slowly in whatever free time I have. I have a established the basic method for communications between the modules.

I thinking about a simple programming language so that users may create their own modules. The language will be based on mathematical expressions to manipulate waves on individual channels. There will be a few commands to manipulate the stream. I haven't worked out the details of this language yet. The first stable version will come with common modules which are programmed in this language so that non-programmers can use it and programmers will have some samples.

I would also like to welcome Paul O'Neill to the project. He is our web designer, and has done a fabulous job on the home page prototype.

That's all for this week.




Week #2: Sound Orgy Gets Rolling

Sun, 03 Aug 2003 05:44:56 -0000

First of all, I'd like to thank Pavel Constantinov for joining the project. He will be designing the logo for Sound Orgy. I had started it last week but realized that my time would go better into developing some code and administering the project.

This week I have started working on some preliminary code. Some of that code will become the library to support Sound Orgy.

I am hoping that SoX (http://sox.sourceforge.net) will become a complementary tool to be used with Sound Orgy. I have had email contact with Chris Bagwell (SoX admin) and have submitted some issues to their tracker. I am hoping they can accomidate us by making a few tweaks to be compatible with Sound Orgy.

That's pretty much all that's been happening this week with Sound Orgy. It's good to get rolling




Project Initiated

Tue, 22 Jul 2003 04:35:43 -0000

I have started the research and developement phase of the project. That basically means I will be writting some experimental code so that I can get an idea of how to put the project together.

I want to develope a few basic modules first. I will be making some documentation for the architecture. Once that is complete, I will be looking for contributors to review my code and make suggestions. I will also need developers to create modules that I have designed. There will be creative input involved. I would like to hear peoples ideas on the functionalities of the designed modules as well as modules they would like to see added.

I hope to make a useful set of tools for sound creation and modification. Each tool should be simple and easy to control. I want to avoid complexaty as much as possible as not to create any barriers to the command line user. A good system is worth more than the sum of its parts and allows users to arrange modules freely for powerful results.

Thanks for taking interest in this project. I hope to hear from people interested in this project, users and developers alike.