Regularly when working with Monitoring some Monitors Tools keep empty - especially after stopping recording - but also without even having started recording.
That is with Live-Spectrogram, Level-Meter and Others. Same with win11 and mac-os.
Same already in WaveLab 12.
Most times first start of Monitoring (the Mikrofon Button in Head of Master Section) works. Then after stopping Monitoring and restarting after a few seconds will hang.
What ASIO block size do you have?
@PG1 Hallo PG1,
sind 512k
Occurs with diverse interfaces. But should be 512k
in most cases.
I guess you mean “512” and not “512k”!
A possible cause is that you are using plugins with very high latency. Is that the case?
No not really. For instance now I’m running with nothing but Microfone.
Even with running only a Spektrum Analyzer this occurs.
But … where you are mentioning ASIO …
Often I use the Zoom F6 Interface. Sometimes Motu M4. If I remember right now
Zoom comes with own drivers. The Same with M4.
Is that a possible problem?
To get it right - I appreaciate the awesome Monitoring capabilities of WaveLab and
it’s rich and powerful Tools!
But often - if I stop recording and try to restart it or if I load
the same project - things that worked before the stop are different after that.
I spend much! time in establishing standard workflows but especially the Monitoring section seems to have some kind of magic behind.
( … many processes and handles to get in right connections and to reestablish when restarting sub processes and beeing tied to the BS (win or mac). )
So I understand the task .. but often that makes me some kind of unhappy that unpredictable behaviour
No, this should not matter.
Do you have a slow or fast computer? A slow computer could be a cause.
Don’t think they are slow. One is a Lenovo Laptop with 16GB and an
actual CPU AMD Ryzen 5 Pro 7540U the mac is an mac mini m2 with
16GB RAM.
From the start of the conversation
“Most times first start of Monitoring (the Mikrofon Button in Head of Master Section) works. Then after stopping Monitoring and restarting after a few seconds will hang.”
this hang doesn’t mean that something’s freezing. All processes continue working
only the mentioned Monitor window’s most of the time the live Spektrogram becomes
black then and stop delivering information.
Today I worked with an USB Microfone. First I connected it via ASIO4ALL that get’s the
described problem as “expected” then I switched to Built In Steinberg ASIO.
And now the whole day there is no fall - everything is working fine.
I keep watching this and will try to run the F6 and M4 with Steinberg ASIO either.
I will report if that is working.
Hello PG1,
wish you had a good start in the day.
Before telling what I experienced this morning
But it is so often very hard to get a working configuration running.
And once you get that. Next day the same things that worked beore
don’t work.
And once more: I know about the hard task getting drivers, OS and own
software to work as targeted. So this is a report thought as a base for getting
hands on some issues. It is thought as a feedback aimed to help analyzing
problems.
May be I’m the dude acting wrong with the program but I don’t think so.
The described phenomena happen regularly and I’m not a unexperienced
Software user.
This morning I tried to open the simple Projekt I saved yesterday in the evening
in working state.
Same Project saved yesterday with Mono Input as Record Bus (Standard no
user defined bus) opened as Stereo with two Faders in Mastersektion (MS).
Environment (Same as yesterday):
In Audio Connections simple configuration:
That same simple configuration that was working yesterday.
And today:
Nothing is working. With reloading the project the Audio Connection Configuration
has changed. Several tries to get Monitoring working. Nothing worked. No kind of
any Monitoring.
Resetting MS (Master Section) and “Neu zuweisen”: No success
In between Dialog Audio: configuration is not fitting something with 44khz.
But 44khz ist nowhere configured not in windows not in WaveLab.
Than after a few more tries resetting audio connection … Program crash.
OK Disconnecting Audio interface and USB Microfone and reconnecting
then starting a new empty Project
Checking the Audio Connection. Everything right in place
In: USB Mic Mono, Out UMC 1, 2
48khz and 24 Bit everywhere
Starting Monitoring (no recorded files yet no Plugins) → Monitoring is working
all Monitoring windows ok
Stopped Monitoring and restarted it: And then
This occurs so often. There is no predictable behaviour.
After that report I nevertheless wish you a good start in the day.
Best regards
Martin
This is not very clear. Do you get a problem when playing an audio file or when recording?
See the following setting. Do you have at least 75? Try with higher values. This increases the latency a bit, but this could help.
This is not because a plugin appears “simple” that it cannot be the cause of a problem. Try without it to see if that makes a difference.
Neither nor. The Problem is before any processing.
It’s just activating Monitoring (the Mic Button in MS)
… and it is already in an empty new Project without any plugins.
Now ASIO Guard with greater values:
Stopping and restarting Monitoring: Live Spectrum and others empty
Spectroramm and meter working …
I think I found the cause; at least I could reproduce it sometimes. And the good news is that this should be fixed in upcoming 13.0.10 version.
The Master Section Live input is not used by many and was not tested as much as the rest of the application, this is why this issue was not often reported.
With the current version, I think you can solve the problem sometimes by just playing an audio file one or two seconds and then activating the live input again.
