TC Electronic Drivers. 10 drivers total Last updated: Aug 20th 2016, 19:58 GMT RSS Feed. Latest downloads from TC Electronic in Audio/DJ Gear. Sort by: last update. TC Electronic Film 6000 Firmware 6.0.0 43 downloads. Audio/DJ Gear TC Electronic. Shop for the TC Electronic Konnekt 24D FireWire Audio Interface and receive free shipping on your order and the guaranteed lowest price. Network up to 4 units via the TC NEAR 1394 FireWire based network to get more inputs, outputs and effects channels. Low latency drivers: WDM, ASIO and CoreAudio (including Intel Macs) Dual headphone. Find helpful customer reviews and review ratings for TC Electronic Studio Konnekt 48 24Bit/192kHz Firewire I/O with Speaker Management, 24In/24Out, MIDI, ADAT, S/PDIF, TC DSP with StudioKontrol Remote at Amazon.com. Read honest and unbiased product reviews from our users. TC Electronic A/S, Sindalsvej 34, 8240 Risskov, Denmark, hereby declares on own responsibility that the following product: Desktop Konnekt 6 that is covered by this certificate and marked with CE-label conforms with following standards: EN 60065 Safety requirements for mains (IEC 60065) operated electronic and related apparatus for household.
- 1394 Firewire Windows 10 Driver
- 1394 Driver Legacy
- Via 1394 Driver
- Ieee 1394 Driver Windows 10
- Microsoft Ieee 1394 Driver Download
Windows 7 includes 1394ohci.sys, a new IEEE 1394 bus driver that supports faster speeds and alternative media as defined in the IEEE-1394b specification. The 1394ohci.sys bus driver is a single (monolithic) device driver, implemented by using the kernel-mode driver framework (KMDF). The legacy 1394 bus driver (available in earlier versions of Windows) includes multiple device drivers that were implemented by using the Windows Driver Model (WDM) in a port/miniport configuration. The 1394ohci.sys bus driver replaces the legacy port driver, 1394bus.sys, and the primary miniport driver, ochi1394.sys.
The new 1394ohci.sys bus driver is fully backward compatible with the legacy bus driver. This topic describes some of the known differences in behavior between the new and the legacy 1394 bus driver.
Note
The 1394ohci.sys driver is a system driver that is included in Windows. It is automatically loaded when you install a 1394 controller. This is not a redistributable driver that you can download separately.
I/O Request Completion
All I/O requests that are sent to the new 1394 bus driver return STATUS_PENDING because the 1394ohci.sys bus driver is implemented by using KMDF instead of WDM. This behavior differs from that of the legacy 1394 bus driver, in which certain I/O requests complete immediately.
A client driver must wait until I/O requests sent to the new 1394 bus driver are complete. You can provide an I/O completion routine that is called after the request is complete. The status of the completed I/O request is in the IRP.
Configuration ROM Retrieval
The new 1394 bus driver tries to use asynchronous block transactions at faster bus speeds to retrieve the contents of a node's configuration ROM. The legacy 1394 bus driver uses asynchronous quadlet reads at S100 speed—or 100 megabits per second (Mbps). The 1394ohci.sys bus driver also uses the values that are specified in generation and max_rom entries of the node's configuration ROM header to improve the retrieval of the remaining content of the configuration ROM. For more information about how the new 1394 bus driver retrieves the contents of a node's configuration ROM, see Retrieving the Contents of a IEEE 1394 Node's Configuration ROM.
IEEE-1394-1995 PHY Support
The 1394ohci.sys bus driver requires a physical layer (PHY) that supports IEEE-1394a or IEEE-1394b. It does not support a PHY that supports IEEE-1394-1995. This requirement is due to the 1394ohci.sys bus driver's exclusive use of short (arbitrated) bus resets.
NODE_DEVICE_EXTENSION Structure Usage
A client driver can reference the device extension in the 1394 bus driver associated with the physical device object (PDO) for the device that the client driver controls. This device extension is described by the NODE_DEVICE_EXTENSION structure. In 1394ohci.sys, this structure remains at the same location as in the legacy 1394 bus driver, but the nonstatic members of the structure might not be valid. When a client driver uses the new 1394 bus driver, they must make sure that the data accessed in NODE_DEVICE_EXTENSION is valid. The static members of NODE_DEVICE_EXTENSION that contain valid data are Tag, DeviceObject, and PortDeviceObject. All other members NODE_DEVICE_EXTENSION are nonstatic, which the client driver must not reference.
Gap Count Optimization
The default behavior of the 1394ohci.sys bus driver is to optimize the gap count when it finds only IEEE 1394a devices on the 1394 bus, excluding the local node. For example, if the system that is running 1394ohci.sys has a host controller that complies with IEEE 1394b but all devices on the bus comply with IEEE 1394a, then the new 1394 bus driver tries to optimize the gap count.
Gap count optimization occurs only if the 1394ohci.sys bus driver determines that the local node is the bus manager.
The 1394ohci.sys bus driver determines whether a device complies with IEEE-1394a by the speed setting in the node's self-id packet. If a node sets both of the bits in the speed (sp) field in the self-id packet, then 1394ohci.sys considers the node to comply with IEEE-1394b. If the speed field contains any other value, then 1394ohci.sys considers the node to comply with IEEE-1394a. The gap count value that is used is based on table E-1 in the IEEE-1394a specification, which provides the gap count as a function of hops. The 1394ohci.sys bus driver does not compute the gap count. You can change the default gap count behavior by using a registry value. For more information, see Modifying the Default Behavior of the IEEE 1394 Bus Driver.
Device Driver Interface (DDI) Changes
In Windows 7, the 1394 DDIs were changed to support faster speeds as defined by the 1394b specification and improved to simplify the development of 1394 client drivers. For more information about the general DDI changes that the new 1394 bus driver supports, see Device Driver Interface (DDI) Changes in Windows 7.
Related topics
The IEEE 1394 Driver Stack
Retrieving the Contents of a IEEE 1394 Node's Configuration ROM
Release Notes: Kernel Drivers
See Release Notes - Libraries for changelogs of some IEEE 1394 userspace libraries.
Release Status
The latest stable releases of Linux IEEE 1394 drivers are those in the latest released Linux 4.x kernels.
The drivers in Linux 2.4 were considered stable too but have not been updated anymore for a long time. Therefore they lack many features and compatibility updates which went into Linux 2.6.x...4.x releases.
The following release notes only summarize more notable changes. A complete list of IEEE 1394 related changes is available via kernel.org git:
- drivers/media/firewire, formerly drivers/media/dvb/firewire
- include/uapi/linux/{firewire-cdev.h,firewire-constants.h}, formerly include/linux/{firewire-cdev.h,firewire-constants.h}
- Documentation/ABI/stable/{firewire-cdev,sysfs-bus-firewire}, Documentation/debugging-via-ohci1394.txt
Linux 4.9
tentative release notes as per v4.9-rc4
- Add missing input validation. Invalid IP-over-1394 encapsulation headers could trigger buffer overflows, potentially leading up to remote code execution (CVE-2016-8633). Also fixed in v4.8.7 and v4.4.31.
- Fix IP-over-1394 link fragmentation headers that were read and written incorrectly, which prevented fragmented reception from/ fragmented transmission to other stacks, including Mac OS X, Windows XP, and older Linux' eth1394. Also fixed in v4.8.7 and v4.4.31.
Linux 4.8
2 October 2016
- Fix possible deadlock in hwdep interface. Also fixed in v4.7.4 and v4.4.21.
- Fix possible deadlock in hwdep interface. Also fixed in v4.7.4, v4.4.21, v4.1.34, v3.18.43.
Linux 4.7
24 July 2016
- Add support for M-Audio Profire 610, and perhaps for Profire 2626.
- Add tracepoints to dump a part of isochronous packet data in order to support debugging of device quirks and of kernel-internal packet processing. The patch changelog describes how to use this feature. A subsequent commit expands the dump format.
- Remove matching of SYT fields of the outbound stream to those of the inbound stream since it proves to be unnecessary in practice. The same was already done in snd-dice in Linux v4.6. This simplifies the kernel code and allows for finer-grained tasklet scheduling.
- Perform sound card registration at least 2 seconds after the last IEEE 1394 bus reset. This was already implemented for snd-dice in Linux v4.5 and is now adopted by the other FireWire audio drivers. It ensures that the bus and device firmware settle into a ready state before userspace initiate I/O to the device.
Linux 4.6
15 May 2016
- internal rework related to streaming recovery after bus reset
- Change how the dependency between number of available PCM and MIDI channels versus sampling rate is handled. Also affects the hw_params ioctl interface. Userspace should set the desired sampling rate before starting PCM I/O.
- Change how phase lock is ensured and how lock status is detected.
- Remove matching of SYT fields of the outbound stream to those of the inbound stream. This synchronization happened when the device was configured for internal clock. It required a startup delay of the outbound stream, which caused DICE II based devices to remain silent at the first attempt to start streaming.
- Add support for previously unavailable higher PCM channels on certain devices with high channel count, notably Focusrite Saffire PRO 40, Focusrite Liquid Saffire 56, and TC Electronic Studio Konnekt 48. These devices spread the PCM and MIDI channels across 2 tx + 2 rx IEEE 1394 channels instead of just 1 tx + 1 rx IEEE 1394 channel, as most other devices do.
- improvements to MIDI I/O
1394 Firewire Windows 10 Driver
1394 Driver Legacy
Linux 4.5
13 March 2016
- Improved handling of DICE II firmware bootstrapping during device start-up.
- Avoid time-out when PCM streaming is started.
- Add support for TASCAM FW-1804.
- The functionality of this driver was moved to the snd-oxfw driver, and the now obsolete snd-scs1x module has been removed.
Linux 4.4
10 January 2016
- Work around JMicron JMB38x initialization quirk. Affected isochronous transmission, e.g. audio via FFADO or ALSA. Also fixed in v4.3.3, v4.2.8, v4.1.15, v3.18.26, v3.16.35, v3.14.59, v3.12.52, v3.10.95, v3.4.113, v3.2.74.
- Fix device identifier of Mackie Onyx 1220/1620/1640 FireWire I/O card.
- Fix device identifier of Mackie Onyx Blackbird and Onyx-i series.
- New driver for Digidesign audio interfaces: Digi 002 Console, Digi 002 Rack, Digi 003 Console, Digi 003 Rack, Digi 003 Rack+. Written by Takashi Sakamoto.
Via 1394 Driver
- Restructured and extended for wider protocol support. Data block processing is split from isochronous packet processing. This work was required for integration of snd-firewire-digi00x and snd-firewire-tascam because devices which are supported by these drivers do not comply with IEC 61883-6. Written by Takashi Sakamoto.
- New driver for TASCAM audio interfaces: FW-1082, FW-1884. Written by Takashi Sakamoto.
- Fix Mackie Onyx Satellite packet discontinuity when device is used in base station mode.
- Add support for TASCAM FireOne.
- Fix calculation of MIDI ports.
- Fix for statically linked (i.e. non-modular) builds.
Linux 4.3
1 November 2015
No functional changes to the FireWire subsystem.
Linux 4.2
30 August 2015
- Add support for
- Digidesign Mbox 2 Pro
- Behringer FCA610, FCA1616
- Improve BeBoB v3 support (PrismSound Orpheus, Behringer UFX1604, Behringer FCA610).
- Improved clock source detection. Add SYT-Match support.
- Internal changes related to packet handling.
- Fix packet discontinuity with newer firmwares. Also fixed in v4.1.6 and v3.18.21.
Linux 4.1
21 June 2015
No functional changes to the FireWire subsystem.
Linux 4.0
12 April 2015
- firewire-core
- The vendor ID and model ID in the Configuration ROM root directory of Linux hosts was changed from 0xd00d1e:0x000001 to 0x001f11:0x023901. This change makes firewire-core's local Configuration ROM comply with IEEE's OUI assignment rules.
- This has been made possible by Openmoko's granting a range of IDs to the Linux IEEE 1394 subsystem. See IEEE OUI Assignments for additional information. This change cannot have negative impact on any standard protocols, but developers of private protocols may need to adapt if they relied on these root directory entries instead of their own unit directory entries.
- The change was also backmerged into v3.12.51.
- Fix initialization of some M-Audio devices with Linux on big-endian CPUs. Also fixed in v3.19.5 and v3.18.13.
- Fix device reference counting and shutdown. Also fixed in v3.19.2.
Linux 3.0...3.19
July 2011 – February 2015
Support of various devices and controllers was improved. IPv6 support was added to firewire-net (v3.10). New drivers ware added:
- sbp-target lets a Linux node act as a storage device (v3.5),
- snd-isight for audio capture through Apple iSight FireWire webcam (v3.0),
- snd-scs1x, a MIDI driver for Stanton SCS.1d and SCS.1m FireWire DJ controllers (v3.8),
- snd-dice for audio playback through some audio devices based on TC Applied Technologies' DICE chipset (v3.13), later also for audio capture and MIDI through basically all DICE based devices (v3.19),
- snd-bebob for audio I/O through BridgeCo DM1000/DM1100/DM1500 based devices with BeBoB firmware (v3.16),
- snd-fireworks for audio I/O through Echo Digital Audio Fireworks based devices (v3.16),
- snd-oxfw for audio I/O through Oxford Semiconductor OXFW970/971 based devices (v3.19). snd-oxfw replaced snd-firewire-speakers in v3.19 and snd-scs1x in v4.5.
The audio I/O drivers are an alternative to the existing userspace drivers which the FFADO project provides. While the FFADO drivers can only be used in conjunction with JACK, the kernelspace drivers can be used with any ALSA compatible application. However, the kernelspace drivers only implement PCM streaming and MIDI streaming, whereas device control is meant to be provided by userspace applications like ffado-mixer.
See Release Notes/3.x.
Linux 2.6.30...2.6.39
June 2009 – May 2011
The older ieee1394 driver stack was removed from the kernel after it coexisted as an alternative to the current firewire drivers until kernel 2.6.36 inclusive. Many new features and fixes went into the newer firewire drivers. Some new drivers were added: firewire-net (IPv4 over 1394, replacing the eth1394 driver), nosy (a bus sniffer, formerly maintained outside of the kernel repository), and snd-firewire-speakers (for LaCie FireWire speakers and Griffin FireWave).
See Release Notes/2.6.3x.
Linux 2.6.20...2.6.29
February 2007 – March 2009
The new alternative firewire drivers were added and gradually stabilized. Since the new drivers were not yet feature-complete, the older ieee1394 stack remained preferred for production but received only few minor updates during this time frame.
See Release Notes/2.6.2x.
Linux 2.6.12...2.6.19
June 2005 – November 2006
Ieee 1394 Driver Windows 10
This is a stabilization phase of the ieee1394 driver stack in Linux 2.6.
See Release Notes/2.6.1x.
Microsoft Ieee 1394 Driver Download