Codecs SAF v6 (based on LAVF) (3 Viewers)

[hoborg]

So you are now using LAVF video decoder instead of MS one?

No, I'm now using LAV instead of ffdshow.

View attachment 108965View attachment 108966View attachment 108967

Everything plays fine, and I don't get any of the delays I was getting with SAF 6.

Such a issue is possible, i have no change to test FFDshow video decoder decoding from NAS.
LAVF Video decoder is part of SAF too, but it is not enabled by default. You can enable it durning SAF install.
LAVF Video dacoder still missing some important features like DVD decoding and subtitles rendering, but it should support it soon.

It will be good if you can test reinstall SAF, enable LAVF video decoder durning install, setup MePo to use LAVF instead of FFDshow.
If file opening from NAS will be fast, it will be clear this issue is caused by FFDshow video decoder.

BTW, FFDshow is slowly replaced by LAVF, it is only a question of time, but there is still a lot of work until it will happend.

 

[Infidelus]

It will be good if you can test reinstall SAF, enable LAVF video decoder durning install, setup MePo to use LAVF instead of FFDshow.
If file opening from NAS will be fast, it will be clear this issue is caused by FFDshow video decoder.

Doesn't make a lot of difference. Still takes 30+ seconds to open an mp4 file with LAV video decoder using SAF 6. Still almost instantaneous if I don't use SAF but use the LAV codecs on the MP Extension Installer.

The only negative I've found so far with the setup without SAF, live TV picture pauses fairly regularly (which I presume is using the MS codec). Videos all play fine though and still no delay.

As for the NAS, it's got nothing to do with that as I've proven already. Files open immediately if I don't use SAF, but take ages if I do use SAF. SAF 5 doesn't have this problem, so it's something that's been introduced in the current version.

 

[Infidelus]

If recording service uses some video decoder then it is simply a bug (unless we are talking about analog video encoders). Please open a bug report instead of forcing people to reboot (or at least automatically restart the recording service). Stopping recording service could kill a recording that is in progress and user has no knowledge of that (and we get blamed for the missing recording!).

I am not a MePo user, so no bugreport from me.
If you search this thread, you will find this was multiple users request and it was general problem with multiple recording software.
Honestly, i have no idea why recoding services lock certain decoders on some systems just after system restart - maybe graph is bulded for EPG update? I dont known.
I prefer to have correctly installed decoders comparing to stoped recording.
And installing SAF (or other decoders) durning recording is simply fault on user side

So it's a user's fault that YOU put in code that stops their recorder working? Nice attitude ... I don't think.

Well, it was a multiple users request, not my own
It is only stoped durning SAF install. After restart, or when aplication call it, it will start again.

No offence, but I'm not really interested if multiple users have requested it. It's a codec pack, and you shouldn't be messing with Windows Services to install something that basic. If it's a bug as tourettes says, you should be reporting it, not arsing around with peoples Windows Services to fudge a fix. Not being a MePo user is a poor excuse, especially when you're on their forum pushing your codec pack to their userbase.

 

[hoborg]

Doesn't make a lot of difference. Still takes 30+ seconds to open an mp4 file with LAV video decoder using SAF 6. Still almost instantaneous if I don't use SAF but use the LAV codecs on the MP Extension Installer.

The only negative I've found so far with the setup without SAF, live TV picture pauses fairly regularly (which I presume is using the MS codec). Videos all play fine though and still no delay.

As for the NAS, it's got nothing to do with that as I've proven already. Files open immediately if I don't use SAF, but take ages if I do use SAF. SAF 5 doesn't have this problem, so it's something that's been introduced in the current version.

Then it is a little mystery to me.
SAF should install LAVF as LAVF installer do. SAF 5 is based on Haali spliter, SAF6 on LAVF splitter.
Too bad i cannot test it by myself to figure it out.
And if you copy the file to local disc, it will open fast?[DOUBLEPOST=1344800203][/DOUBLEPOST]

No offence, but I'm not really interested if multiple users have requested it. It's a codec pack, and you shouldn't be messing with Windows Services to install something that basic. If it's a bug as tourettes says, you should be reporting it, not arsing around with peoples Windows Services to fudge a fix. Not being a MePo user is a poor excuse, especially when you're on their forum pushing your codec pack to their userbase.

It is not that easy.
It is not possible to remove installed filtes if they are in use by recording service. SAF must stop the service to uninstall them.
I am open for ideas how to handle this in other way...

 

[hoborg]

As for the NAS, it's got nothing to do with that as I've proven already. Files open immediately if I don't use SAF, but take ages if I do use SAF. SAF 5 doesn't have this problem, so it's something that's been introduced in the current version.

OK, this seems to explain the problem. This is not in latest SAF, I will build new SAF test version with latest LAVF for test.

EDIT:
Here is the SAF 6.1.3 WIP with updated LAVF.
So if you can, test it please.
Thank you.

 

[doveman]

It is not that easy.
It is not possible to remove installed filtes if they are in use by recording service. SAF must stop the service to uninstall them.
I am open for ideas how to handle this in other way...

Hi hoborg

Maybe you could prompt "SAF needs to stop TVService, this will break any recordings currently in progress. Proceed Y/N" and allow the user to choose?

 

[Infidelus]

As for the NAS, it's got nothing to do with that as I've proven already. Files open immediately if I don't use SAF, but take ages if I do use SAF. SAF 5 doesn't have this problem, so it's something that's been introduced in the current version.

OK, this seems to explain the problem. This is not in latest SAF, I will build new SAF test version with latest LAVF for test.

EDIT:
Here is the SAF 6.1.3 WIP with updated LAVF.
So if you can, test it please.
Thank you.

Tried the WIP. No difference unfortunately. Are you sure there are changes in that file? It's the exact same file size as 6.1.2.[DOUBLEPOST=1344884955][/DOUBLEPOST]

No offence, but I'm not really interested if multiple users have requested it. It's a codec pack, and you shouldn't be messing with Windows Services to install something that basic. If it's a bug as tourettes says, you should be reporting it, not arsing around with peoples Windows Services to fudge a fix. Not being a MePo user is a poor excuse, especially when you're on their forum pushing your codec pack to their userbase.

It is not that easy.
It is not possible to remove installed filtes if they are in use by recording service. SAF must stop the service to uninstall them.
I am open for ideas how to handle this in other way...

I still disagree with you stopping services, but if you're going to, you need to restart them as well after you've finished the (un)install. You can't just leave somebody's recorder in a non-functional state, and the user shouldn't have to sit there trying to work out why their recordings suddenly aren't working. Not everyone's an IT wiz and knows what a Windows Service is, or what it does, and most of them probably don't care either. All they want is their chosen application to function as it's supposed to.

If people are using their MePo machines as PVRs/HTPCs, chances are they don't reboot them that often anyway, but instead put them in standby, which means the service is never going to restart by itself. By the time they realise MePo/FTR/whatever other recorder isn't working, they've already missed programs they wanted to record.

 

[hoborg]

Tried the WIP. No difference unfortunately. Are you sure there are changes in that file? It's the exact same file size as 6.1.2.

Oh, you are right, it was wrong file...
Original link replaced by correct one. It have SAF 6.1.3 in header.
Sorry for that.

 

[hoborg]

I still disagree with you stopping services, but if you're going to, you need to restart them as well after you've finished the (un)install. You can't just leave somebody's recorder in a non-functional state, and the user shouldn't have to sit there trying to work out why their recordings suddenly aren't working. Not everyone's an IT wiz and knows what a Windows Service is, or what it does, and most of them probably don't care either. All they want is their chosen application to function as it's supposed to.

If people are using their MePo machines as PVRs/HTPCs, chances are they don't reboot them that often anyway, but instead put them in standby, which means the service is never going to restart by itself. By the time they realise MePo/FTR/whatever other recorder isn't working, they've already missed programs they wanted to record.

Well, again, this is not that easy. SAF installer have no idea what servises are actually running and which are stopped.
The service can be stoped already durning SAF install by aplication itself and it can be started durning SAF uninstall.
User can even change recording software between SAF install/uninstall.
If SAF remember the original status, it will stop it and then we are in the same dead end.
I can add a question if stoping service should de done or not, but i think it will only bring more problems comparing to how it is done now.

I dont known how MePo handle recording service if aplication ask for it, but for example nPVR start it automatically if service is stoped, so there is no problem here.

 

[Infidelus]

Tried the WIP. No difference unfortunately. Are you sure there are changes in that file? It's the exact same file size as 6.1.2.

Oh, you are right, it was wrong file...
Original link replaced by correct one. It have SAF 6.1.3 in header.
Sorry for that.

Tried the new, new file. Same as before. 30 second delay before movie starts. MPEI LAV filters play film immediately