Dorico 5 input with one second delay

Hi!

I made use of a steinberg offer and upgraded vom dorico pro 4 to latest version 5 - so far so good.

My problem:
Working with bigger orchestral files is very lagging. A note input is delayed by a second, copy and paste even more. Playback works fine though, but there`s no way to work with such input delays…
Same files work in Dorico 4 perfectly fine, no lagging at all, both NP.
Note: I use Win 10 on an Threadripper with 64GB and an RX Vega, latest driver.

Any idea?
Many thanks!

Hi. Is condensing on? If so, turn it off until you are done with entering music. This does slow things down, no matter how powerful your machine is, because some calculations need to be done in series and cannot be pipelined.

Hi Marc,
Jes, condensing is off. Dorico 5 doesn’t switch it on by default, I checked.

The thing I don`t understand is: on the same machine in dorico 4 it works flawless but not in dorico 5 - the same file
For now I switched back to dorico 4…

That’s weird. The Team has improved many routines so that the software feels more snappy and responsive, which is exactly the opposite of what you experience.
Maybe you could share your project with someone from the Team (although I don’t think it’s the appropriate timing for that, given the activity increase in the forum those last four days…)

1 Like

Hi Marc!
Thanks for your efforts!

It’s with all my projects. The bigger, the more laggy.
If I switch the playback enginge from NP to SonicSE the note input lagging reduces about %50, the also the same with the VSL Template (full orchestra)- but not copy and paste, this stays laggy. Scrolling even with playback is no problem. Playback even with VSL works flawless.

I tried an orchestra project on my laptop - and have the same problem there! Note input lag about 7 seconds there! Switching from NP to Sonic reduces note input lag to about half a second, but copy and paste (two bars) stays laggy, about 7 seconds…

Puh…

I suspect the issue could be related to the changes in the Qt application framework that Dorico relies upon. Dorico 4 was built on Qt 5, while Dorico 5 is built on Qt 6. Qt 5 uses OpenGL via ANGLE for its drawing and compositing, and Qt 6 uses a new approach bespoke to Qt called RHI. We have seen that on some systems, the new RHI approach runs much more slowly than the older ANGLE approach, on the same hardware.

What kind of GPU do you have in your machine? Have you got the latest display drivers installed?

1 Like

Hello Daniel!
Thanks for looking into this matter!

On my PC I use a RX Vega with 8GB VRam (HBM2 945MhZ), on my Laptop a Vega Mobile GFX in combination with a R7 3700U
Yep, op PC Adrenalin 24.7.1

Best Regards!

When you run dxdiag, what “shader model” number does it say it supports?

See here:

Display Devices

       Card name: Radeon RX Vega
    Manufacturer: Advanced Micro Devices, Inc.
       Chip type: AMD Radeon Graphics Processor (0x687F)
        DAC type: Internal DAC(400MHz)
     Device Type: Full Device (POST)
      Device Key: Enum\PCI\VEN_1002&DEV_687F&SUBSYS_6B761002&REV_C1
   Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 

Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 40824 MB
Dedicated Memory: 8119 MB
Shared Memory: 32705 MB
Current Mode: 3440 x 1440 (32 bit) (60Hz)
HDR Support: Not Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.651367,0.332031), Green(0.306641,0.630859), Blue(0.150391,0.059570), White Point(0.313477,0.329102)
Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
Monitor Name: LG ULTRAWIDE WQHD(Display Port_8bit)
Monitor Model: LG ULTRAWIDE
Monitor Id: GSM5AE2
Native Mode: 3440 x 1440(p) (59.973Hz)
Output Type: Displayport External
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: Not Supported
Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\u0405470.inf_amd64_2e71ce0e27c179e1\B404884\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0405470.inf_amd64_2e71ce0e27c179e1\B404884\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0405470.inf_amd64_2e71ce0e27c179e1\B404884\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0405470.inf_amd64_2e71ce0e27c179e1\B404884\amdxc64.dll
Driver File Version: 31.00.21916.0002 (English)
Driver Version: 31.0.21916.2
DDI Version: 12
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.7
Hardware Scheduling: Supported:False Enabled:False
Graphics Preemption: Primitive
Compute Preemption: DMA
Miracast: Not Supported by Graphics driver
Detachable GPU: No
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: DISABLE_HWSCH
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 18.06.2024 02:00:00, 1826264 bytes
WHQL Logo’d: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71EE2-2B3F-11CF-B073-EA1E6EC2D235}
Vendor ID: 0x1002
Device ID: 0x687F
SubSys ID: 0x6B761002
Revision ID: 0x00C1
Driver Strong Name: oem97.inf:cb0ae414659058d8:ati2mtag_R7500:31.0.21916.2:PCI\VEN_1002&DEV_687F&REV_C1
Rank Of Driver: 00CF2000
Video Accel: Unknown
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeH264_VLD_NoFGT {4245F676-2BBC-4166-A0BB-54E7B849C380} {6719B6FB-5CAD-4ACB-B00A-F3BFDEC38727} {9901CCD3-CA12-4B7E-867A-E2223D9255C3} DXVA2_ModeHEVC_VLD_Main {EA72396A-67EC-4781-BEDE-56F498F04EF2} {C152CA8F-738C-461B-AD89-FC292CF8F162} {514A356C-7027-4AFF-8A60-AFD2C1F672F1} DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeVC1_VLD {CA15D19A-2B48-43D6-979E-7A6E9C802FF8} {7C74ADC6-E2BA-4ADE-86DE-30BEABB40CC1} DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC {D1C20509-AE7B-4E72-AE3B-49F88D58992F} {84AD67F6-4C21-419A-9F0B-24F0578906C1} {725AD240-786C-471E-AD3C-38F739936517} {95664FF5-9E03-4C74-BB4F-9178D6035E58} DXVA2_ModeHEVC_VLD_Main10 {65D1FA41-58AF-453A-9CAB-5D981156DA9F} {2DB154B6-DBB2-4079-A3FF-60D7A898A6AB} {C74A3FD0-D713-4581-A02E-8EDFB112ACE3} {603A4756-A864-4F91-BB62-2C935B7A1391} {C58B9A06-7E89-11E1-BB00-70B34824019B}
Deinterlace Caps: n/a
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 1
MPO Caps: Not Supported
MPO Stretch: Not Supported
MPO Media Hints: Not Supported
MPO Formats: Not Supported
PanelFitter Caps: Not Supported
PanelFitter Stretch: Not Supported
Component Drivers:
Driver Name: Unknown
Driver Version: Unknown
Driver Date: Unknown
Driver Provider: Unknown
Catalog Attributes: N/A
Driver Name: Unknown
Driver Version: Unknown
Driver Date: Unknown
Driver Provider: Unknown
Catalog Attributes: N/A

I can’t see what version of DirectX is supported by the card, but from a bit of searching, it looks like your card should be capable of running DX12, which means Shader Model 5.0, and that should be sufficient.

I need to check with a colleague about how to force the Qt framework used by Dorico to fall back on OpenGL rendering, which might work better on your system. Please bear with me.

Jep, DirecX 12 ist listed under the system information.