Login at Kodi Home

Rumpelstiltskin · 2018-05-27, 11:12

(2018-05-27, 10:45)fritsch Wrote:
(2018-05-27, 10:28)Rumpelstiltskin Wrote: Hi @fritsch

I can not try Librelec because my nuc does not go (and I do not understand the reason) with the USB boot.
Today I updated to this release 2:18.0+git20180527.0201-0cc5e0f-0bionic and now it seems to work all well as before except the movies in E-AC3 that are out of sync: my AVR go well in e-AC3 But the audio comes 1 second after
Good - we have a bugreport for this EAC3 already ... can you post a 100 MB sample of this file using dd?

Sure, here we go : https://mega.nz/#!Z5hwFKzI!U3zmtAHAf6K_a...udW6hJNBFs
Just a little pleasure, can you confirm that this file is out of sync even in your system?

**fritsch** · (This post was last modified: 2018-05-27, 11:52 by fritsch.)

Quote:[ffmpeg/audio] eac3: Multiple frames in a packet.
AO: [pulse] 48000Hz 5.1(side) 6ch float
[ffmpeg/audio] eac3: Dependent substream decoding is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[ffmpeg/audio] eac3: If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. ([email protected])

Edit: https://trac.kodi.tv/ticket/17871 <- all new information you can add here.
Edit2: Don't blame ffmpeg guys. They can decode it properly - it's most likely our fault in the EAC3 Syncer as decoding works fine also in kodi ... thx for the sample, please add a link to the report above.

redbiro · 2018-05-27, 19:50

(2018-05-26, 03:05)Jester1o1 Wrote: Has anyone done an update from 16.04 to 18.04?

I'm also interested in it. Is there any issues?

**fritsch** · 2018-05-27, 20:06

(2018-05-27, 19:50)redbiro Wrote:
(2018-05-26, 03:05)Jester1o1 Wrote: Has anyone done an update from 16.04 to 18.04?
I'm also interested in it. Is there any issues?

Basically you are on your own and if something breaks we cannot help you.

ppa-purge all ppas before your start, after that do the usual upgrade. I did this on two machines and it worked. Though making a kodi backup and afresh installation is preferred.

Jester1o1 · 2018-05-28, 11:20

Thanks fritsch, understood. Thank you.

ezechiel1917 · 2018-05-31, 11:00

Hi, anyone knows if it is possible to mount removable devices to /media/<LABEL> instead of /media/kodi/<LABEL> ?

**fritsch** · (This post was last modified: 2018-05-31, 13:47 by fritsch.)

Second answer: https://askubuntu.com/questions/214646/h...t-location - only our nightly has udisks2 support

Rumpelstiltskin · 2018-05-31, 19:16

@fritsch

hey fritsch, any news for eac3 "bug"? Smile

**fritsch** · 2018-05-31, 19:21

(2018-05-31, 19:16)Rumpelstiltskin Wrote: @fritsch

hey fritsch, any news for eac3 "bug"?

No - Nobody is working on it. Just disable EAC3 ...

ezechiel1917 · 2018-05-31, 20:50

(2018-05-31, 13:47)fritsch Wrote: Second answer: https://askubuntu.com/questions/214646/h...t-location - only our nightly has udisks2 support

Thanks for this link, I have followed that + https://github.com/xbmc/xbmc/pull/13897
Unfortunately I can't get it working with latest nightly ppa / ubuntu 18.04 udisks2:

If a removable drive is already plugged when kodi starts, it is automounted to /media/<label> - that's what I would like (but if I unplug it and plug it again it will be mounted to /media/kodi/<label>

So once kodi is running, it automounts removable drives to /media/kodi/<label> for some reason

Any idea what could be wrong?

**fritsch** · 2018-05-31, 22:09

No. On bootup it is auto mounted by the system for you and if plugged in later the mounts are done in kodi user's context.

ezechiel1917 · 2018-05-31, 22:44

Just to be more clear:

kodi started , removable drive not connected
sudo service kodi stop
plug in removable drive (no automount at this point)
sudo service kodi start - automount now appears in /media/<label>
unplug removable drive
plug in removable drive - automount now appears in /media/kodi/label>

is this expected behaviour?

My other box is kodibuntu (14.04 lts) with jarvis and removable drives are always automounted to /media/<label>.
Do you know if automount behavior was specific for this distribution or something changed in kodis automount handling code later on?

I'm not sure if I understand it correctly, but should it be possible to automount in 18.04 to /media/<label> when kodi is running and handling automount or not?

**fritsch** · (This post was last modified: 2018-06-01, 12:02 by fritsch.)

To my knowledge kodi has nothing to do with the location, it's done by udisks and friends - depending on which user is currently running with appropriate permissions. Please open your own thread about this issue.

Final idea from arch wiki:

Quote:Mount to /media (udisks2)By default, udisks2 mounts removable drives under the ACL controlled directory

Code:
/run/media/$USER/
. If you wish to mount to

Code:
/media
instead, use this rule:/etc/udev/rules.d/99-udisks2.rules# UDISKS_FILESYSTEM_SHARED
# ==1: mount filesystem to a shared directory (/media/VolumeName)
# ==0: mount filesystem to a private directory (/run/media/$USER/VolumeName)
# See udisks(8)
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"

ezechiel1917 · (This post was last modified: 2018-06-01, 18:18 by ezechiel1917.)

fritsch:
I've double checked all possible logs and found udisks2 can't automount removable device because it gets mounted faster by udevil to /media/kodi/<label>.

Solution:
sudo apt-get remove udevil

Now removable devices are always mounted with udisks2 udev rule from your link to /media/<label>

Thanks for your help.

**fritsch** · 2018-06-01, 19:04

ah! yes of course!!! I will remove udevil from the howto - it's not more needed for v18 or later.