You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Trying to play a mp4 file stored in obsidian vault.
The video plays ok but no sound
To Reproduce
Add a mp4 file in your vault
browse to the mp4
play
video ok, no sound
Expected behavior
Sound should be played and sent to the browser
OS: Ubuntu 22.03 VM, no physical sound card (vmware drivers + pulseaudio on host ok)
Browser latest firefox
Hi, I hope you support this project still, since I found it very useful for my test case, unfortunately audio playback fails, which is blocking.
By the way, /startpulse.sh doesn't exist anymore.
Enabling error logs, I see this every time I try to play a video file with audio: obsidian-remote | [961:0223/173013.413639:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
I have tried to set up pulseaudio on my host as it doesn't have an audio device (simple VM).
Could you please help ?
Thank you
The text was updated successfully, but these errors were encountered:
Describe the bug
Trying to play a mp4 file stored in obsidian vault.
The video plays ok but no sound
To Reproduce
Expected behavior
Sound should be played and sent to the browser
Hi, I hope you support this project still, since I found it very useful for my test case, unfortunately audio playback fails, which is blocking.
By the way, /startpulse.sh doesn't exist anymore.
Enabling error logs, I see this every time I try to play a video file with audio:
obsidian-remote | [961:0223/173013.413639:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
I have tried to set up pulseaudio on my host as it doesn't have an audio device (simple VM).
Could you please help ?
Thank you
The text was updated successfully, but these errors were encountered: