Cubase 13.0.50 Maintenance Update Available

[jackthepilot]

@Misterfly

SFC /SCANNOW

Same here with my MP MIDI. Steinberg completely silent and not helping

[jackthepilot]

@jackthepilot

Same here with my MP MIDI. Steinberg completely silent and not helping

Same here with my MP MIDI. Steinberg completely silent and not helping

[jackthepilot]

I reported strange problems to Steinberg but they are completely silent

[jackthepilot]

I am not sure what is happening but after I upgraded to Cubase 13.0.50 I have to load my MP MIDI controller each time I start Cubase. Up until now it was always loading automatically upon Cubase startup.
Please see the attached video that demonstrates the problem. Thank you

[cubace]

It is very annoying.

[robsnoise]

I have a system with 36 cores (72 in total with HT); and I’ve had an issue opening 13.0.50. Your post prompted me to downgrade to 13.0.21 and this has resolved the multi CPU core support. I wonder why Cubase got rid of the support with systems with more than 32 processors? Have Steinberg advised that they will restore compatability?

[gitarul]

Defect found. @Martin.Jirsak maybe you would like to know.
Running a session with five audio tracks and a Kontakt 7 drum library. Audio performance peak meter travels from 40 to 70 percent when a selected tracks is not a Kontakt track. After selecting Kontakt track this meter shows values between 80 and 100 percent. Nothing else changes except selected track.
Similar issue with Kontakt 8 and Groove Agent 5.
When Padshop was used peaks stay below 25 percent and when the track was selected then peak meter goes on the over 30 percent.

[CKB]

If someone has a similar problem, I have created a separate thread for this:

Cubase 13.0.50 MIDI Remote Encoder Problem

Dear colleagues, with Cubase 13.0.50 there is a MIDI remote encoder problem. This problem is noticeable in the current script for the PreSonus FaderPort. The PreSonus FaderPort has a single central encoder for everything, so this problem crashes the whole script. All previous versions of Cubase since 12.0.70 up to Cubase 13.0.41 did not have this problem. The problem exists with both system platforms (Windows and Mac). The script is very large: 11873 lines the last released version 13381…

[waxxy]

were can i get 13.0.41 update?ive updatd too 13.0.50 and its messed up my dongle and crashes…41 was ok.

[waxxy]

found it…
once i uninstalled .50 update and reinstalled .41 my dongle worked and all my products worked…
there is a bug in .50 which breaks the dongle so if you have a lot of old steinberg products i wouldnt use .50

for anyone wanting older cubase versions heres the link–

Cubase Pro 13 Downloads | Steinberg

[Johnny_Monteo]

@gitarul

After selecting Kontakt track this meter shows values between 80 and 100 percent. Nothing else changes except selected track.

Please keep in mind that the selected track(s) are removed from ASIO Guard. If you have a CPU intense tracks selected it will go fully to the Peak value of the Performance Meter.

[Martin.Jirsak]

Hi,

If you select a track, this becomes Record Enabled, so it’s a “live” track workout any pre-processing. Everything is done on the processor in real-time. So it’s logical the load increases.

[Reco29]

Off topic regarding the title of the thread: Two weeks later and the new 13.0.50 update is still advertised as the new 13.0.41 update in the Steinberg hub. The update is still not up to date, obviously.

[CKB]

There is another MIDI Remote problem with Cubase 13.0.50.

If a fader is assigned to the function ValueUnderMouse,
the fader no longer initializes to where the respective parameter under the mouse has its value.

In the script of the PreSonus FaderPort this task is implemented like this:
On a mappingpage pageMain, the motorized fader controls the Volume.
On a mappingpage pageShift, the motorized fader controls the ValueUnderMouse.

function hostBinding_fader() {
    ...
    pageMain.makeValueBinding(fader.fd_Volume.mSurfaceValue,
        pageMain.mHostAccess.mTrackSelection.mMixerChannel.mValue.mVolume)
    pageShift.makeValueBinding(fader.fd_Volume.mSurfaceValue,
        pageShift.mHostAccess.mMouseCursor.mValueUnderMouse)
    ...
}

Here is a video in which this error is clearly visible,
LluisV took the trouble to create this video.

PreSonus FaderPort 2 (2018) midi remote script

I’m sorry but I cannot do more tests because I rolled back (Nuendo). With Faderport, I toggle the shift key and then the fader should get the value of the knob under mouse. With 13.0.50 the fader sometimes reads the value under mouse, sometimes not. Edit: I reinstalled 13.0.50 and recorded what is happening. With 13.0.41 when I move the mouse over any knob the fader gets the value and I can set it. With 13.0.50 the fader do not get the value of the knob but I can set it, but starting from a…

Regards
CKB

[Martin.Jirsak]

Hi,

This is a known and already reported issue. The value is not sent out when you just hover over the parameter.

There is one more issue related to the AI Knob Lock. If you lock a parameter to a parameter and select another track, the lock becomes released/lost, and you control the mouse-over parameter instead of the locked one.

[m.c]

@Martin.Jirsak

The value is not sent out when you just hover over the parameter.

Yes, it actually retains the value of the previously controlled parameter. And this is what users experience as “jumps” etc.

[Pablin_Drummer2]

Steinberg really should address many of the problems that exist throughout C13 before releasing C14… or else, there will always be (and rightly so) people complaining here and there.

[Joliciel]

When I upgraded last month, I ended up spending 13 hours with tech support. We discovered that the issue was related to systems with more than 32 CPU cores—the new audio engine has compatibility problems with systems using multiple processors. Unfortunately, support couldn’t give me a clear answer on when this will be resolved, whether in version 13 or 14, but they did confirm it’s something Steinberg is actively working on.

[gitarul]

You’re right. Sorry for that.

[Brian_Roland]

@Brian_Roland

I’m getting this on my Windows 11 setup as well.

OK, thanks to m.c. my MIDI remote issue is sorted now.

I had stashed my custom ports script in the wrong file system directory. It’s something m.c. added in case we have our devices named differently. I route a bunch of stuff around via virtual ports, rtp, etc. I’d filled the script out but put it in the wrong folder!

Got it sorted now.

Thanks M.C.!