• Prism Sound 1394 Driver Download
• Prism Sound 1394 Driver Free
• Prism Sound 1394 Driver
• Prism Sound 1394 Drivers
• Prism Sound 1394 Driver Windows 10

Important: MacOS Big Sur

Prism Sound 2020 Mac Compatability Lyra, Titan, Atlas, Callia, – are currently under test with MacOS 11 Big Sur. With Intel Macs, so far everything is very promising and no issues have been found. With the new M1 processor systems, more testing will be required. For Orpheus and ADA-8/XR Firewire, we recommend keeping your current system. In Windows 8, the driver stack for the 1394 legacy devices was separated from the regular installation (see 'FireWire port-based device does not work correctly in Windows 8.1 or Windows 8', Running the Windows 8 driver installer In Windows 10, however, does not seem to work properly.

MacOS Catalina

• Prism Sound has a new website! 9-pin to 6-pin IEEE-1394 firewire cable. This tool will discover any 3rd party drivers that cause audio drop-outs on the.
• Expand IEEE 1394 Bus host controllers, and then locate the host controller. Right-click the host controller, and then click Update Driver Software. The screen shot of the host controller and the Update Driver Software is listed in the following example: Click Browse my computer for driver software.
• Prism Sound: Orpheus Downloads page. Prism Media Products Limited; Registered in the UK, Reg. 2719511, Prism Sound Limited; Registered in the UK, Reg.

The driver for Orpheus is part of MacOS, and is supplied and updated by Apple, so you will find that when connected, Orpheus appears in Audio MIDI setup and you can play and record audio through it.
The Control app allows you to change settings on Orpheus. Under Catalina, Apple now disallows the use of 32bit Apps, so you must use the 64bit v1.10 app on Catalina, and the 32bit 1.07 app on earier versions of MacOS.
Security settings in Mojave and Catalina and higher
An error message “AVCCommand result = 0xe00002be” has been reported by some users who are running Mojave or Catalina, when trying to open the Orpheus Control App.
This is caused by replying “Don’t Allow” to a message that Mojave asks fairly commonly when it first opens some programs... ”Do you want to allow Orpheus access to the Camera” (this question is asked, whether the Mac has a camera or not). If you say “Yes” to that question, Orpheus works as normal, but if you say “No” you will see the error message. Orpheus will work as normal with regard to the audio, but you won’t be able to use the Control Panel until you allow Orpheus to access the camera. To fix this problem, in System Preferences / Security and Privacy / Privacy tab / Camera .. tick Orpheus. Regardless of the setting of this, Orpheus does not use the Mac’s Camera.
There is also a MacOS security setting for access to the Microphone. We have come across reports that some DAW software may need access to the microphone to be allowed in order to record (from any audio input). If users are experiencing issues of this sort, where audio appears in the Orpheus interface but not in the DAW, it would be best to check the setting for the DAW in System Preferences / Security and Privacy / Privacy tab / Camera, or else check the DAW software's website for any further information.
Request a Quotation - Click Here For Our Online Form

Overview

Orpheus is a FireWire multi-track audio interface for with 8 channels of analogue input and output as well as digital I/O and sync. The first two channels of analogue input can be mic, line or instrument, the next two mic or line and the last four are line inputs. Orpheus is ideal for music and sound recording, multitracking, overdubbing, stem-based mastering, analogue summing and critical listening applications.

Signal path

Eight analogue input channels and up to 10 digital input channels are available as inputs for your audio workstation software through the host computer's audio driver. Similarly, eight analogue output channels, up to 10 digital output channels and stereo headphone outputs can play 20 different channels. For low-latency foldback or monitoring to headphones or main outputs, each output pair (1-2, 3-4 etc or the headphone output) can optionally be driven from the built-in DSP mixer with an individual local mix of any selection of inputs through the controller applet. All analogue inputs are electronically balanced with automatic unbalanced operation. Analogue outputs are electronically balanced with 'bootstrapping', i.e. level is maintained if one leg is grounded.

No-compromise, full Prism Sound audio quality

Orpheus makes no compromises on audio quality. It is the result of years of research and development into digital audio conversion and extensive dialogue with Prism Sound's customers.

Standards compliant FireWire interface

Orpheus is easy to connect to your computer and to your outboard gear. For Windows users ASIO and WDM drivers are provided, while for Mac OS X 10.4 or later, Orpheus interfaces directly to Core Audio. For both Mac and PC platforms, there is a controller application to configure the unit and control its built-in mixer and other functions. Aside from the monitor and headphone level controls, everything else is operated solely from the Orpheus controller application. The controller software opens on-screen as a separate panel alongside your existing editing software.

Flexible Inputs and Outputs

Orpheus provides a highly integrated solution with instrument and microphone inputs, and line outputs that could be used for stereo or multi-channel monitoring and/or foldback to performers. Orpheus offers eight analogue recording channels, eight monitoring outputs, stereo digital input and output on a phono connector plus concurrent optical digital I/O ports that can interface to S/PDIF or ADAT data formats, giving Orpheus a maximum capability of 18 concurrent input and output channels plus stereo headphones.

Digital Mixer

Orpheus has a powerful built-in digital mixer that can be configured from the host computer to provide foldback feeds to performers, each with their own stereo mix of workstation playback and any of the inputs.

Flexible Monitoring

The eight analogue outputs on Orpheus allow monitor setups from multi-stereo up to 7.1 surround. Orpheus has a real volume knob which can be assigned to any or all of the analogue or digital outputs for use as a control room monitor control. There are two headphone amps, suitable for all types of headphones, each with its own independent volume control. As well as having its own workstation feed and mixer, the headphones can also be quickly switched across the other output pairs, which is handy for setting up.

Sample Rate Conversion and Noise Shaping

The digital output is equipped with the four Prism Sound SNS noise-shaping curves and includes Prism Sound's renowned synchronous sample-rate conversion, allowing outputs to various external devices at other sampling rates. The sample-rate converter can be used at the outputs as well as the inputs, so as well as dealing with unsynchronised or wrong-rate digital inputs, Orpheus can also generate, say, a live 44.1kHz output from a 96kHz session. Since Orpheus also includes the full suite of the famous Prism Sound 'SNS' noise shapers, you can also reduce to 16-bits at mastering-house quality.

Unsurpassed Jitter Rejection

In the 1990s Prism Sound pioneered testing of sampling and interface jitter and as a result our digital audio products deliver unsurpassed jitter rejection. Prism Sound digital audio products lock up fast and re-generate ultra-stable clock outputs. Another aspect of the traditional Prism Sound converter that is retained was the clocking - it's just as important as analogue-path considerations sound-wise. So whether it's providing a high-quality master clock for the rest of the room, or dealing with a jittery clock from outside, Orpheus is as rock-steady as its forbears.

Support

Over the years, Prism Sound's reputation for audio quality has been matched by its reputation for after-sales support and technical advice. Orpheus has the benefit of that support and customers have access to one of the best technical teams in the business.

Orpheus Videos

Deadmau5 on Orpheus Canadian progressive-house music producer and performer Deadmau5 on his experience using Orpheus

Mark Willsher on Orpheus Lord Of The Rings and The Hobbit music editor Mark Willsher discusses his Cloud based music service and how the Orpheus FireWire interface helps his workflow.

Eros Marcello on Orpheus Producer and engineer Eros Marcello on his experience of moving up to an Orpheus

Third Party Videos

Sound on Sound, NAMM 08 SOS editor Paul White talks to Prism Sound Technical Director Ian Dennis about Orpheus

Gearslutz at AES 2012 Gearslutz Lounge talk to Frank Oglethorpe about Orpheus at AES 2012

DSP Project The DSP project review Orpheus

Orpheus Summary

• 8 A/D Analogue input channels including
  • 4 x Mic/Line inputs on combo connectors
  • 4 x Line inputs on TRS
  • 2 x Front panel instrument inputs on jack
• 8 D/A Analogue output channels
• 2 headphone outputs with independent volume control
• S/PDIF I/O on RCA or TOSLINK
• AES3 I/O via RCA to XLR adaptors (supplied)
• ADAT I/O mode including S-MUX
• Sync I/O on BNC
• ASIO and WDM drivers provided for Windows Vista and higher (32 and 64bit)
• Directly compatible with CORE AUDIO on Mac OS X 10.4+ (Intel & PPC)
• Concurrent operation of ADAT and switchable S/PDIF or AES3 ports
• MS Matrix processing on mic inputs
• RIAA Equalization on inputs 1 & 2
• Prism Sound 'Overkillers' limiters on all analogue inputs
• Fully-floating (isolated) balanced architecture for optimum noise rejection
• Low-latency 'console-quality' digital mixer built in
• Fader, pan, cut, solo on every mixer channel
• Outputs selectable between workstation bus or Orpheus mixer
• Front-panel master volume control, assignable to selected channels
• Configurable for stereo, 5.1 or 7.1 or surround monitoring
• Built-in sample rate conversion (SRC) on S/PDIF Inputs and Outputs
• Prism Sound 4-curve SNS noise shaping on digital outputs
• State-of-the-art clock generation with proprietary hybrid 2-stage DPLL
• MIDI in/out ports

Awards

-->

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.

Prism Sound 1394 Driver Download

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

Prism Sound 1394 Driver Free

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.

Prism Sound 1394 Driver

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

Prism Sound 1394 Drivers

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

Prism Sound 1394 Driver Windows 10

The IEEE 1394 Driver Stack
Retrieving the Contents of a IEEE 1394 Node's Configuration ROM