X1 track inspector patch browser - how does it work?

Author
mcdonalk
Max Output Level: -80 dBFS
  • Total Posts : 547
  • Joined: 2004/04/05 19:04:22
  • Status: offline
2011/08/20 22:26:58 (permalink)

X1 track inspector patch browser - how does it work?

How does the patch inspector in the patch browser work? 1) If I open the track browser for a MIDI track that uses an external hardware synthesizer, a list of patches are displayed that I have never seen before. 2) If I open the patch browser for a track that uses Rapture, again, a lot of patches are displayed that I have never seen before, and the patches that I have created for Rapture and have used are not listed. 3) If I open the patch browser for a track that uses Korg Wavestation VST, the patches in the bank in which the current loaded patch resides are listed. Do patches have to be stored in a specific location for the track browser patch browser to see them, or can I configure the patch browser to include the directories in which store my patches? Unless I can do the latter, then pending further understanding of the track inspector patch browser (I have my own file organization and hope that Sonar does not impose one to be functional), it is not of much use to me.
#1

0 Replies Related Threads

    Jump to:
    © 2024 APG vNext Commercial Version 5.1