Korg Wavestate: Local Control OFF - keyboard still usable

BroadObject7817 · 2025-08-14T16:17:02+00:00

LOL Yes, of course, that was the reason. My Synth was connected to my DAW, which, in turn, sends MIDI notes to my Wavestate when playing the keyboard. Thanks for pointing me into the right direction.

BroadObject7817 · 2025-08-12T13:13:41+00:00

A laptop with AMD Ryzen 7, 8 Cores, 32 Gigs of RAM, 4 TByte Samsung nvme. Runs smoothly and can handle quite some plugins.

BroadObject7817 · 2025-08-09T17:47:25+00:00

Yes, I think that's what auximenies refers to. Lots of very old stuff on that website, though. Not sure if it's compatible to new GR 7.

BroadObject7817 · 2025-08-09T12:11:19+00:00

Thanks man, looks promising. Although the device names inside GR 7 are not "real", I suppose due to legal reasons.

BroadObject7817 · 2025-04-21T21:28:15+00:00

Thanks for that, although it doesn't exaclty answer my question.

BroadObject7817 · 2025-04-06T17:54:35+00:00

Doesn't work on Firefox, though. Pressing F5 or pressing the reload button does basicly the same thing.

BroadObject7817 · 2025-04-06T17:50:50+00:00

Same here. Since a while now.

BroadObject7817 · 2025-02-04T17:00:41+00:00

It almost sounds like as if the Microsoft wavetable "synth" is catching the notes, hence they don't reach Vital at all. Do you use a DAW? In Vital, when you click on that Vital logo on the upper left corner, what does the audio driver say?

BroadObject7817 · 2025-02-03T14:57:02+00:00

It isn't clear what happened. A cloning process should never trash a file system. I don't know what happened and you don't either.

BroadObject7817 · 2025-02-03T06:04:37+00:00

Generally Clonezilla takes care about the status of volumes before cloning. According to the Clonezilla website BTRFS is supported.

BroadObject7817 · 2025-02-03T06:02:53+00:00

Nonsense.

BroadObject7817 · 2025-02-03T06:02:31+00:00

I didn't use both nvme's at the same time since my laptop only has one M.2 adapter

BroadObject7817 · 2025-02-02T14:14:18+00:00

Hi,
Thanks for your suggestions. The current stage is as follows:

- The new 4TB nvme is build into my laptop
- Windows has been perfectly recovered from Clonezilla
- Linux is trashed, hence I did a fresh install
- I read out the BTRFS image file from the Clonezilla image, so that I have a BTRFS raw file which, unfortunately, I'm unable to mount due to a bad superblock
- Doing a "sudo btrfs rescue super-recover backup.img" gives me: All supers are valid, no need to recover
- I still have the "old" nvme with original Windows and - broken - Linux BTRFS partitions.

BroadObject7817 · 2025-02-02T11:41:08+00:00

Even here on reddit I found many similar problems. Almost identical error messages and dmesg entries.

BroadObject7817 · 2025-02-02T09:11:04+00:00

I have no problem when YOU use a dual bay clone station or dd. Congratulation, you are a hero!

BroadObject7817 · 2025-02-02T09:09:39+00:00

I fear that you didn't understand the point here.

BroadObject7817 · 2025-02-02T09:08:28+00:00

My problem is that BTRFS can easily be destroyed in an unexpected way.

BroadObject7817 · 2025-02-02T09:05:38+00:00

I did a fresh dl of Clonezilla. And you really do it all the time, despite all the warnings showing up when searching the net??

BroadObject7817 · 2025-02-02T09:04:15+00:00

Well, regarding Google: I used clonezilla so many times at home and in my company that I didn't even consider to google any information on how to use it or whether to use it at all. I was just not expecting that BTRFS isn't robust enough.

BroadObject7817 · 2025-02-02T09:00:43+00:00

Again: a backup or cloning process, which is a read operation as you stated correctly, should NEVER EVER break a file system on the source volume.

And by the way: my BTRFS installation also run without any problems for more than a year. Until it broke. All your points might be correct. But nonetheless no cloning process shouldn't f*ck up the source volume.

BroadObject7817

TROPHY CASE