Cnfox928

• Got Pro Tools, Media Composer, and/or Sibelius? All subscriptions and perpetual license purchases for these products include an Avid upgrade plan, giving you access to all new software releases, so you always have the latest features.
• I got the Omega which I like but they are a bit misleading, as the Lambda it is only 2 inputs (recording at the same time). Having said that I think you would have better results with the Behringer UMC-22 ($40). The problem with the Lexicon interfaces are the drivers which haven't been updated in a very long time.

• Drivers Lexicon 1394 Software
• Drivers Lexicon 1394 Download
• Drivers Lexicon 1394 App

The Hebrew lexicon is Brown, Driver, Briggs, Gesenius Lexicon; this is keyed to the 'Theological Word Book of the Old Testament.' These files are considered public domain.

The 1394 bus driver constructs these identifiers for a device:

1394VendorName&ModelName

1394UnitSpecId&UnitSwVersion

Where:

• VendorName is the name of the hardware vendor.

• ModelName identifies the device.

• UnitSpecId identifies the software specification authority.

• UnitSwVersion identifies the software specification.

The information that is used to construct these identifiers comes from the device's configuration ROM.

If a device has vendor and model name strings, the 1394 bus driver uses the first identifier as both, the device ID and the hardware ID, and the second identifier as the compatible ID. If a device lacks a vendor or model name string, the bus driver uses the second identifier as both, the device ID and the compatible ID, and returns double null if queried for the hardware ID. Therefore, the IEEE1394 bus driver, under certain circumstances, supplies a device ID but no hardware ID. This is an exception to the general rule that the device ID is one of the hardware IDs.

The device ID for a camera on a IEEE1394 might be:

1394SONY&CCM-DS250_1.08

Multifunction devices have a separate set of identifiers for each unit directory in the device's configuration ROM.

If the device's function driver sits on top of the SBP-2 port driver, then its device ID has the following format.

SBP2VendorName&ModelName&LUNn*

Drivers Lexicon 1394 Software

Where:

• VendorName is the hardware vendor.

• ModelName identifies the device.

• n* is a string representing the lower-order 2 bytes of the logical unit number in hexadecimal. Various functions on a multifunction device produce device IDs that are identical except for this number.

The device ID for a SBP-2 1394 hard disk might be as follows:

SBP2VST_TECHNOLOGIESINC.&VST_FULL_HEIGHT_FIREWIRE_DRIVE&LUN0

As with the 1394 bus, the SBP2 port driver does not classify the device ID as a hardware ID. However, whereas the 1394 bus distinguishes between hardware IDs and compatible IDs, the SBP2 port driver does not. For IRP_MN_QUERY_ID IRPs of type BusQueryHardwareIDs and IRP_MN_QUERY_ID IRPs of type BusQueryCompatibleIDs SBP2 returns the same set of four identifiers:

SBP2VendorName&ModelName&CmdSetIdn*

SBP2Gen

Drivers Lexicon 1394 Download

Gen

Drivers Lexicon 1394 App

SBP2n*&d*

Where:

• n* is the Command Set ID number.

• Gen is one of the generic names that are listed in the Generic Type column of the following table.

• d* is a number formed by taking the lower five bits of the upper two bytes of the logical unit number. This number is the numeric code for the generic name of the device that corresponds to the Gen string identifier.

The fourth ID, listed in the previous example (SBP2n*&d*), is unique among all the SBP2 hardware identifiers in that both n*, the Command Set ID number and d*, the numeric code of the generic name are in decimal, not hexadecimal.

This table lists the generic device names returned by the SBP2 port driver. Most, but not all, of the generic names generated by the SBP2 port driver are a subset of those generated by the SCSI Port driver.