+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Skins Support (https://forum.kodi.tv/forumdisplay.php?fid=67)
+---- Forum: Arctic: Zephyr - Reloaded (https://forum.kodi.tv/forumdisplay.php?fid=221)
+---- Thread: Mod Arctic Zephyr: Generations (Jarvis / Leia) [3.4.70 / Coming Soon] (/showthread.php?tid=257970)
Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta6] - LastDragon - 2017-01-01
I think you can't see them, because there are 0 series and films in your library. When you scrape them both should appear.
Gesendet von iPhone mit Tapatalk
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta6] - hdmkv - 2017-01-01
I'm still using the Jarvis version (as I need SPMC) off the Emby repo... is there a way to disable the AZ splash screen? Thanks.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta6] - johnjohn22 - 2017-01-02
Hello guys,
Just installed this, and it looks absolutely stunning, and running perfectly. Just got a few things I cannot seem to figure out, that I hoped you guys could help me with. I am not running the latest, as Tv does not support it.
-It might be KODI specific(running KODI on my Sony UHD Android TV) - But I cannot seem to find any way to get back to the video I am watching, if I happen to "minimize" it to background. It runs perfectly in the background, but I have to go back and find the source to play it back again - same goes for live tv. I tried with "back" buttons etc. like I have searched, but cannot make it work.
-There are these annoying blue wave bars bouncing in the top right corner below the information about what is currently playing. I have tried a lot of stuff, but cannot make them go away. Any settings for this?
-Are there issues with metadata logos? In my old skin(Amber), my local UHD videos would show up with nice UHD metadata logos. In Arctic Zephyr, they show up as "SD" and then there is another logo saying "HD 2160p". This obviously does not look too neat. Is this fixable?
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta6] - hdmkv - 2017-01-02
(2017-01-01, 17:52)hdmkv Wrote: I'm still using the Jarvis version (as I need SPMC) off the Emby repo... is there a way to disable the AZ splash screen? Thanks.Answering my own question... just need to edit Startup.xml.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta6] - Guardian Hope - 2017-01-04
(2017-01-02, 04:24)hdmkv Wrote:(2017-01-01, 17:52)hdmkv Wrote: I'm still using the Jarvis version (as I need SPMC) off the Emby repo... is there a way to disable the AZ splash screen? Thanks.Answering my own question... just need to edit Startup.xml.
That was an odd request; any reason as to why you wanted to disable the AZ:FA splash screen? It's been in there since AZ:E (Kodi 15) and doesn't really present any issues as far as I know.
In either case, there's a lot of messages to catch up on here but I wanted to update everyone on the impending BETA 7 Update.
It should be released later tonight or early tomorrow; I had medical appointments that took precedence over releasing the latest updates.
Also: you may find in the first post now an updated "draft" of what will become the new first post once Danvers releases. Few notes: we removed "RTFM" and gave you an online wizard to walk you through everything, JIRA is coming, a little hint of For Another Age and Project Erso.
Random music background - papayo29 - 2017-01-05
Hi everyone
Sorry for the silly question. Which is the best way to have a random music background in the music section of the home menu?
I can find options for random movies or random TVshows backgrounds, but no random music background.
Thanks
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta6] - Guardian Hope - 2017-01-07
Arctic Zephyr: From Ashes (Danvers) for Kodi 17 Krypton
Beta 6, Patch Level 1 Update (BETA 7)"
Beta 6, Patch Level 1 Update (BETA 7)"
Anyone With Previously Posted Questions Will Be Answered Soon!
Thanks to @Cranial who would be added to the list of people who have contributed to From Ashes in Beta 8, today's update: Beta 6, Patch Level 1 (BETA 7) has been released to the update origin and will be making its way to your devices in short order. Aside from the start of adding the Caitlin Snow Framework, B6PL1 addresses one issue: the missing font icon symbols. No more squares where buttons should be!
Also, for those willing: Sorry, the Project Erso survey was closed due to the fact that I jumped the gun and thought I had posted the initial information on Erso (1/7/2016 - 10:36am Pacific).
NortheBridge by Design Repository 2.0: https://embycdn.northebridge.com/NatalieDormer/repository.northebridge.by.design.kodi-2.0.00.zip
Enterprise CDN Download: https://embycdn.northebridge.com/AZFA/danvers/4.9.92/skin.arctic.zephyr.fromashes.danvers-4.9.92-beta7.zip
GitHub: https://github.com/NortheBridge/skin.arctic.zephyr.fromashes/releases/tag/4.9.92-beta7
Available in the Emby Beta Repository
Changelog:
Code:
Arctic Zephyr: From Ashes Danvers "Beta 6, Patch Level 1 Update" - Released December, 31, 2016
Danvers: 4.9.92-beta7 (4.9.92-beta7_danvers)
ARCTIC ZEPHYR: FROM ASHES ANNIVERSARY EDITION (CODENAMED "DANVERS") IS PRE-RELEASE SOFTWARE DESIGNED FOR A PRE-RELEASE VERSION OF KODI. THERE IS NO GUARNTEE THAT ALL FEATURES WILL WORK. PLEASE LET US KNOW OF ANY ISSUES YOU RUN INTO. THIS SKIN IS NOW AVAILABLE IN THE NORTHEBRIDGE BY DESIGN(R) REPOSITORY, EMBY BETA REPOSITORY, GITHUB, OR VIA DIRECT ZIP FILE DOWNLOAD ONLY.
Repaired Missing Font Symbols (Fix contributed by "Cranial" on the Official Kodi Forums)RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta7] - Blurayx - 2017-01-07
Hi Guardian Hope,
Beta 7 crashes on my iMac. I'm going to test it on my Nvidia shield tablet and report back.
UPDATE:
SAME ISSUE
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta7] - buxtonlad - 2017-01-07
(2017-01-07, 13:26)Blurayx Wrote: Hi Guardian Hope,
Beta 7 crashes on my iMac. I'm going to test it on my Nvidia shield tablet and report back.
UPDATE:
SAME ISSUE
Same here on my Nvidia shield tv.. Latest Krypton nightly..... Clean install gives a force close..
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta7] - Synopis - 2017-01-07
I'm getting the same issue as the other's on Windows
Edit
Also.. will we be getting the main menu view Artic:Zypher has sometime in the future?
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta7] - Guardian Hope - 2017-01-07
@Blurayx, @buxtonlad @Synopis: Are you all running Kodi nightly builds or are any of you actually running the Release Candidate? The reason I ask is that nightlies break from day-to-day but the fact that several platforms are causing issues is concerning.
Can any of you provide a debug level log? Did any of you get this with Beta 6 as Beta 7 is Beta 6 with the corrections to the Font.xml file.
(2017-01-07, 16:27)Synopis Wrote: I'm getting the same issue as the other's on Windows
Edit
Also.. will we be getting the main menu view Artic:Zypher has sometime in the future?
It was in an earlier preview (Alpha 1-3) of Arctic Zephyr: From Ashes (Danvers). We're going to discuss it and quite a number of other things. Now that we're starting to get back from the Christmas holidays we still have a little settling in to do.
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta7] - Synopis - 2017-01-07
(2017-01-07, 20:07)Guardian Hope Wrote: @Blurayx, @buxtonlad @Synopis: Are you all running Kodi nightly builds or are any of you actually running the Release Candidate? The reason I ask is that nightlies break from day-to-day but the fact that several platforms are causing issues is concerning.
Can any of you provide a debug level log? Did any of you get this with Beta 6 as Beta 7 is Beta 6 with the corrections to the Font.xml file.
I usually wait a week before nightlies. This is what I get or at the very least I saw in my log.
Quote: CTextureBundleXBT::CloseBundle - Closed bundle
14:55:23.929 T:4808 INFO: load skin from: C:\Users\user\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers (version: 4.9.92-beta7)
14:55:23.933 T:4808 INFO: load fonts for skin...
14:55:23.939 T:4808 INFO: Loading fonts from C:\Users\user\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\16x9\Font.xml
14:55:23.971 T:4808 ERROR: Couldn't load font name: font_babylon5(babylon5_station.ttf), trying to substitute arial.ttf
14:55:23.977 T:4808 ERROR: Couldn't load font name: font_bachelorpad(bachelor_pad.ttf), trying to substitute arial.ttf
14:55:23.977 T:4808 ERROR: Couldn't load font name: font_bullpen3d(bullpen3.ttf), trying to substitute arial.ttf
14:55:23.982 T:4808 ERROR: Couldn't load font name: font_terminator(terminat.ttf), trying to substitute arial.ttf
14:55:23.988 T:4808 DEBUG: POParser: PO file has Win Style Line Endings. Converted in memory to Linux LF for file: C:\Users\user\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\language\English\strings.po
14:55:23.989 T:4808 DEBUG: LocalizeStrings: loaded 227 strings from file C:\Users\user\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\language\English\strings.po
14:55:23.989 T:4808 INFO: Loading skin includes from C:\Users\user\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\16x9\includes.xml
14:55:24.178 T:4808 INFO: Error loading includes.xml file (C:\Users\user\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\16x9\Includes_NextAired.xml): Failed to open file (row=0, col=0)
14:55:24.189 T:4808 INFO: load new skin...
14:55:24.190 T:4808 INFO: Loading user windows, path C:\Users\user\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\16x9
Here's the log with debugging enabled
http://pastebin.com/1SegWevU
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta7] - Blurayx - 2017-01-07
Tested with kodi RC2 & Nightlies. Kodi RC2 log shown below
0:12:49.907 T:140735777633216 WARNING: CSkinInfo: failed to load skin settings
20:12:49.907 T:140735777633216 INFO: load skin from: /Users/stephen/Library/Application Support/Kodi/addons/skin.arctic.zephyr.fromashes.danvers (version: 4.9.92-beta7)
20:12:49.908 T:140735777633216 INFO: load fonts for skin...
20:12:49.910 T:140735777633216 INFO: Loading fonts from /Users/stephen/Library/Application Support/Kodi/addons/skin.arctic.zephyr.fromashes.danvers/16x9/Font.xml
20:12:49.935 T:140735777633216 ERROR: Couldn't load font name: font_babylon5(babylon5_station.ttf), trying to substitute arial.ttf
20:12:49.938 T:140735777633216 ERROR: Couldn't load font name: font_bachelorpad(bachelor_pad.ttf), trying to substitute arial.ttf
20:12:49.938 T:140735777633216 ERROR: Couldn't load font name: font_bullpen3d(bullpen3.ttf), trying to substitute arial.ttf
20:12:49.942 T:140735777633216 ERROR: Couldn't load font name: font_terminator(terminat.ttf), trying to substitute arial.ttf
20:12:49.949 T:140735777633216 DEBUG: POParser: PO file has Win Style Line Endings. Converted in memory to Linux LF for file: /Users/stephen/Library/Application Support/Kodi/addons/skin.arctic.zephyr.fromashes.danvers/language/English/strings.po
20:12:49.949 T:140735777633216 DEBUG: LocalizeStrings: loaded 227 strings from file /Users/stephen/Library/Application Support/Kodi/addons/skin.arctic.zephyr.fromashes.danvers/language/English/strings.po
20:12:49.949 T:140735777633216 INFO: Loading skin includes from /Users/stephen/Library/Application Support/Kodi/addons/skin.arctic.zephyr.fromashes.danvers/16x9/includes.xml
20:12:50.024 T:140735777633216 INFO: Error loading includes.xml file (/Users/stephen/Library/Application Support/Kodi/addons/skin.arctic.zephyr.fromashes.danvers/16x9/Includes_NextAired.xml): Failed to open file (row=0, col=0)
20:12:50.028 T:140735777633216 INFO: load new skin...
20:12:50.028 T:140735777633216 INFO: Loading user windows, path /Users/stephen/Library/Application Support/Kodi/addons/skin.arctic.zephyr.fromashes.danvers/16x9
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta7] - Guardian Hope - 2017-01-07
Critical Beta 6, Patch Level 1 (BETA 7) Issues Identified
We have identified the issues with Beta 6, Patch Level 1 and Beta 6, Patch Level 2 (BETA 8) will be released to address Arctic Zephyr: From Ashes (Danvers) Preview crashing Kodi 17.
The relevant log information is here:
Code:
T:20220 DEBUG: CGUIMediaWindow::GetDirectory (addons://repository.northebridge.by.design.kodi/xbmc.gui.skin)
10:58:07.865 T:20220 DEBUG: ParentPath = [addons://repository.northebridge.by.design.kodi/xbmc.gui.skin]
10:58:07.866 T:11932 DEBUG: Unpacking zip://special%3A%2F%2Fhome%2Faddons%2Fpackages%2Fskin.arctic.zephyr.fromashes.danvers-4.9.92-beta7.zip/skin.arctic.zephyr.fromashes/ to C:\Users\Avalon\AppData\Roaming\Kodi\addons\temp\095dbf8c-9bda-4492-9003-2700f649e1b1
10:58:07.866 T:8984 DEBUG: CAddonDatabase: SELECT repo.id FROM repo .. took 0 ms
10:58:07.867 T:8984 DEBUG: CAddonDatabase: query SELECT * FROM addons JOIN addonlinkrepo ON addons.id=addonlinkrepo.idAddon WHERE addonlinkrepo.idRepo IN (2) ORDER BY addons.addonID returned 6 rows in 1 ms
10:58:07.867 T:8984 DEBUG: CAddonDatabase::GetAddons took 1 ms
10:58:07.886 T:8984 DEBUG: CAddonMgr::GetAvailableUpdates took 18 ms
10:58:07.887 T:17512 DEBUG: -->Python Interpreter Initialized<--
10:58:07.887 T:17512 DEBUG: CPythonInvoker(13, C:\Users\Avalon\AppData\Roaming\Kodi\addons\service.nextup.notification\service.py): the source file to load is "C:\Users\Avalon\AppData\Roaming\Kodi\addons\service.nextup.notification\service.py"
10:58:07.887 T:17512 DEBUG: CPythonInvoker(13, C:\Users\Avalon\AppData\Roaming\Kodi\addons\service.nextup.notification\service.py): setting the Python path to C:\Users\Avalon\AppData\Roaming\Kodi\addons\service.nextup.notification;C:\Users\Avalon\AppData\Roaming\Kodi\addons\script.module.addon.signals\lib;C:\Program Files (x86)\Kodi\system\python\DLLs;C:\Program Files (x86)\Kodi\system\python\Lib;C:\Program Files (x86)\Kodi\python27.zip;C:\Program Files (x86)\Kodi\system\python\lib\plat-win;C:\Program Files (x86)\Kodi\system\python\lib\lib-tk;C:\Program Files (x86)\Kodi;C:\Program Files (x86)\Kodi\system\python;C:\Program Files (x86)\Kodi\system\python\lib\site-packages
10:58:07.887 T:17512 DEBUG: CPythonInvoker(13, C:\Users\Avalon\AppData\Roaming\Kodi\addons\service.nextup.notification\service.py): entering source directory C:\Users\Avalon\AppData\Roaming\Kodi\addons\service.nextup.notification
10:58:07.890 T:19884 DEBUG: Thread BackgroundLoader start, auto delete: false
10:58:07.892 T:19884 DEBUG: Thread BackgroundLoader 19884 terminating
10:58:07.926 T:17512 DEBUG: CPythonInvoker(13, C:\Users\Avalon\AppData\Roaming\Kodi\addons\service.nextup.notification\service.py): instantiating addon using automatically obtained id of "service.nextup.notification" dependent on version 2.20.0 of the xbmc.python api
10:58:08.245 T:21916 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> Starting NextUp Service
10:58:08.246 T:21916 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> ======== START NEXTUP SERVICE NOTIFICATION ========
10:58:08.246 T:21916 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> KODI Version: 17.0-RC2 Git:20161230-5c40b5c-dirty
10:58:08.246 T:21916 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> NEXTUP SERVICE NOTIFICATION Version: 1.0.25
10:58:08.255 T:21916 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> Platform: Windows
10:58:08.301 T:17512 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> Starting NextUp Service
10:58:08.302 T:17512 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> ======== START NEXTUP SERVICE NOTIFICATION ========
10:58:08.302 T:17512 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> KODI Version: 17.0-RC2 Git:20161230-5c40b5c-dirty
10:58:08.302 T:17512 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> NEXTUP SERVICE NOTIFICATION Version: 1.0.25
10:58:08.303 T:17512 DEBUG: NEXTUP SERVICE NOTIFICATION Service -> Platform: Windows
10:58:12.940 T:20220 DEBUG: ------ Window Deinit (DialogNotification.xml) ------
10:58:20.042 T:18452 DEBUG: script.tv.show.next.aired: ### search language = "en"
10:58:20.045 T:18452 DEBUG: CVideoDatabase::RunQuery took 1 ms for 0 items query: SELECT * FROM tvshow_view
10:58:25.072 T:11932 INFO: ADDON: cpluff: 'Could not read plug-in directory C:\Users\Avalon\AppData\Roaming\Kodi\addons: No such file or directory'
10:58:25.093 T:11932 INFO: ADDON: cpluff: 'Could not read plug-in directory C:\Program Files (x86)\Kodi\addons: No such file or directory'
10:58:25.095 T:11932 DEBUG: CAddonDatabase: skin.arctic.zephyr.fromashes.danvers has been installed.
10:58:25.510 T:11932 DEBUG: CAddonMgr: enabled skin.arctic.zephyr.fromashes.danvers
10:58:25.529 T:15676 DEBUG: ContextMenuManager: addon menus reloaded.
10:58:25.572 T:20220 DEBUG: CGUIMediaWindow::GetDirectory (addons://repository.northebridge.by.design.kodi/xbmc.gui.skin)
10:58:25.572 T:20220 DEBUG: ParentPath = [addons://repository.northebridge.by.design.kodi/xbmc.gui.skin]
10:58:25.573 T:15676 DEBUG: CAddonDatabase: SELECT repo.id FROM repo .. took 0 ms
10:58:25.574 T:15676 DEBUG: CAddonDatabase: query SELECT * FROM addons JOIN addonlinkrepo ON addons.id=addonlinkrepo.idAddon WHERE addonlinkrepo.idRepo IN (2) ORDER BY addons.addonID returned 6 rows in 0 ms
10:58:25.574 T:15676 DEBUG: CAddonDatabase::GetAddons took 1 ms
10:58:25.640 T:15676 DEBUG: CAddonMgr::GetAvailableUpdates took 65 ms
10:58:25.643 T:11996 DEBUG: Thread BackgroundLoader start, auto delete: false
10:58:25.644 T:11996 DEBUG: Thread BackgroundLoader 11996 terminating
10:58:25.646 T:20220 DEBUG: CGUIMediaWindow::GetDirectory (addons://repository.northebridge.by.design.kodi/xbmc.gui.skin)
10:58:25.646 T:20220 DEBUG: ParentPath = [addons://repository.northebridge.by.design.kodi/xbmc.gui.skin]
10:58:25.648 T:5696 DEBUG: CAddonDatabase: SELECT repo.id FROM repo .. took 1 ms
10:58:25.648 T:5696 DEBUG: CAddonDatabase: query SELECT * FROM addons JOIN addonlinkrepo ON addons.id=addonlinkrepo.idAddon WHERE addonlinkrepo.idRepo IN (2) ORDER BY addons.addonID returned 6 rows in 0 ms
10:58:25.648 T:5696 DEBUG: CAddonDatabase::GetAddons took 1 ms
10:58:25.665 T:5696 DEBUG: CAddonMgr::GetAvailableUpdates took 16 ms
10:58:25.668 T:20220 DEBUG: ------ Window Init (DialogConfirm.xml) ------
10:58:25.668 T:11076 DEBUG: Thread BackgroundLoader start, auto delete: false
10:58:25.669 T:11076 DEBUG: Thread BackgroundLoader 11076 terminating
10:58:27.702 T:20220 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
10:58:27.702 T:20220 DEBUG: CInputManager::OnKey: left (0xf082) pressed, action is Left
10:58:27.702 T:17736 INFO: CActiveAESink::OpenSink - initialize sink
10:58:27.702 T:17736 DEBUG: CActiveAESink::OpenSink - trying to open device DIRECTSOUND:default
10:58:27.721 T:17736 DEBUG: CAESinkDirectSound::Initialize: Using Window handle: 00400C58
10:58:27.726 T:17736 DEBUG: CAESinkDirectSound::Initialize: secondary buffer created
10:58:27.727 T:17736 DEBUG: CAESinkDirectSound::Initialize: Initializing DirectSound with the following parameters:
10:58:27.727 T:17736 DEBUG: Audio Device : Speakers / Headphones (Realtek High Definition Audio)
10:58:27.727 T:17736 DEBUG: Sample Rate : 44100
10:58:27.727 T:17736 DEBUG: Sample Format : AE_FMT_FLOAT
10:58:27.727 T:17736 DEBUG: Bits Per Sample : 32
10:58:27.727 T:17736 DEBUG: Valid Bits/Samp : 32
10:58:27.727 T:17736 DEBUG: Channel Count : 2
10:58:27.727 T:17736 DEBUG: Block Align : 8
10:58:27.727 T:17736 DEBUG: Avg. Bytes Sec : 352800
10:58:27.727 T:17736 DEBUG: Samples/Block : 32
10:58:27.727 T:17736 DEBUG: Format cBSize : 22
10:58:27.727 T:17736 DEBUG: Channel Layout : FL,FR
10:58:27.727 T:17736 DEBUG: Channel Mask : 3
10:58:27.727 T:17736 DEBUG: Frames : 661
10:58:27.727 T:17736 DEBUG: Frame Size : 8
10:58:27.727 T:17736 DEBUG: CActiveAESink::OpenSink - DIRECTSOUND Initialized:
10:58:27.727 T:17736 DEBUG: Output Device : default
10:58:27.727 T:17736 DEBUG: Sample Rate : 44100
10:58:27.727 T:17736 DEBUG: Sample Format : AE_FMT_FLOAT
10:58:27.727 T:17736 DEBUG: Channel Count : 2
10:58:27.727 T:17736 DEBUG: Channel Layout: FL,FR
10:58:27.727 T:17736 DEBUG: Frames : 661
10:58:27.727 T:17736 DEBUG: Frame Size : 8
10:58:27.879 T:20220 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
10:58:27.984 T:17736 DEBUG: CAESinkDirectSound::CheckPlayStatus: Resuming Playback
10:58:28.779 T:20220 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
10:58:29.078 T:20220 DEBUG: CInputManager::OnKey: return (0xf00d) pressed, action is Select
10:58:29.078 T:20220 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x0000, modifier: 0x0
10:58:29.317 T:20220 DEBUG: ------ Window Deinit (DialogConfirm.xml) ------
10:58:29.484 T:20220 INFO: Unloading old skin ...
10:58:29.490 T:20220 DEBUG: ------ Window Deinit () ------
10:58:29.492 T:20220 DEBUG: ------ Window Deinit (AddonBrowser.xml) ------
10:58:29.493 T:20220 DEBUG: CTextureBundleXBT::CloseBundle - Closed bundle
10:58:29.500 T:20220 WARNING: CSkinInfo: failed to load skin settings
10:58:29.501 T:20220 INFO: load skin from: C:\Users\Avalon\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers (version: 4.9.92-beta7)
10:58:29.502 T:20220 INFO: load fonts for skin...
10:58:29.650 T:20220 INFO: Loading fonts from C:\Users\Avalon\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\16x9\Font.xml
10:58:29.843 T:20220 ERROR: Couldn't load font name: font_babylon5(babylon5_station.ttf), trying to substitute arial.ttf
10:58:30.020 T:20220 ERROR: Couldn't load font name: font_bachelorpad(bachelor_pad.ttf), trying to substitute arial.ttf
10:58:30.021 T:20220 ERROR: Couldn't load font name: font_bullpen3d(bullpen3.ttf), trying to substitute arial.ttf
10:58:30.040 T:20220 ERROR: Couldn't load font name: font_terminator(terminat.ttf), trying to substitute arial.ttf
10:58:30.073 T:20220 DEBUG: POParser: PO file has Win Style Line Endings. Converted in memory to Linux LF for file: C:\Users\Avalon\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\language\English\strings.po
10:58:30.073 T:20220 DEBUG: LocalizeStrings: loaded 227 strings from file C:\Users\Avalon\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\language\English\strings.po
10:58:30.074 T:20220 INFO: Loading skin includes from C:\Users\Avalon\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\16x9\includes.xml
10:58:30.360 T:20220 INFO: Error loading includes.xml file (C:\Users\Avalon\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\16x9\Includes_NextAired.xml): Failed to open file (row=0, col=0)
10:58:30.380 T:20220 INFO: load new skin...
10:58:30.380 T:20220 INFO: Loading user windows, path C:\Users\Avalon\AppData\Roaming\Kodi\addons\skin.arctic.zephyr.fromashes.danvers\16x9Project Erso Survey Has Been Closed
This was my fault; I thought I had released the paper describing the Erso Video Media Server but I have not yet. I want to discuss Erso with the team first before publicly releasing details on Erso including all its capabilities. What I will say for now is that Erso is a Unified Entertainment System more powerful than anything currently available today that runs Kodi (rPi3, Veero, etc.). With eight x64 cores of processing power, 8GB of RAM, native 4K UHD support, M-Card Compatibility to replace your set-top-box (and 6 available tuners so you can record five shows while watching a sixth), dual drives (one for the OS and an additional 1TB HDD for your content) and far more. It will redefine the definition of what a "Kodi box" is. All of this running on a Red Hat Enterprise Linux based platform (the Erso OS).
Erso will force For Another Age to have the highest quality code. If we release Erso running a skin the state Danvers is currently in then we run the risk of it being labled like 'Windows Vista' and that's not something you can come back from.
Do remember Erso is currently in preliminary stages of planning.
Concerns About Danvers and For Another Age
In the few responses I got before realizing nothing about Erso is published yet, there was concerns about moving to For Another Age with the state that Danvers is in. Danvers is in Preview Availability. It is not complete and has a lot of bugs to work out before we even reach the Release Candidate stage which is just before General Availability. Please calm yourselves, we're not going to drop everything in favor of For Another Age. We were only forced to do that to Dormer because the code changed so much that coding for Dormer was like coding MS-DOS while Danvers was like coding Windows 7.
When Danvers finally reaches General Availability (GA), For Another Age will begin its Preview Availability (PA) life. Every update to For Another Age (fixes, etc.) will be backported to Danvers throughout the entire Kodi 17 run. It will be seamless because until For Another Age takes on its updated design, Danvers and For Another Age will be the exact same skin.
Concerns About Bugs Not Being Addressed
And there's a lot of them. Even I know that. There are bugs 25 pages back related to Danvers. Some bugs I'm certain have fallen through the cracks which is why in January we're going to institute a bug tracking and project management system. One controlled by the users where users can up-vote the priority of issues needing fixing (to help validate issues because if only one person is having the issue then its that one person) and submit the bugs as well as see their progress to being fixed.
When that notice that says "Danvers Preview" that appears on startup goes away that means you're running a general availability release of AZ:FA. Until then, you're inherently running something in development and that means every update could fix and break something. Look what a minor change did to AZ:FA Danvers today.
Finally, I'd Really Like to Know Who this Is...
Respondent 2 to Erso Survey Wrote:Would not be impressed. From Ashes Danvers still has bugs that have been either ignored or handwaved away with one pithy excuse after the other. When GuardianHope tookover development she/he admitted to having little to no experience in skinning development. And it shows. So,why don't you finish with what you start instead of going off on other projects that in all honesty and based on public evidence of released material and posts, seem completely beyond your capabilities.Beta 7of Danvers has been released, it's causing bootlooops. Yet again a release that causes a fatal error. And will you finally get your thunb out and fix the fonts? You've been saying again and again that you will fix them for the next update. It's over 6 months now,and you still have done nowt.
Dear Respondent 2 to Erso Survey,
I would like to take a moment and personally address you. These surveys are done anonymous so I am not entirely certain who you are. For all I know you could just be some disgruntled person that has nothing better to do or you sincerely feel this way. This is why I have singled you out aside from in the two surveys posted into this thread you are the only person who seems to post a rude response but I would like to put a name to those responses. Allow me to now address you.
When I first took over development of Arctic Zephyr: Exploded more than a year ago, I was being thrusted into the deep end. With the help of 'im85288' and many others I did finally begin to learn and have learned what needs to be done. Do I claim to be a 'skinning master.' No. There are people here with years and years of Kodi skinning experience. The From Ashes Project was only originally intended to keep AZ:E support for Jarvis and beyond. It has grown well beyond that original scope. There weren't going to be any new features. That all has obviously changed.
No valid bug has been "handwaved" or ignored with one excuse after another. There is a priority system. For example, just because you are having an issue with some feature doesn't mean it's not going to be addressed; it's likely not a "showstopping" feature and therefore has a much lower priority. We're turning over the entire bug reporting and bug fixing priority system to the users this month. If others think your bug is that important than it will be addressed in short order. If not, well, it will get addressed much later. If you don't like that there is a phrase that many have coined: "tough."
Arctic Zephyr: From Ashes Danvers and soon Arctic Zephyr: For Another Age are actually worked on by three different people. Yes, that's right - not one, not two, but three. Who are those three? Minus0, Habitual_Sinner, and myself. So when it comes to your 'public evidence of released material and posts' that you seemingly have gathered, apparently you did not even get this fundamental fact right which casts great doubt over much of what you say. Everyone knows that Danvers is in "Preview Availability." It's a Beta right now and there are still a lot of bugs that need addressing. Are we going to address them overnight? No. In fact, everyone was on a break for Christmas.
When we talk about capabilities you are clearly out of your depth. Building a Linux platform device and building a skin for an application are two entirely different things. Without a matter of doubt in my head I can safely say that you have no ideas what capabilities any of us posses.
Danvers Beta 7 was released today and ironically, if you had read the release notes, would have known that Beta 7 was intended to address the missing font faces. In fact, it does. The only problem is that another issue cropped up at the same time when we updated the appropriate files and now they have to be fixed. This is causing AZ:FA to bootloop your device or crash on Windows and any other platform.
I think constructive criticism is great but your criticism is the least bit constructive and far more reeks of entitlement that you should not have given that From Ashes is released to you completely free by volunteers. If you were using the currently preliminary Erso device I would completely understand because then you would have every right to be frustrated but you are not and if we go through with Erso, no For Another Age update would be released without making sure it could run on an Erso device properly.
So please, I would like to know the name of the person who wrote this and is complaining so much about a Beta which is bound to have bugs by the very definition of 'Beta.' It's pre-release software; did you really expect it to work perfectly? In fact, every release of Danvers says that in the Release Notes. Oh, and there might actually be a prompt that comes up when you start it. And I am pretty certain that it also says "Arctic Zephyr: From Ashes (Danvers Preview)" as well. I'm really not certain why you would expect a preview to work perfectly on a version of Kodi still being developed.
I very much doubt you'll reveal who you are on this forum because its always easier to hide behind the fact that you are anonymous but at the very least I have addressed someone as rude as you. You are aware that likely no one here would have given you the time of day and we don't have to ever give you the time of day. I only chose to do it this once because I want to know who cannot understand that Danvers is still pre-release software and due to their lack of understanding decided to continue on a tirade not once, not twice, but actually four different times; the other three I did not post here.
Sincerely,
Guardian Hope
RE: Arctic Zephyr: From Ashes (Jarvis / Krypton) [3.4.70 / 4.9.92-beta7] - Guardian Hope - 2017-01-08
Beta 7 Critical Issue Fix Directions
An issue was identified in Arctic Zephyr: From Ashes Danvers (Preview) Beta 7 shortly after its release that would cause Kodi 17 RC2 and Kodi 17 Nightlies to crash on all platforms.
Cause
The cause of the issue has been identified to be related to a file that was merged into Danvers from the Caitlin Snow Branch.
Fix Directions
Although we will be patching Beta 7 with Beta 8, we can understand that you may not want to wait several hours. As such, we have provided directions to fix the issue until a patch is released. Do note that the Beta 8 Patch will also resolve other issues from Beta 7 that were identified during the identification process.
1) Quit Kodi
2) Browse to "skin.arctic.zephyr.fromashes" under your Kodi addons directory
3) Change directories to "16x9"
4) Delete the file named "Custom_CaitlinSnow-FRAMEWORK.xml"
5) Start Kodi and Enable Arctic Zephyr: From Ashes
Files Effected
- /16x9/Custom_CaitlinSnow-FRAMEWORK.xml
THE BETA 8 PATCH WILL BE RELEASED IN SEVERAL HOURS TO ADDRESS THIS AND OTHER ISSUES IDENTIFIED IN BETA 7.