My faith in the internet is restored thanks to
thescripts.com, wxpython, python google boards for
putting up with me and answering my questions... We are still
more scarphonic (scarface lots of lines)
than python most likely change some day
code can be donated through the bbs
http://groups.google.com/group/dexrow-software-and-programming-group
On the off chance I will also take cash donations
or donations of old python or csound books (god
only knows that I need to read more)
Eric Dexter
3802 caravelle parkway apt 502
corpus christi texas
78415
(361)225-0665
www.dexrow.com
This is the latest Dex Tracker with csound Routines for your version check your readme files or download
the Latest Dex Tracker or Csound Routines(older version may be with your version of Dex Tracker) This is still an early version expect great things.
****************************************************************************************************
New csound reseved words
replace{} with < this is causing problems with html
In exchange for getting allot of new features for csound you get additional requirements to make it all work smoothly
The following are reserved words both inside and in somecases outside the program.
;{header} This defines the line as being a header for a .sco file and will be placed on top of a grid if called
;{pin} This defines a pin, or connecters between instruments
instr This is already a reserved word but you don't want to use it in comments anymore
New Format Requirements
lines containing zar and zawm must start at the begining of the line and all be seperated by one space. This can be done with file converters or format converters if you will. This speeds up the code and gets rid of strange problems. The line must be ended with ; to indicate this is a connecter line this was done to make it easier to convert to the format without worrying about what is in the comments
instr is searced for and will be found regardless of where it is. To work correctly it should be followed by an instrument
number (required I do believe) and then a comment line describing the instrument such as ;flute
****************************************************************************************************
Licence
You may include this in your program. The code is not to be distributed on disk, part of an operating system, or with a publication without the permission of the auther. Donating code will give you more rights and other arangements can also be made. I also require that a link back to the homepage and will allow you to use the library as part of your advertising unless you are endorsing or causing the destruction of other peoples computers.
********************************************************************************************************************************
working routines
get_instr(from_file, to_file, instr_num)
from_file is the .csd file that you are reading to to file is where you wish the shortened orc file saved. Currently the plan is to save then as svc files. instr_num is the instrument number that is to be ripped. The purpose is part of an overall system but it can be used to rip orc files from other csd files. There will be parts of instruments that are not captured in some or maybe alot of .csd files. If there is donated code to adress that it will be given a different name most likely.
csdInstrumentList(From_file)
from_file is the file that is to be read from. This will return two lists instr_number that is a list of numbers currently in the csd file and comments wich is any comment that is included on the instr line following the instr number
full_orc_file(from_file, to_file)
from_file is the shortened orc file to be read from. To file is the full orc file to be written to. The routine reads a shortened orc format and writes a header part to create a
full orc file.
get_score(from_file, to_file, instr_num)
from_file the file to get the score from. to_file is the file it is to be saved to. instr_num the instrument number that is to be ripped from the csd file. Del_Instr(from_file, instr) for instr will pick up i1 and i10 in test splitline is probily helpfull
csoundgrid(filename, header_string)
Loads a file (We want it for .orc files but the editor doesn't care what it is) and places the lines into a grid. The header string is a string that is defined by the user that for the purposes of editing .sco files should be placed at the end of the list of words to be used as a header for the collums. Note that the save function will take out un-needed white space and seperate everything with one space.
sco_editor(self):
This gives a list of all the pins that are defined with zar and zawm. It will return instr number, intrument input and instrument output
Non working routines
delete instr
From file is the file the instr is to be deleted from. instr is the instr number to be deleted this file hangs (at least on my computer
right after temp.tmp is created (that is the temp file that is created befour the old one is deleted and this one renamed) temp.tmp was created as a zero byte file
other routines that are not currently completly debugged can be used through dex tracker 5 (same as csound tracker just later version)