(2016-01-02, 22:07)SavellM Wrote: Sorry totally off topic but what do you mean by Fritsch is gone?
Left the project, or left OE or Kodi?

Can anyone PM me details please?

(2016-01-02, 22:11)SavellM Wrote: PM so we dont derail this project.

(2016-01-02, 22:07)SavellM Wrote: Sorry totally off topic but what do you mean by Fritsch is gone?
Left the project, or left OE or Kodi?

(2016-01-02, 21:00)Milhouse Wrote:

(2016-01-02, 17:27)jjslegacy Wrote: @millhouse is it suppose to do that? Not sure why it overrides my default choice when I put a build that has pulse in it and becomes the default.

No, and it doesn't do it for me.

Can you try shutting down kodi, renaming guisettings.xml (to guisettings.xml.bak), restarting kodi and re-applying your settings - maybe something has become set in your guisettings.xml that makes Kodi think PulseAudio is the default.

(2016-01-02, 21:24)Brian B Wrote: Thanks for all the work and effort, but it is all above my head...Everything seems to be working at the moment, so I will just wait...

(2016-01-02, 22:22)Milhouse Wrote:

(2016-01-02, 21:24)Brian B Wrote: Thanks for all the work and effort, but it is all above my head...Everything seems to be working at the moment, so I will just wait...

In a nutshell, fritsch builds were based on an older (more stable?) version of OpenELEC master with latest Kodi and latest FernetMenta work, my builds are based on latest OpenELEC master with latest Kodi and latest FernetMenta work.

Basically, other than the precise version of OpenELEC, they were pretty much the same. Basing my builds on latest OpenELEC can (and does) lead to some add-on breakage, which is addressed to some extent by the updated addons I provide.

Edit: Forgot to say that my builds also include a small selection of yet-to-be merged pull requests (ie. bug fixes, experimental features) that you wouldn't find in fritsch's builds

(2016-01-02, 21:05)Milhouse Wrote:

(2016-01-02, 17:40)D-an-W Wrote: Am I right in saying that build #1201 is the last to use Jarvis?

I have a couple of Android boxes as well as the Chromebox using a shared database so until there are Android build based on v17 I can't use any newer and still have the database kept in sync.

Strictly speaking, #0904 would be the last build based on "pure" Jarvis as all builds after that were a hybrid of Jarvis + VideoPlayer (the latter being a Kodi 17 feature).

However if all you're concerned about is the database version for Jarvis compatibility, then you want videodb=99 and musicdb=56, which means #1201 is your limit.

(2015-12-26, 21:50)megaup987 Wrote: Gentlemen, not sure if this should be in this thread, so if not, mods, please move it to the appropriate thread.

I am having issues with some 1080p24 VC-1 files having visual artifacts when VAAPI hardware acceleration is enabled. The artifacts do disappear if I turn hardware acceleration off, but then the video stutters.

I am running OpenELEC Generic build #1220 from this thread (OpenELEC-Generic.x86_64-7.0-Milhouse-20151220232738-#1220-gc07aeab), on an ASRock N3000 with Crucial 8GB RAM kit and a 250GB Samsung 850 EVO mSATA drive. I'm playing the video off the mSATA, but the results are the same if I play it off a USB drive. My UEFI version is N3000-NUC P1.50, CPU set to Sport Mode. I'm also having the same issue with OpenELEC 6.0.0.

I cut a section of the video I'm having problems with, and a member on the OpenELEC forum confirmed that they have the same problem on ASRock N3000. I uploaded the debug log and the section of the video below.

Log: http://xbmclogs.com/pvzinnfdj
File: https://docs.google.com/uc?id=0B9X316MN6HHvSlNWb1ZhSGo2X2M&export=download

I tried to address this issue on the OpenELEC forum, but it seems that I may get more support here. OpenELEC forum thread is here: http://openelec.tv/forum/116-vaapi-intel/79224-asrock-beebox-n3000-vc-1-visual-artifacts

Any help is appreciated.

(2016-01-02, 22:48)megaup987 Wrote:

(2015-12-26, 21:50)megaup987 Wrote: Gentlemen, not sure if this should be in this thread, so if not, mods, please move it to the appropriate thread.

I am having issues with some 1080p24 VC-1 files having visual artifacts when VAAPI hardware acceleration is enabled. The artifacts do disappear if I turn hardware acceleration off, but then the video stutters.

I am running OpenELEC Generic build #1220 from this thread (OpenELEC-Generic.x86_64-7.0-Milhouse-20151220232738-#1220-gc07aeab), on an ASRock N3000 with Crucial 8GB RAM kit and a 250GB Samsung 850 EVO mSATA drive. I'm playing the video off the mSATA, but the results are the same if I play it off a USB drive. My UEFI version is N3000-NUC P1.50, CPU set to Sport Mode. I'm also having the same issue with OpenELEC 6.0.0.

I cut a section of the video I'm having problems with, and a member on the OpenELEC forum confirmed that they have the same problem on ASRock N3000. I uploaded the debug log and the section of the video below.

Log: http://xbmclogs.com/pvzinnfdj
File: https://docs.google.com/uc?id=0B9X316MN6HHvSlNWb1ZhSGo2X2M&export=download

I tried to address this issue on the OpenELEC forum, but it seems that I may get more support here. OpenELEC forum thread is here: http://openelec.tv/forum/116-vaapi-intel/79224-asrock-beebox-n3000-vc-1-visual-artifacts

Any help is appreciated.

Gentlemen,

I apologize to hijack the thread again, but my issue is not resolved. I tried the latest build (#0101) and the artifacts are still present when VAAPI hardware acceleration in used. What should I try next?

(2016-01-02, 22:50)_Spook_ Wrote: @Milhouse If they are about the same, why does H.265 files on this build take more CPU then the Fritsch builds? Is the same EGL VAAPI from Intel included in your builds?