Bad FPS when recording solved!!

[USMChardcharger]

I can not find the post on this forum where I got this but it works. I came across a BATCH file that a user on this forum posted that said would reduce the demand on the CPU this programs uses. I printed out his BATCH file he created at work and when I got home I typed it out and executed it and it worked! (I would love to give the author his/her due but can not find the post again)

(Rig: Windows 7 64bits, i53750, Gefoce GTX760, 16G RAM, 150G SSD (60G for Windows/90G For Games/Programs, 600G HHD(for recorded Vids only), 250G External HHD(for storage only) )

Back story on my issue. I bought ACTION and it worked well for 2 to 3 weeks. My frames sat at or around 30 to 35 FPS when I was recording with ACTION. To me, that was acceptable. Then after that 2 to 3 weeks, during a recording session, my frames would drop to 08-12FPS!!! I would have to F9(stop) to stop recording and hit F9(start) to start again...my frames would go back to normal for a few mins then right back down again. (this happened 100% of the time after the two to three wks)

I tried moving my Action software to a different hard drive(I have an SSD and a regular HDD). I tried moving my vids off both Hard drives to an external to see if the freed up space helped. I reinstalled Action.....nothing helped.(I also tweaked the setting of the software as well...such as recording in 480p and different things like that...as I saw advised by Action in these forums...nothing worked)

I started searching the internet for answers and just like this Forum...no one could answer why or help. Just like this forum...I saw repeatedly were one question was asked or the same canned response to a solution was given and then the post just dried up. Zero solutions anywhere!!

Believe me I searched...this is a 2nd source of income this is effecting!!!

Once I found the post on the BATCH file, I gave it a go and now my FPS are above what I originally was getting when ACTION was working as should in the first few weeks of purchase. I'm now getting anywhere from 45 to 58 FPS!

I do not have the BATCH file on me, but I will get it from the house when I get off work and post it in this TOPIC. I will also post how you create it and execute it, because that was not included by the original author of the code. I had to figure it out since I had never done a BATCH file before.

Another note: The guy from Action that is always responding to these post on this forum said that Action would test the BATCH file and if the results are good, that would include in a patch...or something like that. Well, the post was a year or so ago...so what happened? This BATCH file clearly works. You can see my vids for proof at http://www.youtube.com/channel/UCFH8f2KSJwQ05uHj25J20rA. All 4 vids posted from 06/29 to 06/30 are running the BATCH file.

[USMChardcharger]

I forgot to mention that I get off work between 8PM and 9PM Central Time

[USMChardcharger]

Ok, here it is as promised...

wmic process where name="Action.exe" CALL setpriority 16384
wmic process where name="Action_x64.bin" CALL setpriority 16384
wmic process where name="Action_x86.bin" CALL setpriority 16384

to create the Batch file. Open notebook. it is found by clicking on the windows orb. Then click all files and it is found in the accessories folder.
Open notebook and copy and paste the code into the notebook and click on the SAVE AS option. Once there, name the file anything you want, with "bat" at the end. example...actioncpuchange.bat. This part is important...under the file name, change file type to all. if you do not, it will not become a Batch file.
Your done. find the batch file you created and double click it and execute it. Should see FPS rock. Once I located my batch file...I stored it in my action folder and I made a desktop short cut.
Hope this helps everyone as much as it helped me. I was really starting to get mad. Thank you whoever you are that created this batch file. you deserve all the credit!!

[hard]

Ok, here it is as promised...

wmic process where name="Action.exe" CALL setpriority 16384
wmic process where name="Action_x64.bin" CALL setpriority 16384
wmic process where name="Action_x86.bin" CALL setpriority 16384

to create the Batch file. Open notebook. it is found by clicking on the windows orb. Then click all files and it is found in the accessories folder.
Open notebook and copy and paste the code into the notebook and click on the SAVE AS option. Once there, name the file anything you want, with "bat" at the end. example...actioncpuchange.bat. This part is important...under the file name, change file type to all. if you do not, it will not become a Batch file.
Your done. find the batch file you created and double click it and execute it. Should see FPS rock. Once I located my batch file...I stored it in my action folder and I made a desktop short cut.
Hope this helps everyone as much as it helped me. I was really starting to get mad. Thank you whoever you are that created this batch file. you deserve all the credit!!

which of those 3 would i have to start ?

[radi]

Thanks for sharing your solution. I will keep this thread open for any users questions.

[JChamberlin]

"Should see FPS rock."

What?

I created a batch file called action.bat on my desktop. In it, I have the code you supplied:

Code: Select all

wmic process where name="Action.exe" CALL setpriority 16384
wmic process where name="Action_x64.bin" CALL setpriority 16384
wmic process where name="Action_x86.bin" CALL setpriority 16384

I launched Action.

When I double-click the file to run it, it looks like a DOS window pops up and runs something before immediately closing. It happens so fast that I can't read what it says.

I really don't notice any difference in the FPS.