After power outage, can't load project

[ellarah]

I was working in Tracktion (5, because I've been working on / used to it for a while, though I now also have 7) when the power went out (I have a new desktop, and it shut down, after this we'll look into battery backups or something so I'll have a buffer like I had with my old laptop). The power outage/shutdown might have happened right as I saved or right after.

When I got my desktop powered back up, this project wasn't listed inside Tracktion. I tried to open it, but I got the error, "couldn't load project file." (I haven't yet tried making a new project out of all the files in the folder. I hope to save everything I had done in it. I'm also not yet sure the correct steps if I go that route.)

I don't know if the project file AND main edit are corrupted or how to fix that. When I searched for similar issues I mostly saw people offering personalized helps instead of tutorials (nothing else as relevant) so that's why I'm posting (also because I don't want to further break anything; I want to be careful). I usually never ask for help, just read how to fix things.

I've been quite distraught today dealing with everything related to this storm and power outage at & outside the house we're renting. Thanks for help and such with a frazzled, desperate me. There's also quite the story surrounding the other events! Maybe I'll tell that later.

[Peter Widdicombe]

Just so we have an idea, what was in the project(s)? Is it MIDI recording, audio recordings, audio recordings that may have been cut/sliced/looped ... ?

How much "track recordings" might have been made in the last session that was lost?

[jabe]

The format of the .tracktionedit file is XML. The XML tags have to be balanced. This means that each opening tag has to have a closing tag. Tags are often nested within other tags. You can look up XML to find out how it works. If you're already familiar with HTML, you should get it easily.

Sometimes the end part of the file might be overwritten with what are known as "low values". This means the hex values of that part of the file are all x'00'. That won't mean much to you, but if it has happpened, part of the data will have been lost. This might not have happened.

If the XML tags are just unbalanced, you may have lost some data. It might just be a case of fixing up the file so that you get to keep as many tracks as possible. Some tracks might be lost. Some tracks might be partially lost.

I did have an idea that I could either write a program to fix files as well as it might, or to write a tutorial so that people can fix their own, but unfortunately I have other pressing priorities at the moment. If you can't get into the project at all, I'll have some time after new year if you want to send it for me to take a look. I can explain to you what I've done.

[ellarah]

It's not a .tracktionedit file, it's a .tracktion file. (A project file. Like the ones I used/opened [in the "open project" dialog] to re-start my projects when I got a new computer.)

This project does not have any .tracktionedit (just .trkedit) files, but one I switched to T7 has those. I've only worked on this in T5, and it has one .tracktion file that is quite broken, and several .trkedit files. All but one should not have been effected and I hope the one I was using/saving at the time is ok. :\

This .tracktion file looks like a lot of blank space, not empty but a lot of white space, when I open it with Notepad. BUT the working .tracktion file of another working project doesn't even look like XML in Notepad, weird characters and some text I recognize.

The good news is that when I opened the EDIT (.trkedit, still not .tracktionedit) in Notepad it looks like XML, not broken hopefully, but it looks at least fixable if there's something un-closed, etc. I work with HTML and some XML too, so I am quite hopeful there.

Would a backup of an old .tracktion project file maybe work to add the project back and list my edits?? If I put the backup in the current folder? I added no new edits since I backed up and I was wondering if that would work but have been too cautious to take other steps yet.

I have no problem waiting and I can work on another project in the meantime, but I have doubts that the project .tracktion file is actually XML and that this is necessarily related. Still quite hopeful and patient. It might not even be that difficult! I just don't want to mess things up moving files around to check, haha. (For example, one time I lost some game mods while pasting/moving gaming files and that was just for fun/gaming, this is so important that I'm being extra cautious, haha, and also trying to stayyy caaaalm, heh.

---

BTW, to answer Peter's questions; the project has several edits, with everything but midi (I don't use, or at least create my own midi). It's almost finished, so it has just about everything else. (And I do have backups from another date.)

I don't think this is relevant, but I'm not sure what you mean by "track recordings." I didn't record in that session, just worked with things I recorded in the last session. All the recordings are definitely preserved in wave files and backed up. If you mean tracks, or anything else, I didn't create new ones, just replaced some wave files from an older session, etc. It's a fairly sizable, nearly complete, project with loads of tracks and several edits (and most of it was backed up elsewhere).

I just think that most of this is extra information, because you probably thought I meant I couldn't open the edit (/file) but I actually couldn't open the project (/file). This might seem worse at first, but hopefully it's not nearly that bad!!

BUT I wanted to respond to all your questions and such.

---

Sorry if this post is also too wordy! Hahah. ;D

Have excellent holidays!!! Thanks for taking the time to read and reply. <3

[jabe]

The .trkedit files are probably the equivalents of the .tracktionedit files of more recent releases. If you know HTML and XML, you'll know how to balance them up if anything has gone astray. A trek through a few of those will tell you all you need to know about the hierarchy and most of the possible contents. I did fix a broken .tracktionedit file for one of our other users a few years back, so sometimes those do get broken. Probably worth your while checking all your .trkedit ones, even if you just make sure the opening tag is closed at the end of the file.

It sounds like you're more computer savvy than most, which aways helps and, as for your .tracktion file, I'd say yes - very likely to be your best chance. Do rename or back up the broken one, just in case, although I'm not sure how much help I could be with fixing that one. I think those are just binary files with whatever T5 wanted to store at the time, and without the structure of XML or anything else standard.

One more thing - back up all the .trkedit files as well. This is in case the restored .tracktion file is missing any edits. You can always add an edit, but doing so might endanger the existing edit file whose data you need to add. Better to overwrite an emptyish .trkedit with a backup than to have an emptyish one overwrite your only copy of a worked on file.

Let us know how you get on.

[ellarah]

Hey, so it turns out when I was optimistic before, I was checking the "main" edit (so I thought) I had been confused by the filenames and was checking a different edit (an older one I kept around in case I changed my mind, heh). It's only have as hopeful a situation now, heh.

The actual main edit (.trkedit - that WAS MOST up to date) I was saving at the time of the blackout, also has the sad, mysterious white space replacing ALL the XML, super-broken-ness as the project file had.

I got the project open by using the backup .tracktion file, placed within the project folder (amid several backups strewn across my system and the cloud, haha).

For now, I have an older version of my main edit in the project folder that is missing the newest changes. I removed the broken file because when I had both in, I couldn't open both, and depending on the file naming the edit was either a bunch of empty tracks or the older backup. (Older backup it is, then!)

So for now it seems I have most of my project, all of my recordings, and seemingly some annoying duplicate re-work to do, and time lost, putting some changes/additions back into place. At least I know exactly what I want, compared to the playing around to find the sound I wanted before. Maybe eventually I'll be optimistic about that, hah.

I can't edit the XML of this edit file because it doesn't have any visible XML (or likely, any at ALL anymore) instead more than 500kb worth of "empty" space. Probably saving while the power went out made something go haywire and add a bunch of "spacebars" over the actual content. That seems odd to me, but more plausible than some code-made-invisible that's fixable. (In my mind I had a prayer that some sort of invisibilizing happened that I could un-do. Oh well, hah.)

Does this sound like anything you might have heard of?

Anyway, I think I'll focus more on my #2 WIP and then head back into this song. That will ease the frustration of repeating some work, so I won't mind AS much. :\

Thanks for your help. I doubt there's anything anyone can do for the emptied edit, but let me know, haha.

[jabe]

I'm afraid your view of the corrupted .trkedit file is one I've seen before, or certainly similar. If there is some XML, it might be possible to rescue some tracks. The likelihood is that there is a point somewhere in a corrupted file - possibly at the very beginning, but perhaps somewhere later - where the content changes from being real data to being unusable. If this happens part way through data for a track, it might be possible to add closing tags to that track and to the whole file to make some of the data usable again. Some tracks might be lost, and, probably, the last with any real data might have to be cut down somehow to make what remains usable.

In your case it sounds, as you say. like the whole .trkedit file is unusable, leaving you the option to rebuild it as best you can from the recorded files you still have. I hope it goes well when you come to it.

You could find a hex editor to open your file with, but if even the earliest characters in it are unreadable, then all its data is lost.

The answer, as always, is to take copies of our work, but so many - myself included - rarely do.

[ellarah]

I'm working from the backup I have. I just had to re-comp (re-build) the most recent recordings, and next re-build them into the mix.

I did lose the transition after the bridge, which I can't really remember now, but I'll build it/one again after I have it mostly finished. I have more information to go on now (the vocals in the bridge). Ah well!

I try to be good with backups and such. I'll probably be better now.

[jabe]

I'm glad that all was not lost. While reading through your posts in the thread, something occurred to me that might be of use to you another time. If I have a file that I want to keep but not move elsewhere, perhaps if I'm about to replace it, I'll just add an extra character to the file suffix so the software will ignore it. Changing a suffix to .trkedit2 means you can get back to its contents but T5 (or whatever) won't try to open it. In Windows Explorer and other places, F2 is the shortcut to rename a highlighted file name.

[TolmwN]

I did have an idea that I could either write a program to fix files as well as it might, or to write a tutorial so that people can fix their own, but unfortunately I have other pressing priorities at the moment. If you can't get into the project at all, I'll have some time after new year if you want to send it for me to take a look. I can explain to you what I've done.

Hello jabe! I've seen you replying to other such posts and you seem pretty knowledgeable on the subject, so I thought of asking for your help.
I am facing a similar problem and I fear I may have lost a lot of work, which is a huge disappointment, even though I am still hoping.

My problem is with Waveform 12. It all happened one day after trying to open my last edit, and while there had been no problems at all when I saved and closed it. Now I'm trying to open this last edit, as well as any of the approx. last 20 saved edits before it, and all of them just load for a minute and then they crash before opening, displaying the message "Audio Engine Crashed". Edits older than these do load and open without problems.
(I am suspecting there might be a problem with Melodyne as it was the last plugin I introduced to the edit and had I used it on some Audio Files within the project which I have moved around and deleted from my PC since then. So am trying to find a way and disable this plugin (or any other plugin) BEFORE opening the edit, but I don't think there's a way to do that, unless there is and I can't figure it out.)

By now I have tried increasing the buffer size, turning sandbox on/off, updating the program etc...
Now I'm trying to do what you mentioned, fix the XML, but I am very unfamiliar with such concepts so I have no idea what I need to do.
Any instruction or tip regarding this or any other solution you might have in mind would be greatly appreciated.

If you can actually help and it's not a hassle, could you please DM me or tell me how to DM you so we can communicate through email or some other platform because communicating through the forum's comments seems very inconvenient to me?
In fact, I have just made this account right now only to ask for help, and it's my first ever time commenting on a forum.
I'm not even sure if I'm successfully replying to your comment right now or not tbh. I hope you'll be notified of my comment.
Thanks in advance for your time!

[jabe]

I did have an idea that I could either write a program to fix files as well as it might, or to write a tutorial so that people can fix their own, but unfortunately I have other pressing priorities at the moment. If you can't get into the project at all, I'll have some time after new year if you want to send it for me to take a look. I can explain to you what I've done.

Hello jabe! I've seen you replying to other such posts and you seem pretty knowledgeable on the subject, so I thought of asking for your help.
I am facing a similar problem and I fear I may have lost a lot of work, which is a huge disappointment, even though I am still hoping.

My problem is with Waveform 12. It all happened one day after trying to open my last edit, and while there had been no problems at all when I saved and closed it. Now I'm trying to open this last edit, as well as any of the approx. last 20 saved edits before it, and all of them just load for a minute and then they crash before opening, displaying the message "Audio Engine Crashed". Edits older than these do load and open without problems.
(I am suspecting there might be a problem with Melodyne as it was the last plugin I introduced to the edit and had I used it on some Audio Files within the project which I have moved around and deleted from my PC since then. So am trying to find a way and disable this plugin (or any other plugin) BEFORE opening the edit, but I don't think there's a way to do that, unless there is and I can't figure it out.)

By now I have tried increasing the buffer size, turning sandbox on/off, updating the program etc...
Now I'm trying to do what you mentioned, fix the XML, but I am very unfamiliar with such concepts so I have no idea what I need to do.
Any instruction or tip regarding this or any other solution you might have in mind would be greatly appreciated.

If you can actually help and it's not a hassle, could you please DM me or tell me how to DM you so we can communicate through email or some other platform because communicating through the forum's comments seems very inconvenient to me?
In fact, I have just made this account right now only to ask for help, and it's my first ever time commenting on a forum.
I'm not even sure if I'm successfully replying to your comment right now or not tbh. I hope you'll be notified of my comment.
Thanks in advance for your time!

Hi TolmwN

I've tried to PM you, but I'm getting a message that says "Some users couldn’t be added as they do not have permission to read private messages." I'm wondering if this relates to how new you are on KVR and whether it might change in the next few days. I'll try more times in the next few days just in case this is a New User Restriction.

Do you know about the log file? If you can open Waveform with one of your older edits, then click Help, the final option will allow you to look at the log file. It will show message from when you started Waveform and you'll be able to see assorted messages each time you had the Audio Engine Crashed message, as well as each time you didn't. It might give you more clues. I suspect if the loading got as far as that message then your .tracktionedit file should be intact, but it is a while since I looked at similar problems, so I might be remembering wrongly.

It's just occurred to me that looking at your .tracktionedit in a web browser might help. Firefox has File in its menu and Edge and Chrome will bring up a file opening thingy is you press Ctrl and O. As long as the last line shown when your file loads is </EDIT>, the file was no corrupted.

We should be able to work out how to remove either a misbehaving plug-in or temporarily remove a track that contains such a plug-in by turning its data in the file into a comment.

Anyway, I'll keep trying to message you, and if we can sort that, you can send me one of your tracktionedit files and I'll see if I can persuade it to behave and/or get an idea why it's not happy.

Jabe

[TolmwN]

Hi TolmwN

I've tried to PM you, but I'm getting a message that says "Some users couldn’t be added as they do not have permission to read private messages." I'm wondering if this relates to how new you are on KVR and whether it might change in the next few days. I'll try more times in the next few days just in case this is a New User Restriction.

Do you know about the log file? If you can open Waveform with one of your older edits, then click Help, the final option will allow you to look at the log file. It will show message from when you started Waveform and you'll be able to see assorted messages each time you had the Audio Engine Crashed message, as well as each time you didn't. It might give you more clues. I suspect if the loading got as far as that message then your .tracktionedit file should be intact, but it is a while since I looked at similar problems, so I might be remembering wrongly.

It's just occurred to me that looking at your .tracktionedit in a web browser might help. Firefox has File in its menu and Edge and Chrome will bring up a file opening thingy is you press Ctrl and O. As long as the last line shown when your file loads is </EDIT>, the file was no corrupted.

We should be able to work out how to remove either a misbehaving plug-in or temporarily remove a track that contains such a plug-in by turning its data in the file into a comment.

Anyway, I'll keep trying to message you, and if we can sort that, you can send me one of your tracktionedit files and I'll see if I can persuade it to behave and/or get an idea why it's not happy.

Jabe

Hello again, Jabe!
Thanks for responding so quick, honestly this whole situation is upsetting so getting direct support is very encouraging.

I just checked the reason why neither you or me could PM. This is what the Forum says:
"You are not authorised to read private messages. Private Messages are not currently available for members who have fewer than 2 posts in the forum."
So yeah, you were kinda right, that's what the problem was with that.

Regarding my edits' crashing problem, I opened the edit file in Chrome as you instructed, I scrolled down and the last line is indeed </EDIT>. If this truly shows that the file is not corrupted then it's a huge relief!

As for the Log File, I did access it through the settings on the program's main menu as I don't need to load any project to access it.
By the way, I went back and forth and attempted several times (all of them crashing) to launch some of the edits that keep failing just so the info can be included in the Log File anew.
I can't tell if the message you are referring to (which needs to be there for the edit to be intact) is included or not. As I said I'm pretty unfamiliar with such subjects.
In general I saw mentions like "crashed", "crash report created", "crash location: .... ", "Last run failed to shut down cleanly" and such.
Can you make anything of that?

Thanks again for your time and effort. It really means a lot!

(Update: BTW, PM is now available I think, so comments were enough to unlock it, they're considered "posts" too)

[jabe]

Hi TolmwN

I'm pleased to hear your file is intact.

The next step is to try to work out which track is causing the problem.

To do this, I'm going to get you to make changes to your .tracktionedit or .trkedit file. Before you do any editing at all, you need to copy the file somewhere safe and never edit that copy at all. You can copy from it into your project folder to replace an edited version, if necessary.


You've suggested that you're not technical (and other non-technical people will probably read this), so I'm going to briefly explain a common term from programming/coding. It's called "commenting out". If there is some code that you want to exclude, either temporarily or permanently, the code can be commented out. That simply means that the text of the code is still there, but it has been turned into a comment which will be ignored by the software that processes the file. A comment is usually some sort of helpful message to future programmers/coders. Sometimes a programmer might want to include a variation on a piece of code as a one-off and change it back after running the changed version. In this case the line would be copied, made into a comment, and the copied version would get altered. After running it like that, the new line could be deleted and the commenting of the original line removed to put it all back to how it was.


You mentioned that you suspect the track with Melodyne in it might be causing the problem, so we're just going to comment that whole track to start with.

As far as XML goes, there are tags within tag pairs (start tags and end tags). A tag pair for a Waveform track begins with a <TRACK> tag (that usually carries more parameters) and ends with a </TRACK> tag.

[Note - some tags contain their own ends like this: <TAGNAME parameters /> ]


A basic unchanged track within our file might look like this:

<TRACK id="1030" midiVProp="0.28125" midiVOffset="0.359375" colour="ff00ffaa">
<MACROPARAMETERS id="1031"/>
<MODIFIERS/>
<PLUGIN type="volume" id="1032" enabled="1">
<MACROPARAMETERS id="1033"/>
<MODIFIERASSIGNMENTS/>
</PLUGIN>
<PLUGIN type="level" id="1034" enabled="1">
<MACROPARAMETERS id="1035"/>
<MODIFIERASSIGNMENTS/>
</PLUGIN>
<OUTPUTDEVICES>
<DEVICE name="(default audio output)"/>
</OUTPUTDEVICES>
</TRACK>

The stuff between the two track tags is only relevant to us at the moment because it contains tags that tell us about the PLUGINs on the track. If you have a read through your file you should be able to work out which one has the Melodyne plug-in.

I'm going to illustrate commenting out using the track code from above, but I'll remove the stuff in the middle to unclutter things.

We have this:

<TRACK id="1030" and various parameters>
...
</TRACK>

I want you to insert two blank lines before this code and two more after it (One of each is to make it plain where the changes are going and isn't strictly necessary).

On the empty line immediately before the <TRACK ...> tag, add this:

<!--

and on the one after the </TRACK>, add this:
-->

So you have

<!--
<TRACK id="1030" and various parameters>
...
</TRACK>
-->

These additions (which might sometimes be seen on one line, such as <!-- this is a comment --> ) have turned all the code in between into a comment. Our track details will now be treated as a comment instead of code for an actual track.

Be careful not to edit anything else. Save the file after your edit and see if you can open it in Waveform without the Tracktion Engine failing.


If the Tracktion Engine fails again, try to comment out other tracks. You can comment out more than one track at a time, just by moving the <!-- to before an earlier track or the --> to after a later track, or by adding them both around another track or group of tracks. You should be able to narrow the problem down to one track.

I've just done this to one of my files and it does the trick, stopping the commented out tracks appearing in Waveform when it's next opened.


Ultimately, once you've identified the track with the problem, you can try just commenting out the relevant <PLUGIN> tags. This should allow you to keep the rest of the track details and not lose anything else.


Good luck with it and let us know how it went.

jabe

[Watchful]

Jabe, not to confuse TolmwN, but assuming this fixes the problem, we could recommend commenting out the <PLUGIN> </PLUGIN> reference to Melodyne. That way, we don't lose the work in the track itself--it just disables the Melodyne plugin.

Again, I'd recommend this as a second step as it's a little more work, as your suggestion is an easier, broader fix.

[TolmwN]

Hi TolmwN

I'm pleased to hear your file is intact.

The next step is to try to work out which track is causing the problem.

To do this, I'm going to get you to make changes to your .tracktionedit or .trkedit file. Before you do any editing at all, you need to copy the file somewhere safe and never edit that copy at all. You can copy from it into your project folder to replace an edited version, if necessary.


You've suggested that you're not technical (and other non-technical people will probably read this), so I'm going to briefly explain a common term from programming/coding. It's called "commenting out". If there is some code that you want to exclude, either temporarily or permanently, the code can be commented out. That simply means that the text of the code is still there, but it has been turned into a comment which will be ignored by the software that processes the file. A comment is usually some sort of helpful message to future programmers/coders. Sometimes a programmer might want to include a variation on a piece of code as a one-off and change it back after running the changed version. In this case the line would be copied, made into a comment, and the copied version would get altered. After running it like that, the new line could be deleted and the commenting of the original line removed to put it all back to how it was.


You mentioned that you suspect the track with Melodyne in it might be causing the problem, so we're just going to comment that whole track to start with.

As far as XML goes, there are tags within tag pairs (start tags and end tags). A tag pair for a Waveform track begins with a <TRACK> tag (that usually carries more parameters) and ends with a </TRACK> tag.

[Note - some tags contain their own ends like this: <TAGNAME parameters /> ]


A basic unchanged track within our file might look like this:

<TRACK id="1030" midiVProp="0.28125" midiVOffset="0.359375" colour="ff00ffaa">
<MACROPARAMETERS id="1031"/>
<MODIFIERS/>
<PLUGIN type="volume" id="1032" enabled="1">
<MACROPARAMETERS id="1033"/>
<MODIFIERASSIGNMENTS/>
</PLUGIN>
<PLUGIN type="level" id="1034" enabled="1">
<MACROPARAMETERS id="1035"/>
<MODIFIERASSIGNMENTS/>
</PLUGIN>
<OUTPUTDEVICES>
<DEVICE name="(default audio output)"/>
</OUTPUTDEVICES>
</TRACK>

The stuff between the two track tags is only relevant to us at the moment because it contains tags that tell us about the PLUGINs on the track. If you have a read through your file you should be able to work out which one has the Melodyne plug-in.

I'm going to illustrate commenting out using the track code from above, but I'll remove the stuff in the middle to unclutter things.

We have this:

<TRACK id="1030" and various parameters>
...
</TRACK>

I want you to insert two blank lines before this code and two more after it (One of each is to make it plain where the changes are going and isn't strictly necessary).

On the empty line immediately before the <TRACK ...> tag, add this:

<!--

and on the one after the </TRACK>, add this:
-->

So you have

<!--
<TRACK id="1030" and various parameters>
...
</TRACK>
-->

These additions (which might sometimes be seen on one line, such as <!-- this is a comment --> ) have turned all the code in between into a comment. Our track details will now be treated as a comment instead of code for an actual track.

Be careful not to edit anything else. Save the file after your edit and see if you can open it in Waveform without the Tracktion Engine failing.


If the Tracktion Engine fails again, try to comment out other tracks. You can comment out more than one track at a time, just by moving the <!-- to before an earlier track or the --> to after a later track, or by adding them both around another track or group of tracks. You should be able to narrow the problem down to one track.

I've just done this to one of my files and it does the trick, stopping the commented out tracks appearing in Waveform when it's next opened.


Ultimately, once you've identified the track with the problem, you can try just commenting out the relevant <PLUGIN> tags. This should allow you to keep the rest of the track details and not lose anything else.


Good luck with it and let us know how it went.

jabe

I can't thank you enough my friend, this worked like a charm!
I managed to identify the track with the problem immediately (it was indeed the track with Melodyne in it) and so I only need to comment out that specific track from the edit.

For some reason, however, when I try to exclude the plugin separately using the same method to keep the rest of the track intact, it doesn't work. What I do is I insert the <!-- and --> symbols before and after <PLUGIN and </PLUGIN> respectively but then when I load the file it crashes.
I'm not sure if I'm doing something wrong, but to be honest it's a tiny problem for me at the moment compared to how much progress I would've lost if I hadn't managed to open the edit at all, so I don't bother.

What I'm going to do now is create a new project and try to copy all of the original project's contents in there for a fresh start, just to be safe from the original's faultiness while still maintaining the progress.
Is that a good idea or simply staying in the original edit would be fine enough?
And if so, what should I do with the commented out track from now on, leave it as it is?
You mentioned something about transferring (content?) from the copied edit I made at the beginning before the XML process.
Is that related?

In any case, if we can also pinpoint why commenting out the plugin didn't work it might benefit, except from me, others who face similar problems in the future.

So, what I thought is this:
The problematic track was a track containing only audio files, not midi or step clips.
It had Melodyne loaded on it, both as a VST plugin/effect, which was used on some of its audio files, AND Melodyne as a time-stretching tool as well, which was used on others.

Could it be that it's not the Melodyne plugin/effect that kept causing the crash, but the Melodyne stretching tool? If so, I didn't manage to identify it in the XML (though, as I said I did identify the plugin/effect, and commenting it out didn't prevent the crash).
Do you have any idea how it should look like and how I can disable it?
Also do you suspect any other possible reason why commenting out the plugin didn't work?