Posts: 23,264
Joined: Aug 2011
Reputation:
1,074
fritsch
Team-Kodi Developer
Posts: 23,264
The majority of users (currently some millions) could live very good with the 10 seconds we had :-). Problem here is, that the init does not yet know about how many devices we have ... therefore it cannot dynamically wait. There is another problem: If users without audio devices tried to start kodi - they would not see anything for 60 seconds and likely will do another double click.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Posts: 819
Joined: Aug 2012
Reputation:
35
Ace
Team-Kodi Member
Posts: 819
2015-03-09, 10:21
(This post was last modified: 2015-03-09, 10:21 by Ace.)
Not sure if possible with our code and just a thought, but you could mimic dynamic wait by "resetting the timer" each time a device was found. Ofc there's a little chance to wait for ever.
Posts: 78
Joined: Mar 2013
Reputation:
0
14.2 RC has been released. Has anyone tried it yet? Would we still need a special build for the "Unable to create" bug?
Posts: 93
Joined: Jan 2015
Reputation:
0
Hi - out of the sudden I do have the same problem.
Since almost 2 years I am using XBMC / Kodi without any major issue. Since the day one, I am using V15 also without any major issue on several devices. However, today I started my computer (without modifying anything since I turned it off yesterday) the error message came up. Tried to install the V15 beta 1 again - no success. Tried to start the latest hightly (19 May) - no success :-( I can't try V14 because the mySQL server is also running V15...
I do have 3 audio devices and I didn't touch the drivers or changes anything related to the audio devices. So I am on the lost...
I thing I did yesterday - I deactivated the "Beck-up" Plug-in in Kodi - but I don't think it is related to this, isn't it ?
Posts: 93
Joined: Jan 2015
Reputation:
0
You're right- sorry.
However, I just inserted "<loglevel>2</loglevel>" in the advancedsettings.xlm, but the kodi.log in the Kodi folder (one folder above the userdata folder) file is just empty.
There are tow addionalfiles - xbmc_stacktrace.....txt and xbmx_crashlog....dmp.
The ...txt files are as follows:
Thread 988 (process 3488)
# 0
# 1
# 2
# 3
# 4
# 5 BaseThreadInitThunk
# 6 RtlInitializeExceptionChain
# 7 RtlInitializeExceptionChain
The thread number and process number chances with every attemp to start Kodi - the rest remains the same. The ...dmp file I can't read this file with an editor - what shall I do with this file ?
Posts: 93
Joined: Jan 2015
Reputation:
0
After a clean install of Kodi (uninstalled and deleted everthing first, then reinstall) Kodi is working again...