Modify
Warning Please read the Ticket HowTo before creating or commenting on a ticket. Failure to do so may cause your ticket to be rejected or result in a slower response.

Opened 2 years ago

Last modified 16 months ago

#10583 new Bug Report - General

Unable to playback recordings from Panasonic TV via UPnP

Reported by: joe@… Owned by: dblain
Priority: minor Milestone: unknown
Component: MythTV - UPnP Version: 0.25-fixes
Severity: low Keywords: UPNP DLNA TV
Cc: Ticket locked: no

Description

I am unable to playback recorded shows from MythTV on a Panasonic TX-P42G15GB TV via UPnP. I simply get the error message on the TV: "Cannot read file"

If I manually copy the recorded shows to the videos storage group, the TV plays the show back with no problem whatsoever. This leads me to believe that when the recording file is served to the TV in the Recordings storage group, something different is happening in the UPnP code, meaning that the TV is unable to read the file.

Other UPnP clients such as XBMC and VLC can playback the recordings ok, no matter what type of storage group the recording is in, so it's not a widespread problem, just specific to the TV we have/Panasonic TVs in general - this is the only Panasonic TV in the house, so I can't say which for sure.

No errors are showing up in the backend log (with -v all) and unfortunately the error message above is all I've got from the TV.

I've tried to work this one our for myself, but I'm unable to find any more information from logs why this is happening. I'm not a developer, but I do work for a software development company, so I have gained *some* experience working with code. I've therefore tried to have a look into the UPnP code myself, just to try to find some sort of direction to go with this, however I wasn't able to spot anything.

I would appreciate any help I can get on this - at the moment, I'm working around the issue by manually moving recording files from the Recordings storage group to the Videos one, every time someone wants to watch something that's been recorded. This is becoming a bit of chore - don;t mean to sound ungrateful though!

Attached files:
not-working.mythbackend.log: Log file taken when trying to playback a recording as a "Recording" on the TV. (mythbackend -v all)
working.mythbackend.log: Log file taken when successfully playing a recording as a "Video" on the TV. (mythbackend -v all)

If there's any more info needed, I'll be more than happy to provide it. I'm wondering if there's some way I can get more output from what the backend is actually sending to the TV, then diffing the output between a "Recording" and a "Video"?

Thank you.

Joe

Attachments (5)

not-working.mythbackend.log (7.1 KB) - added by joe@… 2 years ago.
Log file taken when trying to playback a file from "Recordings"
working.mythbackend.log (4.1 KB) - added by joe@… 2 years ago.
Log file taken when trying to playback a file from "Videos"
xbmc.log.tar.gz (12.5 KB) - added by Joe Nyland <joe@…> 2 years ago.
Log file from XBMC demostrating the reported behavior
0.24 Successful Recording Playback.log.gz (4.5 KB) - added by Joe Nyland <joe@…> 2 years ago.
Scenario 2
0.25 Failed Recording Playback.log.gz (1.6 KB) - added by Joe Nyland <joe@…> 2 years ago.
Scenario 4

Download all attachments as: .zip

Change History (40)

Changed 2 years ago by joe@…

Log file taken when trying to playback a file from "Recordings"

Changed 2 years ago by joe@…

Log file taken when trying to playback a file from "Videos"

comment:1 Changed 2 years ago by joe@…

My thread from mythtv-users list is here: http://www.gossamer-threads.com/lists/mythtv/users/510224

Unfortunately, no-one was able to offer any assistance.

Also, I missed off the following from my initial ticket post:

$ mythbackend --version
MythTV Version : v0.25
MythTV Branch : fixes/0.25
Network Protocol : 72
Library API : 0.25.20120408-1
QT Version : 4.6.2
Options compiled in:

linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcrypto using_libdns_sd using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2 using_v4l1 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg using_libxml2

comment:2 follow-up: Changed 2 years ago by J.Pilk@…

I'm interested in this, because I have been thinking of getting a Panasonic TV. I downloaded the user manual which lists file types that /may/ be acceptable. I couldn't copy text from the pdf, apparently because of DRM, but it lists PS (.mpg, .mpeg, .vob, .vro) and TS (.m2ts, .tp, .trp, .ts). Maybe this could be useful?

I also came across a 'WmsClientConfig?' post for <DeviceType?>

<$00000409>Panasonic Viera TX-P42G20E (DLNA, 16:9, 1920x1080)</$00000409>
<$00000419>Panasonic Viera TX-P42G20E (DLNA, 16:9, 1920x1080)</$00000419> that might give hints. I'm not clear what device might be destroyed if one tried to actually use it.

Google panasonic_viera_tv_dlna_wide_1920x1080.zip

comment:3 in reply to: ↑ 2 Changed 2 years ago by Joe Nyland <joe@…>

Replying to J.Pilk@…:

I'm interested in this, because I have been thinking of getting a Panasonic TV.

That's great - I'd have no problem recommending one to you, if we were able to resolve this issue.

I downloaded the user manual which lists file types that /may/ be acceptable. I couldn't copy text from the pdf, apparently because of DRM, but it lists PS (.mpg, .mpeg, .vob, .vro) and TS (.m2ts, .tp, .trp, .ts). Maybe this could be useful?

That's correct - I'm now able to do a lossless "Auto Detect" transcode in Myth which conveniently converts the recording from MPEG-TS to MPEG-PS. Once this has completed, the TV plays the file back with no problems, just as long as it's not in the "Recordings" group. As I've mentioned above, if I copy the file to a directory in my "Videos" storage group and re-scan the library, I'm able to playback the transcoded recording on the TV with no problems - FF and RW, play pause work great.

I also came across a 'WmsClientConfig?' post for <DeviceType?>

<$00000409>Panasonic Viera TX-P42G20E (DLNA, 16:9, 1920x1080)</$00000409>
<$00000419>Panasonic Viera TX-P42G20E (DLNA, 16:9, 1920x1080)</$00000419> that might give hints. I'm not clear what device might be destroyed if one tried to actually use it.

Google panasonic_viera_tv_dlna_wide_1920x1080.zip

I'm afraid I'm not familiar with what this is. Could you expand on this a little please?

Thank you for your input.

Joe

comment:4 follow-ups: Changed 2 years ago by stuartm

It sounds like it's just the file extension which is tripping up the TV. Does renaming a file to .m2ts work?

comment:5 Changed 2 years ago by J.Pilk@…

I made my post above in the hope that it would give further background to anyone thinking about this. The list of file types suggests that it might be worth trying a simple rename if myth could be persuaded that the rename didn't matter. The conf file is a mystery to me but someone might see something relevant there. I can't really comment further. Good luck!

comment:6 in reply to: ↑ 4 Changed 2 years ago by Joe Nyland <joe@…>

Replying to stuartm:

It sounds like it's just the file extension which is tripping up the TV. Does renaming a file to .m2ts work?

I hope it's something as simple as that! However, I doubt it, as I'm not renaming it when playing back the recordings after moving to the videos storage group. i.e. it plays back fine with a .mpg file ext. just as long as the file is played back from the Videos group but not the Recordings group.

I will try this tonight though, so we know for sure.

Replying to J.Pilk@…:
That's ok, I understand. Thanks for trying to help!

comment:7 in reply to: ↑ 4 Changed 2 years ago by Joe Nyland <joe@…>

Replying to stuartm:

It sounds like it's just the file extension which is tripping up the TV. Does renaming a file to .m2ts work?

Afraid not: This evening I tried renaming the file to .m2ts as suggested, then updated the file name in the recorded table, so that MythTV served up the correct file name to the UPnP client. I then made sure I could play back the recording with the new file name from MythFrontend - no issues here. I then switched to the TV, but it still can't play the recording back.

comment:8 Changed 2 years ago by J.Pilk@…

Pity. Of course, if it's now a PS file that name wouldn't be appropriate, so if you haven't tried it already it might be worth repeating with a new recording.

comment:9 Changed 2 years ago by Joe Nyland <joe@…>

Unfortunately, after renaming a recording that I haven't transcoded to MPEG2-PS (i.e. it's still a TS contanier) to .m2ts and updating the DB accordingly, I'm still unable to play it back on the TV. As expected though, I can't play this video back in the 'Videos' group either, as it's a TS container, not PS. As far as I can make out from the instruction manual, the TV only supports MPEG2-PS containers.

What's interesting is that last night, I tried to play back some recordings from XBMC via UPnP from MythTV, but I was unable to get anything to play from the 'Recordings' folder there too - in other words, I saw the same behaviour that the Panasonic TV is demonstrating. I know I said in my original report that XBMC could play files back ok, but my only guess is that something changed with XBMC's recent major release since my last test of this issue in XBMC. (OR I didn't test it thoroughly enough to highlight the problem there!)

I'm going to try to see if I can get XBMC to log why it's failing to play the 'recordings' back and that hopefully might help shed a little light on this issue with the TV *fingers crossed*...

comment:10 Changed 2 years ago by Joe Nyland <joe@…>

Ok, I've managed to get a full debug log from XBMC which shows an error when trying to playback a recording from the 'Recordings' folder. I'm attaching the full log, but the messages I'm referring to is:

23:29:43 T:2889241280 DEBUG: OnPlayMedia? upnp://a28c48d5-cfa5-4e02-a552-52398fb1f699/RecTv%2f0%2fitem%3fChanId%3d1003%26amp%3bStartTime%3d2012%2d04%2d06T20%3a59%3a00

23:29:43 T:2889241280 ERROR: CUPnPDirectory::GetResource? - no items returned for object RecTv?/0/item?ChanId?=1003&amp;StartTime?=2012-04-06T20:59:00

23:29:43 T:2889241280 ERROR: Playlist Player: skipping unplayable item: 0, path [upnp://a28c48d5-cfa5-4e02-a552-52398fb1f699/RecTv%2f0%2fitem%3fChanId%3d1003%26amp%3bStartTime%3d2012%2d04%2d06T20%3a59%3a00]

23:29:43 T:2889241280 DEBUG: Playlist Player: no more playable items... aborting playback

...so, it looks like this issue is not just isolated to Panasonic TVs after all. Please let me know what further information is required to troubleshoot this further.
Thanks.

Changed 2 years ago by Joe Nyland <joe@…>

Log file from XBMC demostrating the reported behavior

comment:11 Changed 2 years ago by J.Pilk@…

Hi: I wonder if this is related to the format of the starttime: I've been having problems with this in scripts that used to work in 0.24 but don't in 0.25. mythutil needs YYYYMMDDHHMMSS but the format returned by the database is YYYY-MM-DD HH:MM:SS

comment:12 Changed 2 years ago by Joe Nyland <joe@…>

It could well be. Hopefully, I'm going to get some time tonight/tomorrow night to have a look in the database, as this message looks very strange: "no items returned for object RecTv??/0/item?ChanId??=1003&amp;StartTime??=2012-04-06T20:59:00" Surely this is a database related problem if this isn't returning any filename at all...

I will update with the results. Thanks.

comment:13 Changed 2 years ago by Joe Nyland <joe@…>

Unfortunately I don't seem to be able to get it going - I thought it would be something simple like editing the start time for the recording to an hour before, but this still fails.

Has anyone got any suggestions?

To summarise:

  • I'm unable to playback 'recordings' from MythTV in XBMC. I get the message "ERROR: CUPnPDirectory::GetResource?? - no items returned for object RecTv??/0/item?ChanId??=1003&amp;StartTime??=2012-04-06T20:59:00" when I try to play something back like this.
  • I get the same behaviour on my Panasonic TV over UPnP, but I can't say for sure it's the same root cause as I'm unable to obtain debug logs from the TV - I'm assuming it's the same issue though, as it the exact same behaviour as above.
  • I am able to play back recordings via UPnP in XBMC and on the Panasonic TV, provided I have copied them to the 'videos' storage group and scanned for new videos.
  • I am able to play back 'recordings' and 'videos' in VLC, which is strange, though.

Thanks.

comment:14 Changed 2 years ago by vin@…

Just upgraded to 0.25fixes from 0.23fixes and now am unable to play back recordings on Panasonic Viera.

comment:15 Changed 2 years ago by Joe Nyland <joe@…>

Good to know that it works for you at least - sorry to sound pedantic, but you are definately playing back strictly 'Recordings', not recordings that have been moved to the 'Videos' group?

As I still think this could be time zone related, please could you confirm what time zone you're in?

comment:16 Changed 2 years ago by J.Pilk@…

I now have a current-model Panasonic TV, Series E5, and Myth boxes running 0.25/SL6 and 0.24.3/F15. Both work well via UPnP with some content but not all. Recordings are from dvb-t (SD) and dvb-t2 (HD) in the UK.

Unprocessed recordings usually play well, as do recordings that have been cut with an experimental tool and are still mpeg2-ts. I have one HD recording in which the sound format changed at a programme transition. Myth played it uncut but vlc hung. After cutting, both will play it but the TV will not. As a Video, Myth plays it with no sound. Mediainfo says the cut file has no PAT/PMT. I still have the original and may try another cut.

Most of my SD recordings have been cut using mythcutprojectx, which, like mythtranscode -m, converts them to mpeg2-ps; they do not play via the net. The TV manual suggests that the TV expects an .mpg file to be PS, but in fact it seems happy to play it as TS.

I haven't done much with the Videos. In 0.24 I see only Video Root, with one unplayable .iso file. In 0.25 I now see four copies of everything. Some of them play.

http://www.gossamer-threads.com/lists/mythtv/users/515566#515566

comment:17 Changed 2 years ago by J.Pilk@…

I should have said that the comments above relate to 0.25. SD recordings from the 0.24.3 box play via the net both before and after conversion to PS format. Imported HD recordings play too.

comment:18 Changed 2 years ago by J.Pilk@…

Please delete the reference to the HD recording with no PAT/PMT. This was the product of an experiment with mythutil --pidfilter. The original recording, cut to start after the programme changeover, plays in mythfrontend, in vlc and (simultaneously with one or the other of these if required) via UPnP. As I think I should expect with the TS format, commercial cutting doesn't seem to have caused a loss of A/V sync. Sorry for the confusion.

comment:19 Changed 2 years ago by Joe Nyland <joe@…>

Glad you seem to be having slightly more successful experience than I. Unfortunately, my TV is still not playing back 'recordings', only 'videos' as before.

My instruction manual for my model Panasonic TV clearly states that MPEG2_PS is required - it makes no mention of MPEG2-TS, so I'm assuming this will never work on my TV (it definitely doesn't currently)

I think the idea that you have touched on before about the format change (possibly between 0.24 and 0.25) of the start time seems like the most likely cause to this. i.e. The actual transcoded files playback ok when in the 'videos' group which of course doesn't use the starttime filed in the DB, so it has no problem serving up the correct file via UPnP. However, when the same files are selected via UPnP from 'recordings' it doesn't seem to be able to match the recording file up to the record in the database in order to serve it via UPnP. I just don't know how to fix it.

I'm running this version currently:
MythTV Version : v0.25-58-g58fd2a5
MythTV Branch : fixes/0.25
Network Protocol : 72
Library API : 0.25.20120408-1
QT Version : 4.6.2

comment:20 follow-up: Changed 2 years ago by J.Pilk@…

I'm not sure if you've said whether your TV can play a 'raw' recording (TS) as a Video. It would be perverse if it can't play them at all, because AIUI that's what it does when playing live, plus of course some extra PID filtering to extract it from the mux.

I've just tried using the mythlink script to create links in the Videos directory. They're playable in the (0.25) frontend, but at present UPnP doesn't see them.

comment:21 Changed 2 years ago by J.Pilk@…

I spoke too soon - they've just appeared :-)

comment:22 in reply to: ↑ 20 Changed 2 years ago by Joe Nyland <joe@…>

Replying to J.Pilk@…:

I'm not sure if you've said whether your TV can play a 'raw' recording (TS) as a Video. It would be perverse if it can't play them at all, because AIUI that's what it does when playing live, plus of course some extra PID filtering to extract it from the mux.

No, you're right, I've not specifically tried this (at least I can't remember it), I've only tried PS files from 'videos' over UPnP. I'll try and give this a go later tonight - unfortunately this TV has been 'claimed' for tonight :-). It would be interesting to see if this works or not.

I've just tried using the mythlink script to create links in the Videos directory. They're playable in the (0.25) frontend, but at present UPnP doesn't see them.

Yes, I've had some success with using mythlink.pl as a bit of a work around for now. 'mythutil --scanvideos' is your best way of getting new videos to show up on the UPnP clients, after adding new videos to 'Videos' BTW.

comment:23 Changed 2 years ago by J.Pilk@…

Perhaps it's worth noting, since it won't be obvious otherwise, that the format of the date displayed on the UPnP client's screen is MM/DD/YY. I know MythTV is based in the USA, but... At first I thought that simple M/D confusion might explain things, but the PS/TS split gives a better fit to what I see in 0.25.

comment:24 Changed 2 years ago by joe@…

Just tried playing back an untouched, fresh MPEG2-TS file on the TV from the videos group, but no luck I'm afraid. I think maybe for the slightly older models, MPEG2-PS is required - in the grand scheme of things, this is not really an issue to me.

Thanks for the suggestion though.

comment:25 Changed 2 years ago by mdean

Guys, please take the discussion to the mailing list. Several of the developers try to read every message in every ticket, and since none of the above messages is helpful in telling us what needs to be changed to fix the issue you're seeing, it's a waste of time to read through all of them.

Instead, please try to figure out what's going on through a discussion in the mailing list. Once you arrive at a conclusion--or at least identify something that may be important to fixing the issue--then post a message in the bug database summarizing the findings (and/or linking to the appropriate message within the thread on the list).

I appreciate that you guys are working hard to try to figure out what needs to be done, but it would be much easier for us if you did so on list and kept this ticket short enough that the developer who eventually fixes the issue can read through it quickly without having to wade through all the false starts and trial and error you went through to determine the issue. Thanks.

comment:26 Changed 2 years ago by J.Pilk@…

I posted a summary of my conclusions so far for my Panasonic TV series E5 here:

http://www.gossamer-threads.com/lists/mythtv/users/515837#515837

The only other points I have noticed since then concern playback of 'Videos' in 0.25. The duration shows as zero and the progress bar is inactive, although the speed control works. This applies to both TS and PS formats. I haven't tried this with a Video having its own seektable.

'Recordings' in PS format do not play in 0.25. 'Recordings' in both TS and PS formats are described on-screen as MPEG-TS.

comment:27 Changed 2 years ago by Joe Nyland <joe@…>

Mike, you're right - it does look a little bit too messy in the thread above. As John has said though, a lot of information has been pooled in the mythtv-users thread he's linked to.

Here's a summary of my findings from my recent testing of the issue. I appreciate they aren't very detailed and would be much more helpful with more verbosity, but I'm afraid I can't get any more useful info than the logs I've already attached to this ticket.

Nonetheless, here's a summary of what I've found:

  1. Recordings made on a test VM with 0.24 play back in XBMC and VLC but not on the Panasonic TV. (Expected behaviour)
  2. Recordings made on a test VM with 0.24 then transcoded to MPEG2-PS with MythTranscode? play back in XBMC, VLC and on the Panasonic TV perfectly. (Expected behaviour)
  3. Recordings made on a test VM with 0.25 do not play back in XBMC and do not play back on the Panasonic TV. VLC has great difficulty playing back in such a scenario - it's unwatchable, but there's something there. (Unexpected behaviour)
  4. Recordings made on a test VM with 0.25 then transcoded to MPEG2-PS with MythTranscode? do not play back in XBMC and do not play back on the Panasonic TV. VLC has great difficulty playing back in such a scenario - it's unwatchable, but there's something there. (Unexpected behaviour)
  5. Recordings made on my MythTV server (0.25) do not play back on either XBMC or the Panasonic TV. VLC has great difficulty playing back in such a scenario - it's unwatchable, but there's something there. So I see the same behaviour as scenario 4, but with a physical server, that's working great otherwise - hence this ticket. (Unexpected behaviour)
  6. Recordings made on my MythTV server (0.25) that are transcoded to MPEG2-PS and then copied/moved to the 'Videos' storage group within MythTV play back fine on XBMC, VLC and the Panasonic TV. This is unfortunately limited, as they are presented as a 'video' file, and are therefore not organised into the various groups that recordings are, such as storage group, title, channel, show, etc.

I'm uploading full logs for scenarios 2 and 4, as they are the 'before' and 'after' logs, which should theoretically show the difference, however they don't look too helpful to me. I hope they are of some use to whoever picks this ticket up.

No-one on mythtv-users has been able to chime in to help, so that was the reason for pooling our results here for the developers to have a look when they have time. I hope this is a bit more helpful.

Thanks,

Joe

Changed 2 years ago by Joe Nyland <joe@…>

Scenario 2

Changed 2 years ago by Joe Nyland <joe@…>

Scenario 4

comment:28 Changed 20 months ago by Peter Mitchell <peterpf_mitchell@…>

The problem with UPNP recorded tv playback being experienced with Panasonic TVs with mythtv 0.25.x is located in the following module:

mythtv/programs/mythbackend/upnpcdstv.cpp: Line 408 onwards:

Sony BDPS370 requires a DLNA Profile Name
FIXME: detection to determine the correct DLNA Profile Name
if (sMimeType == "video/mpeg")
{

sProtocol += ";DLNA.ORG_PN=MPEG_TS_SD_NA_ISO";

}

If the above section of code is deleted / commented out then people possessing a Panasonic TV will once again be able to stream TV recordings via UPNP to their TV just as they were prior to 0.25.

As the above appears to be a fix for a particular Sony bluray player I would suggest this part of the code be enhanced to ensure that the protocol string is only applied when a sony device is attached.

comment:29 Changed 20 months ago by J.Pilk@…

http://code.mythtv.org/trac/ticket/9446#comment:10

Is there a way of making changes like this configurable, without needing a rebuild?

comment:30 Changed 20 months ago by J.Pilk@…

See http://code.mythtv.org/trac/ticket/10583#comment:28 for effects on Panasonic, and maybe other, devices.

comment:31 Changed 20 months ago by J.Pilk@…

Comment 30 above got attached to the wrong browser tab. It was intended for #9446

I haven't tried the suggested cure yet, but on reflection, although it might work, it doesn't look as if it would be the main issue for me. I think the _NA_ is likely to refer to North America, while I'm in the UK. However, I did come across this, which lists the results of interrogating several UPnP clients about their capabilities and could be useful. Mine is the E5B series, downmarket from the first-listed ET5B series under Panasonic.

http://wiki.serviio.org/doku.php?id=devices_format_support

comment:32 Changed 20 months ago by J.Pilk@…

Bah!. I should have re-read the full patch, not just the bit in upper case. Yes, it looks as if it's switching output to something appropriate to N America. That could explain why I see a difference between 0.24 (which I no longer have) and 0.25. I'm not clear why it's that specific difference.

In unpatched 0.25 I can play dvb-t Recordings in TS format but not after conversion to PS; via mythlink, as Videos, both formats play. I only see an 'All Videos' option; no directory structure.

comment:33 Changed 17 months ago by dataclue@…

I just wanted to say that my symptoms with my Panasonic and 0.26fixes just upgraded are as follows:

  1. can't play mpeg2's from recordings
  2. using mytharchive OR
  3. simply moving the file to "videos" allows the file to be played

There is NO CHANGE to the ".mpg" file itself in step 2 -- it is not transcoded by mytharchive, and in 3 it's just "cp".

Do I need to try applying the patch above or is there a fix for this now?

comment:34 Changed 16 months ago by hanjo@…

Same issue with mythtv on Ubuntu 12.10 ( 0.25.2+fixes.20120802.46cab93-0ubuntu1.12.10 )
as upnp server and xbmc as upnp client.
xbmc shows the preview-pictures bur did not play the recording.

Workaround:
Just add the directory from your recordings ( /var/lib/mythtv/recordings )
to the storage Group "Videos" and do a scan (mythutil --scanvideos).
Now you can access all recordings via "videos" but without preview-picture.

comment:35 Changed 16 months ago by robert@…

If this code is indeed a problem:

// Sony BDPS370 requires a DLNA Profile Name
// FIXME: detection to determine the correct DLNA Profile Name
if (sMimeType == "video/mpeg")
{
  sProtocol += ";DLNA.ORG_PN=MPEG_TS_SD_NA_ISO";
}

.. then I think it can be safely removed because a few lines up, there's this code:

// If we are dealing with a Sony Blu-ray player then we fake the
// MIME type to force the video to appear
if ( pRequest->m_eClient == CDS_ClientSonyDB )
{
  sMimeType = "video/avi";
}

And although I don't have a BDPS370 it looks like the Sony BDPS370 sends the X-AV-Client-Info header which makes MythTV identify it as a CDS_ClientSonyDB.

So, sMimeType is never "video/mpeg" for a Sony BDPS370 and the problematic code is actually not run for the BDPS370.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.