Export midi file extension

Cubase
1

Morning all
Something strange
When I export a midi file C13 pro the file has no extension *.
However, is not very important because I rename the file adding extension *. mid.
Strange because with C12 pro it’s export correctly
Something wrong on C13 pro ?
Should I do something to correct this issue?
Nota: Same computer same windows 10

2

Hi,

I believe, you can type .mid in the Export file dialog.

3

Hello Martin
yes when I export I type EXPORT MIDI
Definitely C13 pro export a file but without extension *.mid
E.G. file A exported as requested midi file appear as “A” without extension, (white no applications can open it) then I rename this file “A” exported adding .mid and the file become A.mid (midi file)
On C12 pro which I didn’t remove for reference, when I am doing same operation exported a file with extension *.mid means midi file correctly.

4

Hi,

I mean, you can write A.mid name in the Export File window. Then you don’t have to rename the file afterwards.

1 Like
5

Thanks Martin I will try it, sorry I didn’t understand

6

I think Mr @Gennaro is trying to say that, usually, Cubase adds the ext for you. Eg, if you omit the .cpr ext when saving a project for the first time or as a Save As, Cubase will add it for you.
In the case of .mid files, C13 isn’t doing that, whereas it used to in C12.

1 Like
7

Reminds me of the 1980’s, where you occassionally had to add suffixes manually.

It fits the theme of Cubase 13 - you know, removing the Beat Calculator so that we have to use the pocket calculator again like in the 80’s.

You know what the sad part about a “bug” like this is? Either they fix it right away or not in 20 years, with chances being huge on the latter one.

1 Like
8

Thank you so much team
While trying the suggestion of Martin, he was right; The extension need to be wrote manually.
Yes Googly on C13 this was my issue when on C12 was normal adding automatically the extension.
Yes Johnny I remember, but we are on 2024 and is OK manually it’s work
Please consider the issue closed

9

Hi,

The issue is going to be fixed in the next update.

10

Thanks Martin
good news