Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qubes appVMs/StandaloneVMs fast speed for youtube playback #1698

Open
TNTBOMBOM opened this issue Jan 26, 2016 · 30 comments
Open

Qubes appVMs/StandaloneVMs fast speed for youtube playback #1698

TNTBOMBOM opened this issue Jan 26, 2016 · 30 comments
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: audio hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@TNTBOMBOM
Copy link

one of the strangest thing im getting atm , all my appVMs r blazing with its speed which it cant be useable for streaming videos.

for e.g:-

youtube videos moving in very high speed in which the connection speed can catch the speed of the video processing so no forward stream.

1------3-----8----10 loading 12------15----18---loading...etc (time in seconds)

also tried to run an audio player inside debian , i cant hear anything and the minutes line is rushing.

i dunno how to reproduce this , or how can i give a useful info to work on.

do u have commands , logs , ...etc i can check and report them back here ?

btw, all the rest r the same even appVMs from fedora-23 = youtube videos cant play normally

only an OLD whonix-WS-appVM & also some old appVMs which r based on fedora 21 the youtube (or any video online) inside them is working good = dont ask me why it just weird i know.

@TNTBOMBOM TNTBOMBOM changed the title debian speed fire up Qubes appVMs speed fire up Jan 26, 2016
@TNTBOMBOM
Copy link
Author

UPDATE 1

not just the appVMs & even the standaloneVMs

and i think something has changed in the last fidora-23 update which poisoned the entire qubes OS with this bug.

hope u participate in helping here urgently guys.

@TNTBOMBOM
Copy link
Author

UPDATE 2

any new whonix-WS , is also infected with this bug. cant watch anything inside the TBB

cross linking

https://forums.whonix.org/t/streaming-videos-inside-the-tbb-not-possible-whonix-qubes-specific/2018

@TNTBOMBOM
Copy link
Author

printscreen1111111111111111111111

^^^^ this one ppl what do u call it ? video line or whatever ....

when i run any video i cant watch it because the red dot (as u c it in the pic) Moving very fast and jumping through seconds from 0 to 3 to 8 to ...etc.

so streaming any video inside Qubes = impossible

@marmarek how can i help u with this to get more info ?

@marmarek
Copy link
Member

Does it happen also with other video players, or just youtube in TBB? How about normal Firefox/Iceweasel? It is running using HTML5, or flash player (try switching to HTML5 if using flash)?

@adrelanos
Copy link
Member

I can confirm, that I also experienced this issue in past. Not enough
information to write a bug report, but hth... Already in R3.0 iirc.
Could be hardware dependent.

The approximate(!) steps to reproduce would be:

Start a browser in AppVM A.
Start a youtube video in AppVM A.
Change dom0 sound settings if you have multiple sound cards and outputs.
Close the browser in AppVM A.
Start a new browser in the [same] in AppVM A.
Now the video might be played super fast.

I could only restore to normal after reboot. AppVM restart did not help.
IIRC

@TNTBOMBOM
Copy link
Author

Does it happen also with other video players, or just youtube in TBB? How about normal Firefox/Iceweasel? It is running using HTML5, or flash player (try switching to HTML5 if using flash)?

as i have mentioned already above and as patrick also said = in all of VMs. firefox or iceweasel or TBB , whonix or not ..etc

@Jeeppler
Copy link

Jeeppler commented Feb 1, 2016

Have you tried to delete your AppVM and create a new one?

@TNTBOMBOM
Copy link
Author

yep i did. and again its not just the appVMs even standealoneVMs (which they r based on fedora-23 or debian-jessie or whonnix-ws/gw templates).

@TNTBOMBOM TNTBOMBOM changed the title Qubes appVMs speed fire up Qubes appVMs/StandaloneVMs speed fire up Feb 1, 2016
@TNTBOMBOM
Copy link
Author

all my appVMs/standaloneVMs r infected witha same speed problem , except one appVMs which is an old whonix-WS. ( i have created new one based on the current template , but it is infected witha same problem).

so a useful thing to do for this issue:-

how can we extract some useful information which may help us from the old WS which is not infected and compare it with an infected WS ? good commands for this i dont really know, but how about u guys ?

*WS = workstation or whonix-workstation.

@marmarek
Copy link
Member

marmarek commented Feb 2, 2016

Check pulseaudio settings in that VM. First of all, check if module-vchan-sink is loaded: pactl list modules, also listing sinks may be useful. Some video players (not sure if youtube is one of them) synchronize playing speed to audio, so if there is something wrong with audio, it would affect playing speed.
Another idea is system clock - does the time in VM is correct?

@TNTBOMBOM
Copy link
Author

well ahm i said good commands to type not good places to check.

so in WS how to do this checkism with commands?

@marmarek
Copy link
Member

marmarek commented Feb 4, 2016

Execute pactl list modules in WS and search for module-vchan-sink. If itsn't there, that may be a source of the problem. If you have the module in place, to the same with pactl list sinks.
As for system clock - simply check date output - does it match the current time (more or less)?

@TNTBOMBOM
Copy link
Author

found the error , its module-vchan-sink (Usage counter: 0)

  • Purple = WS-appvm not infected
  • Orange = WS-appvm infected
  • Green = debian-standaloneVM infected

modules11111111111111111111111111111

  • Fedora-23 appvm = infected

modules2

pactl list sinks= good no difference

date = good no deference

@marmarek
Copy link
Member

marmarek commented Feb 4, 2016

Usage counter should be "0", when idle. But should be "1" (or greater) when playing. You can also check vchan sink state - it should be "RUNNING" when playing. BTW How many sinks you have - there should only one.

@TNTBOMBOM
Copy link
Author

Usage counter should be "0", when idle. But should be "1" (or greater) when playing. You can also check vchan sink state - it should be "RUNNING" when playing.

well then they r all the same (damn thought we got this issue).

BTW How many sinks you have - there should only one.

u mean this command:-

user@host:~$ pactl list sinks
Sink #0
State: RUNNING
Name: vchan_output
Description: Qubes VCHAN sink
Driver: module-vchan-sink.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 4
Mute: no
Volume: front-left: 81920 / 125% / 5.81 dB, front-right: 81920 / 125% / 5.81 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: vchan_output.monitor
Latency: 0 usec, configured 46439 usec
Flags: DECIBEL_VOLUME LATENCY
Properties:
device.string = "vchan_output"
device.description = "Qubes VCHAN sink"
device.icon_name = "audio-card"
Formats:
pcm

so i think these commands they look like all having the same results , do u have more ?

@marmarek
Copy link
Member

marmarek commented Feb 4, 2016

The same - only one. It must be something else...

@TNTBOMBOM
Copy link
Author

hmm well here is a pic of pactl list sinks from

  • Purple = WS-appvm not infected
  • Orange = WS-appvm infected
  • Blue = Fedora-23 appvm infected

modules33333333333333333333333

The same - only one. It must be something else...

well how to check/solve this , if this is the problem ?

@marmarek
Copy link
Member

marmarek commented Feb 4, 2016

Check how that looks during some video playing

@TNTBOMBOM
Copy link
Author

  • Purple = WS-appvm not infected
  • Orange = WS-appvm infected
  • Blue = Fedora-23 appvm infected
  • Green = debian-standaloneVM infected

modules4444444444444444444444444

@marmarek marmarek added T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. P: minor Priority: minor. The lowest priority, below "default." labels Feb 4, 2016
@marmarek marmarek added this to the Release 3.0 updates milestone Feb 4, 2016
@adrelanos
Copy link
Member

I am also experienced this bug.

It happened to me while I tried to get sound to work over (intel audio) hdmi. In pavucontrol Conflagration I have set to Digital Stereo (HDMI 2) Output. (The others were marked as (Unplugged).) Then it started.

After setting it to Digital Surround 5.1 (HDMI 2) Output the video speedup bug stopped and HDMI sound worked. Seems reproducible. Although switching back and forth broke HDMI sound again.

Any more debug output required for this?

@marmarek
Copy link
Member

Take a look at pactl list and compare output between working and not working settings.

@adrelanos
Copy link
Member

pactl list outputs...

diff hdmi_audio_with_audio_lag.txt hdmi_audio_with_video_super_speedup.txt

40c40
<       Usage counter: 1
---
>       Usage counter: 4
227c227,320
< Sink Input #40
---
> Sink Input #42
>       Driver: protocol-native.c
>       Owner Module: 6
>       Client: 40
>       Sink: 0
>       Sample Specification: float32le 2ch 44100Hz
>       Channel Map: front-left,front-right
>       Format: pcm, format.sample_format = "\"float32le\""  format.rate = "44100"  format.channels = "2"  format.channel_map = "\"front-left,front-right\""
>       Corked: yes
>       Mute: no
>       Volume: front-left: 81920 / 125% / 5.81 dB,   front-right: 81920 / 125% / 5.81 dB
>               balance 0.00
>       Buffer Latency: 100000 usec
>       Sink Latency: 0 usec
>       Resample method: copy
>       Properties:
>               media.name = "AudioStream"
>               application.name = "CubebUtils"
>               native-protocol.peer = "UNIX socket client"
>               native-protocol.version = "29"
>               application.process.id = "5617"
>               application.process.user = "user"
>               application.process.host = "social"
>               application.process.binary = "iceweasel"
>               window.x11.display = ":0"
>               application.language = "en_US.UTF-8"
>               application.process.machine_id = "360b0ab67e13483195c906dbc0c08d2f"
>               application.process.session_id = "c1"
>               application.icon_name = "iceweasel"
>               module-stream-restore.id = "sink-input-by-application-name:CubebUtils"
> 
> Sink Input #43
>       Driver: protocol-native.c
>       Owner Module: 6
>       Client: 40
>       Sink: 0
>       Sample Specification: float32le 2ch 44100Hz
>       Channel Map: front-left,front-right
>       Format: pcm, format.sample_format = "\"float32le\""  format.rate = "44100"  format.channels = "2"  format.channel_map = "\"front-left,front-right\""
>       Corked: yes
>       Mute: no
>       Volume: front-left: 81920 / 125% / 5.81 dB,   front-right: 81920 / 125% / 5.81 dB
>               balance 0.00
>       Buffer Latency: 82585 usec
>       Sink Latency: 0 usec
>       Resample method: copy
>       Properties:
>               media.name = "AudioStream"
>               application.name = "CubebUtils"
>               native-protocol.peer = "UNIX socket client"
>               native-protocol.version = "29"
>               application.process.id = "5617"
>               application.process.user = "user"
>               application.process.host = "social"
>               application.process.binary = "iceweasel"
>               window.x11.display = ":0"
>               application.language = "en_US.UTF-8"
>               application.process.machine_id = "360b0ab67e13483195c906dbc0c08d2f"
>               application.process.session_id = "c1"
>               application.icon_name = "iceweasel"
>               module-stream-restore.id = "sink-input-by-application-name:CubebUtils"
> 
> Sink Input #45
>       Driver: protocol-native.c
>       Owner Module: 6
>       Client: 40
>       Sink: 0
>       Sample Specification: float32le 2ch 44100Hz
>       Channel Map: front-left,front-right
>       Format: pcm, format.sample_format = "\"float32le\""  format.rate = "44100"  format.channels = "2"  format.channel_map = "\"front-left,front-right\""
>       Corked: yes
>       Mute: no
>       Volume: front-left: 81920 / 125% / 5.81 dB,   front-right: 81920 / 125% / 5.81 dB
>               balance 0.00
>       Buffer Latency: 100000 usec
>       Sink Latency: 0 usec
>       Resample method: copy
>       Properties:
>               media.name = "AudioStream"
>               application.name = "CubebUtils"
>               native-protocol.peer = "UNIX socket client"
>               native-protocol.version = "29"
>               application.process.id = "5617"
>               application.process.user = "user"
>               application.process.host = "social"
>               application.process.binary = "iceweasel"
>               window.x11.display = ":0"
>               application.language = "en_US.UTF-8"
>               application.process.machine_id = "360b0ab67e13483195c906dbc0c08d2f"
>               application.process.session_id = "c1"
>               application.icon_name = "iceweasel"
>               module-stream-restore.id = "sink-input-by-application-name:CubebUtils"
> 
> Sink Input #46
299c392
< Client #42
---
> Client #45
306c399
<               application.process.id = "5728"
---
>               application.process.id = "5850"

@marmarek
Copy link
Member

I meant pactl list in dom0...

@adrelanos
Copy link
Member

I needed to install pulseaudio-utils beforehand.

sudo qubes-dom0-update pulseaudio-utils

@marmarek
Copy link
Member

Interesting - you have "combine" module enabled. Even more interesting - in cases "with lag" there is no real sound card sink present.
Try disabling "combine" - either unload the module with pactl unload-module module-combine-sink, or disable it in paprefs GUI tool.

@adrelanos
Copy link
Member

Disabled it using paprefs. Fortunately, I do personally not require simultaneous hdmi and analog audio. This helped, no more video super speedup, but still audio lag over hdmi.

@TNTBOMBOM
Copy link
Author

good thing @adrelanos figured it out , actually just turning on/off the built-in audio is giving direct effect on the speed inside the virtual machine.

OFF = normal , ON = hyper-speed .

this problem still exist in Qubes 3.2 fresh installation

@andrewdavidwong
Copy link
Member

This issue is being closed because:

If anyone believes that this issue should be reopened, please let us know in a comment here.

@TNTBOMBOM TNTBOMBOM changed the title Qubes appVMs/StandaloneVMs speed fire up Qubes appVMs/StandaloneVMs fast speed for youtube playback Feb 7, 2022
@TNTBOMBOM
Copy link
Author

TNTBOMBOM commented Feb 7, 2022

This issue is back again with qubes 4.1, This is a video showing whats going on:

cantplay.cleaned.mp4

This is happening in debian 11, fedora 34

  • Semi/Half-Solution

I have upgraded debian to 12 and found out that the video is working with proper speed, But due to this issue #6986 pulseaudio-qubes wont work and by this the solution for video is resolved but for audio not yet.

@andrewdavidwong please reopen.

cc @marmarek i dont think this is a minor issue for new users.

@TNTBOMBOM
Copy link
Author

Found a work around:

  • My current Qubes setup is:

PC has no internal Audio connectivity, Connected to TV by HDMI which from it i can watch and listen.

This is what causes the issue listed above.

To resolve it:

Bring outside headphone/set connect it to your PC, Go to qubes pulseaudio turn OFF the HDMI from the configuration and keep only the connected headphone/set.

Magic! = videos going to work with proper speed

Note: This is not considered solution, New users will suffer and very few will look into a ticket since 2016

@DemiMarie DemiMarie reopened this Feb 7, 2022
@andrewdavidwong andrewdavidwong added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. C: audio hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. and removed P: minor Priority: minor. The lowest priority, below "default." labels Feb 8, 2022
@andrewdavidwong andrewdavidwong added the affects-4.1 This issue affects Qubes OS 4.1. label Aug 8, 2023
@andrewdavidwong andrewdavidwong removed this from the Release 4.1 updates milestone Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: audio hardware support needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

6 participants