After putting in my support request to Magix, they finally got back to me after
several weeks with a very helpful reply that I thought might be of interest to
others on this list. I am just getting around to working through this (and
other e-mail) after returning from our recent trip around Colorado.
Anyway, this relates to the drop out problems I was seeing with the
Independence instruments. There were three main points of advice that Magix
gives in their reply (copied below my signature below). I’ll summarize the
major points here if you don’t want to read through the whole thing and think
you might need to tune up your system:
1. They suggested changing to the “High Performance” Power Plan in Windows
and making a number of modifications.
2. They also had a number of very specific suggestions about configuring
USB 3.0 devices. Since I’m using a firewire device (the Saffire Pro), this
isn’t my problem, but these suggestions might help others.
3. They also suggested turning off “Core Parking”. This is a feature that
turns off cores that aren’t being used in the CPU when there isn’t a high load
on the system. Apparently there can be a lag time when turning on these cores
when the demand gets high.
Anyway, read the note below if you want more details on how to tweak your
system if you are having similar problems. I still need to get a chance to
test some of this out in Samplitude. Hopefully in the next few days (although
our daughter will be visiting then so it might have to wait a bit longer
still!).
--Pete
From: MAGIX Pro Support [mailto:prosupport@xxxxxxxxx] ;
Sent: Monday, June 4, 2018 7:13 AM
To: ptorpey00@xxxxxxxxx
Subject: Re: [Ticket#2018050417008804] Ihre Anfrage an den Kundendienst
Dear Pete,
Thank you for your message.
experiencing audio dropouts and/or glitches when using instruments from the
Independence Pro Library and wonder if this is a known problem or if you have
any suggestions (or an update) for fixing this. To verify the problem and
narrow it down to Independence Instruements, here is the experiments I ran: 1.
I created a new project in Sampllitude with one of the FM Rhodes instruments
from the Independence Library on one track and Ivory Piano on a second track in
the same project. 2. On the track containing the Independence instrument I
played and held down a triad of
Please clean up your system from any traces of Independence. Use Control
Panel/Programs and Features first.
Also don't miss remains in following folders
- c:\Users\All Users\MAGIX\Common\Packages\
- c:\Users\All Users\MAGIX\Independence Libraries\bundles\
- c:\Program Files (x86)\Common Files\MAGIX Services\Independence Libraries\
- c:\ProgramData\MAGIX\Independence Libraries\bundles\
- c:\Users\All Users\MAGIX\Independence Libraries\libraries\
- c:\ProgramData\MAGIX\Independence Libraries\libraries\
- c:\Users\[username]\AppData\Roaming\MAGIX\Independence\Preferences\
- c:\Users\[username]\AppData\Local\MAGIX\Independence\Preferences\
- c:\Users\[username]\AppData\Local\Temp
Then try the installation again.
experiencing audio dropouts and/or glitches when using instruments from the
Independence Pro Library and wonder if this is a known problem or if you have
any suggestions (or an update) for fixing this. To verify the problem and
narrow it down to Independence Instruements, here is the experiments I ran: 1.
I created a new project in Sampllitude with one of the FM Rhodes instruments
from the Independence Library on one track and Ivory Piano on a second track in
the same project. 2. On the track containing the Independence instrument I
played and held down a triad of
The USB environment must be right!
1.
To make sure everything runs smoothly, you have to pay attention in
advance: It is a USB 2.0 interface, which in principle claims a USB 2.0
controller on its own due to the high data rate required. No
matter how many ports the computer makes available, if only an extended
USB host is displayed in the Device Manager, you should not use any
other 2.0 devices (extra hard drive etc.) parallel to the USB
AudioInterface. Where the 1.1 devices are connected (for example, the
codemeter), one must also work out, so that the bus is not braked. Therefore,
our tip is: Spend your computer for a few euros a second USB 2.0
controller (as a PCI or PCMCIA card), where then only the USB audio
interface is operated. Then
you have to pay attention to high-quality cables, the included USB
cables are often very short, in most cases, you will want to have the
USB device near the mixer, but for me a cheap Thomann USB extension made
everything go awry, a solid one , long USB cable did but then his service. In
addition, it is worth charging the line inputs symmetrically when the
outputs of the mixer or other sound sources give that, the investment in
appropriate cable is worthwhile. When everything is properly wired and
installed, working with the USB audio device is pure joy.
2. You may not use a USB 3 interface! Some older audio interfaces have problems
with it.
experiencing audio dropouts and/or glitches when using instruments from the
Independence Pro Library and wonder if this is a known problem or if you have
any suggestions (or an update) for fixing this. To verify the problem and
narrow it down to Independence Instruements, here is the experiments I ran: 1.
I created a new project in Sampllitude with one of the FM Rhodes instruments
from the Independence Library on one track and Ivory Piano on a second track in
the same project. 2. On the track containing the Independence instrument I
played and held down a triad of
Turn off Core Parking Instructions Registry .
Regedit open
Search key: 0cc5b647-c1df-4637-891a-dec35c318583
Subkey ValueMax Set ValueMax to 0 **
Repeat this procedure in all keys with the identifier
0cc5b647-c1df-4637-891a-dec35c318583
Restart the computer
Weblinks:
https://helpdesk.flexradio.com/hc/en-us/articles/202118758-Win7-Core-Parking-Optimization-for-Intel-i7-CPUs
http://www.coderbag.com/Programming-C/Disable-CPU-Core-Parking-Utility
Core Parking
Core Parking is a sleep state, C6, supported by most modern processors and
Operating Systems.
Core Parking dynamically disables CPU cores in an effort to conserve power when
idle.
Disabled cores are re-enabled as the CPU load increases once again.
This technology is very similar to frequency scaling, in that it seeks to
throttle the CPU when idle.
he problem is that Window’s default power profiles are configured far too
aggressively when it comes to core parking, especially on workstations. Their
interest was in conserving energy, even if this meant marginally decreasing
performance.
A number of complex parameters control when a core should be parked, and
Microsoft tuned heavily
towards power savings. BTW, to deal with this issue, Intel changed Skylake to
manage it’s own CPU core parking. Read more here…
<https://bitsum.com/product-update/intels-speed-shift-validates-parkcontrol-and-process-lasso/>
The core parking settings in Windows are implemented as parameters of power
plans (aka power profiles). That means you can, for example, disable core
parking for the High Performance power plan, but
leave it enabled for other plans. And that is exactly the desired tweak for
most users: disable parking only for high performance power plans.
Efficacy
Empirical evidence shows that disabling core parking can make a real difference
in system performance. There are many factors that will determine how
efficacious it will be for any given system, including the
CPU type, application load, and user behavior. However, we find that Windows is
often over-aggressive in its core parking, resulting in excess latency as cores
are unparked to accommodate bursting loads (the
most common type of CPU load).
In our tests, we’ve found AMD processors benefit most from disabling core
parking. This is perhaps due to the dramatic difference in the way AMD
processors share (hardware) computational resources between logical
cores. Microsoft optimized for Intel’s Hyper-Threading, which has much less
capable secondary cores. AMD’s secondary logical cores are near full CPUs.
--
With kind regards
Ed Myer
*****************************************************************
* Please make sure to include your original correspondence and *
* leave the e-mail's subject line unchanged when replying. It's *
* necessary to properly assign your message and process it more *
* quickly and effectively. *
*****************************************************************
MAGIX Software GmbH
Ed Myer
Supportmanager
Postfach 500109
01067 Dresden - Germany
Support Hotline: Tel: +1 775 562 0528 (Mon-Fri, 10am-4pm EST)
http://www.samplitude.com
Managing Directors: Klaus Schmidt, Jörg Stüber
Commercial Register: Berlin Charlottenburg, HRB 127205
04.05.2018 23:23 - ptorpey00@xxxxxxxxx <mailto:ptorpey00@xxxxxxxxx> schrieb:
[METADATA_START]
Interview: Do you wish to contact Technical Support? -> Music -> My enquiry is
about Music Studio
Processor:
- i770
Operating system:
- Windows 10 64-bit
Memory:
- 16 GB
Sound Card:
- Saffire Pro 40
Graphics Card:
- Intel HD Graphics 630
Browser:
- Chrome
[METADATA_END]
I have been experiencing audio dropouts and/or glitches when using instruments
from the Independence Pro Library and wonder if this is a known problem or if
you
have any suggestions (or an update) for fixing this.
To verify the problem and narrow it down to Independence Instruements, here is
the
experiments I ran:
1. I created a new project in Sampllitude with one of the FM Rhodes instruments
from the Independence Library on one track and Ivory Piano on a second track in
the same project.
2. On the track containing the Independence instrument I played and held down a
triad of notes (e.g., F-A-C) and held the chord for a measure or so or until the
sound had nearly A(but not quite) decayed. I then hit the triad of notes and
held
it again. I kept repeating this until I heard an audio dropout or stutter.
3. When playing the Independence instrument I would generally hear a dropout or
stutter after about 25-50 measures.
4. I then repeated the experiment by doing the same thing on the track with the
Ivory Piano – i.e., I hit and held a triad of notes, hit the triad again after
the
sound had nearly decayed, and repeated the process.
5. When playing the Ivory Piano I never heard an audio dropout, stutter, or
glitch and could play rock solid for over 100 measures.
6. I also repeated the above experiment by substituting one of the instruments
from Dimension Pro 64-bit (which came with Sonar Producer) for the Ivory Piano
and
using various other pianos from the Independence Library. Again, within the
same
project, the instruments from Independence always caused an audio dropout within
about 25-50 bars while the instruments from Dimension Pro were rock solid and I
never heard an audio dropout or glitch.
I’ve also varied the buffer settings in Samplitude from min to max, varied the
ASIO buffer settings for my Saffire Pro 40 fire-wire connected audio device,
turned off as many background processes on my PC as I could and observed that
none
of the changes made any difference to the frequency or nature of the audio
dropouts observed with the Independence instruments.
My computer is a very new Windows 10 64-bit system with an i770 CPU, 16 GB of
RAM,
and an SSD, so I don’t think that is the problem. I also did a separate
experiment in which I ran the Independence instruments from an ordinary hard
drive
on my system and then copied the Independence Library to my SSD, but that did
not
make any difference to the frequency or nature of the problem with the
Independence instruments.
I have the latest build of Samplitude X3 Pro.
Thanks for any suggestions (or a fix!).
--Pete
[METADATA_START]
Weitere registrierte Produkte:
Sound Forge Pro 11.0
Celemony Melodyne Essential
Samplitude Pro X3 Suite
Birdline Skins
[METADATA_END]
