Mailing List Archive

MythMusic Basics
Hi,

Could someone answer some basic questions for me about MythMusic...

I am running mythtv with the frontend and backend on different
machines. Of course, the database is therefore on the backend.

I would like to understand how MythMusic fits in with the front/back
design.

That is, where do I install what?

Do I install MythMusic on both front and back, then install and manage
the music database on the backend, like mythtv? In this case is the
audio sent to the frontend over a socket?

Or is MythMusic a frontend only process (i.e., like get the music from
NFS)? In this case, I don't understand where the database fits.

If there is documentation explaining this, please point me to it.

Thanks for any help.

Dick
RE: MythMusic Basics [ In reply to ]
Mythmusic currently doesn't fit in to the frontend/backend architecture.
It's a frontend-only application, meaning it needs direct access to the
music files. However, as you observed, the metadata is kept in the
database. However, AFAIK, the database/backend doesn't need access to the
actual music files. Of course, if you have multiple frontends, you'll want
to NFS mount the directory with the music files in the same place on each
frontend; but beware, as there's little or no buffering in MythMusic, so any
network latency could cause playback problems.

I imagine at some point someone will undertake to make MythMusic a
frontend/backend type module. Right now the focus is on a large-scale UI
overhaul.

-JAC

> -----Original Message-----
> From: mythtv-users-bounces@snowman.net
> [mailto:mythtv-users-bounces@snowman.net]On Behalf Of rwk@americom.com
> Sent: Thursday, May 29, 2003 6:21 AM
> To: mythtv-users@snowman.net
> Subject: [mythtv-users] MythMusic Basics
>
>
> Hi,
>
> Could someone answer some basic questions for me about MythMusic...
>
> I am running mythtv with the frontend and backend on different
> machines. Of course, the database is therefore on the backend.
>
> I would like to understand how MythMusic fits in with the front/back
> design.
>
> That is, where do I install what?
>
> Do I install MythMusic on both front and back, then install and manage
> the music database on the backend, like mythtv? In this case is the
> audio sent to the frontend over a socket?
>
> Or is MythMusic a frontend only process (i.e., like get the music from
> NFS)? In this case, I don't understand where the database fits.
>
> If there is documentation explaining this, please point me to it.
>
> Thanks for any help.
>
> Dick
Re: MythMusic Basics [ In reply to ]
JAC,

Thanks, I almost understand...

What I am still unclear on is the database. Are you saying I must run a
separate mysqld on the frontend, or can MythMusic talk to mysqld on the
backend? If so, does it use the same mysql.txt file that mythtv uses to
discover the backend hostname?

Thanks again,
Dick

> Mythmusic currently doesn't fit in to the frontend/backend architecture.
> It's a frontend-only application, meaning it needs direct access to the
> music files. However, as you observed, the metadata is kept in the
> database. However, AFAIK, the database/backend doesn't need access to the
> actual music files. Of course, if you have multiple frontends, you'll want
> to NFS mount the directory with the music files in the same place on each
> frontend; but beware, as there's little or no buffering in MythMusic, so any
> network latency could cause playback problems.
>
> I imagine at some point someone will undertake to make MythMusic a
> frontend/backend type module. Right now the focus is on a large-scale UI
> overhaul.
>
> -JAC
>
> > -----Original Message-----
> > From: mythtv-users-bounces@snowman.net
> > [mailto:mythtv-users-bounces@snowman.net]On Behalf Of rwk@americom.com
> > Sent: Thursday, May 29, 2003 6:21 AM
> > To: mythtv-users@snowman.net
> > Subject: [mythtv-users] MythMusic Basics
> >
> >
> > Hi,
> >
> > Could someone answer some basic questions for me about MythMusic...
> >
> > I am running mythtv with the frontend and backend on different
> > machines. Of course, the database is therefore on the backend.
> >
> > I would like to understand how MythMusic fits in with the front/back
> > design.
> >
> > That is, where do I install what?
> >
> > Do I install MythMusic on both front and back, then install and manage
> > the music database on the backend, like mythtv? In this case is the
> > audio sent to the frontend over a socket?
> >
> > Or is MythMusic a frontend only process (i.e., like get the music from
> > NFS)? In this case, I don't understand where the database fits.
> >
> > If there is documentation explaining this, please point me to it.
> >
> > Thanks for any help.
> >
> > Dick
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@snowman.net
> http://lists.snowman.net/cgi-bin/mailman/listinfo/mythtv-users
>
Re: MythMusic Basics [ In reply to ]
Hmmm... not 100% sure, but I think MythMusic uses the same discovery
mechanism (mysql.txt) to find the database... so you should only need the one
mysqld running on the backend.

-JAC



----- Original Message -----
From: rwk@americom.com
Date: Thursday, May 29, 2003 6:44 pm
Subject: Re: [mythtv-users] MythMusic Basics

> JAC,
>
> Thanks, I almost understand...
>
> What I am still unclear on is the database. Are you saying I must
> run a
> separate mysqld on the frontend, or can MythMusic talk to mysqld on
> thebackend? If so, does it use the same mysql.txt file that mythtv
> uses to
> discover the backend hostname?
>
> Thanks again,
> Dick