Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Capturing and Editing Video > Avisynth Development

Reply
 
Thread Tools Search this Thread Display Modes
Old 18th June 2018, 17:40   #161  |  Link
Aktan
Registered User
 
Join Date: Feb 2002
Posts: 303
Quote:
Originally Posted by Stereodude View Post
I know it can be changed after starting, but x265 spawns more threads to start with because it sees all the logical processors in the system. Restricting it after it starts doesn't fix that. If you start a program correctly with restricted affinity the program only detects those cores allocated to it and spawns less threads as a result. I did this with x264 regularly. I also do it with handbrake.
If it's anything like x264, you can just set the threads param yourself...
Aktan is offline   Reply With Quote
Old 18th June 2018, 19:55   #162  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,429
Good point, does "--pools" or "--numa-pools" not work? It doesn't seem to let you restrict to specific cores, only specific NUMA nodes.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 19th June 2018, 20:00   #163  |  Link
Stereodude
Registered User
 
Join Date: Dec 2002
Location: Region 0
Posts: 1,436
Quote:
Originally Posted by qyot27 View Post
The most important question here is 'why are you using avs2pipemod in the first place'? The answer to that will change the solution.

If you're using it simply as a piping tool to get y4m from AviSynth to x265, but both are still 32-bit (or 64-bit), then the solution is to use either libx265 through FFmpeg, or the x265-Yuuki patchset from msg7086 (assuming the build of x265-Yuuki has its LAVF input enabled, and was built against an FFmpeg configured with --enable-avisynth). In those cases, there's no piping, so the affinity should take without any issue.

If you're using it to get 32-bit AviSynth output to input 64-bit x265, then you could try to manually pipe, but insert the affinity command after the pipe, at the beginning of the x265 command. That is, if it allows you to do so.
I'm using it to get the avisynth output into x265 since it can't accept an .avs natively. I'm not crossing 32-bit to 64-bit or anything like that.

Quote:
Originally Posted by Asmodian View Post
Good point, does "--pools" or "--numa-pools" not work? It doesn't seem to let you restrict to specific cores, only specific NUMA nodes.
I didn't try them. I wanted to avoid having to handle all that manually.
Stereodude is offline   Reply With Quote
Old 29th November 2024, 07:14   #164  |  Link
Kurt.noise
Registered User
 
Join Date: Nov 2022
Location: Aix en Provence, France
Posts: 60
avs2pipemod 1.1.2 released

For those who interested, I updated avs2pipemod in order to include channelmask information from latest avisynth+.

https://github.com/Kurtnoise-zeus/avs2pipemod/releases
Kurt.noise is offline   Reply With Quote
Old 29th November 2024, 15:59   #165  |  Link
tebasuna51
Moderator
 
tebasuna51's Avatar
 
Join Date: Feb 2005
Location: Spain
Posts: 7,127
Thanks Kurt, I'll test it.

[EDIT]Works fine for me thanks
__________________
BeHappy, AviSynth audio transcoder.

Last edited by tebasuna51; 8th December 2024 at 12:08.
tebasuna51 is offline   Reply With Quote
Reply

Tags
avs2pipe

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 17:23.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.