Studio One → Nuendo. Drop a Studio One .song song and get a .dawproject Nuendo imports: the real session rebuilt, not bounced to stems.
Full walkthrough: How to convert your session to another DAW
Every track, clip and note, written into a .dawproject Nuendo imports, not flattened to stems.
Tracks with their names, volume, pan and mute; audio events with their files traveling in the song folder; MIDI notes; the tempo and time-signature maps, every change, even a song with a thousand of them; markers. Third-party plugin state isn’t promised on the Studio One–Nuendo pair yet. Studio One’s built-in effects and instruments arrive by name only, and the report lists each one. Automation isn’t promised on this pair yet. Nothing is silently dropped: every conversion comes with a report of what changed.
Local conversions stay right in your browser: your session never leaves your computer, nothing uploaded, nothing stored. Uploaded sessions move over an encrypted connection into your own private space, with access only you control, and yours to delete anytime.
Not as a native Nuendo project. Doseedo converts it: upload your .song, or zip the whole song folder (the .song with its Media/) so the audio travels with it, and it writes a .dawproject (the open DAWproject format Nuendo imports) with the tracks, MIDI, audio and tempo map in place.
The .song. Studio One (renamed Fender Studio Pro in version 8) saves a song as a .song file in a song folder with its audio in Media/. Zip the whole song folder so the audio travels with it; a bare .song converts the arrangement, MIDI and mixer, but its audio stays behind on your disk.
People describe the same job five ways (export Studio One to Nuendo, import a .song into Nuendo, transfer the project, open a Studio One project in Nuendo), and none of it needs stems. Upload the .song and it converts to a .dawproject Nuendo imports with tracks, MIDI, audio and the tempo map intact.
Tracks with their names, volume, pan and mute; audio events with their files traveling in the song folder; MIDI notes; the tempo and time-signature maps, every change, even a song with a thousand of them; markers. Third-party plugin state isn’t promised on the Studio One–Nuendo pair yet. Studio One’s built-in effects and instruments arrive by name only, and the report lists each one. Automation isn’t promised on this pair yet.
Third-party plugin state isn’t promised on the Studio One–Nuendo pair yet. Studio One’s built-in effects and instruments arrive by name only, and the report lists each one. Nothing is faked: whatever doesn’t cross the Studio One–Nuendo boundary is named in the conversion report.
Nuendo’s own .npr format isn’t publicly documented, and a file we can’t be sure opens would only look like a conversion. DAWproject is the open project format Bitwig and PreSonus created together; Nuendo imports it through its DAWproject import. The download is that one file, with the audio inside it.
Nuendo has no DAW-to-Nuendo importer for another DAW’s own project, but it reads DAWproject, the open format the download is written in. Open the .dawproject from Nuendo’s DAWproject import, and the tracks, MIDI, audio and tempo map come in as a Nuendo project. Cubase reads the same file.
Your project is uploaded over an encrypted connection into your own private space, converted, and is yours to delete anytime.
3 conversions a month with no account; a free account gets 120 credits a month and Pro 2,000 (a conversion is 1 credit), every plan at full fidelity. No watermark, cancel in one click. One conversion is one project translated one direction; a round-trip is two.