Path: chuka.playstation.co.uk!news From: "grim" Newsgroups: scee.yaroze.programming.sound Subject: Re: Attribute Definition Files Date: 10 Apr 1997 20:17:41 GMT Organization: froth kid Lines: 39 Message-ID: <01bc2a5f$db0c3000$c793989e@fourny.demon.co.uk> References: <01bc2846$fa391d00$c793989e@fourny.demon.co.uk> NNTP-Posting-Host: fourny.demon.co.uk X-Newsreader: Microsoft Internet News 4.70.1155 Here I answer my own questions. Maybe they were so dumb noone else did. > Has anyone worked out which voices in the example sound data are mapped to > which MIDI patch numbers? (especially drums) Drums are on patch 127 (channels 0-127) > Is this information in the > Attribute definition file? Yes > Is there an example Attribute Definition File > somewhere on the website? You can make an example attribute definition file by using the mkvab -r option to analyse the std0.vh file in the sample data > Would sony like to post the VAG files and > Attribute Definition Files for the example VAB VB/VH files??? > > That way we could make a composite new VAB with some tone data taken from > sony example data (would save having to sample lots of new stuff for game > music) and add some sound effects VAGs for the game. > I have a better question now; what is the format of the VB file? Is it just the VAG files concated together? Is it possible to extract individual VAGs by just splitting the VAB given the sample lengths at the end of the VH file? Also I have another question. How do you make VAB files using lots of VAGs when you have to list all the VAGs on the command line of mkvab? You soon run out of command line space (about 120 characters, isnt it?) especially since you have to include the .vag suffix. Is it possible to list the vag files in another text file or even the attribute definition file?? Graeme