I'm using PT2022 B3 and found that when I render MIDI tracks to a WAV file, the CPU overloads and I get instrument drop-outs. I've tried files that previously rendered OK and they also cause an overload. I tried the same files in RealBand 2023 and, again an overload.

I then tried the original offending MIDI file on a laptop with PT2020 and, while the CPU didn't overload, there were instrument drop-outs, even though the MIDI file played correctly on PT.

I haven't exceeded the polyphony limits and I've checked CC64 for errors. My audio drivers are up-to-date and I'm using a Focusrite Scarlett 4i4 3rd gen interface.

Any ideas what is causing the problem? I need to resolve this as I have a number of backing tracks that are waiting to be finalised.

Any advice would be appreciated.

martin/stella.
There are many possible reasons for a pc based music production rig to hiccup.

1.using a pc that has never been optimised for music production.
and letting gunk build up. see on the pg forums/souncard manufacturers sites/the net n' you tube.
google 'optimise a pc for music production'.

2.using a pc thats old or underpowered and its not capable of doing the trak n' plug in counts needed by the user.

3.lots of people get problems because some plug ins need a LOT of pc resources so problems ensue.
thus i recommend that before using a plug in one tests it out first as to pc resource usage so one isnt surprised.

4.sometimes if doing recording using same old drive that windows resides on, win can interrupt to do its own thing thus a hiccup.

maybe you already know the above, but i dont know you so thought i should mention it just in case.


having stated the above and not knowing the details of your rig perhaps you might post details of your pc please. processor ? ssd or not ?
the virtual instrument your using with midi ? etc etc.
have you measured the vi resource useage ?

the above assumes there is no bug in the software being used.


more details of your rig would really help otherwise one is flying blind trying to help.


happiness and a great 2023.


om

ps i'm from uk n' had loadsa fun in your area when i was young n' crazy lol.

Does it happen if you render an individual track to wave, or just the when you render all tracks to wave?
What is the synth you are using to render the song through?

I know I had to futz around a bit to get my Focusrite devices to work as expected in RB/PT, but that was mostly making sure I had matching bitrates and a good USB cable.
The Focusrite supplied USB cabled worked as expected but when I tried a longer one I had on hand it choked in unexpected ways..
Once I bought a good cable things started behaving as expected.
I think I splurged a whole $15 on the new cable. <grin>
It was a bugger to solve at first, almost returned the unit(s)

Thanks for your replies, guys. In answer to your questions (and I should have included these stats originally – sorry ☹):-
PC is old (2012 Chillblast custom build Music Production PC) but still runs well, especially after the SSD and RAM upgrades.
Processor: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz 3.40 GHz (Quad core)
RAM: 16GB
System: Windows 10 Home 64-bit, x64 based processor
PowerTracks 22 - Build 3
System Disc – 1TB SSD
Data Disc – 2TB SSD
Focusrite USB ASIO
VST – PG Music Coyote WT/ DXi/VSTi
I sometimes use a limited number of SF2’s via Coolsoft Virtual Synth, but not when I want to render the tracks to WAV.

I don’t understand what you mean by vi resources. I haven’t used any additional plugins if that’s what you mean, only the virtual synth.

I’m currently using the supplied USB cable for the Focusrite.

I rendered the piano track containing CC64 events and the CPU load went up to 99.7%. I then rendered another piano track with no CC64 events and, again, the CPU load was 99.7%.

I can’t find a log reporting the error. I have checked CPU temperatures and they seem to be fine. I did notice that only core#1 load went to maximum.

One problem solved though. Part of the cause for instrument dropout was that I was using Windows Media Player 32-bit for playback. This also started up WUDFHost, which together used up all CPU capacity even before it started to play the file. I switched to Groove Music player and it sounded much better with minimal dropout. Looks like a combase.dll problem, which I can try to fix, although I’ll stay with Groove Player.

Gouge

sorry i missed your reply 'derby'.
(your footie team is doing better.)

looking at your pc specs they are definitely good.

heres some ideas.

1. are there any other high cpu useage tasks showing in
win task mgr when your running powertraks ??

2. does the cpu useage drop from 99 % when running no plug ins ? (vi = virtual instr.) in powertraks ??

3, this pc...is it ALSO running the net while ptw running ?? if so try not running the net.
i never run the net on a recording pc rig.

4. how long does this pc take to boot up from cold ?
(i'm just a few secs till desktop appears.)

5. have you ever run latency mon ? which will tell you
if there are problems with your rig for audio production ?

https://www.resplendence.com/latencymon

just some ideas.

happiness.

om

Sorry I haven't responded sooner - I'm breaking in a new PC and only one monitor so having to switch regularly.

No other high usage tasks in Task Mgr.

I don't use any plug-ins other than the VI. I have tried it without Coyote and there is still a high cpu.

Yes I am connected to the net when running ptw, but no issue on Task Mgr.

Very quick bootup - maybe 10 -15 secs until password screen.

I haven't run latency mon recently. I can try it.

Thanks for the suggestions. I'll get back to you as soon as I can.

Derby.

i'm a tad confused ..is the high cpu usage with your new or with old pc ??

please be patient ..its sorta a checklist i go thru'. this is odd.

please post back….

1..does taking the pc off the net realise the high cpu use going away ?
ie disabling the net/av etc.

2..what does latency mon say ?? any warnings ?? all green ?

3..in realband in action>> test audio performance. please tell me what the result of running that says. 150 traks plus ?

4..how long does realband take to display from clicking on rb icon ?AND how long does windows take to shut down (not sleeping.) ? ie hard shutdown.
here its about 3 secs max for both.

5..in rb what drivers are you using ? asio ? or win driver model wdm ?
what latency figures for your sound interface are reported ? and what sampling rate//bit depth used ?? 44.1//16 ??
have you tried if not already tested... setting win + sound interface + rb/ptw ALL to 44.1//16 ??

i might have to ask you next for pics to be posted of…
your win audio settings. rec n' playback. including advanced.your sound interface settings // sound control panel.and your rb/ptw driver settings.

i'm curious in one final check...in biab when you generate a trak eg real trak guitar does this take a looong time ?? how long. ??


best.

om

You might try some housekeeping which is always a good idea from time to time.

1. In the Startup screen of Task Manager, disable all apps that you know you don't need on start up.

2. Do a defrag on all drives, then analyze them after to ensure they are in fact defragged.

3. When producing music, shut down all programs you don't need.

--Thump

Hi guys.
I'm really sorry I haven't sent an update on the problem. I was busy setting up my new Win11 PC and got so involved I forgot to send an update.
The problem was with my old PC. However, when I set up my new PC, it asked how many cores I wanted to use for PT 2022. That sent a warning signal to me, so I checked my old PC and it was only using one core of the CPU (hence the high temperature). I tried it with all CPU cores active and the problem went away. So problem solved. I was going to get a new PC anyway, but not quite this soon.

Thanks for all your responses and, once again, I'm sorry that I left the thread hanging for so long.

Interesting. I've never encounted Windows asking about how many cores to use. Does the new PC have AMD chip or an Intel chip? Thanks for the update.

I have never seen that either. I am very interested in how you did this part -

My new PC has a 13th Gen Intel(R) Core(TM) i7-13700K 3.40 GHz processor. My old PC was also an Intel, I think it was a Z22 chipset, but I no longer have the PC. Now you have me wondering whether my memory is failing me!!! It was during the setup period and I was re-installing all my music programs on my new PC. It might have been during the re-install of Ableton. I had the same problem with Ableton on my old PC so it could have been Ableton that asked for the number of cores to be used. I know this is a vague response. I'll look into it further to try to get more information on what I did. All I know is, it worked.

I've also never seen Windows "ask" which cores to use, however it is possible to "tell" Windows which cores to use - you can do this in the Task Manager under the Details tab, by right clicking on a process and choosing Set Affinity

https://www.thewindowsclub.com/processor-affinity-windows

Keep in mind that this would be considered a rather advanced thing to do, with potential performance consequences, but it can be handy for limiting a program that's "hogging" the CPU, or occasionally for very old programs that don't understand multiple processors.