On Apr 25, 2007, at 4:26 PM, stuart wrote:

>
> Hi Roger...
>
> Roger Heflin wrote:
>> stuart wrote:
>>> Hi Jan...
>>>
>> [snip]

>> According to the datasheet the MediaMVP cannot handle more than
>> 12Mbits so even if it could handle the 720p or 1080i resolution  
>> (which
>> I also think there is probably a limit there too) the bit rate
>> would be too high.
>>
>> You could detect the audio being not decodeable, and go to VLC, or
>> one could detect wrong resolutions and go to VLC.   But someone would
>> need to code these features in.
>>
>> Right now I deal with by having an automatic process that makes  
>> symbolc
>> links to all of the files in the highdef directory with .avi on  
>> it, and
>> then view via the file viewer with vlc.
>
> Ha! the audio not decodeable! That's an idea. Although, if it is easy,
> you are still faced with setting up all those locally mirrored files.
> Or would you be?  Hummm... VLC only works on mvpmc while in the file
> browser.  If you are in the mythtv application of mvpmc and you  
> started
> receiving a file w/o normal audio you couldn't tell mythtv to use VLC.
>

Ah yes. I see the problem. If we're using the mythtv protocol to get  
the file, then it would be hard to redirect to VLC (or whatever it  
takes to do that).


> I think what this detection buys you is that you may be able to NFS
> export your mythtv files and mvpmc might then detect which do not have
> ordinary audio and ask VLC to transcode.

If you have the file available (via NFS) can't you look into it a SEE  
what it is?

For example, the unix 'file' utility tells me this about a regular SD  
file:

1065_20070303210000.mpg: MPEG sequence, v2, program multiplex

For an HD file, it tells me this:

3700_20070415170000.mpg: data

So obviously there SOME way to read a file header or whatever and see  
what the file is (not just the extension). Would that help?

I doubt this would help with the mythtv-protocol for access, but I  
can live with setting up NFS exports for these files (i.e. when I use  
the myth interface on the mvpmc, instead of requesting the file via  
mythtv protocol, look to see if it's in the preconfigured NFS mounted  
directory first and use THAT instead).

>   So, it would save you from
> having to make the soft links w/the different avi file name endings.
>
> I am assuming that mvpmc will be able to at least tell that there  
> is no
> regular audio.  Right now I am not sure if it gets that far.
>
> But you would not get all the great native mythtv support like file  
> show
> names and the like.  You would be left with long files names that look
> like dates and times.
>
> I still think the best would still be if mythtv back end would handle
> client limitations.
>

Yes, that would be nice...

jan


>
>
>
>
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Mvpmc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mvpmc-users
> mvpmc wiki: http://mvpmc.wikispaces.com/


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to