Mailing List Archive: MythTV: Users

What can we expect in 0.23?

Index | Next | Previous | View Threaded

nospam312 at gmail

Nov 2, 2009, 10:40 AM

Post #1 of 7 (1482 views)
Permalink

What can we expect in 0.23?

Just a friendly request - does anyone know what may be worked on in 0.23?

I guess the major feature of 0.22 was MythUI and 0.23 will build on
this going on what I have read so far but are any other features
planned?

For me I would like to see proper BBC iPlayer (and ITV/C4/five Player)
support with a decent integrated interface. I would certainly try to
help out with testing.

TIA
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

robert.mcnamara at gmail

Nov 2, 2009, 10:46 AM

Post #2 of 7 (1408 views)
Permalink

Re: What can we expect in 0.23? [In reply to]

On Mon, Nov 2, 2009 at 11:40 AM, nospam312 <nospam312 [at] gmail> wrote:
> Just a friendly request - does anyone know what may be worked on in 0.23?
>
> I guess the major feature of 0.22 was MythUI and 0.23 will build on
> this going on what I have read so far but are any other features
> planned?
>

More MythUI, possibly some work on MythUI'ing MythMusic, and some
other stuff that I'd rather not commit to on the list on the chance it
doesn't happen. Everyone has their own priorities and it's not really
centrally administrated. We're also working to clean up/remove
unnecessary, redundant, and unused settings and improve usability,
though that may be an ongoing effort.

> For me I would like to see proper BBC iPlayer (and ITV/C4/five Player)
> support with a decent integrated interface. I would certainly try to
> help out with testing.

This is pretty unlikely to happen as a) nobody has indicated they plan
to work on it and b) it would need to be done in a way that does not
violate iPlayer terms of service, meaning (likely) running it in a web
browser. Anything could happen, but unless at least there's someone
with the time and inclination to work on it, and unless we have a ToS
compliant way of doing it, it's unlikely to be seen in Myth.

Robert
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

davehoz at gmail

Nov 2, 2009, 4:38 PM

Post #3 of 7 (1388 views)
Permalink

Re: What can we expect in 0.23? [In reply to]

One feature I would like to see is proper naming (Ie human readable)
file naming of mythtv recordings. Similar to the WMC filemame
convention, or is there already a way to do this?

2009/11/3 Robert McNamara <robert.mcnamara [at] gmail>:
> On Mon, Nov 2, 2009 at 11:40 AM, nospam312 <nospam312 [at] gmail> wrote:
>> Just a friendly request - does anyone know what may be worked on in 0.23?
>>
>> I guess the major feature of 0.22 was MythUI and 0.23 will build on
>> this going on what I have read so far but are any other features
>> planned?
>>
>
> More MythUI, possibly some work on MythUI'ing MythMusic, and some
> other stuff that I'd rather not commit to on the list on the chance it
> doesn't happen. Everyone has their own priorities and it's not really
> centrally administrated. We're also working to clean up/remove
> unnecessary, redundant, and unused settings and improve usability,
> though that may be an ongoing effort.
>
>> For me I would like to see proper BBC iPlayer (and ITV/C4/five Player)
>> support with a decent integrated interface. I would certainly try to
>> help out with testing.
>
> This is pretty unlikely to happen as a) nobody has indicated they plan
> to work on it and b) it would need to be done in a way that does not
> violate iPlayer terms of service, meaning (likely) running it in a web
> browser. Anything could happen, but unless at least there's someone
> with the time and inclination to work on it, and unless we have a ToS
> compliant way of doing it, it's unlikely to be seen in Myth.
>
> Robert
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

--
David Hunter
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

robert.mcnamara at gmail

Nov 2, 2009, 4:42 PM

Post #4 of 7 (1394 views)
Permalink

Re: What can we expect in 0.23? [In reply to]

On Mon, Nov 2, 2009 at 5:38 PM, David Hunter <davehoz [at] gmail> wrote:

> One feature I would like to see is proper naming (Ie human readable)
> file naming of mythtv recordings. Similar to the WMC filemame
> convention, or is there already a way to do this?
>

Please don't top post on this list.

Yes, you can use the mythrename script.

Robert
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Nov 2, 2009, 5:15 PM

Post #5 of 7 (1390 views)
Permalink

Re: What can we expect in 0.23? [In reply to]

On 11/02/2009 07:42 PM, Robert McNamara wrote:
> On Mon, Nov 2, 2009 at 5:38 PM, David Hunter wrote:
>
>> One feature I would like to see is proper naming (Ie human readable)
>> file naming of mythtv recordings. Similar to the WMC filemame
>> convention, or is there already a way to do this?
> Please don't top post on this list.
>
> Yes, you can use the mythrename script.

Though doing so will likely cause issues.
http://www.mythtv.org/wiki/Mythrename.pl

In truth, Myth is /already/ doing the right thing by naming the
recordings using only Arabic numerals, the underscore, period, and "mpg"
or "nuv". When you use human-readable names, you end up with the
problems of dealing with a) characters that are illegal in filenames on
some file systems/platforms, b) characters that are not present in the
character encoding used by the file system's filenames, c) file names
that are too long for filenames on some file systems/platforms, d)
disagreement on how the "broken" filenames were corrected to
file-system-usable filenames in various different parts of the code
(i.e. Myth libs, Perl bindings, Python bindings, ...) and/or redundant
coding of the same rules which must always be kept up-to-date, and e)
many more issues...

So, use mythrename.pl --link (which will /never/ cause issues--the
--link argument is critical) and get the best of all 5 worlds:

1) recording filenames that /always/ work no matter what
2) human-readable filenames that can be used when reading files
directly off the file system (and that if "broken" can usually still be
recognized by a human)
3) a directory that contains /only/ information about recording files
(i.e. no PNG preview pixmaps, etc.)
4) the recordings from /all/ directories in /all/ local storage groups
are /all/ visible in the same location (meaning you don't have to hunt
down recording files across multiple different directories/file systems)
5) as many different views as you want each named/sorted differently.

(There may be other worlds that I'm forgetting. I'm intentionally not
mentioning the world I care most about, "makes it less likely for users
to mess with Myth's data," since many will disagree with me about who
owns the data.)

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

jan at horde

Nov 3, 2009, 12:53 AM

Post #6 of 7 (1368 views)
Permalink

Re: What can we expect in 0.23? [In reply to]

Zitat von "Michael T. Dean" <mtdean [at] thirdcontact>:

> On 11/02/2009 07:42 PM, Robert McNamara wrote:
>> On Mon, Nov 2, 2009 at 5:38 PM, David Hunter wrote:
>>
>>> One feature I would like to see is proper naming (Ie human readable)
>>> file naming of mythtv recordings. Similar to the WMC filemame
>>> convention, or is there already a way to do this?
>> Please don't top post on this list.
>>
>> Yes, you can use the mythrename script.
>
> Though doing so will likely cause issues.
> http://www.mythtv.org/wiki/Mythrename.pl
>
> In truth, Myth is /already/ doing the right thing by naming the
> recordings using only Arabic numerals, the underscore, period, and
> "mpg" or "nuv". When you use human-readable names, you end up with
> the problems of dealing with a) characters that are illegal in
> filenames on some file systems/platforms, b) characters that are not
> present in the character encoding used by the file system's
> filenames, c) file names that are too long for filenames on some
> file systems/platforms, d) disagreement on how the "broken"
> filenames were corrected to file-system-usable filenames in various
> different parts of the code (i.e. Myth libs, Perl bindings, Python
> bindings, ...) and/or redundant coding of the same rules which must
> always be kept up-to-date, and e) many more issues...
>
> So, use mythrename.pl --link (which will /never/ cause issues--the
> --link argument is critical) and get the best of all 5 worlds:
>
> 1) recording filenames that /always/ work no matter what
> 2) human-readable filenames that can be used when reading files
> directly off the file system (and that if "broken" can usually still
> be recognized by a human)
> 3) a directory that contains /only/ information about recording
> files (i.e. no PNG preview pixmaps, etc.)
> 4) the recordings from /all/ directories in /all/ local storage
> groups are /all/ visible in the same location (meaning you don't
> have to hunt down recording files across multiple different
> directories/file systems)
> 5) as many different views as you want each named/sorted differently.
>
> (There may be other worlds that I'm forgetting. I'm intentionally
> not mentioning the world I care most about, "makes it less likely
> for users to mess with Myth's data," since many will disagree with
> me about who owns the data.)

There's also mythtvfs which I prefer because it is a fuse solution and
thus works in real-time. Not sure if it still works with 0.22 though.

Jan.

--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

fayoeu at gmail

Nov 5, 2009, 6:09 PM

Post #7 of 7 (1299 views)
Permalink

Re: What can we expect in 0.23? [In reply to]

Not working yet...

[root [at] mytht mythtvfs-fuse-0.6.0]# ./mythtvfs -o host=mythtv
/export/data3/mythtv/ /mnt/test
Could not find compatible protocol version (mythtvfs=40, backend=50)
Perhaps try with '-o program-width=N' where N is the new protocol width?

On Tue, Nov 3, 2009 at 12:53 AM, Jan Schneider <jan [at] horde> wrote:

> Zitat von "Michael T. Dean" <mtdean [at] thirdcontact>:
>
>
> On 11/02/2009 07:42 PM, Robert McNamara wrote:
>>
>>> On Mon, Nov 2, 2009 at 5:38 PM, David Hunter wrote:
>>>
>>> One feature I would like to see is proper naming (Ie human readable)
>>>> file naming of mythtv recordings. Similar to the WMC filemame
>>>> convention, or is there already a way to do this?
>>>>
>>> Please don't top post on this list.
>>>
>>> Yes, you can use the mythrename script.
>>>
>>
>> Though doing so will likely cause issues.
>> http://www.mythtv.org/wiki/Mythrename.pl
>>
>> In truth, Myth is /already/ doing the right thing by naming the recordings
>> using only Arabic numerals, the underscore, period, and "mpg" or "nuv".
>> When you use human-readable names, you end up with the problems of dealing
>> with a) characters that are illegal in filenames on some file
>> systems/platforms, b) characters that are not present in the character
>> encoding used by the file system's filenames, c) file names that are too
>> long for filenames on some file systems/platforms, d) disagreement on how
>> the "broken" filenames were corrected to file-system-usable filenames in
>> various different parts of the code (i.e. Myth libs, Perl bindings, Python
>> bindings, ...) and/or redundant coding of the same rules which must always
>> be kept up-to-date, and e) many more issues...
>>
>> So, use mythrename.pl --link (which will /never/ cause issues--the --link
>> argument is critical) and get the best of all 5 worlds:
>>
>> 1) recording filenames that /always/ work no matter what
>> 2) human-readable filenames that can be used when reading files directly
>> off the file system (and that if "broken" can usually still be recognized by
>> a human)
>> 3) a directory that contains /only/ information about recording files
>> (i.e. no PNG preview pixmaps, etc.)
>> 4) the recordings from /all/ directories in /all/ local storage groups
>> are /all/ visible in the same location (meaning you don't have to hunt down
>> recording files across multiple different directories/file systems)
>> 5) as many different views as you want each named/sorted differently.
>>
>> (There may be other worlds that I'm forgetting. I'm intentionally not
>> mentioning the world I care most about, "makes it less likely for users to
>> mess with Myth's data," since many will disagree with me about who owns the
>> data.)
>>
>
> There's also mythtvfs which I prefer because it is a fuse solution and thus
> works in real-time. Not sure if it still works with 0.22 though.
>
> Jan.
>
> --
> Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads