Login at Kodi Home

**da-anda** · (This post was last modified: 2015-07-10, 18:50 by da-anda.)

remember that after you changed advancedsettings that you still have to select the newly added step sizes in the according sections (audio/video) or they won't apply. AS.xml only allows to adjust the available options, but won't apply them automatically.

Hrvoje · 2015-07-10, 19:14

(2015-07-10, 18:49)da-anda Wrote: remember that after you changed advancedsettings that you still have to select the newly added step sizes in the according sections (audio/video) or they won't apply. AS.xml only allows to adjust the available options, but won't apply them automatically.

Added values are not visible in video section.

~~Ned Scott~~ · 2015-07-11, 02:52

Make sure the as.xml file is being loaded by looking at the debug log (wiki). The steps you add in as.xml will show up as visual options in the video GUI settings.

Hrvoje · (This post was last modified: 2015-07-13, 20:41 by Hrvoje.)

(2015-07-11, 02:52)Ned Scott Wrote: Make sure the as.xml file is being loaded by looking at the debug log (wiki). The steps you add in as.xml will show up as visual options in the video GUI settings.

You are right, seems it is not loading:

Quote:20:37:08 T:988 NOTICE: special://profile/ is mapped to: special://masterprofile/
20:37:08 T:988 NOTICE: -----------------------------------------------------------------------
20:37:08 T:988 NOTICE: Starting Kodi (15.0-BETA2 Git:20150614-daedd5f). Platform: Windows NT x86 32-bit
20:37:08 T:988 NOTICE: Using Release Kodi x32 build
20:37:08 T:988 NOTICE: Kodi compiled Jun 14 2015 by MSVC 180030723 for Windows NT x86 32-bit version 6.0 (0x06000000)
20:37:08 T:988 NOTICE: Running on Windows 8.1, kernel: Windows NT x86 64-bit version 6.3
20:37:08 T:988 NOTICE: Host CPU: Intel® Xeon® CPU X3440 @ 2.53GHz, 4 cores available
20:37:08 T:988 NOTICE: Desktop Resolution: 1920x1080 32Bit at 60Hz
20:37:08 T:988 NOTICE: Running with administrator rights
20:37:08 T:988 NOTICE: Aero is enabled
20:37:08 T:988 NOTICE: special://xbmc/ is mapped to: C:\Program Files (x86)\Kodi
20:37:08 T:988 NOTICE: special://xbmcbin/ is mapped to: C:\Program Files (x86)\Kodi
20:37:08 T:988 NOTICE: special://masterprofile/ is mapped to: C:\Users\Hrvoje\AppData\Roaming\Kodi\userdata
20:37:08 T:988 NOTICE: special://home/ is mapped to: C:\Users\Hrvoje\AppData\Roaming\Kodi\
20:37:08 T:988 NOTICE: special://temp/ is mapped to: C:\Users\Hrvoje\AppData\Roaming\Kodi\cache
20:37:08 T:988 NOTICE: The executable running is: C:\Program Files (x86)\Kodi\Kodi.exe
20:37:08 T:988 NOTICE: Local hostname: HrvojeX3440
20:37:08 T:988 NOTICE: Log File is located: C:\Users\Hrvoje\AppData\Roaming\Kodi\kodi.log
20:37:08 T:988 NOTICE: -----------------------------------------------------------------------
20:37:08 T:988 NOTICE: load settings...
20:37:08 T:988 WARNING: CSettingString: unknown options filler "timezonecountries" of "locale.timezonecountry"
20:37:08 T:988 WARNING: CSettingString: unknown options filler "timezones" of "locale.timezone"
20:37:08 T:988 NOTICE: No settings file to load (special://xbmc/system/advancedsettings.xml)
20:37:08 T:988 NOTICE: No settings file to load (special://masterprofile/advancedsettings.xml)

Hrvoje · 2015-07-16, 01:41

What should I do, so Kodi can load AS?

~~Ned Scott~~ · 2015-07-16, 03:20

Double check the file is in the right location. Then check to see if it's named correctly (especially that the file ends with .txt, which might require you to expose file extensions depending on what OS you use). If it passes both of those steps, then make sure it is a plain text file and not a "rich text file" or something like an MS-Word document.

Hrvoje · 2015-07-16, 03:51

(2015-07-16, 03:20)Ned Scott Wrote: Double check the file is in the right location. Then check to see if it's named correctly (especially that the file ends with .txt, which might require you to expose file extensions depending on what OS you use). If it passes both of those steps, then make sure it is a plain text file and not a "rich text file" or something like an MS-Word document.

Thank you again.Now as.xml is loaded, but seeking is still not accurate.The reason is probably disabled accurate seeking, as mentioned by @FernetMenta.Will someone from Kodi team enable it again, or is there a way I can do it?Just a reminder, it worked in v15 Alpha 2.

~~Ned Scott~~ · 2015-07-16, 04:19

The behavior should be no different from v14. When he says accurate seeking was enabled, that was because it was only disabled in a v15 development build.

Hrvoje · 2015-07-23, 23:54

(2015-07-16, 04:19)Ned Scott Wrote: The behavior should be no different from v14. When he says accurate seeking was enabled, that was because it was only disabled in a v15 development build.

I've tried v15 final release, and it's the same.As far as I can se it, it is still predetermined by keyframes.If they are close fastforward work with small steps, like 3 seconds.Otherwise it is 10 or even more(!) seconds, which again proves that accurate seeking is still disabled, and it is depandable on keyframes.

~~Ned Scott~~ · 2015-07-24, 03:27

Compare it to v14 and you shouldn't see any difference. At least I can't when I tested. If you really do see a difference then maybe we can figure something out. I don't mean to sound like I don't believe you, but I actually made this same mistake recently.

Hrvoje · (This post was last modified: 2015-07-26, 00:57 by Hrvoje.)

(2015-07-24, 03:27)Ned Scott Wrote: Compare it to v14 and you shouldn't see any difference. At least I can't when I tested. If you really do see a difference then maybe we can figure something out. I don't mean to sound like I don't believe you, but I actually made this same mistake recently.

I compared it multiple times with v15 Alpha2, and I am sure there is difference.One of the Kodi developers mentioned that he disabled accurate seeking, and Kodi is behaving exactly as described in his post.Which is logical, of course.
Could you please check it with @FernetMenta, it would mean a lot to me.
1995369 (post)

EDIT: Fernet calls it recovery points, but in other players it is known as keyframes.With accurate seeking disabled Kodi will jump to nearest keyframe, which is usually 10 seconds.Therefore chosen time jump is not precise, and my selection(3 or 5 seconds) will be overridden.

~~Ned Scott~~ · 2015-07-26, 08:03

If it's not different when compared to v14 then they won't see it as a bug.

Hrvoje · 2015-07-30, 00:32

(2015-07-26, 08:03)Ned Scott Wrote: If it's not different when compared to v14 then they won't see it as a bug.

I don't know about v14, but my guess would be it worked, based on fact that feature worked until v15 Alpha2
I really appreciate your efforts, but this is going nowhere.As mentioned several times, only @FernetMenta could give us correct answer and solution.

Hrvoje · 2015-08-02, 01:25

I reinstalled v15 Alpha2 and it's working flawlessly, as expected.Therefore I stand by statement that change occured in later releases.

~~Ned Scott~~ · 2015-08-02, 06:54

Yes, we know. No, they're not going to change it. It's the same as it was for v14.