There's a rather easy way to create these lists Here's what you do:

1.      Find a similar list and copy it to the new file name. So for
example, if you had a Roland ZQ-1800 which is similar to the Roland Zq-1000,
use an instrument definition file for the 1000 and change the name.
2.      Open the file in Notepad. Also open an Excel session and another
instance of notepad. Also open a website or other source for the patch list
for your particular instrument.
3.      Cut the patch list, with all of its formatting information, out of
the definition file and paste it in your  blank notepad instance. Go to the
first line and delete the first comma, and press tab. Select the tab with
the characters directly before and after it. Press CTRL+H to get into the
find and replace dialog.
4.      In the find box, put a comma. In the replace box put your copied
material using CTRL+V. Delete the characters before and after the tab, so
only the tab is there. Press Shift+Tab three times to get to the replace all
button. Hit the spacebar.. This may take a bit. Press tab, and when you hear
it say "Cancel" hit the space bar.
5.      Press CTRL+A, then CTRL+X. Go to Excel and paste this. You should
now have everything in columns, where the first one is the MIDI channel, the
second one is the patch number, and the third one is the bank, followed by
the patch name. Delete all incorrect patches, or if you want to do this the
fast and easy way press CTRL+- and select "Delete Entire Column" in the list
of options then hit enter.
6.      Paste your correct patch numbers into the spreadsheet. Make sure
that any leading spaces are removed, as this makes it impossible to hit the
first letter of the patch name to accelerate to it. Press CTRL+A again and
then CTRL+C. Paste this in your notepad session.
7.      Repeat the process of Find in Replace in reverse, converting tabs to
commas. You now have a formatted patch list proper for QWS. Once more press
CTRL+A and then CTRL+X and then paste this in the definition file. Save it
and close your other notepad session, Excel, and the patch list.
When you get used to this it takes about five minutes to make an instrument
definition file. Excel is handy for this because it allows you to manipulate
data in terms of columns, while Notepad is the only text editor among the
usual suspects that allows you to use tabs for find and replace. You can do
this without Notepad, but it's a slower process -- set it to load CSV files
and it should parse things to the right columns, though if your patch
descriptions have any commas in them then it'll break those cells up, which
isn't preferable.
If anyone runs into any problems with this let me know. I just used it a
couple of days ago to create a definition file for the E-mu Proteus VX, and
that has over 1000 patches.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Dewald
Sent: Tuesday, July 10, 2012 10:23 AM
To: QWS list
Subject: Re: QWS List Instrument definition file for Yamaha SP710

Why don't you create your own?
I took the Yamaha instrument file on the QWS site, and adapted it for my
Yamaha PSR E323.

I just went down the list of my instrument manual and checked which items
were there, and took out of the instrument list which wasn't on my keyboard.

I left the purcussion list as it were, because it was exactly the same.

Regards,
Dewald.

DL van Deventer
Cell: +27824614865
Fax: +27867214949
E-mail:
[email protected]
Skype: <Dewie007>


On 7/10/2012 9:53 AM, David (Mr Music) wrote:
> Hi friends
> I am urgently looking for an instrument definition file for the Yamaha 
> SP710.
> Can anyone help please?
> Thanks
> David
>
> --
> This message has been scanned for viruses and dangerous content by 
> *Pinpoint Securemail*, and is believed to be clean.

To unsubscribe or change list options, see http://lists.andrelouis.com

for archived list posts, see http://www.mail-archive.com/[email protected]

To unsubscribe or change list options, see http://lists.andrelouis.com

for archived list posts, see http://www.mail-archive.com/[email protected]

Reply via email to