I have been to busy lately to keep testing all the time but I just tried the newest build and I still have bad playback. Plus I assumed just constant saying that it didn’t work yet would not be helpful when you have the sample to test on your own.
But any hope it can be figured out sometime soon? It does seem like playback performance should be a fair high priority.
it is but compared to OE, OSMC is far more complex and may i remind you that this is alpha software with 1 developer on it ?
so do you think its fair to n00b rush things ?
All I’m asking for is some peace of mind that it is being worked on, I have had issues including other places before where I thought something was being done and then after a month I find out it was just forgotten. For the checking of different builds nothing changes so I wanted to make sure it was not forgotten again. It is not like I’m constantly bringing it up I have waited a month since the last time.
You seriously don’t see the daily new builds that keep magically appearing with new commits and changes?
I wasn’t saying work in general just that the one issue never send to change.
The links aren’t valid. When you say it works with OE, are you referring to a stable, or Milhouse nightly build?
It was a current nightly from around the time of Milhouse helping me in this thread HEVC frame dropping on Raspberry Pi 3
Working link http://s000.tinyupload.com/index.php?file_id=97038983516597011541
What clock settings did you use to play it back in OE/LE? Are you matching them on OSMC?
I’m using these same settings on both OSMC and OE and found from a kodi.log that the OE nightly I have was compiled Mar 30 2016
arm_freq=1275
over_voltage=4
sdram_freq=575
sdram_schmoo=0x02000020
over_voltage_sdram_p=6
over_voltage_sdram_i=4
over_voltage_sdram_c=4
core_freq=500
v3d_freq=500
h264_freq=333
gpu_mem=256
Possibly NEON related.
Will look in to it when I get some time, but we did spend a while last year looking at this issue to no avail.
Thanks
16.8-080, 13 May 2016: Based off OSMC commit 49be9df and newclock5 (656a69da)
Build Highlights
newclock5
New commits in this build:
mmalcodec: Also wake up decoder when a new input buffer is available (656a69da)
Commits no longer in build:
[omx] Report decoded image name (c8daea72)
VideoPlayer: Different accurate value for omxplayer_mode has no effect (162c2efb)
mmalrenderer: Avoid creating presenting thread when it is not required (7a3a0d41)
mmalcodec: Set initial aligned height explicitly to avoid multiple reconfigures in renderer (a02702f0)
omxplayer: Reset the EOS state on a flush (36aac474)
rbp: Fix possible leak in rendercapture interface (87ccd49a)
omximage: Fix resolution in logging message (80f86190)
Hi,
AdvancedSettings.xml is updated in the new krypton for the network section. I believe its not there within the default advancedsettings on these krypton builds.it would be nice if you can move the network section into the new cache tag.
<cache>
<memorysize>0</memorysize> <!-- number of bytes used for buffering streams in memory
When set to 0 the cache will be written to disk instead of RAM -->
<buffermode>0</buffermode> <!-- Choose what to buffer:
0) Buffer all internet filesystems (like "2" but additionally also ftp, webdav, etc.) (default)
1) Buffer all filesystems (including local)
2) Only buffer true internet filesystems (streams) (http, etc.)
3) No buffer -->
<readfactor>4.0</readfactor> <!-- this factor determines the max readrate in terms of readbufferfactor * avg bitrate of a video file.
This can help on bad connections to keep the cache filled. It will also greatly speed up buffering. Default value 4.0. -->
</cache>Thanks - will look into this. I see there are a few other changes as well.
In the upcoming Kodi v17, the following tags are removed from network and placed under a new cache tag. Also, cachemembuffersize is renamed to memorysize and readbufferfactor is renamed to readfactor.
16.8-081, 15 May 2016: Based off OSMC commit 1a9335b and newclock5 (cd093962)
Build Highlights
OSMC
Add fix for EPG search (1a9335b00)
newclock5
New commits in this build:
mmalcodec: temp: Add an extra input buffer to reduce chance of stutter after seek (54a30996)
mmalrender: Allow renderer to be reconfigered from GetPool (cd093962)
This was discussed in Slack with @popcornmix a couple of days ago.
Looks like we only need readfactor to be set in advancedsettings.xml now.
Sam
16.8-082, 16 May 2016: Based off OSMC commit 1a9335b and newclock5 (2288ed4c)
Build Highlights
newclock5
New commits in this build:
mmalrender: Allow renderer to be reconfigured from GetPool (7e5e875b)
RenderSystem: Load correct identity (3a635607)
mmal: Make some of the more verbose logging a build time option (2288ed4c)
Commits no longer in build:
mmalcodec: temp: Add an extra input buffer to reduce chance of stutter after seek (54a30996)
mmalrender: Allow renderer to be reconfigered from GetPool (cd093962)
@gmc Is there an issue with the repo ?
It’s been a while since I last updated, but apt-get update is failing with the following message:
W: Failed to fetch http://download.osmc.tv/dev/gmc/./Packages 404 Not Found
?
I’m also experiencing the same issue. Will look into it and let you know when its fixed.
Can you try again now - issues has been fixed.