Wednesday, August 27, 2008
Command line csound parsing
Command line csound parsing
This will parse a csound file and add a number to the so called ifn (the function number) in the orc. file.. Not all commands will follow the rule that is used in this "parser".. for extra credit find a parser that follows the rules of another group of commands...
The file is cross platform and should run on any platform that csound runs on including cell phones (if that is usefull).. distributed by permission only, The csd file is from csound and goes by thier licince (I don't get backing from a university)
This will parse a csound file and add a number to the so called ifn (the function number) in the orc. file.. Not all commands will follow the rule that is used in this "parser".. for extra credit find a parser that follows the rules of another group of commands...
The file is cross platform and should run on any platform that csound runs on including cell phones (if that is usefull).. distributed by permission only, The csd file is from csound and goes by thier licince (I don't get backing from a university)
Sunday, August 24, 2008
mingus for python and parsing csound
2008/08/24 mingus 0.1.7.5 has been released. The release pushes some bug fixes in the core and adds a lot of new features (tutorials should be expected soon). Work on the mingus.draw sub-package has also begun, resulting in some simple images already.
It parses!!!!!! I parsed csound found the command and was able to change if ifn (I think that is integer function number and if it isn't that is what I am going to call it anyway)... I seem to be saving out several copies of my line though. I found some things in python that seem realy odd. nested for line in infile (replace infile with name of second file)... once you go through the file that is it.. your finished it doesn't reset. That seems to be the bigest chalenge in parsing csound files. Fighting with python to make it fit the flowchart.. The example on the python board wasn't to close but I made major changes and it has error checking stuff that made sence. joining doesn't seem to work all that well for them and it is a concept I haven't been using.. I am not a joiner I am a man of words i.e. for word in line:
I am excited to see mingus for python is supporting graphics.. I am not sure what I can do with it, I have been wanting a piano roll but I am expecting that it is going to be staff notation... some concepts like bpm are being ignored right now to take a different path.. One taken by some notable packages like stk toolkit.
It parses!!!!!! I parsed csound found the command and was able to change if ifn (I think that is integer function number and if it isn't that is what I am going to call it anyway)... I seem to be saving out several copies of my line though. I found some things in python that seem realy odd. nested for line in infile (replace infile with name of second file)... once you go through the file that is it.. your finished it doesn't reset. That seems to be the bigest chalenge in parsing csound files. Fighting with python to make it fit the flowchart.. The example on the python board wasn't to close but I made major changes and it has error checking stuff that made sence. joining doesn't seem to work all that well for them and it is a concept I haven't been using.. I am not a joiner I am a man of words i.e. for word in line:
I am excited to see mingus for python is supporting graphics.. I am not sure what I can do with it, I have been wanting a piano roll but I am expecting that it is going to be staff notation... some concepts like bpm are being ignored right now to take a different path.. One taken by some notable packages like stk toolkit.
Labels: csound, mingus, parsing
Sunday, August 17, 2008
another try at parsing
after a day of debugging my code generator seems like alot of work in python and it seems like it would be alot easier to generate in awk. What does that mean.. It's the aproach yes I could do it the way I am doing it but it would be easier to use a grid and create and parse it with another grid and not generate any code (I think)... THe comment language is almost the only thing that works the same as those befour me.. I only looked at windows and projects that worked on my machine well.
I am looking at the enthought python package. I had avoided using it because it was 2.4 and I moved to 2.5.. I am under the impression that there is no problem using muliple versions (I wasn't then).. The plugin system looks interesting in that they have editors already built.. There is some broken stuff also but it is stuff that probily isn't of use to me anyway.. (enthought may want to know about it though).. There is some instructions in the graphics maya I believe that should have come with an example batch file. I am in the looking phase.. It looks like there are output windows for code (compilers like csound) and thats a big feature that I have been looking for.. The right to distribute code though is a big question mark.. I have been very fortunate that my computer didn't get wet... I had more real rain drops than water splash screens...
I am looking at the enthought python package. I had avoided using it because it was 2.4 and I moved to 2.5.. I am under the impression that there is no problem using muliple versions (I wasn't then).. The plugin system looks interesting in that they have editors already built.. There is some broken stuff also but it is stuff that probily isn't of use to me anyway.. (enthought may want to know about it though).. There is some instructions in the graphics maya I believe that should have come with an example batch file. I am in the looking phase.. It looks like there are output windows for code (compilers like csound) and thats a big feature that I have been looking for.. The right to distribute code though is a big question mark.. I have been very fortunate that my computer didn't get wet... I had more real rain drops than water splash screens...
Labels: csound, enthought, parsing, python
