58 replies to this topic

[damtom85]

With line above you check what revision of drivers your image uses

[speed]

so are there new drivers?

is the problem solved yet?

so I can update? or is it still not fixed, and I should stay on old image?

[speed]

hi

is the problem solved yet?

can I flash or should I still wait?

[damtom85]

update drivers
20150623
 - Fix scrambling bit in recording
 - Improve transcoding

Found this on vu+ website, new drivers in June, I will flash new image on Monday, give you feedback

[speed]

after lack of any response I decided today to flash and try myself

 

cccam 2.2.1 doesn't work correct, when recording on 2nd tuner black screen

however that was solved with replacing 2.2.1 with 2.3.0

 

I don't have any of the movies from before to try if they play correct

but after trying all movies currently on the hdd, all seems to be working again

 

funny enough when coming here to post my results, seen you replied damtom85

let me know Monday if its the same result for you

[damtom85]

I will do, I have plenty movies on my hdd, with different codecs.

[speed]

and to add

on the new image with cccam 2.2.1 also don't see the cardreaders

also solved with changing to 2.3.0

[speed]

after some testing most formats I have tried are playing fine

only problem I have is with .mkv files

I can start, but then only can see them from start, cant pause forward or rewind, then it start from beginning again

[Erik Slagter]

No there is definitely no problem with mkv files (as I tell over and over). There IS a problem though with BROKEN mkv files. But that counts for all containers.

[speed]

so far all kmv have same issue

and if I go back to old december 2014 image these "broken" mkv files play fine?

[Erik Slagter]

Then I will guarantee you that if you re-pack them into mp4, you will have exactly the same problems.

[speed]

ok lets assume they are broke

then is it possible to let new images play broke mkv files?

just as the old December 2014 image plays broke mkv files perfectly?

[Erik Slagter]

My point is, and apparently you didn't take it, is that the problem is in the video bitstream. It's very probable not in the container. Processing of the video bitstream occurs mainly in hardware and just a tiny bit in the drivers. Both we have no control over. The demuxing of the container is done by gstreamer, of which we have been shipping version 0.10 over the last few years, no change there.

[damtom85]

Erik, so why if you play video everything is OK, only when you start skipping forward or reverse, solo2 have problems? Few post earlier you say it is driver problems now you say our mkv are broken? Make your mind, man.

[Erik Slagter]

Broken MKV files are incorrectly demuxed by gstreamer. That's why they're called broken. They're not according to specification. Besides that the driver is a part of the chain to make video playback work. If the drivers has bugs, you may experience problems with playback of whatever material. Both may be the case, at the same time. With VU+, it's not "unthinkable" there are driver bugs. I found two of them in the last two weeks (for features that work on other manufacturers' receivers).

[The_Raven]

I have similar problems but with iso files. I can not say if it has worked before, but now i have "strange" problems. For example the menu shows not correct but audio is working. If i press play, then the movie starts, but i have no audio. The iso plays ok on a computer (linux mint) with vlc.

[Erik Slagter]

The part of the image that plays both "iso" files and mkv is called gstreamer 0.10 and hasn't changed by us or the developers for a really long time. So it must be a driver update.

[The_Raven]

Ok, i hope VU read in this thread: Please update/fix the drivers!

If you need support in form of logs or something, let me know.

[theparasol]

Vu wont read along here... they seem to even ignore mail from the majority of users.

Guess its just wait and see what happens (if ever)