Dragging Chords in Arrange Mode causing Cubase 14 Pro to become unstable

Scaler 3 Support Fixed
1

Does not occur all the time, but when selecting and chords around in arranger view, Cubase is “becoming unstable” and generating errors.

cubase-error
cubase-error788×581 48 KB

1 Like
2

Same thing happening here cubase 13 pro

1 Like
3

Early days, but :crossed_fingers: the latest update is more stable, only had it for a day to play with, but no repeat of the Cubase becoming unstable alert. Will give it some more testing to see if I can crash it…

1 Like
4

Spoke too soon, one “unstable alert” today, but not changing chords. Was in arrange page, with previous loaded chords, and just previewing, clicked on 3-dots in Main Track and up popped the message. Not sure if I have a corrupt chord set / file. Just noticed another strange one.

Previewing chord sound, clicking on chord (see 1) and as you can see details recorded in pane correctly (see 2). However, then I get a few chords over and you can see the data does not get displayed. Not sure if related to unstable alerts. However, there is no way for me to change the midi-modifiers for this chord (and a bunch of other chords that follow) and then it sorts itself out near the end of the progression.

Example All OK

chord-ok
chord-ok1102×786 79.8 KB

Example with error:

chord-not-ok
chord-not-ok1111×780 74.8 KB

1 Like
5

Just checking @MusicTilly Have you tried the following:

Please delete Scaler 3 Settings File and restart Scaler 3:

  • Mac → /Users/[NAME]/Library/Application Support/Scaler 3.settings
  • PC → C:\Users[NAME]\AppData\Roaming\Scaler 3.settings
6

Tried it. Changed a little bit but not showing the full set of midi modifiers.

Good Chord

2025-04-04_22h41_39
2025-04-04_22h41_39689×722 68.7 KB

Corrupt Setting

2025-04-04_22h43_01
2025-04-04_22h43_01685×745 64.1 KB

7

Just to add, I do flip a bit between standalone mode and DAW instance, not sure if they share the same settings or not? I renamed the old settings, just in case needed.
2025-04-04_22h46_48

8

I am also running into Cubase becoming unstable and crashing when dragging chords. I am running Cubase 13.0.55.

Scaler 3 is becoming quite frustrating across many aspects now. I feel the software is just not ready for prime-time just yet.

image
image1520×681 81.6 KB

Here is the Exception Analysis of the Cubase DMP file:

*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1062

    Key  : Analysis.Elapsed.mSec
    Value: 107034

    Key  : Analysis.IO.Other.Mb
    Value: 28

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 111

    Key  : Analysis.Init.CPU.mSec
    Value: 390

    Key  : Analysis.Init.Elapsed.mSec
    Value: 66044

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 200

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Failure.Bucket
    Value: INVALID_POINTER_READ_c0000005_Scaler_3.vst3!Unknown

    Key  : Failure.Exception.Code
    Value: 0xc0000005

    Key  : Failure.Exception.IP.Address
    Value: 0x7ff8ef27e822

    Key  : Failure.Exception.IP.Module
    Value: Scaler_3

    Key  : Failure.Exception.IP.Offset
    Value: 0x67e822

    Key  : Failure.Hash
    Value: {ff1996a6-36e5-ccd8-ee99-b01ee8396963}

    Key  : Failure.ProblemClass.Primary
    Value: INVALID_POINTER_READ

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 69158

    Key  : Timeline.Process.Start.DeltaSec
    Value: 1690

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.Process.Version
    Value: 13.0.55.328


FILE_IN_CAB:  Cubase 13.0.55 64bit2025.4.24 9.00.53.033.dmp

CONTEXT:  (.ecxr)
rax=0000000000000000 rbx=0000000000000000 rcx=000000000014f6f0
rdx=000000000014f5d0 rsi=0000000000000000 rdi=000000000014f640
rip=00007ff8ef27e822 rsp=000000000014f500 rbp=0000000000000000
 r8=000000000014f650  r9=00007ff8ef93bee8 r10=0000000000000006
r11=000000000014f5a0 r12=000000000014f5d0 r13=000000000014f650
r14=00007ff8ef93bee8 r15=000000000014f6f0
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
Scaler_3!essentia::streaming::SinkBase::setId+0x5b282:
00007ff8`ef27e822 4c8b33          mov     r14,qword ptr [rbx] ds:00000000`00000000=????????????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff8ef27e822 (Scaler_3!essentia::streaming::SinkBase::setId+0x000000000005b282)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

PROCESS_NAME:  Cubase13.exe

READ_ADDRESS:  0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

STACK_TEXT:  
00000000`0014f500 00007ff8`ef284405     : 00000000`a312d570 00000000`ffffffff 00000000`c75b4ea0 00000000`f99daa00 : Scaler_3!essentia::streaming::SinkBase::setId+0x5b282
00000000`0014f5a0 00007ff8`ef28a06d     : 00000000`0014f6f8 00000000`c75b4ea0 00000000`f99d3901 00000000`a18462b0 : Scaler_3!essentia::streaming::SinkBase::setId+0x60e65
00000000`0014f5d0 00007ff8`ef288861     : 00000000`f99d3950 00000000`00000001 00000000`f99d3950 00000000`4644cb40 : Scaler_3!essentia::streaming::SinkBase::setId+0x66acd
00000000`0014f6e0 00007ff8`ef079486     : 00000000`fa1f5120 00007ff8`ef7678e8 00000000`00570000 00000000`00000000 : Scaler_3!essentia::streaming::SinkBase::setId+0x652c1
00000000`0014f720 00007ff8`ef2d516e     : 00000000`cad4e600 00000000`52ddb5a0 00000000`0014f7d9 00000000`fcb05770 : Scaler_3!essentia::Parameter::type+0x170816
00000000`0014f760 00007ff8`eef21a98     : 00000000`cb9a33b0 00000000`00000000 00000000`c7ba8a20 00000000`00000000 : Scaler_3!essentia::streaming::SinkBase::setId+0xb1bce
00000000`0014f840 00007ff8`eef24302     : 00000000`0014f860 00000000`c7ba89e0 00000000`a29e9aa0 00000000`a29e9aa0 : Scaler_3!essentia::Parameter::type+0x18e28
00000000`0014f8c0 00007ff8`eef23bd7     : 00000000`4640d490 00000000`cb9a3390 00000000`00000000 00000000`4640d490 : Scaler_3!essentia::Parameter::type+0x1b692
00000000`0014f8f0 00007ff8`eef249a6     : 00000000`c7ba89e0 00000000`0000047b 00000000`00000000 00000000`000305dc : Scaler_3!essentia::Parameter::type+0x1af67
00000000`0014f940 00007ff9`67d8b643     : 00000000`80000022 00000000`0014fba0 00000000`000305dc 00000000`80000022 : Scaler_3!essentia::Parameter::type+0x1bd36
00000000`0014f970 00007ff9`67d891cd     : 00000000`00634830 00007ff8`eef24960 00000000`00000000 00000001`4476fa23 : user32!UserCallWinProcCheckWow+0x503
00000000`0014fad0 00000001`4475d539     : 00000000`00634830 00000000`00634758 00000000`00634830 00007ff9`67db8d02 : user32!DispatchMessageWorker+0x1dd
00000000`0014fb50 00000001`4474e89f     : 00000000`00634828 00000000`00000000 00000171`0000026e 00000000`32ca0000 : Cubase13+0x475d539
00000000`0014fbd0 00000001`4474bb00     : 00000000`00634758 00000000`00000000 00000000`000304e6 00000000`00634758 : Cubase13+0x474e89f
00000000`0014fc00 00000001`4474b97b     : 00000000`00634758 00000000`00634758 00000000`00000000 00000001`443d3989 : Cubase13+0x474bb00
00000000`0014fc40 00000001`443cf7c8     : 00000000`00000000 00000000`00634760 00000000`00000000 00000000`00000000 : Cubase13+0x474b97b
00000000`0014fc90 00000001`434f0504     : 00000000`006076a0 00000000`006076a0 00000000`006078e8 00000000`00607920 : Cubase13+0x43cf7c8
00000000`0014fcc0 00000001`4489c4d6     : 00000000`00000000 00000000`0014fce8 00000000`0014fd28 00000000`0014fce8 : Cubase13+0x34f0504
00000000`0014ff20 00007ff9`66dce8d7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Cubase13+0x489c4d6
00000000`0014ff60 00007ff9`688d14fc     : 00000000`00000000 00000000`00000000 000004f0`fffffb30 000004d0`fffffb30 : kernel32!BaseThreadInitThunk+0x17
00000000`0014ff90 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2c


STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME:  Scaler_3+5b282

MODULE_NAME: Scaler_3

IMAGE_NAME:  Scaler 3.vst3

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_Scaler_3.vst3!Unknown

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  1.0.5.0

FAILURE_ID_HASH:  {ff1996a6-36e5-ccd8-ee99-b01ee8396963}

Followup:     MachineOwner
---------

I also noticed some odd behaviour when dragging chords to Cubase, and this may be related to the crash I mentioned previously. Firstly, when I drag the Chords from Scaler to an existing midi track in Cubase it is ignored, and a new midi track is created with the chords. Also an error appears from Scaler saying “Time Type Mismatch”. Secondly, when I repeat the dragging of chords to cubase, instead of a single new midi track being created, two duplicate midi tracks are created. See below for a short video demonstrating the issue.

Recording 2025-04-24 at 09.45.27

9

Small update to my previous post relating to the strange behavior in dragging chords to Cubase.

I have discovered the issue only occurs if you have used the Project / Tempo Detection function in Cubase. Tempo Detection creates a Tempo Track. What is odd, is if you delete the Tempo Track, and all Tempo Change points after a Tempo Detection then the issue still persists with dragging the chords to cubase. However, if you create a Tempo Track manually and manually add Tempo Changes then Scaler works fine. It seems using Tempo Detection causes something to break for Scaler.

10

Hi all. We’ve made some improvements to MIDI timing and MIDI drag-and-drop in Scaler 3 1.0.6. I’m curious whether a clean install and update to version 1.0.6 resolves any of the issues mentioned in this thread — please let me know. Cheers.

1 Like