East-West Opus software

[Obsidian Dragon]

Originally Posted by Media Man

System details in the first post. Plenty of RAM and system and sample library on SSD drives.

Well that level of system detail is not going to get you much help here. There are some pretty savy folks here that would offer to help if they are given more system information (such as a Sandra report). Regardless, you seem to have taken it as far as you can with East-West Opus support without a solution. Something just isn't playing nice between East-West Opus and the version of Protools. Without more system information, there is not much anyone on this forum can add.

[LightWing]

Here's the Sandra Hardware Report below. Thanks for any assistance.

***** Start of Report *****
--------------------------------------------------------------------------------

<<< Status >>>
--------------------------------------------------------------------------------

< SiSoftware Sandra >
Name: SiSoftware Sandra Lite (Eval)
Version: 2021.6.31.29
Platform Compliance: x64
URL: https://support.sisoftware.co.uk
E-Mail: [email protected]
Twitter: https://twitter.com/sisoftwareuk
Facebook: https://facebook.com/SiSoftware

< SiSoftware Sandra >
Copyright: Copyright © SiSoftware 1995-Present. All Rights
Reserved. Moral Rights Asserted.
Registered Owner: DAW
Registered Organisation: Unknown
Licence Status: Free strictly for personal/educational use; 21
days trial for any other use.
Licence Extra: You are on day %d of your trial period. Please
see 'Help - Get More' for purchase details.

< Environment >
Host Name: DAW
User: DAW
Computer ID: {4425F83A-F551-4FC2-B3DC-61F128366DE7}
Result ID: {1A18D046-DF83-4309-A4E6-AEF0393A94EA}
Date: Tuesday, August 3, 2021 @ 4:50:24 AM

<<< Comments >>>
--------------------------------------------------------------------------------

Comments on report: Generated 8/2/21

<<< Computer Overview >>>
--------------------------------------------------------------------------------

< ID >
Host Name: DAW
Workgroup: WORKGROUP

< Computer >
Model: Dell Precision Tower 7910
Serial Number: C4X5JB2
Chassis: Dell Tower
Mainboard: Dell 0NK5PH
Serial Number: /C4X5JB2/CN7220063V00BD/
BIOS: Dell A33 01/10/2020
TPM - Trusted Platform Modu:WEC 1.2 2010 (24PCR 6Ses 7Obj 4Ctr)
Intel Management Engine (ME:9.1.45.3000
NUMA Support: 2 Unit(s)
Total Memory: 128GB ECC DIMM DDR4

< Processors >
Processor: Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz (10C
20T 2.6GHz, 3GHz IMC, 10x 256kB L2, 25MB L3)
Processor: Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz (10C
20T 2.6GHz, 3GHz IMC, 10x 256kB L2, 25MB L3)
Socket/Slot: FC LGA2011

< Chipset >
Memory Controller: Dell Xeon (Haswell-E) DMI2 100MHz
Memory Controller: Intel Xeon (Haswell-E) Integrated Memory
Controller 0 Target Address, Thermal & RAS
Registers 100MHz, 2x 16GB ECC DIMM DDR4 2.13GHz
128-bit
Memory Controller: Intel Xeon (Haswell-E) Integrated Memory
Controller 1 Target Address, Thermal & RAS
Registers 100MHz, 2x 16GB ECC DIMM DDR4 2.13GHz
128-bit
Memory Controller: Intel Xeon (Haswell-E) Integrated Memory
Controller 0 Target Address, Thermal & RAS
Registers 100MHz, 2x 16GB ECC DIMM DDR4 2.13GHz
128-bit
Memory Controller: Intel Xeon (Haswell-E) Integrated Memory
Controller 1 Target Address, Thermal & RAS
Registers 100MHz, 2x 16GB ECC DIMM DDR4 2.13GHz
128-bit

< Memory Module(s) >
Memory Module: Hynix (Hyundai) HMA81GR7AFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7AFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7MFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7MFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7MFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7MFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7MFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7AFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA41GR7AFR8N-TF 8GB ECC DIMM
Registered DDR4 2Rx8 PC4-17100R DDR4-2134 (15-15-
15-37 4-52-17-6)
Memory Module: Hynix (Hyundai) HMA81GR7MFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) xMA41GR7AFR8N-TF 8GB ECC DIMM
Registered DDR4 2Rx8 PC4-17100R DDR4-2134 (15-15-
15-37 4-52-17-6)
Memory Module: Hynix (Hyundai) HBx81GR7AFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7AFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7AFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)
Memory Module: Hynix (Hyundai) HMA81GR7MFR8N-UH 8GB ECC DIMM
Registered DDR4 1Rx8 PC4-19200R DDR4-2400 (17-17-
17-40 4-57-19-6)

< Video System >
Monitor/Panel: LG TV
(3840x2160, 72.3")
Monitor/Panel: LG TV SSCR
(3840x2160, 72.3")
Video Adapter: NVIDIA GeForce GT 710 (192S 1C SM5.5 953MHz,
512kB L2, 2GB 5GHz 64-bit, PCIe 2.0 x8)
Video Adapter: NVIDIA GeForce GT 710 (192S 1C SM5.5 953MHz,
512kB L2, 2GB 5GHz 64-bit, PCIe 2.0 x8)

< Graphics Processor >
CUDA: NVIDIA GeForce GT 710 (192S 1C SM3.5 953MHz,
512kB L2, 2GB 5GHz 64-bit)
OpenCL: NVIDIA GeForce GT 710 (192S 1C SM1.2 953MHz,
512kB L2, 2GB 5GHz 64-bit)
D3D 11: NVIDIA GeForce GT 710 (192S 1C SM11.5 953MHz,
512kB L2, 2GB 5GHz 64-bit)
OpenGL: NVIDIA Corporation GeForce GT 710/PCIe/SSE2
(2GB)
OpenGL: NVIDIA Corporation GeForce GT 710/PCIe/SSE2
(2GB)

< Storage Devices >
Disk: ATA SSD PLUS 480GB (480.1GB, SATA)
Disk: Seagate ATA ST2000DM001-1ER1 (2TB, SATA, 3.5")
Disk: ATA Samsung SSD 860 (1TB, SATA)
Disk: ATA Samsung SSD 860 (1TB, SATA)
Disk: INTEL SSDPEKNW010T9 (1TB, PCIe2/3x4/NVMe, SSD,
SED)
Disk: JMicron Technology 9561 (130PB, USB2)
Disk: JMicron Technology 9561 (130PB, USB2)
Disk: JMicron Technology 9561 (130PB, USB2)
Disk: JMicron Technology 9561 (130PB, USB2)
Optical: HL-DT-STDVD+-RW GHB0N (SATA, DVD+-RW, CD-RW)

< Logical Storage Devices >
Sessions SSD (D:): 446GB (NTFS, 4kB) @ ATA SSD PLUS 480GB (480.1GB,
SATA)
Plugins And Downloads HD (F:2TB (NTFS, 4kB) @ Seagate ATA ST2000DM001-1ER1
(2TB, SATA, 3.5")
Internal SSD (K:): 932GB (NTFS, 4kB) @ ATA Samsung SSD 860 (1TB,
SATA)
Plugin And Content SSD (E:):932GB (NTFS, 4kB) @ ATA Samsung SSD 860 (1TB,
SATA)
Win 10 Boot SSD (C:): 931GB (NTFS, 4kB) @ INTEL SSDPEKNW010T9 (1TB,
PCIe2/3x4/NVMe, SSD, SED)
East West (X:): 4TB (NTFS, 4kB) @ JMicron Technology 9561 (130PB,
USB2)
Backup Plugins-Content (G:):4TB (NTFS, 4kB) @ JMicron Technology 9561 (130PB,
USB2)
Ext SSD 1 (I:): 477GB (NTFS, 4kB) @ JMicron Technology 9561
(130PB, USB2)
Ext SSD 2 (J:): 477GB (NTFS, 4kB) @ JMicron Technology 9561
(130PB, USB2)
Hard Disk: 464MB (NTFS, 4kB) @ ATA SSD PLUS 480GB (480.1GB,
SATA)
Hard Disk: 450MB (NTFS, 4kB) @ ATA SSD PLUS 480GB (480.1GB,
SATA)
Hard Disk: 521MB (NTFS, 4kB) @ INTEL SSDPEKNW010T9 (1TB,
PCIe2/3x4/NVMe, SSD, SED)
Optical Drive (Z:): N/A @ HL-DT-STDVD+-RW GHB0N (SATA, DVD+-RW, CD-
RW)

< Peripherals >
LPC Hub Controller: Dell ICH99 (Wellsburg) LPC Controller
LPC Hub Controller: T1 08-00
Audio Device: Dell ICH99 (Wellsburg) HD Audio Controller
Audio Codec: Realtek Semi 280 High Definition Audio
Audio Device: ASUS GK208 HDMI/DP Audio Controller
Audio Codec: nVidia nForce4 ISA Bridge
Serial Port(s): 2
Disk Controller: Dell ICH99 (Wellsburg) 6-Port SATA Controller
[AHCI mode]
Disk Controller: Dell SAS3008 PCI-Express Fusion-MPT SAS-3
Disk Controller: Intel Standard NVM Express Controller
USB Controller: Dell ICH99 (Wellsburg) USB3 xHCI Host Controller
USB Controller: Dell ICH99 (Wellsburg) USB2 Enhanced Host
Controller #2
USB Controller: Dell ICH99 (Wellsburg) USB2 Enhanced Host
Controller #1
SMBus/i2c Controller: Intel ICH SMBus
SMBus/i2c Controller: Intel MCP4-E(P) XMB Ch 0 SMBus
SMBus/i2c Controller: Intel MCP4-E(P) XMB Ch 1 SMBus
SMBus/i2c Controller: Intel MCP4-E(P) XMB Ch 0 SMBus
SMBus/i2c Controller: Intel MCP4-E(P) XMB Ch 1 SMBus
SMBus/i2c Controller: Intel MCP4-E(P) XMB Ch 0 SMBus
SMBus/i2c Controller: Intel MCP4-E(P) XMB Ch 1 SMBus
SMBus/i2c Controller: Intel MCP4-E(P) XMB Ch 0 SMBus
SMBus/i2c Controller: Intel MCP4-E(P) XMB Ch 1 SMBus

< Printers and Faxes >
Printer: Microsoft XPS Document Writer v4 (600x600,
Colour)
Printer: Microsoft Print To PDF (600x600, Colour)
Fax: Microsoft Shared Fax Driver (200x200)

< Biometrics >
Voice: Analog NUI Voice Virtual Sensor (Voice)

< Peripherals >
Media Player: (477GB)
Media Player: (3.64TB)
Media Player: (477GB)
Media Player: (3.64TB)

< Network Services >
Network Adapter: Intel(R) Ethernet Connection I217-LM (Ethernet)
Network Adapter: Intel(R) I210 Gigabit Network Connection
(Ethernet)
Wireless Adapter: Realtek 8812AU Wireless LAN 802.11ac USB NIC
(Wifi5 (802.11ac/VHT), AES-CCMP, 520Mbps)

< Operating System >
Windows System: Microsoft Windows 10 Professional 10.0.19042
Platform Compliance: x64

[cqd]

I don't know if it will be anything to do with your system..

Mine is a gigabit i9 with 64gig ram, and yeah, I think it might be just that Opus is still a bit clunky in pro tools..particularly in a larger session..like, play was pretty bad until version 6..Does a small 3 or 4 track project open OK?..

Try the drive settings and the never preload in settings, but consider investing in ve pro would be my suggestion..Even for running large templates with kontakt it's more stable..

[falcowe]

I found Play unusable in ProTools (admittedly this was a few years ago at this point), and have since moved on to primarily Kontakt instruments hosted in VEPro. And while I have not experimented in ProTools recently I would suggest (and suspect) that ProTools doesn’t handle VIs very well for whatever reason, so I would modify your workflow to work with VEPro. My guess is it’ll save you time in the end not having to load massive templates every time you want to work on a project.

[Media Man]

Originally Posted by falcowe

I found Play unusable in ProTools (admittedly this was a few years ago at this point), and have since moved on to primarily Kontakt instruments hosted in VEPro. And while I have not experimented in ProTools recently I would suggest (and suspect) that ProTools doesn’t handle VIs very well for whatever reason, so I would modify your workflow to work with VEPro. My guess is it’ll save you time in the end not having to load massive templates every time you want to work on a project.

I'll give that a look. The client's computer is at a different location, but it's a strong box. Mine is stronger, but I'll try it here first.

Thanks for the tip. When the sample player tech support doesn't help, time to move on instead of trying to solve it for them.

[Obsidian Dragon]

Thanks for posting the Sandra report. The Dell Precision 7910 was a nice machine. Although a little bit old by today's standards, (it was released back in 2014), it should be fine for Protools. I don't see anything out of the ordinary, but perhaps some of our more seasoned techies can take a look. If everything is in order, then I might have to agree with a previous poster that it just might be East-West Opus not working well in the Protools environment.

[daeron80]

Yep. I figured Opus just wasn't ready for prime time. Went back to using Play for the few ew things I still use. Have mostly gone to using Spitfire products, especially BBC SO Pro, which is stunningly good for most things. Hard to beat the ew Steinway for the price, though. And the choir with Word Builder. That's about the only ew I use anymore. If they get Opus right, it could be useful for pattern generation.

[[email protected]]

yes it crashed my session yesterday. i have a tough time loving east west stuff.

Originally Posted by Media Man

Is anyone having trouble using East West Opus and it's sample libraries as a plug-in to Pro Tools?

Asking for a friend. He has no problem recording numerous midi tracks that play back just fine using the Opus Player plug-in, but when he closes the session and re-opens the next day, or even a few minutes later, Opus plug-ins are randomly greyed out and inactive, and cannot be re-activated, with various error messages that Opus tech support says Avid does not even understand. Closing and opening a second time causes more Opus tracks to become inactive.

A new beta version was provided, but the problem was not fixed at all .... now just an error message about "lack of resources", which can't possibly be true.

Asking for a friend. Everything else in Pro Tools is working fine.

Question #2 ... what is your sample library of choice for orchestral type stuff?

Media Man

His system is Pro Tools 2021.x
Lenovo i7
Windows 10
SSL 2+

[LightWing]

Originally Posted by Obsidian Dragon

Thanks for posting the Sandra report. The Dell Precision 7910 was a nice machine. Although a little bit old by today's standards, (it was released back in 2014), it should be fine for Protools. I don't see anything out of the ordinary, but perhaps some of our more seasoned techies can take a look. If everything is in order, then I might have to agree with a previous poster that it just might be East-West Opus not working well in the Protools environment.

As a retired IBM Senior IT Hardware and Infrastructure Project Manager I can safely say "Oh it's more than 'it should be fine for Protools.'." HW especially for PT and any other DAW software with excellent performance is about "Balance" between all the components. Dual 10 Core Xeons, 20 total and 40 Virtual, 128GB RAM and ALL SSD drives are a pretty well Balanced environment to work in that cost me less that cost me $2K to put together.

It does of course depend on the type of stress you put it under and I've run tests on this box with a mix of over 100 tracks and NEVER had performance run over 60% at that level.

Based upon some of the other members comments it appears the AAX implementation of OPUS and/or Orchestrator are having "issues" shall we say.

Runs wonderful under Studio One 5.3 which has become my "go to" DAW as of late. PT continues to be a PITA and I won't be renewing my subscription in two months.

[LightWing]

Originally Posted by cqd

I don't know if it will be anything to do with your system..

Mine is a gigabit i9 with 64gig ram, and yeah, I think it might be just that Opus is still a bit clunky in pro tools..particularly in a larger session..like, play was pretty bad until version 6..Does a small 3 or 4 track project open OK?..

Try the drive settings and the never preload in settings, but consider investing in ve pro would be my suggestion..Even for running large templates with kontakt it's more stable..

Blows up even on 3-5 track test projects. Works OK on first use in a track but subsequent reloads of the track spew out JSON loading errors all over the place resulting in the VI being disabled across all tracks it on.

Not going to scrap all the work/time/effort and expense I've done with EW and Opus just to get what I need in PT. Easier to just walk away from PT to Studio One 5.3 where EW/and Opus work flawlessly.