Thanks Brad. Are you saying you get the issue if you do this the same way as I do it?
I will try and do what you suggested, but it should work the way I do it, and as I said there is no issues with any other virtual instruments.
Really appreciate your help and input on this 
OK, so I did what you suggested and yes, I do hear the drums in the mixdown file so when that is imported in to the Project Page it is heard also (understandably)
However, this is not how the Project Page is intended to work. If you do it this way, then you make any changes to the song, you would need to mix it down again then re-import the file in to the Project Page as it detects no changes. The whole idea of the Project Page is to hold all your finished songs in one place and master them all from there. That way certain plugins can be assigned to the whole project globally such as maybe a limiter and a VU meter, whilst each song can have its own plugin for each mastered track. Then if any changes are made to a song that belongs in the Project Page, it detects the change and updates. This is very good if it becomes evident at the mastering stage that something is not quite right and needs a tweak, which can be done at the mixdown stage of the song rather than adjusting EQ for example in the Mastered track. The perfect mix in many ways is one where very little is required at the mastering stage, certainly where it comes to balancing instruments or a specific track’s EQ.
In the case of SD3, if a song which contains an SD3 instrument (midi) track is saved then you close the song, next time the Project Page is opened, it detects that change but at that point it does not play the drums until the edit song steps are taken as I mentioned earlier.
Thanks again.
Thanks Brad. Are you saying you get the issue if you do this the same way as I do it?
I will try and do what you suggested, but it should work the way I do it, and as I said there is no issues with any other virtual instruments.
Really appreciate your help and input on this
OK, so I did what you suggested and yes, I do hear the drums in the mixdown file so when that is imported in to the Project Page it is heard also (understandably)
However, this is not how the Project Page is intended to work. If you do it this way, then you make any changes to the song, you would need to mix it down again then re-import the file in to the Project Page as it detects no changes. The whole idea of the Project Page is to hold all your finished songs in one place and master them all from there. That way certain plugins can be assigned to the whole project globally such as maybe a limiter and a VU meter, whilst each song can have its own plugin for each mastered track. Then if any changes are made to a song that belongs in the Project Page, it detects the change and updates. This is very good if it becomes evident at the mastering stage that something is not quite right and needs a tweak, which can be done at the mixdown stage of the song rather than adjusting EQ for example in the Mastered track. The perfect mix in many ways is one where very little is required at the mastering stage, certainly where it comes to balancing instruments or a specific track’s EQ.
In the case of SD3, if a song which contains an SD3 instrument (midi) track is saved then you close the song, next time the Project Page is opened, it detects that change but at that point it does not play the drums until the edit song steps are taken as I mentioned earlier.
Thanks again.
Good morning. I guess we would need to find an instrument that works like SD3 does, that being that it needs to load samples into RAM before it is fully functional. My theory is that is what is happening. When you are rendering a “master” stereo file, Studio One loads up the session and creates a stereo .wav file and I believe it’s not waiting until SD3 has finished loading into RAM.
By moving the drum pattern and audio in 20 seconds, without moving the start marker in your song, you will help prove whether my theory is true. Many other virtual instruments stream from disk, therefore do not require the extra time.
Do you use Trilian from Spectrasonics? I believe it loads into RAM as well. I will try a session with it later today and see if it causes the same thing to happen.
Another thought I just had (it’s just about 7am here so nowhere near enough caffeine in my bloodstream) is in the original song, convert the SD3 track to audio and see if the same thing happens. Again only to prove or disprove my theory.
Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)
Definitely not a RAM thing, I have left it to render the entire song and at no time do I hear any drums
Definitely not a RAM thing, I have left it to render the entire song and at no time do I hear any drums
Then that’s different than what I am getting. My result is that some of the drum track is missing at the beginning of the master file, however during import I hear nothing at all, no audio from any track.
Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)
Exactly the same thing. In fact when I first opened the ticket with Presonus two years ago, they suggested I enabled real-time processing! It made no difference. However, doing the same edit and then saving the song as per my instructions does work so at least you’ve reminded me about this and ultimately it will save me some time with it disabled! I think I will leave it that way and see how it goes. I do vaguely remember another small issue though that occurs when not enabling real-time, but can’t remember what it was!
Exactly the same thing. In fact when I first opened the ticket with Presonus two years ago, they suggested I enabled real-time processing! It made no difference. However, doing the same edit and then saving the song as per my instructions does work so at least you’ve reminded me about this and ultimately it will save me some time with it disabled! I think I will leave it that way and see how it goes. I do vaguely remember another small issue though that occurs when not enabling real-time, but can’t remember what it was!
So now that we’re doing things pretty much the same way. I still experience a bit of a lag of the drum track coming when as the samples load, when the song isn’t already open in Studio One.
Does that make any difference with you? Having the song track you’re importing already open.
Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)
