Forum Replies Created
Same here. M1Pro Monterey 12.0.1
LP 2022.BET2 compiled for M1 crashes when changing buffer lower than 256.
But the strangest part is, that if I run standard LP version (2022.0.1), change buffer to lower (it does not crashes) and go back to LP M1 version, the program works with smaller buffer.
Also looks like, the M1 version shows higher DSP load.
- This reply was modified 11 months, 3 weeks ago by sfxter.
Are there any news regarding these issues?
Thank you for your answer, Nikolai. I would really love to use your application, because I find some features very helpful in a live gigs.
Maybe someone who have OS X could do this test and confirm the console output:
Start Dante Virtual Soundcard, set samplerate to 48000 and the buffer to 64 samples. At this condition, in console I see no “performWatchdogOutput” (easy to find when you type in Consoles search “watchdog”).
When I change buffer size to 32 samples, my console is flooded with “performWatchdogOutput” (about 2000 messages per second).
Same test with built in output and input device gives totally different result.
Setting buffer to 32 samples almost does not output “performWatchdogOutput” messages (just few of them, while driver is changing).
I would really appreteate if anyone using Dante could try and reproduce this test on their machine.
Not the most active forum as I see 🙂
but anyway, I will just post here my experiment. Looks like my OS X are set correctly and the computer is powerful enough, because I can load more plugin instances in Multirack Native until I get the same level of audio stability.
I have created this chain: Waves CLA-2A to API 2500 to L3 UltraMaximizer. Then I duplicated the same chain multiple times until I started receiving in console
IOAudioEngineUserClient[<private>]::performWatchdogOutput(<private>, 187784) – (105b,19b4)
In LiveProfessor it started after 12 duplicated chains. DSP load was about 25%
Multirack allowed me to create 24 duplicate chains until i started receiving the same message in console. DSP load was about 35%.
I dont want to say anything bad about LiveProfessor, because I really love the way it opens up more possibilities to use more plugins. But the stability is still an issue as well as CPU handling. Creators of this software already did an amazing job and have brilliant ideas, but I believe that other users as well as me, would love to see more stable release instead of new features.
Just my 2 cents.
Thank you Nikolai for new version. This listen bus looks like a great idea.
But am I the only one, who had bands on Fabfilter PRO q2 soloed, when opened my recent projects with this new version?
Also one band of F6 was soloed on main vocal chain, when I restarted LP2.
Any one else noticed anything similar?
I have recently found this https://www.logicprohelp.com/forum/viewtopic.php?f=17&t=116566
and looks like other applications are affected too.
I had this issue yesterday during a show. Not the best feeling.
I doubt that this is related with a plugin, because all chains are delayed at the time of issue, although chains have different plugins.
App Nap was turned off.
No other application using audio during a show.
Did not tried this setup with waves multirack, because I’m using some Slate Digital plugins.
Sample rate is 48kHz.
I dont think that this is a driver problem, because switching audio device (does not matter – input or output) in Live Professor from “Dante” to “<<none>>” and then back to “Dante” fixes everything.
During the issue, Live Professor was not in background, I was not pressing or tweaking anything. It just came out of the blue. I’ve checked the time it happened and there are some interesting logs in console:code :
4/12/18 7:06:25.666 PM LiveProfessor 2: dynamic_cast error 1: Both of the following type_info's should have public visibility. At least one of them is hidden. 16WCParamExtension, 29WCParamExtensionMeterWithClip.code :
4/12/18 7:08:56.000 PM kernel: IOAudioStream[<ptr>]::clipIfNecessary() - Error: counted 1 clip more than one buffer ahead errors.code :
4/12/18 7:08:56.967 PM LiveProfessor 2: 19:08:56.966 WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
Any ideas, how to troubleshoot, would be appreciated.
Dear Nikolai, I believe that you are busy developing software and generating new ideas, but maybe you could help me solve this mystery? Is there a way to collect useful data, which could be used for investigation and problem reproduction?
This bug renders software to be kind of hard to use in pro application.
Thank you in advance.