The Yamaha AN1x Synthesizer mailing list

--- In AN1x-list@y..., "nuvalerium" <alan@s...> wrote:
> All this means is that I have to connect the midi in and out from 
the 
> sound module to the in and out of the AN1x. If I want to use the 
An1x 
> as the master controller on my set-up, does this mean I have 
to then 
> connect the midi thru on the AN1x to the next instrument in my 
set-
> up. If so then what is the best way to do this. Do I need a midi 
thru 
> box? I have a Korg N364, an Alesis Data disk and a Boss 
Dr77o all to 
> hook up to the system.
> 

Before making a purchase decision I'd encourage you to 
consider how quickly you anticpate your MIDI set-up to grow. 

From your description - today you have a synth, a ROMpler, a 
drum machine and a Data Disk. I'm uncertain what purpose the 
Data Disk will serve once you connect everything to your Laptop? 
Possibly a back-up for live use in case the laptop should crash?

Assuming the TO HOST port on the TG100 works as anticipated 
(see Gary's post - I can't imagine it wouldn't work as expected) it 
will serve as a standard MIDI Interface, i.e., only 16 MIDI 
Channels IN and OUT from the Laptop to your MIDI kit. With only 
a few devices in your kit that's *probably* sufficient for your 
immediate use (Data Disk included) but what happens when 
you add a multitimbral sound module/synth/sampler (such as 
your Korg N364) to your kit? IMO, you'll likely find it frustrating
to exploit  the multitimbral capabilites of another device when 
you're limited to 16 MIDI Channels by using a standard MIDI 
Inteface. There's also the possible issue of 'MIDI timing slop' 
rearing it's ugly head when you daisy chain more then three to 
four devices together.

For these reasons I'd encourage you to consider a true multiport 
MIDI Interface from the likes of MIDIMAN, MOTU, Steinberg, 
Emagic, etc. where each port can address 16 Channels 
independently. This will provide enough capacity to grow your 
MIDI kit without having to revisit the issue each time you consider 
a purchase. Not too mention the improved ease of use when 
addressing SysEx data to individual devices.

Regarding Opcode/MIDI Quest MIDI Interfaces: as much as I've 
enjoyed using Opcode products (Mac) over the years - I'm 
currently using a Studio 128x - I'd suggest you stay away from 
them for Win use based soley on the fact that there is NO 
SUPPORT and NO ONGOING DEVELOPMENT and the drivers 
don't work on anything more recent then Win98 (this means 
Win98SE on up to XP.) Note: if you need some Opcode info 
check the Vision Info site at http://www.fm-music.com/v/

It's my advice to base a purchase decision on whichever 
software platform you currently use or plan to use, i.e., Steinberg 
or Emagic or whatever, because their software is typically 
optimized to exploit product specific features exclusive to their 
own devices. If you are using a product from a manufacturer who 
does not market their own brand name MIDI Interface then 
consider one from the likes of a company such as MIDIMAN who 
are wdiely used cross platform and provide ongoing support and 
development of device drivers. This is especially import if you 
plan to switch to from serial ports to USB ports at some time as 
USB MIDI drivers are reputed to be much more difficult to code 
efficiently on either platform then serial port drivers.

> Sorry for so many questions. This is doing my head in.
> 

Hope this helps.

regards,

Jon