I am looking for info on how to convert a Studio One song (well, the MIDI parts anyway) into a Notion 5 score.
Thanks

Donald Barks
Dog Eared Sound
ASUS X99-A II, i7 5820K 3.30GHz, 32GB, ASUS GTX 950 Strix,
Corsair H80i v2, Samsung 850 500GB SSD
Tascam FW 1884, SIIG Firewire 400 (TI Chipset)
S1 Pro v3.2.2, Cubase 9 (hey, I am promiscuous)
KRK Rokit 5 Studio Monitors
Rode NT1; Shure SM57, SM588
Don't even ask about my analog synth pile..

Groucho Barx wroteI am looking for info on how to convert a Studio One song (well, the MIDI parts anyway) into a Notion 5 score.

(1) In your Studio One project, select the MIDI for an Instrument and then right-click on the MIDI. This displays the following dialog where you can do the MIDI export . . .

Code: Select all

(2) Import the MIDI into NOTION 5 via the File->Import dialog . . .
(3) Use the NOTION 5 Tools Menu 'Convert to Notation' function to convert the MIDI to music notation . . .
Lots of FUN!

The Surf Whammys
Sinkhorn's Dilemma: Every paradox has at least one non-trivial solution!

Thanks for that, S Wham. This rather vital function is stuck in a sub-menu, and the Studio One manual ('Look Mom, No Midi!) leads you to believe it doesn't exist.

thomasbaxter wroteThanks for that, S Wham. This rather vital function is stuck in a sub-menu, and the Studio One manual ('Look Mom, No Midi!) leads you to believe it doesn't exist.

Glad to help!
THOUGHTS
I generally avoid reading user guides, based primarily on decades of working as a software engineer . . .
My perspective on this is that user guides typically are written by technical writers who try to glean information from software engineers, which is nearly impossible to do, since (a) it requires understanding the way software engineers think and communicate and (b) it would take too long and cost too much . . .
Explained another way, user guides nearly never make sense to me, because they don't provide all the information in a concise way that folks can follow step-wise to do something productive . . .
Instead, I use the mouse and keyboard to do a bit of what I call 'scouting around', where the goal is to discover how the software engineers decided to do stuff . . .
Applications always do stuff, but all the stuff they do seldom is documented in detail, hence the strategy of exploring by clicking and right-clicking with the mouse, where the latter activity reveals context menus, which is the way I found the MIDI export context menu item . . .
Without reading the user guide, it was obvious to me that Studio One exports MIDI--because it would be highly illogical not to be able to export MIDI--but how it does this was a mystery until I started clicking and right-clicking . . .
It wasn't in the application menus (File, Edit, and so forth), hence it had to be someplace else . . .
NOTION is similar in this respect, and it does a lot more stuff than is documented in the user guide, as is the case basically with every digital music production application . . .
For example, when I decided to make sense of ReWire in 2010, it took about three months to discover the various rules, and this was when I applied to become a third-party ReWire developer with Propellerhead Software, which took about 18 months, and now I have all the information about adding ReWire to an application, which is useful . . .
There are some public ReWire diagrams and various information, but getting the software development kit (SDK) requires being approved, since it's proprietary information and requires a non-disclosure agreement (NDA) . . .
Since 2010, I have spent several hundred hours documenting in this forum (PreSonus and Notion Music before PreSonus) how to do ReWire with NOTION and a handful of Digital Audio Workstation (DAW) applications, which includes making YouTube video tutorials . . .
It's not difficult to do ReWire sessions with NOTION and DAW applications that support ReWire, but discovering how to do it is difficult, because all the required information is not found anywhere in user guides, including the Propellerhead Software website, and they are the ones who created and maintain ReWire technology . . .
[NOTE: However, there are topics in this forum that explain everything in detail, so it's documented here, at least for a few DAW applications, some of which only are available on the Mac, like Logic Pro X . . . ]
The reality is that it's neither practical nor affordable for a company to document all this stuff in detail, because (a) there are too many variations and scenarios and (b) by the time a variation or scenario is documented fully, it's very likely that something will change and by doing so will make the documentation 'out of date' for new versions of the ReWire host controller or ReWire slave(s) . . .
Lots of FUN!

The Surf Whammys
Sinkhorn's Dilemma: Every paradox has at least one non-trivial solution!

Groucho Barx wroteI am looking for info on how to convert a Studio One song (well, the MIDI parts anyway) into a Notion 5 score.
Thanks

In Studio One use File>Save As and change the file 'Type' to Midi File on the dropdown menu.
Add a new name, click the save button.
Then click Yes when asked 'Do you want to save a copy of 'xxx' as format MIDI File?'
,Newberry

johnnewberry wroteIn Studio One use File>Save As and change the file 'Type' to Midi File on the dropdown menu.
Add a new name, click the save button.
Then click Yes when asked 'Do you want to save a copy of 'xxx' as format MIDI File?'

Elegant! Best answer, for sure!

The Surf Whammys
Sinkhorn's Dilemma: Every paradox has at least one non-trivial solution!

John's answer is correct, especially when you consider that the other method doesn't include tempo or markers or even correct time placement.

Lawrence wroteJohn's answer is correct, especially when you consider that the other method doesn't include tempo or markers or even correct time placement.

Excellent!
THOUGHTS
This is the only information I was able to find about exporting MIDI in the Studio One 3 Reference Manual:

Exporting MIDI Files
To export an Instrument Part to a MIDI file, [Right]/[Ctrl]-click on the Part and select Export Parts to MIDI File. Choose a file name and storage location in the pop-up menu and click OK. A Standard MIDI File is created, with a .mid file extension.
Multiple Instrument Parts can be exported at once to a single file. To do this, select the desired Parts and use the same process as above. One MIDI file is created that includes individual MIDI clips for each Part, in the correct sequence, with a common start time.
You can also drag-and-drop any Instrument Part to a location in the File Browser to export a MIDI file to that location. If you drag-and-drop multiple parts at once, they are written to one MIDI file with multiple Parts.
Standard MIDI Files exported from Studio One can be used by virtually any application that supports MIDI.

[NOTE: If the File menu 'Save As . . . ' information is documented in the Studio One 3 Reference Manual, then it's not anywhere I can find it . . . ]
Toward the goal of providing more information, I did a MIDI export in each of the two ways, (a) by part and (b) by the File menu 'Save as . . .' menu item, and the results are as you described, as shown in the following detailed analyses done with MidiKit (a personal favorite) . . .
MidiKit (Mixage Software) ~ Mac App Store
[NOTE: This is the export MIDI by part(s) method . . . ]
[NOTE: This is the 'Save As . . . ' export MIDI method . . . ]
As you wrote, there clearly is more information provided in the 'Save As . . . ' method . . .
SUMMARY
Kudos to you and John for the excellent information!
Now it's fully documented, which is fabulous . . .

Fabulous!

The Surf Whammys
Sinkhorn's Dilemma: Every paradox has at least one non-trivial solution!