![]() ![]() Not trying to chime in like I know what I’m talking about as I really don’t but I know what I see in the cpu isuage window, I think your agreeing that live cannot utilize multi core properly as bitwig is, because even if you did the same test with live with no side chaining or inner track dependency as the bitwig test your not gonna fill up past half of the first slot on a core, I’ve never in any situation seen live let me fill up past half the first slot on a core and just barely give me an 1/8th or 1/16th and most times nothing on the second slot in cpu usage window, the OP stated that he’s getting 90 to 95 percent full in the cpu usage window, something I’ve never seen live be able to even come close to doing, without getting into terminology and things I don’t know much about that’s the simplest way I can explain what the difference is. Mon 6:42 pm Multi-core CPU handling FAQ – Ableton: ![]() Any dependant set of tracks will use one thread each. If two tracks are "chained" by routings, for instance by a side-chain routing, a track being fed to a return track or any tracks being fed into each-other, they are considered dependent tracks and count as one signal path. In tracks where instrument or effect racks are used, with multiple chains in parallel, Live may use one thread per chain depending on how CPU-intensive each chain may be. A signal path is a single chain of audio flow. Live uses one thread to process a signal path. How many threads are used per Live track? In Live 9, if your computer only has a single-core processor, hyper-threading is automatically disabled in order to preserve the correct order of the threads to be processed. Hyper-threading is enabled by default in Live for computers with multi-core processors. Hyper-threading is a feature of certain processors which allows them to further subdivide cores so that two concurrent threads can be handled per core. Sorry about this stupid question but maybe somebody can shed some light, so i demo'd Bitwig yesterday and only had a sec to tinker with it but I noticed right away that loading the same nexus 3 patch and hitting the same note at default came in quite a bit lower than Ableton, I eventually gain stage everything lower and properly regardless just wondering why Bitwig at default would be -16 db and Ableton around - 7db? Loaded a new blank project and it doesn't seems like there's anything on the track or buss effecting the level but will have to look deeper, like I said I eventually stage everything properly but just found it a lil strange that the same plug-in comes in 9 db lower at default I was always told this is how DAW's work and get over it haha what a joke, in my cpu window only the first slot of each core is filled half way and the second slot maybe an 1/8 before live takes a crap, if Bitwig has figured out to utilize 90 to 95 percent of cpu usage as shown in the cpu usage window I'm in Awe! Guess what Live does? it uses only one of the two possible threads a core can use, in Activity Monitor every other thread is empty, and each CPU is only at about half filled before Live seems to bog down. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |