[Solved] Same file plays fine in X3e, but in Platinum I get dropouts and glitches Windows 7 64

have you gone in to preferences and adjusted your buffer size to 500 ?
Something important to leave in your OP would be: is if the project is mostly audio or mostly midi. or both.
are your windows update all up to date ?
that's all I can think of at this time.
 
I suspect buffers all the way seeing how it runs in X3 fine 

its possible (about the line 6) believe it or not, I noticed a huge difference in the way cores were not only distributed but handled in platinum vs. X3 but not at first...this was after several updates. I hope you get to enjoy these benefits as well (im sure you will) we just have to get down to the route of the problem that's all.
 
I noticed when I installed platinum over X3, it didn't keep my settings from X3, I needed to adjust some things. this was a while ago though. I do remember though, in platinum they changed the buffer default rate, si now its best to bump it up to 500. (cant remember if they bumped it down or if just seems to run better on 500 vs. 256.
hang in there man, we will figure it out.

pinguinotuerto
Hi folks,
 
Not too happy at the moment. Just got Platinum and I open a file I've been working on in X3e and I'm getting dropouts and Platinum becomes randomly and temporarily unresponsive. I re-open in X3e and everything is fine. Please bear in mind that I've been using my system for years without issues and X3e is working fine. Core parking is disabled, and my system specs are in my signature. Below are pics of the performance meters for both. Sometimes, the file opens in Platinum without the 1st meter being in the red and plays back better, but still with a few dropouts (playback doesn't stop). I am perplexed and disappointed. 
 
 
 
Performance meters Platinum

 
Performance meters X3e

One thing does jump right out at me ... why is your 1st CPU core pegging red on Platinum and not on X3e???
 
Is there a plugin-in in your old project that is getting greedy on the new Platinum?
 
Maybe try rebuilding the project from a clean template in Platinum and adding the plugins one at a time ...

Reminder:  Noel Borthwick, Cakewalk CTO's first suggestion in the other thread was to delete all plugins.
 
His other suggestion related to disk streaming throughput, which I believe we have eliminated.
 
Please follow up on his first suggestion and then get back to us.

If it turns out to be a 32 bit plugin. That is still not good news for me and Platinum. If it works fine in X3e, one would expect it to work just as well (or even better) in Platinum. I will report back once I test it. Thank you both.

pinguinotuerto
If it turns out to be a 32 bit plugin. That is still not good news for me and Platinum. If it works fine in X3e, one would expect it to work just as well (or even better) in Platinum. I will report back once I test it. Thank you both.

Geek Alert!  I have no idea if this even relates to the topic, but I was curious about how Sonar and Windows allocate CPU cores.  How this may relate to plugins is still a mystery to me.  But I'm willing to learn :-)
 
I realize that you are still on Windows 7.
 

Windows 7:

http://blog.cakewalk.com/how-windows-7-will-effect-your-music-production/
 
Scalability and Distribution of Workloads
In Vista and earlier, on a highly multi threaded system (e.g. SONAR running on an 8 core hyper-threaded Intel Core I7 PC), you have many threads all processing tiny audio buffers at low latency. All these threads are ultimately waiting on the dispatcher lock when it comes time for them to be managed by the Windows scheduler. This global lock becomes a bottleneck in the system and prevents efficient multi-core workload distribution and scalability. This problem gets magnified as you increase the number of cores since they are all gated by a common lock. In Win 7 the kernel team changed the logic in the Windows scheduler to abolish this global dispatcher lock and use per object locks. This effectively removes this age old bottleneck and allows Win 7 to scale better even under workloads of 256 processors.
This change means a lot to applications like SONAR that rely on multithreaded processing of very small workloads. Initial benchmark results have been promising in this regard. SONAR performs more efficiently at low latency on multi core machines.
 
Power-Saving Processing
Windows 7 has a new feature called Core Parking. Core Parking is a power saving optimization that shifts processing load to one or more cores and puts other less busy cores to “sleep”. The objective is to let other cores idle if workload levels allow for it. This optimization had us scratching our heads when we ran a benchmark test on a Quad Core I7 machine. At any point in time we would notice that some cores were idle in task manager. The reason for this turned out to be Core Parking. Core parking can be useful to save battery life while running projects on laptops.
 

Windows 8:

Here is some info on Windows 8 and Sonar:
http://blog.cakewalk.com/windows-8-a-benchmark-for-music-production-applications/
 

Benchmark: SONAR X1 performance in Windows 8 vs Windows 7

SONAR CPU load at low latency

SONAR CPU gains were observed when using Windows 8 for Low latency performance tests. These gains mean you can run bigger loads in Win8 at low latency without audio glitching.
low latency plugins… 15.5% CPU reduction
input monitoring… 8% CPU reduction
high track count… 23% CPU reduction
High bandwidth audio …6.2% CPU reduction 

SONAR multi-core CPU load balancing at low latency

Workloads for cores are more evenly balanced at low latencies on Windows 8. Better balanced core workloads translate to more efficient use of multiple CPU core hardware and thereby better workload scaling for large projects.
low latency plugins… 23% improvement
input monitoring… 31.7% improvement
high track count… 30.6% improvement
High bandwidth audio …17.5% improvement 

Memory usage

A 7.9% reduction in memory use under Win8 was observed when loading a large real world SONAR project (Cori Yarkin project from SONAR sample content) under identical system configuration. Reduced memory load can be observed in most of the tests.

Disk Performance

A 78% improvement under Win8 was observed in disk read/write performance while reading large buffer sizes. Improvements were more moderate at smaller buffer sizes.

 

Windows 10:

Also ran across this article at Cakewalk Blog about Windows 10 enhancements for music and a few lines jumped out at me...
 
http://blog.cakewalk.com/...s-10-music-production/

AUDIO CORE ISOLATION

Drivers and applications can “opt in” to isolate and dedicate low latency audio processing to a single CPU core, which can minimize the effect of DPC latency spiking from networking, Bluetooth, or other DPC spiking processes by preventing interruptions to audio processing. Behind the scenes this is done using interrupt steering and thread affinity. This is an opt-in feature at the WASAPI level where an app has to identify the threads that need to belong to this isolated core.
This feature looks promising, particularly because Microsoft says they’re looking to expand this to multi-core scenarios that relate to DAWs like SONAR.

Thanks abacab, but it's not a Windows issue. Otherwise, Sonar x3e would have the same issue. The issue lies within Platinum. I appreciate your help.

pinguinotuerto
Thanks abacab, but it's not a Windows issue. Otherwise, Sonar x3e would have the same issue. The issue lies within Platinum. I appreciate your help.

I agree that is how it should work.  It may turn out be a Platinum issue, but is Cakewalk really testing all of the code in Platinum (excluding 3rd party plugins) for full backwards compatibility with all previous OS's?
 
My best guess is that they are primarily developing on the Windows 10 platform.  So that could leave a corner case that gets past the testers where it fails to perform as expected on older OS kernels.  Such as the use of a particular (in this case as yet unknown) plug-in?

Worst case scenario, I'll have to stick with X3e on this computer (which I'm very happy with). I bought Platinum because of the "lifetime" updates, which eventually, when I move on to a new system, I'll be able to take advantage of. Plus, I got 3 new Addictive Drums Ad Packs and apparently, a few extra Pro Channel modules, I can use in X3e. So it's not the end of the world.

Glad it's solved. I was watching this thread before diving in.

I believe that pod farm 2.5 has 64 bit .dll's

scottfa
I believe that pod farm 2.5 has 64 bit .dll's

Yes, I thought so. but for some reason it seems like Platinum was only seeing the 32 bit ones although they were in the same folder. I copied the 64 bit ones and created a new folder just for them and removed the old folder from Platinum's scan locations. Scanning now.

Now the scanner is not launching! 

You were right, scook, it was still running in the background. There was an error message popup I hadn't seen for ARX and that's why it was stuck. Anyway, I was wrong about the Line 6 plugin being 32 bit. It was the 64 bit version, but after deleting the old directory from Platinum and scanning the new directory, Platinum's meters don't spike and I don't have dropouts.  I remember having to uninstall all my Line 6 stuff a few months ago and perhaps something became corrupted. So just to push the new release of Platinum, I just opened the project I've been having issues with, left my network adapter on and my browser open, and played drums through AD2 along to the tracks without any dropouts or glitches while the meters were running low all along. Seems to be great now!
 
P.S. Just wrote and sent this message with file playing in the background without a hickup!

scook
Make sure to update the subject line with [Solved] when you are sure the problem is gone.

I want to give it a day or so, but I'm pretty sure it is resolved.