Two Strange Vibelink Bugs

At least with my Vibe+Ultra, I've never once encountered the same issue you're having.

Are you controlling Vibe's power using the WiiM app? If not, you also have the option to hide Vibe from the WiiM app. By denying the WiiM app's "Nearby Devices" permission, the WiiM app will no longer connect to Vibe via Bluetooth.
The bug #2 just happened again a moment ago. Ultra and Vibelink both show COAX as output/input, but there is no sound. Other inputs of the Vibelink are not used. Switching the Ultra (!) to Line In and back solves the problem. Yes, I control power of the Vibelink with the app. So I can switch it off without standby time. And perhaps #2 is a bug of the Ultra and not the Vibelink.
 
The bug #2 just happened again a moment ago. Ultra and Vibelink both show COAX as output/input, but there is no sound. Other inputs of the Vibelink are not used. Switching the Ultra (!) to Line In and back solves the problem. Yes, I control power of the Vibelink with the app. So I can switch it off without standby time. And perhaps #2 is a bug of the Ultra and not the Vibelink.
Would you mind trying my earlier suggestion? (If you have the trigger cable, please use that.)

If the bug you mentioned "Bug 2" is related to "Bug 1", disconnecting the Bluetooth connection for the Vibe to WiiM app may help work around the issue. And please also try the optical connection, as already suggested.

Even if this is a firmware bug, it's unclear when it might be fixed, so I'm proposing workarounds.
 
Would you mind trying my earlier suggestion? (If you have the trigger cable, please use that.)

If the bug you mentioned "Bug 2" is related to "Bug 1", disconnecting the Bluetooth connection for the Vibe to WiiM app may help work around the issue. And please also try the optical connection, as already suggested.

Even if this is a firmware bug, it's unclear when it might be fixed, so I'm proposing workarounds.
It seems to me after the latest occurrence, bug#1 is not related to bug#2.
 
The bug #2 just happened again a moment ago. Ultra and Vibelink both show COAX as output/input, but there is no sound. Other inputs of the Vibelink are not used. Switching the Ultra (!) to Line In and back solves the problem. Yes, I control power of the Vibelink with the app. So I can switch it off without standby time. And perhaps #2 is a bug of the Ultra and not the Vibelink.
i think the problem is with the Vibelink: before I got it, I used the optical output with Ultra with an external DAC (had ground loop noises with RCA outputs so just had to use an external DAC) and it never once had this issue.
Currently with the Ultra+Vibelink connected on optical, it happens every now and then but not too much. maybe the COAX input on the Vibelink is causing its DAC to "go nuts & go silent" more often
 
Would you mind trying my earlier suggestion? (If you have the trigger cable, please use that.)

If the bug you mentioned "Bug 2" is related to "Bug 1", disconnecting the Bluetooth connection for the Vibe to WiiM app may help work around the issue. And please also try the optical connection, as already suggested.

Even if this is a firmware bug, it's unclear when it might be fixed, so I'm proposing workarounds.
Many of us seem to be suffering from bug 2.... I've been in conversation with support a few times about it, followed all suggestions no matter how mad they seem! Including using line in as well as coax, I'm using a trigger cable and makes zero difference along with any suggestion from support....
I'm suspicious why none of the team have commented since they have been tagged a few times... The only way to solve the issue when it happens is to reboot the ultra... Then it happens again so not a real solution...
 
What would be useful is if anyone reading this thread that doesn't have a vibe amp and ultra combination and still suffers bug 2 using the ultra plus something else...
 
Many of us seem to be suffering from bug 2.... I've been in conversation with support a few times about it, followed all suggestions no matter how mad they seem! Including using line in as well as coax, I'm using a trigger cable and makes zero difference along with any suggestion from support....
I'm suspicious why none of the team have commented since they have been tagged a few times... The only way to solve the issue when it happens is to reboot the ultra... Then it happens again so not a real solution...

Strangely enough, I have all Ultra outputs (Coax, Opt, Line) connected to my Vibe, yet I've never experienced audio cutting out during playback on any input.

If this were a firmware bug, all Vibe users would likely be experiencing the same issue, but for now it seems to occur only on some users' devices. It's puzzling...

I'd like to ask you something: Does this issue occur multiple times a day?

Also, could you connect a device other than the Ultra to the Vibe to see if the same issue occurs?
(Unfortunately, I can't test this since I can't reproduce the issue on my Vibe...)
 
Strangely enough, I have all Ultra outputs (Coax, Opt, Line) connected to my Vibe, yet I've never experienced audio cutting out during playback on any input.

If this were a firmware bug, all Vibe users would likely be experiencing the same issue, but for now it seems to occur only on some users' devices. It's puzzling...

I'd like to ask you something: Does this issue occur multiple times a day?

Also, could you connect a device other than the Ultra to the Vibe to see if the same issue occurs?
(Unfortunately, I can't test this since I can't reproduce the issue on my Vibe...)
It's not really cutting out as such it just stops output to main speakers but the sub carries on playing until a ultra reboot...
Never known it happen more than once a day, but usually give up soon after it happens out of frustration...
Sadly I can't test it as I sold my old amp a few days ago, that's why I posted if anyone has seen this happening not using a vibe amp please speak up...
Edit,.., Since it's multiple users this is happening to i think we need an update from @WiiM Team i presumed it was only happening to me before this thread appeared..
I have multiple tickets as when it happens Edan asked me to raise a new one each time...
 
It could sound as a SPDIF loose of synchronization. This can happen due to several reasons. This includes bad (too long) cables, external noise or sample rate mismatch.

For the sample rate mismatch, maybe the Ultra changes sample rate without the Vibelink is noticing it?

I have been running my Ultra out to external devices (wireless hub and DAC) on both Coax and Optical for more than a year and never seen this issue.
 
It could sound as a SPDIF loose of synchronization. This can happen due to several reasons. This includes bad (too long) cables, external noise or sample rate mismatch.

For the sample rate mismatch, maybe the Ultra changes sample rate without the Vibelink is noticing it?

I have been running my Ultra out to external devices (wireless hub and DAC) on both Coax and Optical for more than a year and never seen this issue.
I'm using all original cables apart from coax which is a audioquest forest Digital coaxal cable 1.5m
Edit... for reference one of these
 
Last edited:
When you have the issue, check it by removing the cable and reinserting it, instead of changing the output of the Ultra. If the sound comes back when the cable is inserted, it's very likely a synchronization issue.

I would try another cable short cable.
Changing the source does nothing hgo the mains remain silent, the only solution is to reboot the ultra.. Shorter than 1.5 meter (i think it may have been the shortest available)? Sadly I only have that one cable for coaxial...
It's not happened for a while but I haven't been listening to much music recently, been too busy sadly. Two hours in today and it's still working it seems very random...
 
Changing the source does nothing hgo the mains remain silent, the only solution is to reboot the ultra.. Shorter than 1.5 meter (i think it may have been the shortest available)? Sadly I only have that one cable for coaxial...
It's not happened for a while but I haven't been listening to much music recently, been too busy sadly. Two hours in today and it's still working it seems very random...
The OP said that changing the output to line in and back solved bug #2. So not the same problem then?
 
Back
Top