Failed to parse Config.xml and KeyBindings.xml after every reboot

Help, Support & Bugs
1

Hello, back here with another config problem. This time it happens consistently. The steps to reproducing the problem might be really short because that’s how I reproduced the problem on every boot.

Here are the steps to reproduce the problem:

  1. Open Renoise. At this stage the error will pop up already, but let’s do some testing here.
  2. Since the config will save at program end, close Renoise.
  3. Shut down and boot your computer again. A restart also works.
  4. After the reboot, open Renoise.

When I check both the Config.xml file and KeyBindings.xml file, the contents were empty. I have uploaded both here, even though it might not look like much.
Config.xml (50.3 KB) KeyBindings.xml (165.5 KB) Log.txt (2.4 MB)

I mean, it’s not really a big problem to set the config and keybinds every time after a reboot, but I’m pretty sure there’s gotta be a solution to this.

Thank you in advance.

1 Like
2

So just to get this more clarified…

What you are saying is that you open Renoise, close Renoise, reboot and the Config.xml and Keybindings.xml contain zero bytes?

What I’d first of all do is to make sure Renoise (and the os) is writing the files to the HD/SSD (which is it btw?)

I’d open Renoise, close Renoise (don’t reboot) and check to make sure that there is xml data (and not just zeros) in those .xml files written to the HD/SSD.

If there is I’d then reboot the machine. Once rebooted I wouldn’t load Renoise. I’d check to see if there is still valid xml data in those xml files.

1 Like
3

Oh, no. The files does not seem to contain 0 bytes.

After I closed Renoise, the preferences and keybind data are there just fine.

When I rebooted it and check the files again, however, it seems to only have 00s. The files I uploaded earlier is the result of this step.

4

Uh huh, on reboot (without loading Renoise) the xml files just (magically) zero out (probably reading the files before the reboot out of cache(?)) At the moment if that was happening to me I would suspect bad blocks/broken HD/SSD??

5

Ahh, I see… I’ll have to find a way to check for bad sectors then…

Are permissions playing any role in this, if I may ask?

6

I wouldn’t know, sorry.

7

It’s okay friend

I should look into changing my workstation…

8

This maybe is caused by your anti virus software - when the XML gets marked as spam, dangerous, whatever else? Which anti virus software do you use?

9

For the record, I am not using any antivirus software. I also have Windows Defender disabled.

10

Update: This phenomenon seems to only happen in Renoise, I’m not sure why.

11

This is not an antivirus problem for sure.

12

I get this problem too a lot. I’m not sure what causes it, just happened again. I’ve no antivirus just Windows Defender.

13

https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html

Try to redirect your renoise prefs folder to another place (disk?)

14

Thanks for the reply dude but that is complete gobbledeegook to me as i am an idiot. Ive found the problem and surprise surprise its the waveshells again.Why would they work perfectly and just all of a sudden decide fuck you.

15

VST api is not perfect

16

I don’t even know what that means.Whats an API?

17

API is not the correct word😉
VST sdk is not perfect

1 Like
18

I’m gonna have to get rid of all my waves stuff because its just miserable.Couple of hours ahead of me now uninstalling and reinstalling everything.Probably the last time i’m gonna do it, sick to death of it.

19

I have no problem with WAVES plugins
On my machine It work good

I avoid big registry and OS customization
Windows 10 is ‘locked’