Hi folks,
I am experimenting with alternative tunings. I have a sequencer on channel 1 sending notes to a round robin mapper to 15 racks. Each rack forces the note to a new MIDI channel (2 to 15), microtunes the note using pitchbend, and plays the note using MUX FM bell preset with a long release. I need separate MIDI channels so each can have its own pitchbend.
Even with MuLab set to 4 threads at 44.1khz, this maxes out my 4 processor i5 almost immediately. I'm guessing I should rely instead on samples rather than FM synthesis. Or, perhaps there are other solutions (besides buying a faster computer) ?
-D. Vyd
Maxing CPU with 15 FM MUX bells
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
Reducing the number of FM bells from 15 to 4 does not solve the problem. Eventually, the CPU overloads. I think there is another issue. I've turned off all the other racks and their inner components. I've attached a screenshot and would welcome anyone to help troubleshoot. Perhaps the long sustains on the bells causing a problem?
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
I'm able to use eight racks of Kontakt sampler tuned gongs with my processor running at about 50%. So, something with the FM bell seems especially taxing--perhaps just the difference between synthesis and sample playback.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
Thank you for your response. I cannot recreate this problem. Now, fifteen MUX FM bells use only 50% of my four processor i5. In the file attached, I've removed the extra VSTs (including the micro-tonal tuner), which do not appear to add much overhead. These are the issues and questions that remain:
1) Is there an easier way of mapping ALL incoming MIDI notes to a single channel, besides the MIDI channel mapper?
2) I noticed a few times that the note dispatcher stopped working correctly. It began to send only to the first output. When I deleted and recreated all the connections, it worked fine.
1) Is there an easier way of mapping ALL incoming MIDI notes to a single channel, besides the MIDI channel mapper?
2) I noticed a few times that the note dispatcher stopped working correctly. It began to send only to the first output. When I deleted and recreated all the connections, it worked fine.
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
Issue 3
You will notice in the attachment that some of the racks are not connected to the note dispatcher. I have made those connections several times and used them in sessions, but when I save and reload the file--the connections are gone. Usually it is the last 4 connections from the right side that are not saving.
-D. Vyd
You will notice in the attachment that some of the racks are not connected to the note dispatcher. I have made those connections several times and used them in sessions, but when I save and reload the file--the connections are gone. Usually it is the last 4 connections from the right side that are not saving.
-D. Vyd
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
Since the FM bells worked, I decided to make the piece more complex. I added several copies of a Guitar Strum VST and several copies of Kontakt with different instruments. The project rendered at 96khz in about 5 minutes, producing a correct audio file. The project rendered at 192khz in about two hours (!!!), producing a playable but horribly incorrect audio file. I am trying high sample rates because the files can then be stretched and pitch shifted with fewer artifacts.
Please find attached:
Image ZIP
1) Image of MuLab MUX network
2) Image of 96khz soundfile
3) Image of 192khz soundfile
Project ZIP
4) It references VSTs that are not included
I also removed some notes and modules
to reduce file size
I would welcome any advice or explanation.
-d. vyd
Please find attached:
Image ZIP
1) Image of MuLab MUX network
2) Image of 96khz soundfile
3) Image of 192khz soundfile
Project ZIP
4) It references VSTs that are not included
I also removed some notes and modules
to reduce file size
I would welcome any advice or explanation.
-d. vyd
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
That's the only way i see atm.d.vyd wrote:Is there an easier way of mapping ALL incoming MIDI notes to a single channel, besides the MIDI channel mapper?
Is this repeatable? Which steps do i have to take to repeat this?I noticed a few times that the note dispatcher stopped working correctly. It began to send only to the first output. When I deleted and recreated all the connections, it worked fine.
-
- KVRist
- Topic Starter
- 219 posts since 3 May, 2016
I think the first step in troubleshooting is:
1. add the missing connections to the note dispatcher
2. Save the project and close MuLab
3. Open the project and see if connections are still there.
To make the note dispatcher stop working correctly, perhaps try to change your audio settings and sample rate a few times. Start, stop, and rewind the project a few times at a high sample.rate. usually then the note dispatcher is sending only to the first connection.
1. add the missing connections to the note dispatcher
2. Save the project and close MuLab
3. Open the project and see if connections are still there.
To make the note dispatcher stop working correctly, perhaps try to change your audio settings and sample rate a few times. Start, stop, and rewind the project a few times at a high sample.rate. usually then the note dispatcher is sending only to the first connection.
-
- KVRian
- 855 posts since 3 Mar, 2009
My first thought was that sustain could be ON. It's not, but I still think the problem is that you run > 50 voices after the first notes.
I have a recent i7 7700k, 128 byte buffer size, 44.1kHz sampling
With your original MicroTuning_Template_03_simple session with all 16 connections I get 23% average cpu and 68% max.
When I shorten all release times to 7 sec, the average number of notes played per patch reduces from 3-4 to 2-3. Now I get an average cpu of 16% although max cpu was still 64% (with long time hovering at 55%).
Suggestion:
- increase your sound card buffer size
(switch from 128 to 256 buffer reduced cpu from 23%/68% to 18%/35%)
- shorten the release times
I have a recent i7 7700k, 128 byte buffer size, 44.1kHz sampling
With your original MicroTuning_Template_03_simple session with all 16 connections I get 23% average cpu and 68% max.
When I shorten all release times to 7 sec, the average number of notes played per patch reduces from 3-4 to 2-3. Now I get an average cpu of 16% although max cpu was still 64% (with long time hovering at 55%).
Suggestion:
- increase your sound card buffer size
(switch from 128 to 256 buffer reduced cpu from 23%/68% to 18%/35%)
- shorten the release times
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
About the dispatcher connections issue: confirmed issue. Will be fixed in the next version.