does live input rendering work for you?

Here it seems completely broken. Can’t get the dedicated window to show up anymore - only worked a couple of times.

The only times it did work it didn’t release the process so it kept monitoring the input causing a delay abd eventually crashed the program.

tested some more. It’s the very live input rendering window - show here at 1:47 - that simply doesn’t open.

here’s a video showing the issue.

so…after changing skin and opening an old audio file I got the LIR window to show up - after trying to record something the process hung not allowing me to stop the rendering. Eventually WL crashed while trying to close the program.

Process: WaveLab Pro 10.0 [607]
Path: /Applications/WaveLab Pro Pro 10.0
Identifier: net.steinberg.WaveLab-Pro-10-0
Version: (
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: WaveLab Pro 10.0 [607]
User ID: 501

Date/Time: 2019-10-30 13:52:34.781 +0100
OS Version: Mac OS X 10.13.6 (17G8037)
Report Version: 12
Anonymous UUID: AADC4F82-150A-7A32-29D6-12533D64080E

Time Awake Since Boot: 690 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue:

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
abort() called
*** error for object 0x7fb0eb1b3bb8: incorrect checksum for freed object - object was probably modified after being freed.

Thread 0 Crashed:: Dispatch queue:
0 libsystem_kernel.dylib 0x00007fff6732cb66 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff674f7080 pthread_kill + 333
2 libsystem_c.dylib 0x00007fff672881ae abort + 127
3 libsystem_malloc.dylib 0x00007fff67391b58 szone_error + 596
4 libsystem_malloc.dylib 0x00007fff6739cf23 tiny_free_no_lock + 2439
5 libsystem_malloc.dylib 0x00007fff6739d2d2 free_tiny + 628
6 libqtx.dylib 0x0000000104f11594 TApplication::CanQuitCurrentActivities(bool) + 1028
7 libqtx.dylib 0x0000000104ffe659 SaveAllFilesDialog(QWidget*, TFileGroup const*, ESaveAllContext, TDocument const*, QList<TDocument*>) + 201
8 libqtx.dylib 0x0000000104ff959e TDocWorkspace::closeEvent(QCloseEvent
) + 206
9 net.steinberg.WaveLab-Pro-10-0 0x00000001038679ec 0x101e1f000 + 27560428
10 org.qt-project.QtWidgets 0x0000000105e1585d QWidget::event(QEvent*) + 1165
11 org.qt-project.QtWidgets 0x0000000105f3f344 QMainWindow::event(QEvent*) + 4852
12 org.qt-project.QtWidgets 0x0000000105ddcbf4 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 324
13 org.qt-project.QtWidgets 0x0000000105dd960b QApplication::notify(QObject*, QEvent*) + 587
14 libqtx.dylib 0x0000000104f22adc TGuiApplication::notify(QObject*, QEvent*) + 3692
15 net.steinberg.WaveLab-Pro-10-0 0x0000000102e2972e 0x101e1f000 + 16820014
16 org.qt-project.QtCore 0x0000000105812ecc QCoreApplication::notifyInternal2(QObject*, QEvent*) + 188
17 org.qt-project.QtWidgets 0x0000000105e0d2f5 QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) + 165
18 org.qt-project.QtWidgets 0x0000000105e3743c QWidgetWindow::event(QEvent*) + 1628
19 org.qt-project.QtWidgets 0x0000000105ddcbf4 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 324
20 org.qt-project.QtWidgets 0x0000000105dd960b QApplication::notify(QObject*, QEvent*) + 587
21 libqtx.dylib 0x0000000104f22adc TGuiApplication::notify(QObject*, QEvent*) + 3692
22 net.steinberg.WaveLab-Pro-10-0 0x0000000102e2972e 0x101e1f000 + 16820014
23 org.qt-project.QtCore 0x0000000105812ecc QCoreApplication::notifyInternal2(QObject*, QEvent*) + 188
24 org.qt-project.QtGui 0x00000001065e95ab QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 3483
25 org.qt-project.QtGui 0x00000001065c617b QWindowSystemInterface::sendWindowSystemEvents(QFlagsQEventLoop::ProcessEventsFlag) + 219
26 libqcocoa.dylib 0x00000001096f9490 QCocoaEventDispatcherPrivate::processPostedEvents() + 320
27 libqcocoa.dylib 0x00000001096f9a7b QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 43
29 0x00007fff3f35fedc __CFRunLoopDoSource0 + 108
30 0x00007fff3f288340 __CFRunLoopDoSources0 + 208
31 0x00007fff3f2877bd __CFRunLoopRun + 1293
32 0x00007fff3f287023 CFRunLoopRunSpecific + 483
33 0x00007fff3e571d96 RunCurrentEventLoopInMode + 286
34 0x00007fff3e571a0f ReceiveNextEventCommon + 366
35 0x00007fff3e571884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
36 0x00007fff3c821a3b _DPSNextEvent + 2085
37 0x00007fff3cfb7e34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
38 0x00007fff3c81684d -[NSApplication run] + 764
39 libqcocoa.dylib 0x00000001096f87a0 QCocoaEventDispatcher::processEvents(QFlagsQEventLoop::ProcessEventsFlag) + 2656
40 org.qt-project.QtCore 0x000000010580ae7e QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) + 462
41 org.qt-project.QtCore 0x0000000105813232 QCoreApplication::exec() + 130
42 net.steinberg.WaveLab-Pro-10-0 0x0000000102e1de66 0x101e1f000 + 16772710
43 net.steinberg.WaveLab-Pro-10-0 0x0000000103ad0c07 0x101e1f000 + 30088199
44 libdyld.dylib 0x00007fff671dc015 start + 1

when trying to switch off LIR

PG - any thoughts?

I have no clue. The picture of the message you provide, should only appear in WaveLab when quitting WaveLab, if some process takes place (inc. Live Recording).
Apart Live Recording, can you record through the standard dialog, or on a montage track? Just to check your audio inputs.

regular recording and recording in montage is working just fine.

The LIR window simply doesn’t open.

If I create a new empty file and try to open LIR I’m told the output file name is not valid and purple box appears for a second.

I can get the LIR to open by changing skin :confused:

Quite a shame because I bought the update for this very feature

Check the video

I can’t read the message box, what does it say?
Before you call the render function, can you hear the audio in real time, when clicking on the microphone icon?

it says “the output file name is not valid”

Yes - audio is passing when enabling LIR - just no GUI to control it :wink:

the output file name is not valid

Select “Unnamed File” or select a valid name there:

This is a Render function: you need to set the Render parameters first.

Ok!!! Exiting - didn’t have a clue that was how it worked :crazy_face:

The concept is this: the Master Section can have 3 sources:

  1. audio file

  2. audio montage

  3. live input

  4. is new to WaveLab 10.

But in all cases, the render settings must be set.
And for 3, it is recommended to have an audio file open, to have the same render options active.

There is a bug though - once I get the LIR to run, as per your instructions, it is not possible to stop it. Though it’s not recording / rendering the STOP button is greyed out - it’s impossible to get out of the LIR unless I render something.

After that the LIR is still active and impossible to stop it.

Do you see the red state at some point or not (after clicking on the “Render” button at the bottom right).

Yes - the function itself seems to work. But it locks up if you open LIR and then decide not to render anything and wish to switch if off again. Or say you’ve set the wrong input and wish to change that. No es possible?

This video shows what happens:

So to me - this feature needs som re-work. I’d like to be able to LIR just as easy as it is to record something the regular way.

Having to open an old file, press render, name the file before being able to start this - great - feature is too bad :slight_smile:

ALSO - this is a nice-to-have - somehow being able to track the file WITHOUT effects at the same time so you end up with both a processed and unprocessed file would be mega awesome. Lets say I’ve set the gate too high so certain words got chopped off - would be nice to have the raw recording. OR for backup purposes. Just a thought :wink:

Yes. I prefer to just send the audio to analog using reference tracks. You can send a reference track to more than one stereo output if needed. Then, you can record the audio back to a new montage track, “the regular way”. You can even record two tracks at the same time with different hardware inputs.

Cool :sunglasses: thing is though I’m not using hardware except for some light compression and preamp going in. So looking for a way to track through my fav VO chain while keeping an unprocessed track

I think more info is needed. When you say “fav VO chain”, do you mean plugins in WaveLab after your hardware preamp and compressor?

I’m sure there is a way.