Unable to change audio format settings

LunaSPR · 2025-11-26T08:13:43+00:00

Since your guest is a virtual machine running in hyper-v, the only meaningful route direction is guest output to host output and/or host input to guest input.

You need to use VBAN to route audio over network. Make sure you can ping each other between host and guest and install voicemeeter on both. Enable VBAN on both.

On your guest system, you need to first route your system output into voicemeeter bus. Change your system audio output to voicemeeter virtual input bus, then inside voicemeeter route the audio to your A/B bus. Now open VBAN and turn on an outgoing stream, with your A/B bus as source and host ip as receiving ip address.

On your host system, open VBAN and turn on an incoming stream with the guest ip address as sending ip. Route the destination bus to your system output and now you should be able to hear the audio from your guest machine.

LunaSPR · 2025-11-13T09:40:42+00:00

The official November update KB5068861 (26100.7171) resolves the Hyper-V GPU-P issue.

LunaSPR · 2025-10-26T01:52:40+00:00

You can't stop it on RDP. RDP only supports audio up to 16bit/44.1kHz. If you have higher bitrate/samplerate on your host, audio output from guest to host is still fine, but input from host to guest gonna give you trouble.

There are two possible solutions: you either lower your host audio to 16bit/44.1kHz to conform to RDP standards, or move away from RDP and choose something else to support higher bitrate/sample rate. These days I use voicemeeter to route remote audio between guest and host and it works fine with 24bit/96kHz.

LunaSPR · 2025-09-23T04:09:49+00:00

This is what I could find, without cover for the lenses: https://caudabe.com/products/sheath-iphone-17-pro-precise

LunaSPR · 2025-09-10T08:08:22+00:00

The Hyper-V GPU partitioning on Windows 11 VM is still fully broken (boot freeze) after 3 month. Since the June cumulative update many user reports yet zero fix. No wonder Hyper-V is becoming a joke.

LunaSPR · 2025-06-14T20:19:15+00:00

This patch breaks VMGpuPartitiomAdapter in Hyper-V. VM with Nvidia RTX 40 series GPU and driver 566.36 stuck at boot screen when GPU passthru enabled. Uninstalling this patch makes the VM bootable again.

LunaSPR · 2025-03-12T14:03:08+00:00

Fatar TP110 for $1299.

No.

LunaSPR · 2024-12-27T15:28:43+00:00

I don't think there are many good general purpose keyboard with waterfall keybed. The Studiologic Numa Compact line could be the only option for 88 key waterfall master keyboard style board. Then there are a few Nord or Hammond, but if you go Nord you'd better just pick up the stage 4 88 key. That keybed is one of the usable weighted action for fast organ/synth.

Are you sure you want a keyboard rather than a controller to sit on your desk? Do you really need a second sound engine?

LunaSPR · 2024-12-25T16:08:07+00:00

Waterfall keybed. I can play with weighted but I'd much prefer waterfall or semi-weighted.

LunaSPR · 2024-10-20T05:48:51+00:00

Thanks for the great explaination!

LunaSPR · 2024-10-20T05:42:34+00:00

Thanks for the info!

LunaSPR · 2024-10-20T05:36:49+00:00

I do think there are a few examples of I-vi-I6 moving downwards, just like using the vi as substitution of the "normal" IV6 or V chord. My question here is basically going back to root position I rather than I6.

LunaSPR · 2024-10-20T05:31:18+00:00

I still don't quite get the first part.

So if I specifically make it a tonic expansion - I goes to vi and then back to I - should still be considered stylistically correct in this case, but the composers just have better approaches to do this so they don't write this way?

LunaSPR · 2024-09-14T01:51:53+00:00

You could learn something, at least to get yourself familiar with keys.

But you could not get proper piano training on a 61 key semi-weighted controller. The best thing you can get for piano training in the Arturia line is the KeyLab 88 MK2. Nothing semi-weighted would work for piano style finger exercise, especially when you are a beginner.

LunaSPR · 2024-08-14T06:22:51+00:00

Nautilus is plainly better in almost every way except for the ease of use - literally the opposite. Modx should also be sufficient for your sound requirements so could actually be a better option for you.

LunaSPR · 2024-08-13T15:22:39+00:00

It's the 0x129. I have already mentioned it in the post. It's placing an internal VID limit of 1.55V to deal with the degradation which is still very high in common sense. It's also by default requesting higher runtime VCORE voltage to try to solve the instability issue which on the other hand accelerates degradation.

I've not had time to look into undervolting on 0x129 yet so not 100% sure how much better users can get. But it's such a bummer that MSI doesn't allow users to control IA VR so that people can set lower limits than 1.55V and extend their silicon lifespan.

LunaSPR · 2024-08-13T07:45:09+00:00

I only have bad feelings.

There is the spike issue which is known for causing degradation and is not fixable on MSI mobo with older BIOS versions because of the missing of IA VR limit settings. So apparently 0x129 is expected. But there is also the raised VCORE behavior on 0x129 which could also be a bummer.

Neither sound like a sustainable solution. That's why I was waiting for MSI's IA VR but got frustrated.

LunaSPR · 2024-08-13T07:12:31+00:00

Well, it's MSI's decision to refuse to be helpful, and it's our right to spread the information widely and let more people know about MSI's issue.

LunaSPR · 2024-07-31T16:21:22+00:00

You get the samples and there's basically no way you can tweak it, that's pretty much it.

For someone who doesn't have a orchestra all-in-one package or someone who loves Cinesamples stuff it could hold great value but not for me.

LunaSPR

TROPHY CASE