Skip to main content

Samplitude Pro X6 delay at start

When I open samp and open a song, even the included demo, there is a few second delay before it starts playing. After that, as long as I haven't closed the DAW, every song starts just fine. If I close out of samp and restart it, the same thing happens every time.

Does anyone have a clue what might be up or have this same problem?

I've searched the manual and internet high and low with no success.

Comments

audiokid Sat, 04/30/2022 - 10:45

I'm on Pro X 5 so I can't advise but sounds like it could be a bug.

Whats your install  history of this version? Did this just start happening or did you just upgrade from a previous version?

vibrations1951 Sat, 04/30/2022 - 11:16

Well... it's kind of a long complex mess but basically, I upgraded from Prox5 and as I remember, that had developed the same glitch. 

The short story is I had to basically stop developing my studio build nearly a year ago due to my wife's medical conditions which are finally abating. At that time both of my Computers (Box 1 and Box 2) were failing and after 12 years so it was time to start new.

 

Fortunately Kyle has been a godsend in this process and continuing to get me up and running. My samp was in Box 2 only. I loaded it into box 1 and it is displaying the same issue (along with many others, likely related to the tweaks we are doing on the new rig).

So I was hoping it might be a setting in the DAW I've mistakenly clicked. I've tried to post this on the Magix samp forum but I have not had much luck navigating that forum yet.

Thanks for replying Chris. Maybe Marco or others might have an idea. Maybe I'll have some luck with Magix but I'm not holding my breath. It's not a big deal but I'm a bit fussy about things like this I guess.

Boswell Sun, 05/01/2022 - 05:33

It's sounding like a caching effect.

Have you got a rotating disk drive, a solid-state drive (SSD) or both in this computer? If both, how have you assigned the different drives?

It's important not to use your system drive for audio data.

vibrations1951 Sun, 05/01/2022 - 05:45

All ssd. I'll have to check this out. We got temporarily delayed with installing the planned Raid system so I'm not remembering if I'm using the external HD for projects or just running everything through the system drive.

Thanks for the pointer. I'll get back to you soon.

Boswell Sun, 05/01/2022 - 09:23

If it's all SSD, the seek times are minimal, so the advice about not using the system drive for audio is less important. However, it's still a good idea to separate the drives for the audio and for the system as they will then be independently cached.

vibrations1951 Sun, 05/01/2022 - 09:40

Boswell wrote:

If it's all SSD, the seek times are minimal, so the advice about not using the system drive for audio is less important. However, it's still a good idea to separate the drives for the audio and for the system as they will then be independently cached.

Will do. Thanks Bos,

vibrations1951 Sun, 05/01/2022 - 10:41

My computers are in a machine room about 15 meters cable run away and I use USB/Cat5 powered extenders as follows,

(https://www.avacces…) "USB Extender 60m/196ft , 4x USB2.0 Port, Plug & Play, Supports All Operating Systems ." "High-speed USB2.0 up to 60m/196ft:
Up to 480Mpbs data transmission. Supports all operating systems (Windows, MacOS, Android, Linux); Compatible with USB 1.1 peripheral devices. Certificated by FCC, CE."

Could they somehow be the culprit? It seemed like a compatible and capable unit. I have 4 of them, 1 provides keyboard/mouse for my computer 1, another for my Faderport 16 via USB for the DAW in computer 1. Then another for my Pure 2 ADDA via USB for computer 2 and lastly the one for computer 2 keypad/mouse. Utilizing Samp in both computers I get the same delay. I don't believe I have any of them running off the same USB headers in either computer.

Been doing a considerable amount of tweaks to computer 1 and a few to computer 2 but same issue in both. They are both relatively new and powerful PC's running win 10 pro.

paulears Mon, 05/02/2022 - 04:02

Is it thinking the available ram is a bit limited, so the audio is being loaded into a buffer, before playing? Or hard drives getting a bit fuller than it likes, meaning some extra shuffling around before it tries to play What kind of software monitoring can you access, to see disc activity and processor load?

vibrations1951 Mon, 05/02/2022 - 06:49

Thanks Paulears. Here are the 2 computer specs. I'm doubtful it's a RAM issue but who knows?

Computer 1 has 64GB Ballistix Ram, AMD Ryzen 9 5950x 16 core @3.40 GHz, 64 bit with Zotac NVIDIA GT 710-1GB graphics card. ASRock X570 Creator motherboard. ADDA : 2-Lynx Aurora 16's with AES16e PCIe cards. Additional External HD 

Computer 2 is an HP Desktop M01-F1024 PC with 32GB RAM, AMD Ryzen 7 4700G @3.60GHz and 64 Bit with Radeon Graphics. ADDA: Antelope Pure 2 USB connection, 2 channel. Additional  External HD

Both computers are basically new with vey very little use. Same issue with both computers. The only apparent commonalities are the Samp DAW, power supply form the Equitek iso transformer and the usb extender rigs. And of course this not very experienced operator!

I know Marco has a lot of experience with Samplitude so I'm hoping he sees this. I can't seem to PM him through ROG. My messaging doesn't seem to be working. I know Chris is still trying to get all the bugs out of this new structure. Probably I'm not knowing how to navigate ROG these days. I've been away a while now.

I will try and contact Magix again. My Samp prox6 forum post remains unanswered.  I'll probably end up trying to contact support.

Any other thoughts are very welcome. Thanks again Paulears.

vibrations1951 Mon, 05/02/2022 - 06:58

OOPS! I forgot to mention that I have saved and played the samp demo on the external HD's and I'm running LatencyMon. I'm not very experienced with LatencyMon but it doesn't say there are problems and the highest reading I get is with the "DPC routine execution time.NVIDIA Windows Kernel Mode Driver" which can read read up to 780??? This means little to me.

 

Not sure if I mentioned that this problem occurs with other songs as well that I have recorded.

pcrecord Mon, 05/02/2022 - 10:50

All right, there is a few good probable causes posted here.

What makes me wonder is it's only the first project that you try to play that does this and you are good afteward. 

Here's one Idea, what if the project's drive is on idle ? Computers may stall drives to save energy. 

One test to be made is, before you start Samplitude, go on the project's drive and create an empty folder or a a text file. then do the same on the Vsti drive (if different) then open samp and start to play.. 

If everything runs fine, your solution lies in tweaking the power management settings. 

Let us know ! I'll try to figure out other causes.. ;)

Boswell Tue, 05/03/2022 - 06:35

In your description of your two computers, you say that both have an "Additional  External HD". What physical form do these take, how are they interfaced (including powering), and what do you put on them?

vibrations1951 Tue, 05/03/2022 - 07:19

Both computers have their own 4TB Seagate drive connected by separate usb to each. I utilize separate cat5 extenders for each computer.
I try to keep all projects/songs on these drives.  Some samples as well as drivers, firmware, system back ups and manuals. My DAW programs are on the system c drive.

Boswell Tue, 05/03/2022 - 09:56

If the external USB drives are the ones with the project data on them, then it's likely that they are spinning down if the time between accesses is greater than a certain figure. Once you access them, they will spin up (which may take a few seconds) and stay in that state for whatever the timeout period is set to after the last access.

If you look at the drive settings in Disk Manager, you may find that you can either prevent the spin down, or else set a much longer time before it decides that it's time to drop off.

vibrations1951 Tue, 05/03/2022 - 10:26

I'm a bit over my head because when I open the Device Manager and access the drive and open it I can't find a way to manipulate a settings. Can you advise?

But, I also have an internal A drive on one of my computers which I also stored the projects on. I'm basically using the external for back up in this computer. It is an ssd so no spinning up time and I get the same issue utilizing the songs from there. Does this make sense?

vibrations1951 Tue, 05/03/2022 - 10:31

Further diagnostics.

I have Studio one loaded on computer 1 and Nuendo on computer 2. Projects/songs from those DAWs are stored on the same respective drives as the Samplitude ones yet they don't experience this delay issue.

Boswell Tue, 05/03/2022 - 15:15

This is all good information, apparently ruling some things out.

Samplitude is a large and extensive program with many overlays. It could be that your problem is on the system drive when the Samplitude overlay that has the replay code in it comes to load. But you say it is the same on two different systems, so unless it happened with a particular update of either Samp or the OS, it's hard to see how it could arise.

kmetal Tue, 05/03/2022 - 20:09

To add further information/confusion, I have the same HP as John, also with an upgrade to 32gb of RAM, and as far as I know, samplitude doesn't exhibit the behavior he's experiencing on my system. I can possibly double check later this week, but I don't recall any of this happening over here in samp pro x5

Is it possible that maybe it's a setting in Samplitude? I'm not super familiar with the settings in samp yet.

Would windows event viewer maybe give us insight into anything?

The only time I've experienced delayed playback in a daw is at super high buffer settings or when the computer is starting to sweat. The latter isn't the case for John. Maybe somehow the buffers are wicked high?

vibrations1951 Wed, 05/04/2022 - 02:36

Boswell wrote:

This is all good information, apparently ruling some things out.

Samplitude is a large and extensive program with many overlays. It could be that your problem is on the system drive when the Samplitude overlay that has the replay code in it comes to load. But you say it is the same on two different systems, so unless it happened with a particular update of either Samp or the OS, it's hard to see how it could arise.

Because of the long interruption in my box 1 and box 2 computer install process, some memories are returning to me. I have a vague recollection of my upgrade to samp 6 and that may have been when this started happening. I'm not sure if I had this issue before this with the previous Box 2 computer or samp 5.

So much going on about then that I let it go at the time. Upon returning to the new installs many months later now, I just loaded samp into my box 1 as well from my Magix account.

Could I have a faulty license with a bug or some such? I'm awaiting a second response to my Magix support ticket. 

audiokid Wed, 05/04/2022 - 16:43

When you start the session that has this problem, are you loading or importing it in a personal template. 
Im wondering if this would still do this if you opened up a default session and hit play. 
 

This is starting to point to something you saved within the template that has a few bits ahead of start. 
 

thoughts?

audiokid Wed, 05/04/2022 - 16:51

I suspect you’ve been debating this as well…  
 

Trying the clean install and then re setup your system. erk… 🤔 major pain but it may be the simpler and best way to resolve things. 

x

Register

Your recently read content