[Afolabi Lipede]

Thank you Olof,

So I should not worry if the Project File is named ‘Untitled/Default’ when I open the Cubase project?  Where is the SD3 data actually saved when the Cubase Project is saved?

It does seem to be the correct SD3 data file that I was working on that opens when I reopen the Cubase Project, but it is just a little alarming that the name I saved does not come up when I look in the SD3 Drums/Grooves/Mixer/Tracker window.  I guess that saving the SD3 project file with a relevant project name to my chosen folder functions as a backup?

So my SD3 work remains safely tucked into the Cubase Project file when I save in Cubase?  I think it is a bit disconcerting for SD3 newbies when we are used to the very tight way that Cubase file management works to have a more flexible approach to Project file management in SD3.  Not a problem if this is the way it consistently works, and I don’t need to panic when I don’t see the file name that I saved in the SD3 window!

All best to you.

Reply To: [Bug?] File/ Project 'Untitled' version: 3.2.7
Operating system: macOS High Sierra (10.13)

[Afolabi Lipede]

Just following on from the previous OP, has this been fixed yet and what steps need to be taken so that when I save a project in Cubase including lots of work done on SD3.2.7 that the saved SD3 file opens inside the Cubase project instead of ‘Untitled’ for SD3?  It is of course possible to go back and open from in the SD3 Project drop down but it can become confusing when trying to do work over an album-size project!  It would be really nice to know that when I come back to a song that the correct SD3 file opens up with the Cubase Project.  Would it be possible to streamline the saving process in SD3 so that it fits conveniently into a busy workflow please?  Or does this already happen but every time an instance of SD3 is opened it just calls itself – Project Untitled? And then has to be renamed/saved as?

Many thanks,

Afunja Music

Reply To: [Bug?] File/ Project 'Untitled' version: 3.2.7
Operating system: macOS High Sierra (10.13)

[Afolabi Lipede]

Just following on from the previous OP, has this been fixed yet and what steps need to be taken so that when I save a project in Cubase including lots of work done on SD3.2.7 that the saved SD3 file opens inside the Cubase project instead of ‘Untitled’ for SD3?  It is of course possible to go back and open from in the SD3 Project drop down but it can become confusing when trying to do work over an album-size project!  It would be really nice to know that when I come back to a song that the correct SD3 file opens up with the Cubase Project.  Would it be possible to streamline the saving process in SD3 so that it fits conveniently into a busy workflow please?  Or does this already happen but every time an instance of SD3 is opened it just calls itself – Project Untitled? And then has to be renamed/saved as?

Many thanks,

Afunja Music

Reply To: [Bug?] File/ Project 'Untitled' version: 3.2.7
Operating system: macOS High Sierra (10.13)

[Afolabi Lipede]

Maybe I should rephrase this because the above looks woolly!  What would be really great for all of us musicians working at distance in the world governed by Covid is to have a way to send DAW files to the other band members with the correct SD3 file tucked into the DAW saved file so no effort is necessary to retro engineer the delivered file for the recipient to hear the complete set of tweaks and additions that have been made by the sender of the DAW file.  If the recipient could just open the DAW file and not have to search around, find and load the correct, saved SD3 file to make sense of the workflow between studios would save us time and effort.  And it does make sense, really – doesn’t it?  This is not a daft request.  That being said, SD3 is a superb piece of kit, many thanks for that.  It would be world beating if the SD3 files could be sent completely integrated within the commonly-used DAW files of choice in a wholly reliable way to our collaborators!

 

Many thanks,

A Lipede

Reply To: SD3 will not save session. version: 3.2.7
Operating system: macOS Sierra (10.12)

[Afolabi Lipede]

I have found the same issue; if I save the SD3 Project file and name it to match the current working track in Cubase 10.5, when I reload my Cubase 10.5 file SD3 will offer up the ‘default’ un named file.  This is not a big issue when I am mixing in my own studio, but when I send the file to my collaborator in another studio the C10 file opens up with the ‘Default’ SD3 loaded – it does save my kit pieces, but not the performance tweaks that I had laboured over for some lonely hours!  Is there a way for you guys at Toontrack to tag the SD3 file that has been saved with the C10.5 file we have been working on so it will load when the Cubase .cpr file is reopened at another studio, please?

Many thanks to all who have reported this issue, and to the hard-pressed techs at Toontrack!

 

All best, A Lipede

[Author]

Replies