Tracktion Software

lmv · Post by **lmv** » Thu Aug 03, 2023 5:34 pm

I started a track in Waveform 12.5.5, then saved a new edit after some time and saved yet a new edit after some more time.

Then one of the plugins crashed, I had to kill Waveform and now the two last edits never open. The plugin that crashed was not even present in the second edit, but it won't open either.

That happens after two years of not using Waveform. The instability of this DAW is just astounding.

Well, is there some way to tell Waveform to load the edit without any plugins?

pough · Post by **pough** » Thu Aug 03, 2023 6:38 pm

I'm not 100% sure that I know what you're talking about because your description seems a bit vague to me, or at least it leaves out details that are important, but I think that you are experiencing a Waveform issue that reminds me of a classic joke: What's the difference between a duck? One of its legs is both the same.

(It's not funny in the traditional way.)

If you have one Edit open and you save as a new Edit and both are open at the same time, changes to one will reflect in the other. One of its legs is both the same, you see. It's a dumb flaw and I don't know if they ever fixed it and I don't know if it happened to you because "after some time" may include closing the original Edit. Or not. It's often the details we leave out that can help help help.

Anyways, don't forget to save and don't forget to close, too.

Edit files are usually text files (XML) and can be edited (don't forget to save) except in some cases when things crash, in which case they are stored as binary for whatever reason. If you are luckier now than when you had the crash, you will be able to remove the chunks of the Edit that are the instances of plugins.

I also don't know what you mean by "never open." It could mean that Waveform refuses to recognize the file as an Edit. It could mean that Waveform sees the file but refuses to open it. It could mean that Waveform tries to open the file but never succeeds - with a variety of possible responses. All of those are VERY different scenarios.

lmv · Post by **lmv** » Thu Aug 03, 2023 7:20 pm

pough wrote: Thu Aug 03, 2023 6:38 pm If you have one Edit open and you save as a new Edit and both are open at the same time, changes to one will reflect in the other.

It's worse than that.

I had one project. Very old. Two years maybe. Just two tracks, instrument #1 and instrument #2, and a few notes. A stupid draft.

I open it. It plays. I open it. It plays. I open it. It plays. Several times.
Why so many times? I don't know. I was just getting used to Waveform again. But it opened every time.

So I added two more tracks with new instruments. Instrument #3 and instrument #4. They loaded. I added notes. They played.

I wasn't happy with instrument #4 so I deleted it and added another in its place (no "replace" command).

Then instrument #4 crashed. It stuttered like crazy until it crashed and burned and brought Waveform down with it.

I reloaded Waveform. It loaded. I tried to open the project and it shows the "loading" twirl thingy forever. The project never loads. I have to kill Waveform.

I decided to open the directories of instrument #3 and instrument #4 and rename the DLLs. So Waveform loaded and the project loaded. I deleted the plugins from their tracks, saved, closed and reopened. The project loaded. So I renamed the DLLs to their original names, added instrument #3 again, saved, closed, reopened and the project would not open.

I did everything again but this time I readded only instrument #4. All the same.

I did everything again but this time I also renamed the instrument #2 DLL, reopened the project, deleted the plugin, saved, renamed the instrument #2 DLL to its original name, reopened the project, readded instrument #2, saved, closed, reopened and... it fails. Even instrument #2 which had been there for more or less two years and opened and ran fine multiple times before the whole ordeal won't work anymore.

There never seems to be any problem with instrument #1.

It gets worse.

I created a new project from scratch. I copied and pasted the MIDI tracks from the doomed project and added instrument #1. Saved and closed, reopened, it loads. So I added instrument #2, saved and closed, reopened, it freezes.

It's doomed. Waveform has become unusable to me. Again.

dysjoint · Post by **dysjoint** » Thu Aug 03, 2023 7:40 pm

Have you updated waveform versions at all? Opening old projects from old versions of Waveform can cause numerous hidden errors (hidden to me at least) I keep a version of T6 on my pc to use to convert stuff to audio stems if I want (even that struggles with some old T3 projects)

This doesn't explain your last paragraph I know. What instruments? And is it specific to those exact plugins?

lmv · Post by **lmv** » Thu Aug 03, 2023 7:43 pm

The same instruments. I tried to recreate the project from scratch.

I was using v12.1.3 when the problem started. I eventually upgraded to v12.5.5 after the fact, but that didn't help.

lmv · Post by **lmv** » Thu Aug 03, 2023 11:46 pm

I was on Linux, installed Waveform 12.5.5 on Windows and imported the broken project. The two first edits load although it can't find the plugins. The two edits that freeze on Linux won't load on Windows.

And on the list of edits, two first edits display their last changed date while the two broken ones display "???".

pough · Post by **pough** » Fri Aug 04, 2023 5:39 pm

Do you have plugins sandboxed? Sometimes you can save things by sandboxing. However, sometimes sandboxing itself can cause problems. I recall some Wusik plugins had their own sandboxing and apparently sandboxing a sandbox can get flaky.

But if you had sandboxing turned off you might be able to turn it back on and make the loading of problematic plugins not crash Waveform.

Watchful · Post by **Watchful** » Fri Aug 04, 2023 6:45 pm

Back when the developers used to talk to us, a "safe mode" was something I suggested--basically, a way to open a project with all the plugins disabled so you could easily find which one was causing the problem. I doubt we'll ever see anything like that now.

When I had a plugin go bad (support for it stopped so nothing answered it when it tried to authenticate), I was able to open the project and disable it by opening it in T6, the version in which the project was created. I was lucky that T6 was able to open every old project file that had it (I had it backed up, so please: back up!!!), so I could delete it and save it. Then they opened in the then-current W10 just fine.

lmv · Post by **lmv** » Fri Aug 04, 2023 7:05 pm

Watchful wrote: Fri Aug 04, 2023 6:45 pm Back when the developers used to talk to us

Oh. I considered asking pough if he worked for Tracktion because he seems to be the only one who replies here. Now I see it.

Strainer · Post by **Strainer** » Sun Dec 03, 2023 2:27 pm

Hello! I'm having the same problem with couple of my projects, Waveform just swirls the "loading thingie" center of the screen, but nothing happens, and eventually I have to kill the process of waveform.

Has anyone found a solution to "safe mode" start or something?

Or can I somehow copy even the midi files from the unopenable project to a new project and start over that way?
Or do I have to just play everything from the start again?

Br,
Jani

operandx · Post by **operandx** » Sun Dec 03, 2023 3:21 pm

Strainer wrote: Sun Dec 03, 2023 2:27 pm Hello! I'm having the same problem with couple of my projects, Waveform just swirls the "loading thingie" center of the screen, but nothing happens, and eventually I have to kill the process of waveform.

Has anyone found a solution to "safe mode" start or something?

Or can I somehow copy even the midi files from the unopenable project to a new project and start over that way?
Or do I have to just play everything from the start again?

Br,
Jani

As a last resort you could try editing the .tacktionedit file for the edit in question. These are XML files which can be edited in a text editor. The file is structured and references of plugins are between <plugin> </plugin> tags. You could delete references to any plugins that you think might be responsible for the issues. I would save a backup copy of the .tracktionedit file and edit original (the copy wont be seen by the project file) just in case. The tracktionedit and project files are in the project folder. If you are not sure where that is, you can find by right clicking on project name on project tab and choosing the menu option to open project folder.

jabe · Post by **jabe** » Sun Dec 03, 2023 3:28 pm

Strainer wrote: Sun Dec 03, 2023 2:27 pm Hello! I'm having the same problem with couple of my projects, Waveform just swirls the "loading thingie" center of the screen, but nothing happens, and eventually I have to kill the process of waveform.

Has anyone found a solution to "safe mode" start or something?

Or can I somehow copy even the midi files from the unopenable project to a new project and start over that way?
Or do I have to just play everything from the start again?

Br,
Jani

From what I've seen the MIDI isn't usually a separate file but is part of the .tracktionedit file. However, it's a while since I checked, and if you've imported a MIDI file from elsewhere it should still exist.

The very first thing to do is to open the log file. Normally the way to do this is via the Help button in Waveform, but since you're having bother getting to it, here's where it is, assuming you're on Windows:
C:\Users\YourName\AppData\Roaming\Tracktion\Waveform\Temporary

...the file is called something like Waveform12Log.txt

open it with a text editor and look at the latest entries. They may tell you what the problem is. Post a section or all of it from your most recent attempt to open Waveform and we might be able to help.

If you still have trouble with the open:

You could edit the .tracktionedit file. It has an XML layout. Make 100% sure that you have copied the .tracktionedit file to a safe location outside the project OR rename it - possibly change the suffix.

Any text editor should suffice for editing the file. If you are uncertain about XML, there is a tutorial here: https://www.w3schools.com/xml/

It shouldn't be too difficult. First make sure that your tags are balanced. This means that if there is a tag like this: <EDIT (probably with other parameters in it)> there will need to be a later ending one like this: </EDIT>. This will contain other paired and lower level pairs of tags. Sometimes a tag contains its own closing, so there won't be a second one, like this: <PITCH startBeat="0.0" pitch="60"/> where the slash at the end indicates its closing.

If your tags are not balanced, it means your file has become corrupted. If the closing EDIT tag is missing at the end, this is a sure sign of corrution and the best you can hope for is to resure any data that remains in the file by adding closing tags to balance all the ones that were opened and not closed.

If the tags are all balanced it might be a case of trial and error to, perhaps, remove a troublesome plug-in.

Within the <EDIT....> </EDIT> tags are a number of further tags. These have a hierarchy.

The first ones that you see will be global settings for the edit. These may include info about the key, tempo, attached equipment, master plug-ins and settings, etc, etc.

Next there are <TRACK (with parameters)> </TRACK> tags containing info about each track. This may include info about plug-ins and their settings, audio file references, MIDI data, and whatever other information a track may hold.

If the log file has indicated a particular problem with a plug-in, you should be able to remove the tags within which the plug-in is specified. This may or may not solve your problem.

If you decide that you've messed up your editing, copy the saved version over it and try again. When you do your edits, make a note of what they were, just in case you need to make the same ones again.

If you can find the MIDI data you're worried about losing, it may be that you can start a new project, or even a new edit, and copy the data into the new .tracktionedit file.

Looks like you've just been given a response that's not dissimilar to mine. Good luck with it.

Peter Widdicombe · Post by **Peter Widdicombe** » Sun Dec 03, 2023 4:52 pm

I just tried 12.5 briefly yesterday, so had a look at ITS .tractionedit file, and it looks like saved blobs, and not .xml. There are keywords and names in there, so it's not compressed/encrypted, but definitely not editable, unlike I remember in older versions.

ff00ff00 currentTake speed ð?QUANTISATION GROOVE SEQUENCE ver channelNumber &NOTE p < b ¼Ý¸²10@l @PüsÛ
@v c NOTE p C b Þ–µºx4@l ÕS¾zÏØ?v c NOTE p A b xOj5@l @ec8±ºÚ?v c NOTE p @ b _Nö¼ˆh6@l àá0¾

(that's just one "line" in the file).

From the old "Subways t4.trkedit file, it was readable XML... Is there a non-default setting that saves in non-binary ? It looks like all my projects from version 10 on seem to be direct saves (as above) and the older ones as XML (below).

Interestingly, I took that same binary .tractionedit and opened it normally, and specifically SAVED rather than just using the default save (and answer yes) when closing Waveform, and it saved as an editable .xml file. I guess I NORMALLY do that; hence all my .tractionedit files are the binary/temporary versions...

<?xml version="1.0" encoding="UTF-8"?>

<EDIT appVersion="3.0.4.8 (built: 4 February 2008)" modifiedBy="unnamed"
mediaId="d177a/12d39b00" fps="24" timecodeFormat="beats">
<VIEWSTATE viewleft="0" viewright="157.6" tracktop="0" cursorpos="0" markIn="0"
markOut="153.6" scrollWhenPlaying="1" scrollSmoothly="0" loopPlayback="1"
automationLocked="1" recordPunchInOut="0" snapToTimecode="1"
filterAreaWidth="0.711883724" panelAreaWidth="0.383054674" rackEditorHeight="-0.200000003"
midiTimecodeIgnoringHours="0" midiTimecodeOffset="0" markerMode="2"
lastMarkerMode="0" tempoTrackVisible="0" midiControllerHeight="0.5"
midiVelocityHeight="0.163306445" midiTimecodeSourceDevice="MIDI Yoke NT: 1"
midiTimecodeEnabled="0"/>
<ID3VORBISMETADATA date="2006" trackNumber="1"/>

talby · Post by **talby** » Sun Dec 03, 2023 5:32 pm

My first thought on all this, based on my own recent experience with symptoms appearing like the once described in this thread, was: deactivating Plugin Sandboxing might solve it.
However, if you cannot even open Waveform and reach the Settings panel anymore, then try to manually fix it in some settings file (keep a save copy of the original setting file as a backup!). Unfortunately, I could not find in the various setting files where the parameter for Plugin Sandboxing OFF/ON would be defined. Therefore I suggest to care to at least get Waveform to start properly again, what the OP called "safe start", and then to have access to the Plugins Sandboxing option by the GUI again.

(1) Find file "Waveform.settings" in the config folder for "Tracktion/Waveform/".
On Linux assume it to be located here:

Code: Select all

/home/username/.config/Tracktion/Waveform/Waveform.settings

(2) Remember that there exists the following configuration option in the GUI:
SETTINGS - GENERAL - Startup - Upon launch reopen edits

The option should be deactivated, so that no Edit becomes opened automatically and any malfunctioning of that or those Edit(s) cannot right away freeze the Wavform app. The entry appears to be the following one, and setting it to "0" (zero) deactivates the automatic opening of the last opened Edit(s):

Code: Select all

  <VALUE name="reloadEdits" val="0"/>

I guess that is what you are searching for as a "safe start".

By the way, there would also exist the following option in the settings:
SETTINGS - GENERAL - Startup - Upon launch
The list of entries in that submenu appear to be numbered in the config code by values, 0, 1, 2, 3. In order to launch the Waveform app and right away show up with its SETTINGS Tab presented, the following would have to be configured:

Code: Select all

  <VALUE name="appLaunchMode" val="1"/>

Good luck!

PS: If someone would know where the toggle for de/activating Plugin Sandboxing is configured, please tell us.

Strainer · Post by **Strainer** » Tue Dec 05, 2023 9:16 am

Thank you all for your help! I got it open by editing the traktionedit file of the project. I had a hunch that the culprit was the ESW vinyl guitar 2 plugin, that I had to install and uninstall couple of times, because I had problems with the sample library file.

Here's the log file text:
Waveform 64-bit version: 12.5.11 (Built: 26 June 2023)
Log started: 5 Dec 2023 10:46:32am
------------------------------------------------
5 Dec 2023 10:46:32 Initialising...
5 Dec 2023 10:46:32 Finding MIDI I/O
5 Dec 2023 10:46:32 MIDI output: Microsoft GS Wavetable Synth
5 Dec 2023 10:46:32 MIDI output: PANORAMA T4 (enabled)
5 Dec 2023 10:46:32 opening MIDI out device:PANORAMA T4
5 Dec 2023 10:46:32 MIDI output: MIDIOUT2 (PANORAMA T4) (enabled)
5 Dec 2023 10:46:32 opening MIDI out device:MIDIOUT2 (PANORAMA T4)
5 Dec 2023 10:46:32 MIDI output: MIDIOUT3 (PANORAMA T4) (enabled)
5 Dec 2023 10:46:32 opening MIDI out device:MIDIOUT3 (PANORAMA T4)
5 Dec 2023 10:46:32 MIDI output: MIDIOUT4 (PANORAMA T4) (enabled)
5 Dec 2023 10:46:32 opening MIDI out device:MIDIOUT4 (PANORAMA T4)
5 Dec 2023 10:46:32 MIDI input: PANORAMA T4 (enabled)
5 Dec 2023 10:46:32 opening MIDI in device: PANORAMA T4
5 Dec 2023 10:46:32 MIDI input: MIDIIN2 (PANORAMA T4) (enabled)
5 Dec 2023 10:46:32 opening MIDI in device: MIDIIN2 (PANORAMA T4)
5 Dec 2023 10:46:32 MIDI input: MIDIIN3 (PANORAMA T4) (enabled)
5 Dec 2023 10:46:32 opening MIDI in device: MIDIIN3 (PANORAMA T4)
5 Dec 2023 10:46:32 MIDI input: MIDIIN4 (PANORAMA T4) (enabled)
5 Dec 2023 10:46:32 opening MIDI in device: MIDIIN4 (PANORAMA T4)
5 Dec 2023 10:46:32 MIDI input: Vienna Instruments MIDI
5 Dec 2023 10:46:32 MIDI input: Virtual (enabled)
5 Dec 2023 10:46:32 MIDI input: Panorama T4
5 Dec 2023 10:46:32 Wrote settings file: C:\Users\sihvo\AppData\Roaming\Tracktion\Waveform\Waveform.settings
5 Dec 2023 10:46:32 ASIO: found Generic Low Latency ASIO Driver
5 Dec 2023 10:46:32 ASIO: found Solid State Logic ASIO Driver
5 Dec 2023 10:46:32 ASIO: found Generic Low Latency ASIO Driver
5 Dec 2023 10:46:32 ASIO: found Solid State Logic ASIO Driver
5 Dec 2023 10:46:33 Audio block size: 480 Rate: 44100
5 Dec 2023 10:46:33 Rebuilding Wave Device List...
5 Dec 2023 10:46:33 Wave In: Input 1 (enabled): 0 (L)
5 Dec 2023 10:46:33 Wave In: Input 2 (enabled): 1 (L)
5 Dec 2023 10:46:33 Wave Out: Output 1 + 2 (enabled): 0 (L), 1 (R)
5 Dec 2023 10:46:33 Default Wave Out: Output 1 + 2
5 Dec 2023 10:46:33 Default MIDI Out: PANORAMA T4
5 Dec 2023 10:46:33 Default Wave In: Input 1
5 Dec 2023 10:46:33 Default MIDI In: MIDIIN2 (PANORAMA T4)
5 Dec 2023 10:46:33 Creating Default Controllers...
5 Dec 2023 10:46:33 Loading Custom Controllers...
5 Dec 2023 10:46:33 Initialising windows...
5 Dec 2023 10:46:33 Language: en
5 Dec 2023 10:46:33 Initialising plugins...
5 Dec 2023 10:46:33 No Cmajor DLL found
5 Dec 2023 10:46:33 Image database loaded 0 images in 1 ms seconds
5 Dec 2023 10:46:33 Last run failed to shut down cleanly
5 Dec 2023 10:46:33 C:\Program Files\Tracktion\Waveform 12\Waveform 12 (64-bit).exe
5 Dec 2023 10:46:33 Windows 11
5 Dec 2023 10:46:33 CPU: 3942MHz Cores: 24 32676MB
5 Dec 2023 10:46:33 Events file size: 1.3 KB
5 Dec 2023 10:46:33 Initialising file formats...
5 Dec 2023 10:46:33 Initialising projects...
5 Dec 2023 10:46:33 Initialising devices...
5 Dec 2023 10:46:33 Loop library loaded 3 loops in 176 ms
5 Dec 2023 10:46:33 MIDI External controller assigned: MIDIIN2 (PANORAMA T4)
5 Dec 2023 10:46:34 Initialising ReWire...
5 Dec 2023 10:46:34 Preset database loaded 1286 presets in 763 ms seconds
5 Dec 2023 10:46:35 Reloading Windows...
5 Dec 2023 10:46:35 Crash report uploaded: Waveform 12.5.11 Crash Log 2023-11-29.dmp as 2800000000ba6a18c392853d3_MainWindow.cppMainWindow~MainWindow3234.dmp
5 Dec 2023 10:46:35 Machine ID: W4BF00CDBF:WC51ADA81A U
5 Dec 2023 10:46:35 Feature set: auto
5 Dec 2023 10:46:42 ASIO: opening device: Generic Low Latency ASIO Driver
5 Dec 2023 10:46:43 ASIO: 2 in, 2 out
5 Dec 2023 10:46:43 ASIO: 441->441, 441, 441
5 Dec 2023 10:46:43 ASIO: outputReady true
5 Dec 2023 10:46:43 ASIO: Rates: 44100
5 Dec 2023 10:46:43 ASIO: Latencies: in = 1764, out = 882
5 Dec 2023 10:46:43 ASIO: creating buffers (dummy): 4, 441
5 Dec 2023 10:46:43 ASIO: Latencies: in = 1764, out = 882
5 Dec 2023 10:46:43 ASIO: device open
5 Dec 2023 10:46:43 ASIO: closed
5 Dec 2023 10:46:43 ASIO: opening device: Generic Low Latency ASIO Driver
5 Dec 2023 10:46:43 ASIO: 2 in, 2 out
5 Dec 2023 10:46:43 ASIO: 441->441, 441, 441
5 Dec 2023 10:46:43 ASIO: outputReady true
5 Dec 2023 10:46:43 ASIO: Rates: 44100
5 Dec 2023 10:46:43 ASIO: Latencies: in = 1764, out = 882
5 Dec 2023 10:46:43 ASIO: creating buffers (dummy): 4, 441
5 Dec 2023 10:46:43 ASIO: Latencies: in = 1764, out = 882
5 Dec 2023 10:46:43 ASIO: device open
5 Dec 2023 10:46:43 ASIO: closed
5 Dec 2023 10:46:43 ASIO: opening device: Generic Low Latency ASIO Driver
5 Dec 2023 10:46:43 ASIO: 2 in, 2 out
5 Dec 2023 10:46:43 ASIO: 441->441, 441, 441
5 Dec 2023 10:46:43 ASIO: outputReady true
5 Dec 2023 10:46:43 ASIO: Rates: 44100
5 Dec 2023 10:46:43 ASIO: Latencies: in = 1764, out = 882
5 Dec 2023 10:46:43 ASIO: creating buffers (dummy): 4, 441
5 Dec 2023 10:46:43 ASIO: Latencies: in = 1764, out = 882
5 Dec 2023 10:46:43 ASIO: device open
5 Dec 2023 10:46:43 ASIO: clock: Internal (cur)
5 Dec 2023 10:46:43 ASIO: disposing buffers
5 Dec 2023 10:46:43 ASIO: creating buffers: 4, 441
5 Dec 2023 10:46:43 ASIO: channel format: 18
5 Dec 2023 10:46:43 ASIO: Latencies: in = 1764, out = 882
5 Dec 2023 10:46:43 ASIO: 441->441, 441, 441
5 Dec 2023 10:46:43 ASIO: starting
5 Dec 2023 10:46:43 Rebuilding Wave Device List...
5 Dec 2023 10:46:43 Wave In: Input 1 (enabled): 0 (L)
5 Dec 2023 10:46:43 Wave In: Input 2 (enabled): 1 (L)
5 Dec 2023 10:46:43 Wave Out: Output 1 + 2 (enabled): 0 (L), 1 (R)
5 Dec 2023 10:46:43 Default Wave Out: Output 1 + 2
5 Dec 2023 10:46:43 Default MIDI Out: PANORAMA T4
5 Dec 2023 10:46:43 Default Wave In: Input 1
5 Dec 2023 10:46:43 Default MIDI In: MIDIIN2 (PANORAMA T4)
5 Dec 2023 10:46:43 ASIO: found Generic Low Latency ASIO Driver
5 Dec 2023 10:46:44 ASIO: found Solid State Logic ASIO Driver
5 Dec 2023 10:46:44 ASIO: found Generic Low Latency ASIO Driver
5 Dec 2023 10:46:44 ASIO: found Solid State Logic ASIO Driver
5 Dec 2023 10:46:46 ASIO: stopping
5 Dec 2023 10:46:46 ASIO: closed
5 Dec 2023 10:46:46 ASIO: opening device: Solid State Logic ASIO Driver
5 Dec 2023 10:46:46 ASIO: 4 in, 2 out
5 Dec 2023 10:46:46 ASIO: 16->2048, 256, -1
5 Dec 2023 10:46:46 ASIO: Rates: 44100 48000 88200 96000 176400 192000
5 Dec 2023 10:46:46 ASIO: Latencies: in = 322, out = 331
5 Dec 2023 10:46:46 ASIO: creating buffers (dummy): 4, 256
5 Dec 2023 10:46:46 ASIO: Latencies: in = 322, out = 331
5 Dec 2023 10:46:46 ASIO: device open
5 Dec 2023 10:46:46 ASIO: clock: Computer (cur)
5 Dec 2023 10:46:46 ASIO: disposing buffers
5 Dec 2023 10:46:46 ASIO: creating buffers: 6, 256
5 Dec 2023 10:46:46 ASIO: channel format: 18
5 Dec 2023 10:46:46 ASIO: Latencies: in = 322, out = 331
5 Dec 2023 10:46:46 ASIO: 16->2048, 256, -1
5 Dec 2023 10:46:46 ASIO: starting
5 Dec 2023 10:46:46 Rebuilding Wave Device List...
5 Dec 2023 10:46:46 Wave In: Input 1 (enabled): 0 (L)
5 Dec 2023 10:46:46 Wave In: Input 2 (enabled): 1 (L)
5 Dec 2023 10:46:46 Wave In: Loopback L: 2 (L)
5 Dec 2023 10:46:46 Wave In: Loopback R: 3 (L)
5 Dec 2023 10:46:46 Wave Out: Output 1 + 2 (enabled): 0 (L), 1 (R)
5 Dec 2023 10:46:46 Default Wave Out: Output 1 + 2
5 Dec 2023 10:46:46 Default MIDI Out: PANORAMA T4
5 Dec 2023 10:46:46 Default Wave In: Input 1
5 Dec 2023 10:46:46 Default MIDI In: MIDIIN2 (PANORAMA T4)
5 Dec 2023 10:46:48 ASIO: stopping
5 Dec 2023 10:46:48 ASIO: clock: Computer (cur)
5 Dec 2023 10:46:48 ASIO: disposing buffers
5 Dec 2023 10:46:48 ASIO: creating buffers: 6, 128
5 Dec 2023 10:46:48 ASIO: channel format: 18
5 Dec 2023 10:46:48 ASIO: Latencies: in = 194, out = 198
5 Dec 2023 10:46:48 ASIO: 16->2048, 128, -1
5 Dec 2023 10:46:48 ASIO: starting
5 Dec 2023 10:46:57 Loaded edit: Grand maze Edit 1
5 Dec 2023 10:47:10 Loaded edit: Grand maze Edit 2 Tiivistetty edit
---------------------------------------------

5 Dec 2023 10:46:57 Loaded edit: Grand maze Edit 1
This edit it did open correctly.

5 Dec 2023 10:47:10 Loaded edit: Grand maze Edit 2 Tiivistetty edit
This edit froze waveform 12, and did not open, I had to kill the process of waveform.

I did not find any mention of the problem plugin on the log file, but edited the project edit file of "Grand maze Edit 2 Tiivistetty edit" and removed all data of that plugin, from

<PLUGIN... to </PLUGIN>

Hope this helps anyone else struggling to get edits open!

I can try to make a better explanation of this process, if my text is too disoriented.

Br,
Jani

Tracktion Software

KVR Audio

Is there a safe start mode for Waveform?