Startup Parameter "-multi"

[spike5884]

Upgraded to 4.1 and now the startup parameter "-multi" does not work. Checked the manual and it is not listed anymore.

Why was this removed?? I was using it to start-up another session for use with Studio. When I click on my other shortcut, it just brings up the already started session.

[ke6guj]

When Sage set up the extender licensing, it would not be smart to leave in a back door around the licensing requirements that each extender had its own license. Removing the -multi takes out the backdoor.

[spike5884]

So, I now have to set-up another PC and buy another Client license if I want to use Studio because I like to play and watch TV at the same time. Not good.

And something like this should have been noted in the Release Notes.

[ke6guj]

yup, should have been noted.

And another item that should have been noted in the release notes but Andy confirmed it on the forums.

Can't use 4.0 client with 4.1 server, probably has to do with the -multi issue. During the V3 betas, Sage set it up so that you could mix and match versions, carried through into 4.0. I set up a 4.1 server and I couldn't connect with my spare 4.0 client.

[Opus4]

Originally Posted by ke6guj

Can't use 4.0 client with 4.1 server, probably has to do with the -multi issue. During the V3 betas, Sage set it up so that you could mix and match versions, carried through into 4.0. I set up a 4.1 server and I couldn't connect with my spare 4.0 client.

This has nothing to do with the multi parameter; it is because there were big changes made regarding how the server & client communicated to improve it. The server & client still just have to be compatible versions, not exact matches -- you don't need a perfect match betwen v4.1 versions for the server & client to talk to each other, but it certainly is not comaptible w/v4.0. (Yes, there were beta versions I ran before v4.1.3 & they talked to each other.)

Regarding multiple instances of Studio: this is still covered in the Studio manual. You can run the server in non-service mode, then run a 2nd UI w/the -client parameter. So far, that still works.

- Andy

[ke6guj]

thanks for the clarification Andy.

[sfisher]

Hey! Multi in the client was a good thing. It let me have PIP features on my Client computers. I used it all the time.

[GKusnick]

Here's an idea: reinstate -multi with the restriction that any instance started that way cannot play back any media files. That way you could still bring up multiple instances of Client+Studio, tweak your UI layout, copy and paste widgets between different STVs, and so on. You just couldn't run more than one playback engine at a time, thus sidestepping any licensing issues.

To me this seems like a much better solution than suggesting that people do STV development on their live production servers. The whole point of the client/server separation is to leave the server alone to do its thing undisturbed by users banging on the keyboard.

[sleonard]

Originally Posted by GKusnick

Here's an idea: reinstate -multi with the restriction that any instance started that way cannot play back any media files. That way you could still bring up multiple instances of Client+Studio, tweak your UI layout, copy and paste widgets between different STVs, and so on. You just couldn't run more than one playback engine at a time, thus sidestepping any licensing issues.

To me this seems like a much better solution than suggesting that people do STV development on their live production servers. The whole point of the client/server separation is to leave the server alone to do its thing undisturbed by users banging on the keyboard.

I agree. I'm not about to do any Studio Dev on my server. That's what I bought a client license for. However, I do like to have an instance open for watching while playing w/ Studio. I sometimes also like to have 2 instances of Studio going so I can visually compare features of one STV w/ another.

If GKusnick's suggestion won't work, please find another way we can have two client windows open for Studio development.

[jbuszkie]

Damn! I was hoping to use -multi. I just tried it for the first time and it didn't work and then I found this thread! I'm not going to mess with the server to do development. We need a better solution!! Crud!

Jim

[BobPhoenix]

When I bought my MVP licenses I had an extra client licence so I installed SageTV client on a VirtualPC session to develop on. Not ideal but I can have two instances of SageTV open this way on the same machine.

BobP.

[Mike]

If I understand correctly, it is no longer possible to run multiple instances of a single licensed copy of Sage client, but from what BobPhoenix is saying, If I have multiple licenses I could have multiple installations where each had its own license. is that correct?

This ability is important to me because I am trying to put together a system that uses as few boxes as possible. Paying for more licenses is a lot cheaper than building more clients.

Thanks,
MBrew

[ByteRisc]

This should be re-enabled, or functionality given back in some other fashion. During the trial period I was specifically looking for a multiple viewing application. It's one of the reasons I CHOSE SageTv. Now that I've just purchased the product (both server and client) I'm somewhat ticked that you've taken away the main feature I was looking for.

Why do you want me to purchase a $30 license for each view of the same server, from the same client machine? This seems unfair, and greedy.

With windows media player, I can open multiple copies of same multimedia, for free (never use that app though).

With WinAmp (favorite) I can open multiple copies of same multimedia, for free.

Why are you different? Please try to find a solution that meets your security needs, but also gives your users multiple client views on the same machine... for the same license.

Thank you.

[Mike]

ByteRisc,

When I didn't get any response on this, I put in a support request and recieved the following response; " Unfortunately you can't run multiple instances, but you can run one SageTV and one SageTV Client on the same pc."

That wasn't a big help to me so I also contacted them with a feature request. I know that they monitor the boards, but if it's something you're really interested in, you might do the same.

Good Luck,
Mbrew

[blade]

Originally Posted by ByteRisc

This should be re-enabled, or functionality given back in some other fashion. During the trial period I was specifically looking for a multiple viewing application. It's one of the reasons I CHOSE SageTv. Now that I've just purchased the product (both server and client) I'm somewhat ticked that you've taken away the main feature I was looking for.

Why do you want me to purchase a $30 license for each view of the same server, from the same client machine? This seems unfair, and greedy.

With windows media player, I can open multiple copies of same multimedia, for free (never use that app though).

With WinAmp (favorite) I can open multiple copies of same multimedia, for free.

Why are you different? Please try to find a solution that meets your security needs, but also gives your users multiple client views on the same machine... for the same license.

Thank you.

If you do a little reading on the MVP and the -multi parameter you'll see why they removed it. Basically the media extender software is run from a server. Being able to run multiple instances of Sage on one computer would allow people to run numerous media extenders from one license. Basically they don't want people buying one $30 client license and having MVP's connected to every TV in their home all using the one license.

[jbuszkie]

Originally Posted by Opus4

Regarding multiple instances of Studio: this is still covered in the Studio manual. You can run the server in non-service mode, then run a 2nd UI w/the -client parameter. So far, that still works.
- Andy

I Tried this (quickly) and I couldn't get it to work. It's complaining about reusing a client license... Do I need another client license to be able to do this? (I'm not running in service mode)

I have another machine that's my server and another one that's a client. But I want to do my development on a completly different machine! The server comes up fine on the development machine, but I want to have two studio windows open. Right now it's a real pain going back and forth between the stvi and the real STV to test the import.

Jim

[Opus4]

What exactly are you running?

You can only run a single instance of a client on a PC. If you are trying to use a client on a 2nd PC, then yes, that PC needs a client license also.

- Andy

[jbuszkie]

I'm trying to get two instances of studio up on my develpoment machine...while not disturbing the real server or client machine. I'm trying to run the Sage -client on the development machine and have it connect to the server on the same machine..

The studio manual say I can use the -client parameter... but it's complaining about reuse..

[Opus4]

So you are running the server on the 2nd PC? It is probably trying to connect to the main server, or at least finding it when it looks for all local servers... and complaining because it is probably the same license.

- Andy

[jbuszkie]

yeah.. I'm running the same server license on two computers. Maybe that's what it's complaining about.
I'll have to find some time when the wife's not watching ty to shutdown the main server to test this.
I guess technically it's a violation of the EULA.. But not the spirit of it. I have no encoders hooked to it and I only use it to develop. I wish they would find a way to use the -multi parameter again...

Jim