PDA

View Full Version : AlienBBC and Mac



Daniel Cohen
2004-11-21, 02:14
As I mentioned in another post, I have now succeeded in getting
mplayer for Mac OS X, and am almost ready to try AlienBBC.

But I still have a few questions.

Does one actually need to compile alienstream any more? I take it the
instructions are out of date, as even if alienstream is needed, it is
included in AlienBBC now.

Where exactly should the cook codec from RealPlayer be put? Is it
actually to go in a folder called "unknown"? As far as I can see,
there is no need to use the Terminal to put it in the right place,
simple drag-and-drop should be enough.

Once downloaded and unpacked, one has a folder called alienbbc0.10
containing alienstream, transcoderproxy.pl (I've forgotten what the
keystroke for the underscore is), and a folder called Plugins. Does
the whole alienbbc0.10 folder go into my main Plugins folder, do put
the individual plugins into that folder, do I put alienbbc's Plugins
folder itself into my main Plugins folder, or what? What exactly goes
where?

Is the HTML::Parser module still needed?

Once I've got everything in the right place and working, I will be
able to write an alternative set of instructions. I can see ways of
using the Mac and Fink GUIs to make installation a lot easier than
your instructions.
--
Daniel Cohen

Jules Taplin
2004-11-23, 09:14
Hi Daniel.

If you've got mplayer, then I'd suggest you ditch alienstream just as
fast as you possibly can ;)

As far as where the cook codec goes, anywhere that mplayer will look for
a codec is fine. If it helps any, on my RedHat box, it lives in
'/usr/lib/win32'.

Unpack the archive directly into your main slimserver directory. So...
'transcoder_proxy.pl' should be at the same level as 'slimserver.pl',
and the .pm files should be in 'Plugins/Alien' below that. You can
safely ignore (or delete) alienstream.

And I think you still will need HTML::Parser, yes. It's key to decoding
what on earth the BBC pages are up to ;)

-- Jules



Daniel Cohen wrote:

> As I mentioned in another post, I have now succeeded in getting
> mplayer for Mac OS X, and am almost ready to try AlienBBC.
>
> But I still have a few questions.
>
> Does one actually need to compile alienstream any more? I take it the
> instructions are out of date, as even if alienstream is needed, it is
> included in AlienBBC now.
>
> Where exactly should the cook codec from RealPlayer be put? Is it
> actually to go in a folder called "unknown"? As far as I can see,
> there is no need to use the Terminal to put it in the right place,
> simple drag-and-drop should be enough.
>
> Once downloaded and unpacked, one has a folder called alienbbc0.10
> containing alienstream, transcoderproxy.pl (I've forgotten what the
> keystroke for the underscore is), and a folder called Plugins. Does
> the whole alienbbc0.10 folder go into my main Plugins folder, do put
> the individual plugins into that folder, do I put alienbbc's Plugins
> folder itself into my main Plugins folder, or what? What exactly goes
> where?
>
> Is the HTML::Parser module still needed?
>
> Once I've got everything in the right place and working, I will be
> able to write an alternative set of instructions. I can see ways of
> using the Mac and Fink GUIs to make installation a lot easier than
> your instructions.

Daniel Cohen
2004-11-23, 13:22
On 23/11/04 at 4:14 pm +0000, Jules Taplin wrote
>Hi Daniel.
>
>If you've got mplayer, then I'd suggest you ditch alienstream just
>as fast as you possibly can ;)
>
>As far as where the cook codec goes, anywhere that mplayer will look
>for a codec is fine. If it helps any, on my RedHat box, it lives in
>'/usr/lib/win32'.
>
>Unpack the archive directly into your main slimserver directory.
>So... 'l' should be at the same level as 'slimserver.pl', and the
>.pm files should be in 'Plugins/Alien' below that. You can safely
>ignore (or delete) alienstream.
>
>And I think you still will need HTML::Parser, yes. It's key to
>decoding what on earth the BBC pages are up to ;)
>
>-- Jules

Great. I'll play with it again in a day or so when I have more time.

Interstingly, when I looked at /usr/local, I found it now had an
mplayer directory, and this contains cook.bundle. So I guess I should
just leave that (in particular, not rename it, which your notes
suggest).

One point, which is not your issue but a basic one abouthow
SlimServer works when updating on the Mac. Slimserver on the Mac is a
preference pane, with a whole collection of folders and subfolders
inside it. Does an update replace the whole preference pane. or does
it just update relevant files? Specifically, when putting
transcoder_proxy.pl in the place you give, will it get destroyed in
an update or does it remain? A similar issue would apply to the
plugins, except that there is another Plugins folder available on the
Mac which certainly does not get changed on an update.
--
Daniel Cohen

Jules Taplin
2004-11-25, 11:17
Hi Daniel.

I'm afraid I know nothing about preference panes. :(

Bear in mind that I haven't a single Linux box in the house that even
has a GUI on it. My machines are strictly CLI only - point'n'click
interfaces aren't my thing on UNIX-like systems.


-- Jules

Daniel Cohen wrote:

> On 23/11/04 at 4:14 pm +0000, Jules Taplin wrote
>
>> Hi Daniel.
>>
>> If you've got mplayer, then I'd suggest you ditch alienstream just as
>> fast as you possibly can ;)
>>
>> As far as where the cook codec goes, anywhere that mplayer will look
>> for a codec is fine. If it helps any, on my RedHat box, it lives in
>> '/usr/lib/win32'.
>>
>> Unpack the archive directly into your main slimserver directory.
>> So... 'l' should be at the same level as 'slimserver.pl', and the .pm
>> files should be in 'Plugins/Alien' below that. You can safely ignore
>> (or delete) alienstream.
>>
>> And I think you still will need HTML::Parser, yes. It's key to
>> decoding what on earth the BBC pages are up to ;)
>>
>> -- Jules
>
>
> Great. I'll play with it again in a day or so when I have more time.
>
> Interstingly, when I looked at /usr/local, I found it now had an
> mplayer directory, and this contains cook.bundle. So I guess I should
> just leave that (in particular, not rename it, which your notes suggest).
>
> One point, which is not your issue but a basic one abouthow SlimServer
> works when updating on the Mac. Slimserver on the Mac is a preference
> pane, with a whole collection of folders and subfolders inside it.
> Does an update replace the whole preference pane. or does it just
> update relevant files? Specifically, when putting transcoder_proxy.pl
> in the place you give, will it get destroyed in an update or does it
> remain? A similar issue would apply to the plugins, except that there
> is another Plugins folder available on the Mac which certainly does
> not get changed on an update.