• 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 7
Kodi 15 and "Sync playback to display" setup
#46
RemoteControl off. Everything is off, only laptop and external hard drive. Ruled with touchpad. But I see remoteControl Big Grin. This is a delirium. Just at this time I hear the drops and dupes.
http://pastebin.com/qZR7e9YY
Reply
#47
Here was RemoteControl, but I dont see any problem http://pastebin.com/jaKX7TKQ
Reply
#48
Quote:00:17:56 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:18:01 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:18:02 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:18:03 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:18:08 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:18:09 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:18:10 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:18:12 T:4092 DEBUG: Thread JobWorker 4092 terminating (autodelete)
00:18:12 T:2852 DEBUG: Thread JobWorker 2852 terminating (autodelete)
00:18:12 T:728 DEBUG: Thread JobWorker 728 terminating (autodelete)
00:18:12 T:2364 DEBUG: Thread JobWorker 2364 terminating (autodelete)
00:18:15 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:18:16 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:18:17 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:18:22 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:18:23 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:18:24 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:18:29 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:18:30 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:18:31 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:18:36 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:18:37 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:18:38 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:18:43 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:18:44 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:18:45 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:18:50 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:18:51 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:18:52 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:18:57 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:18:58 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:18:59 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:19:04 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:19:05 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:19:06 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:19:11 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:19:12 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:19:13 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:19:18 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:19:19 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:19:20 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:19:25 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:19:26 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:19:27 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:19:32 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:19:33 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:19:34 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:19:39 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:19:40 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:19:41 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:19:46 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:19:47 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:19:48 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:19:53 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:19:54 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:19:55 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:20:00 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:20:01 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:20:02 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:20:07 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:20:08 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:20:09 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:20:14 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:20:15 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:20:16 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:20:21 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:20:22 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:20:23 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:20:28 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:20:29 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:20:30 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:20:35 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:20:36 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:20:37 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:20:42 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:20:43 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:20:44 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:20:49 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:20:50 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:20:51 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:20:56 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:20:57 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:20:58 T:2540 DEBUG: CRemoteControl::Connect - failed to connect
00:21:03 T:2540 DEBUG: CRemoteControl::Connect - connecting to: ::1:24000 ...
00:21:04 T:2540 DEBUG: CRemoteControl::Connect - connecting to: 127.0.0.1:24000 ...
00:21:05 T:2540 DEBUG: CRemoteControl::Connect - failed to connect

^^ you see that? This is your issue. Remove that!
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#49
ALL removed. Pure laptop.
Reply
#50
LOL
Reply
#51
So - any changes now?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#52
Component specific logging enable, may be it do this?
Reply
#53
So log above from pure laptop. No remote, mouse or something. Nothing
Reply
#54
There is something wrong with the remote I also have seen that in Linux lately ... perhaps over the night I get an idea.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#55
But anyway not resampled. I hear missing pieces of words. And no remote Smile
Reply
#56
...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#57
fritsch,
If you need more information or tests, tell me. I have a lot of free time Smile
Reply
#58
could you please play sintel.iso, try different audio devices, and post log. what shows rr on codec screen? is the value stable?
Reply
#59
(2015-03-25, 18:58)FernetMenta Wrote: PAL speed down? when playing 24hz or 23.976 on a 50hz screen playback is 4% faster. this behaviour did not change. "sync playback to display" activates smooth video in which case audio gets resampled.
I refer to a lot of DVD content that was published at 25fps when the original was 23.976 (they speed up everything by 4%).
With Reclock one has the ability to slow down the playback, so as to get the original sound. For a moment I thought there was a way to achieve this in Kodi but I'm probably mistaken.
For troubleshooting and bug reporting please make sure you read this first (usually it's enough to follow instructions in the second post).
Reply
#60
http://pastebin.com/nZnQe83P
Naked laptop. Even wi-fi disabled. Played video from the internal hard disk. Audio device changed. First AMD HDMI Wasapi, after HDMI DirectSound, latter to Wasapi Speakers. Poor video for the test, too little speeches.
rr is stable 1.00000
..and again remotecontrol lol
Reply
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 7

Logout Mark Read Team Forum Stats Members Help
Kodi 15 and "Sync playback to display" setup0