Scoring Central

Full Version: Quick & dirty orchestra with TX16Wx
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I put this together for those who might be interested in giving this virtual orchestra thing a shot. It's a small setup with only the most basic articulations (sustain and pizzicato strings, sustain brass and winds).

It'll take some effort on your part though, but nothing too scary.

1. Download these orchestral sample packs from bandshed.net:

bass_bow.zip
bass_sect.zip
bassoon_sect.zip
blocks.zip
cello.zip
cellos.zip
chimes.zip
choir.zip
clarinet.zip
clarinet_sect.zip
flute.zip
flute_sect.zip
french_horn_sect
glock.zip
harp.zip
jg_violins.zip
marimba.zip
oboe_sect.zip
orchperc.zip
shaker.zip
sleighbell.zip
solobassoon.zip
soloviolin.zip
soloviolin2.zip
timpani.zip
trombone_sect.zip
trumpet.zip
trumpet_mute.zip
trumpet_sect.zip
tuba_sect.zip
vibes.zip
viola.zip

2. Create a folder somewhere on your hard drive with a descriptive name, e.g. "Bandshed.net Samples" and unpack all the zip files to that folder, making sure to keep directory structures intact.

3. Download this file, which contains some additional samples plus programs and performances for the TX16Wx sampler, and unpack it to the same folder.

4. Download TX16Wx and install it.

5. Fire up your DAW and load TX16Wx, and create 16 MIDI channels sending to it.

6. In TX16Wx, click on the little wrench icon at the top left and choose "Load performance". When the file open dialog shows up, browse to the folder you created and select one of the .txperf files.

7. To load a second performance, add another instance of TX16Wx.

Additional notes
  • This is a rough first revision with only section strings, brass and winds mapped. I'll add solo instruments and percussion when I find the time.

  • The above assumes that you have a DAW and know how to use it. If not, REAPER has a 60 days unrestricted trial period.

  • You can also load individual presets, if you prefer, by clicking on the folder icons in the TX16Wx program slots. Add more program slots by clicking the "+" icon at the top of the program slot list.

  • On sustain articulations, the mod wheel controls attack time, timbre and volume.

Let me know if you encounter any bugs.

Enjoy!
I just realized that the pizzicatos are horribly out of tune, haha.

I'll fix it for the next round of updates Smile
Is this the start of something that will eventually replace Sonatina Symphonic Orchestra? If that's the plan, great. I'll try to get some testing done for you.
(05-30-2016, 02:08 PM)pbattersby Wrote: [ -> ]Is this the start of something that will eventually replace Sonatina Symphonic Orchestra? If that's the plan, great. I'll try to get some testing done for you.

I don't have any big plans for it really, we'll see where this ends up Smile
(05-29-2016, 02:04 PM)Mattias Westlund Wrote: [ -> ]2. Create a folder somewhere on your hard drive with a descriptive name, e.g. "Bandshed.net Samples" and unpack all the zip files to that folder, making sure to keep directory structures intact.

There is a problem. In the same directory that the .txprog and .txperf files are placed, there needs to be a subdirectory specifically called "Samples". Into that directory, all the samples from all the instruments need to be copied from their individual subdirectories.

For example, if I keep the CelloSect samples in the CelloSect directory as suggested by the cellos.zip file, the Celli Sus.txprog file won't find the samples because of this:


Code:
<tx:wave tx:id="1" tx:path="Samples\2_Db.wav" tx:root="C4" tx:fine="0">
 <tx:loop tx:name="1" tx:start="99072"  tx:end="227328" tx:mode="Forward"/>
</tx:wave>

If I'm reading this right, the samples are expected to be all mixed together and not in their instrument specific subdirectories.
Aaah, my bad! For some reason it seems TX16Wx has saved some of the samples in a Samples dir. I must have accidentally checked "Copy content" while saving the txprog. Oops :/

Edit: a quick fix would be to change the path in the txprog file to the correct one. IIRC the path is only stated once then invoked with an alias throughout the file.
(05-31-2016, 01:10 PM)Mattias Westlund Wrote: [ -> ]a quick fix would be to change the path in the txprog file to the correct one.

I've gone through all the .txprog files and set the path so that all the samples can be placed in a Samples folder and kept within their individual subfolders as they appear in the .zip file. Same layout as SSO. (so all .zip files would be unzipped in the Samples subdirectory)  I've attached these new .txprog files if you want to use them.

I've only had time to do a little testing but I see some mapping issues:

1st Violins Sus highest midi note is 72
2nd Violins Sus highest midi note is note 96
  - 2nd violins are mapped higher on the keyboard than 1st Violins

Violas Sus highest midi note is 91 = G
  in SSO highest midi note is 84 = C

Celli Sus highest midi note is 96 = C
  in SSO it's 72 (also a C)
Celli Sus lowest  midi note is 48 = C
  in SSO it's 36 = C

Basses lowest midi note is 48 same as Celli Sus but the sound is an octave lower
  in SSO it's 24
highest midi note is 84 = C
  in SSO it's 60

As it stands there would be a lot of transposing to simply drop this in place of SSO, in a song for testing.
Yeah, I know there's a lot of inconsistencies. Like I wrote above this is a rough first revision and moreover I'm not sure what will become of all this. It was kind of refreshing messing around with the bandshed.net samples as I didn't encounter them until recently, and I wanted to see what they could be used for. Some of them aren't so great though, or at least not any better than their SSO equivalents. So I dunno.
If you someday decide to turn this first revision in to an orchestral library as complete as SSO (would definitely need staccato samples), let me know and I can help find and fix inconsistencies like the ones I reported.