- #Pro tools 12.7 playback wrong speed how to#
- #Pro tools 12.7 playback wrong speed Patch#
- #Pro tools 12.7 playback wrong speed pro#
- #Pro tools 12.7 playback wrong speed Pc#
- #Pro tools 12.7 playback wrong speed mac#
Interface is a Presonus Studio 68 at 48 kHz.
#Pro tools 12.7 playback wrong speed pro#
I run Native in Studio One Pro 3.51 with an i7-7700 Quadcore 2,8 GHz and 32 GB.
#Pro tools 12.7 playback wrong speed mac#
I don't have a mac to test the Mac link below but it seems to follow some similar steps to possibly help So I would try to double check your power/processing settings on your PC/Mac and see if it helps at all.
![pro tools 12.7 playback wrong speed pro tools 12.7 playback wrong speed](https://venturebeat.com/wp-content/uploads/2018/06/Farpoint_20180606222327.jpg)
After about an hour of trouble shooting I realized that I had my computer set to POWER SAVER power plan on my device Instead of the settings that I set up to UAD recommendations. The very first time I tried to open up helix native(single instance on one track) all I got was a garbled mess of noise and my processor said it was using 50-80% power. Processor says its running at 40-50%, Reaper says about 5% each instance I'm running on a Lenovo Yoga X1 laptop (i7 7600U, 16GB RAM) and apollo 8p using reaper I am able to record 4-5 different tracks all with a random different preset instance of helix native on each track before I hit the point where it pops/crackles. My band and I collaborate in pro tools 12 so trying to get everyone on another platform just so my workflow can improve is not doable. Logic runs great at 32! I don't use logic so this is a problem. I am using PT 12 and cannot go below 128. Everyone else is using logic or something else. I have only had one person comment they weren't having any issues in Pro tools.
![pro tools 12.7 playback wrong speed pro tools 12.7 playback wrong speed](https://i.ytimg.com/vi/4PrjrbRukbU/maxresdefault.jpg)
I have a post going on the helix user group on Facebook and it seems most people come back with no issues using other software. In PT12 at 256 samples, it feels almost unplayable for me with input monitoring (using a pretty fast Thunderbolt interface too), GarageBand, not so much.Īll this considered (as well as being the only track and only plugin being used on either DAW), maybe this is a Pro Tools specific bug/problem? Any other PT users able to comment? To compare, I tried using with GarageBand (latest version) as don't have Logic X or any other DAW, whilst I don't know the buffer size of GarageBand uses and seems theres no way to check or change, it feels okay to play (and no clicks or pops). I'm using it with Pro Tools 12 on a fairly moderately spec'd Mac - i5 processor, (24GB RAM for what it's worth) and can only use with a 256 sample buffer! Any thing lower has terrible clicks and pops, with the CPU maxing out easily.
#Pro tools 12.7 playback wrong speed Patch#
So I don’t think the cpu is that bad, I am sure they could improve it a bit but it isn’t causing this machine any problems with that patch.ĭoes anyone have a problem patch from the factory bank I could test? The maximum tracks I could get at 1024 buffer was 45 tracks with 1017% cpu. Logic Pro 1 audio track record enabled 5.4%Īdd helix with default patch Factory 1/01AĨ tracks with default 01A patch, record enabled on all tracksĪt 32 buffer (4 ms in to out) I get no crackles at all.įor playback test I set the buffer to 128 (8.8 ms in to out) and duplicated the tracks until I heard crackles, here it managed 37 tracks with cpu of 900%
#Pro tools 12.7 playback wrong speed Pc#
So 50% cpu on a 4 core mac would read as 6.25% on a pc and on a 12 core mac would read 2% on a pc. Note for pc owners: cpu readings on macs are % of a logical core, so this machine has 24 logical cores and a max cpu reading of 2400% Logic pro x 12 core mac pro with a Apollo Duo interface.
#Pro tools 12.7 playback wrong speed how to#
I would need to figure out how to resolve this in the next two weeks before I'd be confident purchasing after the trial is up. I LOVE the plugin and I'm excited about it, but it's not really usable on a regular basis currently. After I disabled all the Native plugins on the tracks, the problem went away. I even tried to just record without the monitor, just going by what I could hear acoustically from the electric guitar, but it kept freezing up and giving me an error that the audio had dropped out while recording.
![pro tools 12.7 playback wrong speed pro tools 12.7 playback wrong speed](https://images.squarespace-cdn.com/content/v1/54d696e5e4b05ca7b54cff5c/1533044299506-Y5SX62HDXU42W5ZP3PBW/PT2018.7-Multi-Select-GIF1-optimized.gif)
I could see all the meters on the tracks working, so sound was going through, but the only way to hear it through the monitors was to disable the "monitor" button on that track.which makes it hard to record because I can't hear any sound from the track I'm recording.
![pro tools 12.7 playback wrong speed pro tools 12.7 playback wrong speed](https://i.ytimg.com/vi/d2a3kTqM0y8/maxresdefault.jpg)
When I enabled a track to record with Native as a plugin, ALL the sound dropped out after I hit the monitor button on that track. After installing Native I immediately got clicks and pops and sound dropping out. I've not had any performance issues since this computer was built a few months ago. I'm using an 8 core 4Ghz processor and 32G of RAM. I'm also having performance issues after installing Native.