STV: SageMC 16x9 Version 6.x (latest dev build) - Page 88

reboot_this · #**1741** 10-04-2006, 10:55 PM

I love SageMC, but I can't use it... still on v2.2.2beta, that's a whole different story...

I have been following (when I can keep up) SageMC's progress dreaming of the day when I'll actually be able to use it.

My idea about the version numbering would be to just add a decimal point. This would "differentiate" the transition to a new numbering system... right now there is SageMC v6.0, v6.1, v6.2 etc. But if the versioning was to jump to using 2 decimals in the version this wouldn't be confusing at all... SageMC v6.0.11, v 6.0.13, v6.0.15, then BAM! v7.0.1 (for a small $30 fee of course

, sorry, I just HAD to say it!)

And the version numbers could use letters to designate stv bug fixes... SageMC v6.0.11, v6.0.11a, v6.0.11b, 6.0.11c, etc.

I think both those ideas would work and will minimize confusion as to what version stv works with what version of the sage software... and putting them into use would soften the blow from adopting the new version numbering sytem as well.

On the flip-side, it might get confusing to some if one version of the stv were compatible with several different versions of the sage software, but I think don't think it would be TOO much of a headache. I'm just also trying to think of the "bads" of using my ideas for you, Dirk. I would hate for people to blame me if using my ideas gets out of whack in the future!

BTW, wanted to give praise to Dirk for continuing the SageMC stv project!!

dflachbart · #**1742** 10-05-2006, 05:26 AM

Quick update:

Quote:

Originally Posted by flachbar

- the metadata for all my imported videos is gone (luckily I have most of it as DVD profiler info available)

Andy's suggestion in the beta forum regarding this issue worked, all my video info is still there.

And I am confident that support will figure out the other two problems too.

Dirk

dflachbart · #**1743** 10-05-2006, 05:45 AM

Quote:

Originally Posted by reboot_this

My idea about the version numbering would be to just add a decimal point. This would "differentiate" the transition to a new numbering system... right now there is SageMC v6.0, v6.1, v6.2 etc. But if the versioning was to jump to using 2 decimals in the version this wouldn't be confusing at all...

Yeah, I had the same idea yesterday. Since we are now on 6.12, I think a 6.2.0 would seem more intuitive than a 6.0.0. Some guys already voted above for the 6.50, so what do you think about this new idea ?

I know, how can we possibly waste time on something so silly as numbers and decimal points ...

Dirk

Kirby · #**1744** 10-05-2006, 06:20 AM

How about code names for releases? Oregon and Washington state must have some river names still not used. Seems to work well for Intel and AMD and many other companies!

Kirby · #**1745** 10-05-2006, 06:57 AM

Morning Dirk,

Got a possible bug, not sure if its V6, or MC on V6 related, so I will post it here. I was messing around with the default STV (google video) and then switched back to my MC STV, and went to play a normal show (HD 16:9 picture). The media player squeezed the 16:9 down to 4:3 when set to 'source'. I could force it back by setting it to "16:9" mode, but nothing would reset the client back to operating the way it should (i.e. 16:9 source should show that way on 'source' and '16:9' setting). Even a complete reboot on the client couldnt fix it.

What are you thoughts? Bug with MC operating on V6, or purely a V6 bug that I should report to Sage?

geogecko · #**1746** 10-05-2006, 08:37 AM

I like the idea of the added decimal point.

Starting with 6.2.0 would make since as well.

On a side note, what's the deal with Google video? I haven't really looked into see what the big deal is about. Isn't it just like YouTube? Most video's on that site are not the best in quality, IMO. Maybe I'm missing something, like being able to find lost episodes of MacGyver or something...

acrowe · #**1747** 10-05-2006, 08:42 AM

I'll all for the move to double dotted releases.

We can start the Sage 6.x branch of MC as SageMC 6.5.0.

Then again I say "we" like I have anything to do with it

Maybe someday I'll get a chance to get a new job that will enable me to slack off again so I can help!

Kirby · #**1748** 10-05-2006, 09:26 AM

If we are going to double dotted, then maybe do like Linux does on their kernels. 2.EVEN.x are stable (v5) and 2.ODD.x are development kernels (v6). However in this case, I would swap that around a bit. Now I am not implying that v6 is not stable, but then you could release the same MC release for both versions like this:

Code:

SageMC 6.5.13 = next release for SageMC 6 for Sage v5, patch level 13
SageMC 6.6.13 = next release for SageMC 6 for Sage v6, patch level 13

You still maintain the 6 and 13 from what everyone would expect for the next release, and the middle digit becomes the Sage Version.

What do you guys think of that?

acrowe · #**1749** 10-05-2006, 09:48 AM

Quote:

Originally Posted by Kirby

If we are going to double dotted, then maybe do like Linux does on their kernels. 2.EVEN.x are stable (v5) and 2.ODD.x are development kernels (v6). However in this case, I would swap that around a bit. Now I am not implying that v6 is not stable, but then you could release the same MC release for both versions like this:

Code:

SageMC 6.5.13 = next release for SageMC 6 for Sage v5, patch level 13
SageMC 6.6.13 = next release for SageMC 6 for Sage v6, patch level 13

You still maintain the 6 and 13 from what everyone would expect for the next release, and the middle digit becomes the Sage Version.

What do you guys think of that?

certainly an interesting idea...

Course how much more development is going to come out for v5 SageMC now?

it hink it makes tons of sense if Dirk et al are going to continue to maintain 2 forks of the devel (one for v5 sage, 1 for v6). but if they are "only" going to maintain a single fork then I think it might get messy to keep it easy?

Heck I could even see dropping the second dot when we move up to sage 7 (and thus sageMC to 7)

MeInMaui · #**1750** 10-05-2006, 09:51 AM

Quote:

Originally Posted by Kirby

If we are going to double dotted, then maybe do like Linux does on their kernels. 2.EVEN.x are stable (v5) and 2.ODD.x are development kernels (v6). However in this case, I would swap that around a bit. Now I am not implying that v6 is not stable, but then you could release the same MC release for both versions like this:

Code:

SageMC 6.5.13 = next release for SageMC 6 for Sage v5, patch level 13
SageMC 6.6.13 = next release for SageMC 6 for Sage v6, patch level 13

You still maintain the 6 and 13 from what everyone would expect for the next release, and the middle digit becomes the Sage Version.

What do you guys think of that?

Yes. Lets do that. Now where's the next release?

geogecko · #**1751** 10-05-2006, 11:39 AM

I think that is why he is mysteriously absent from the forums, for the most part...must be hard at that code!

dflachbart · #**1752** 10-05-2006, 01:06 PM

Quote:

Originally Posted by geogecko

I think that is why he is mysteriously absent from the forums, for the most part...must be hard at that code!

Yeah, I know this is what you all would like to hear

, but sorry this is not the reason, I'm just swamped at work ...

Dirk

geogecko · #**1753** 10-05-2006, 01:28 PM

Quote:

Originally Posted by flachbar

Yeah, I know this is what you all would like to hear

, but sorry this is not the reason, I'm just swamped at work ...

Dirk

Work

We need to get the excitement up for what is to come in SageMC.

Come on, everyone join me...

Morgan111 · #**1754** 10-05-2006, 02:08 PM

Quote:

Originally Posted by geogecko

Work

We need to get the excitement up for what is to come in SageMC.

Come on, everyone join me...

GO DIRK GO!

geogecko · #**1755** 10-05-2006, 02:13 PM

LOL, that's awesome...it would be even better if there wasn't a delay until they restart the wave...

The green guy is screwing everything up...maybe he needs some

Kirby · #**1756** 10-05-2006, 02:16 PM

Quote:

Originally Posted by geogecko

The green guy is screwing everything up...maybe he needs some

He must be a Michigan State fan no doubt! (Do I need to explain that?)

millers_35 · #**1757** 10-05-2006, 02:17 PM

Thats so purty.

Miller

geogecko · #**1758** 10-05-2006, 03:25 PM

Hmm...something is eating at my bandwidth, wonder what that could be?

dflachbart · #**1759** 10-05-2006, 06:05 PM

I know you SageMC guys are a little bored and depressed since you have no new toys to play with like the default STV users, but this seems to be getting out of control ...

Dirk

Muchacho · #**1760** 10-05-2006, 07:14 PM

Quote:

I know you SageMC guys are a little bored and depressed since you have no new toys to play with like the default STV users, but this seems to be getting out of control ...

Dirk
__________________
Latest SageMC 16x9 STV version: 6.13
Download here.

Should I read anything into the change in your signature?

I dont recall a 6.13 being released yet?

Nice.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)