Yamaha SY85 Owner's Manual (getting Started) (image) - Page 67

Create a Well-organized Data Library, Make Separate Performance Disks or Cards

Page 67 highlights

s Create a Well-organized Data Library It's amazing how quickly you can lose track of what voices, performance combinations, and sequences you've stored where. A well-organized data library is essential. It's a good idea to store different categories of voices or performance combinations on different disks (or at least in different files). In the same way, it's obviously a good strategy to store voices/performance combinations, and sequences on separate disks. If you're looking for a particular bass voice, for example, you can simply load your "Bass" disk (make sure your disks are labelled) and select the requisite voice. You could even have further categories - acoustic bass, fretless bass, funky bass, and so on. The bigger your data library is, the more you should categorize and organize. s Make Separate Performance Disks or Cards If you will be working in the studio or some other situation in which you don't know exactly what data you'll need, it's probably a good idea to take your entire data library along. (Actually, it's better to take a copy of your data library and leave the master disks at home so all your data can't be lost or destroyed at once.) If you will be performing on stage or in any situation involving predetermined sets and voices, it's far more efficient to make separate "performance" disks or cards specifically tailored to the job. Ideally, you want all the voices, performance combinations, and perhaps sequences you'll be using for a performance or set loaded into the SY85 INTERNAL memory. Loading each voice individually from your data library is not practical when time is limited - and time is severely limited in most performance situations. If you prepare by transferring the voices you need from your library to a separate performance disk or card, you can load everything you need from a single disk file or card in one operation. 6. Data Management 65

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71

6. Data Management
65
Create a Well-organized Data Library
It’s amazing how quickly you can lose track of what voices, performance
combinations, and sequences you’ve stored where. A well-organized data library
is essential.
It’s a good idea to store different categories of voices or performance
combinations on different disks (or at least in different files). In the same way,
it’s obviously a good strategy to store voices/performance combinations, and
sequences on separate disks. If you’re looking for a particular bass voice, for
example, you can simply load your “Bass” disk (make sure your disks are
labelled) and select the requisite voice. You could even have further categories
— acoustic bass, fretless bass, funky bass, and so on. The bigger your data
library is, the more you should categorize and organize.
Make Separate Performance Disks or Cards
If you will be working in the studio or some other situation in which you
don’t know exactly what data you’ll need, it’s probably a good idea to take
your entire data library along. (Actually, it’s better to take a copy of your data
library and leave the master disks at home so all your data can’t be lost or
destroyed at once.) If you will be performing on stage or in any situation
involving predetermined sets and voices, it’s far more efficient to make sepa-
rate “performance” disks or cards specifically tailored to the job.
Ideally, you want all the voices, performance combinations, and perhaps
sequences you’ll be using for a performance or set loaded into the SY85 IN-
TERNAL memory. Loading each voice individually from your data library is
not practical when time is limited — and time is severely limited in most
performance situations. If you prepare by transferring the voices you need from
your library to a separate performance disk or card, you can load everything
you need from a single disk file or card in one operation.