Okay so as above - i'm doing some "indirect" trial testing of this exact version of PT 12.5.0.395 - but just to be exact - the same problem occured on PT 12.3.1.88512 and PT 10.3.9

First off - i only just found out which setting in preferences was causing the issue im going to describe. I am not yet sure that this is the only setting responsible for this but that's what happens:

After installing and checking the issue with every single version - i encountered this. When you go to:
Setup --> Preferences --> Editing --> and here at the bottom we see undo levels - maximal value is 64. And i selected 64 because my ryzen damn 7 2700x should easily be able to handle this (well, at least i thaught so), and after i did so i went to midi editor (either window editor or directly on-playlist-one).

After i started putting notes on piano roll - each next note caused IMMENSE fps drops when holding/placing/stretching/editing a note/a group of notes. Basically the more UNDO steps got written into memory the bigger were the fps drops/lags when editing any note - and yes this issue corresponds ONLY to editing notes.

With mod wheel automation graph hand painting UNDOs work smoothly for example.
I would really appreciate some professional IT specialist help as i'm fed up with fl studio automation clips. Pro Tools is just WAY more convenient for learning and playing around with huge orchestral templates what i exactly do.

How i did try to fix the issue (none of those worked):
- Turn off automatic CPU overclocking (aka turbo boost) in bios
- Updated NVIDIA 1050ti GPU drivers to latest version

I'm running windows 10 home premium 64bit,
motherboard: MSI X470 Gaming Plus
CPU: AMD Ryzen 7 2700x (8 x 3.7 - 4.5 GHz)
Ram: 2x8GB 3000 MHz
GPU: Nvidia 1050ti (4gb of memory)

 

Last edited by a moderator: Sep 29, 2018

Oh SHIT! I just noticed i created this thread in wrong forum section. Moderators please move this to proper section if you can.

 

Sorry, man, I have 12.8 (legit) for the Mac, and it's over a year old. You may be experiencing a bug (PT is still a bit buggy when it comes to MIDI) that may or may not have been fixed a long time ago. Your best bet is to do what I do: find a DAW with great MIDI to compose in, then export the finished MIDI file to PT 12 and record the audio that way. Or find a more recent version of PT.

 

Thank you for info! Okay so we have option 1: a bug unfixable by a non-coder. Let's wait for other suggestions, as im really curious and a bit pissed off by that software.

PS: Honestly - do you think it's a universal PT bug amog windows 10? I heard some people had it too but it is weird that it occurs with 3 different versions (cracked by three different saviors)

 

This may be of some help:
http://avid.force.com/pkb/articles/en_US/Troubleshooting/Windows-10-Guide

https://support.focusrite.com/hc/en-gb/sections/201616569-PC-Optimisation

http://www.blackviper.com/

 

What I'm saying is, I think it might be an issue with PT 12.5 itself (I haven't had any MIDI issues with 12.8), and that it might have been fixed in the many subsequent versions that have been released since 12.5 came out. There really aren't even numbered versions anymore; they went to a dated version system like Waves has (the latest version is "2018.7").

Here's a much, much easier solution that may solve your problems without scouring the Internet for a new k'd version: simply go to Avid's site, open an account and download Pro Tools First for free. Here's a chart of what your limits with PT First are compared to regular Pro Tools or Pro Tools HD (now "Ultimate").

 

Last edited: Sep 29, 2018

Did you go through all Avid recommended optimisations for PT? > http://avid.force.com/pkb/articles/en_US/troubleshooting/en349411?popup=true
The fact that not only PT12 but also PT10 gives the same error makes me think your problem is system related (the way the system is setup), or even caused by a piece or version of hard-or software in your setup.

 

I've moved your thread to "Pro Tool" section.

And I have deleted all links from it. You can speak about it, but links to warez are not allowed either.
I strongly recommend that you read our rules (click) so you can take advantage of this fantastic place.

 

@Iggy Thanks for informing me about that - i didn't know there is a free version. But there is a big "BUT" here - in the first post i wrote "playing around with huge orchestral templates what i exactly do"
--> and here we have like a pathethic number of max audio/midi/instrument tracks - 16, damn i need 16 tracks for different cello articulations only- not to mention other instruments. So turns out that even with the - like those "pro-fessionals" called it - Pro Tools Ultimate HDX Native HD Hyper Super Quantum Boosted Super Nano DAW, you will be only able to have maximum 512 midi tracks... Well, that's A L I T T L E too few as for a 1000$ + software haha :D.

@quadcore64 @boomoperator yes i did all of the optimisation procedures now - didn't help

 

Yeah, that's the downside; PT First is extremely limited. For that matter, regular PT is pretty limited for track counts/MIDI tracks. The only reason I suggested PT First is, it might help you see whether or not your issues are related to 12.5, your setup or a buggy k.

 

Yea, well that might be worth testing tho. I'll check that out today. In the meantime let's leave this thread open for Pro-Coders to maybe look at.

 

The problem with Pro Tools First disappeared. So... problem remains unsolved. But at least i know that it's a software-side bug.

 

For heavy orchestration Pro Tools should work. Another DAW option could be Digital Performer from MOTU or, Reaper.
Reaper offers really heavy track count, custom MIDI setup through ready made scripts or, ones you create.

Synthetic Orchestra BSRO Articulate

Also make sure you have the latest Windows 10 Update. Last I saw was August while setting up a Surface Book for my son running Pro Tools 12.5. Working perfectly...