MMA 1.4 released

[bvdp]

Version 1.4 of MMA - Musical MIDI Accompaniment - is now
available for downloading. Included in this release:

 -  -T command line option to limit tracks generated.

 -  AllGrooves command makes it easy to change a set of parms in a library file

 -  Debian package added to download section.

 - 'man' pages have been created for mma, mma-renum and mma-libdoc.

 - A simple math parser has been added. You can use this anywhere a
   macro is valid. Anything in $( )$ delimiters is evaluated (safely)
   using Python.

 - lots of bug fixes and library additions. Read the complete change log
   in the distro: CHANGES-1.3.

MMA is a accompaniment generator -- it creates midi tracks
for a soloist to perform with. User supplied files contain
pattern selections, chords, and MMA directives. For full details
please visit:

   http://www.mellowood.ca/mma/

If you have any questions or comments, please send
them to: bob@mellowood.ca

[bvdp]

A deb package is on the site as well as a rpm. This should make it real easy to install MMA on your system.

[kara]

Cool to see MMA grow out as a MATURE software

k

[bvdp]

I have uploaded updated deb and rpm files. Same version number, etc. so it'll be invisible unless you really want to know The change is in the postinst script  which is supposed to call mma to update the library database. In the original I was calling /usr/local/bin/mma which didn't exist after a deb install. I've changed that to /usr/bin/mma so all should be well.

If you installed the original mma doing a "mma -G" from the command line will update the library properly.

[bvdp]

Just for your interest ... the download rates for the 3 different MMA packages are:

  The plain tar.gz file wins with 55%
  Next is the .deb file with 32%
  And trailing badly is the rpm with 12%

Honestly, I have no idea what these numbers mean ... but it's interesting?
 

[folderol]

I've downloaded the deb package. I'll let you know how it goes!

Update!

deb package installed without problems in 64studio (etch based), however I keep getting the message 'No RC file was found or processed' every time I run it. Doesn't seem to stop it working though.

I wonder if there should be a note for people to move the demo files to userspace, or a script to do that. It's not exactly obvious where they are, and noobs might not appreciate that the can't write the MIDI files where these files are located.

Good work nevertheless.

[bvdp]

The "no rc file" this is a bit odd I guess. Not sure what else to do ... having an rc file really does add a lot of "stuff" if you like (like where to store midi files, smf type, etc.) If there was just one option as to the location of the rc file that would be simple. But, you can have rc files in a number of locations so I figure it's just as well to notify users if they don't have one. Example: you normally have you mma files in /home/bob/music/mma/ and you have a rc file there. All works Now you compile some files in /home/bob/music/mma/teststuff and you get odd results. The "no rc file" message may give you a clue.

Yes, a note about the example files might be a good idea. I see a lot of stuff happening like that in Ubunutu/Debian. Even docs sometimes need to be processed and so I need to do it as root. A bit of a bother. Not sure what the easy way around this is.

Oh, and if have set a default midi file location in the rc file then you can process the example files in /usr/...

[bvdp]

I've just uploaded a developer release 1.4a. You can grab it from:

  http://mellowood.ca/mma/index.html#developer

A few fixes, mainly in the Aria code which should now work as advertised.