New release version? (now v1.19)

[Mike]

I'd like to increase the latest release version, currently v1.19. Which versions gets your vote?

Thanks.

[wiav8r]

1.23 for me +1

[Mike]

Thanks Allan, much appreciated.

[jak]

On our last recording session we used 1.25 for a couple of hours, with no problems seen.

[Mike]

Thanks Jan, but a few hours is rather short. I am looking to hear what you have been using for the past weeks or even months. Note v1.19 is almost a year old.

[wiav8r]

Mike I have been using ver1.23 in production since it came out in January with no hickups at all

[Mike]

Thanks Allan. Has anyone else been using VidBlaster?

[Rinkfink]

v1.25 used here for my last couple of hockey broadcasts without any major issues, had to reboot between periods a couple of times when responsiveness started to lag, but it didn't act up during play.

[Mike]

Thanks Greg. Responsiveness getting slower over time usually indicates a memory leak, could be a driver.

Anyone else please?

[weconverse]

1.21

I live on the edge of danger, meaning virtually always going live with the latest beta release (after some testing first of course). Been using 1.21 quite extensively without any major issues. Not counting known bugs, which can be discussed if they should be left in a "release" version. The bugs I am thinking of concerns functionality, not stability. The latter are not acceptable in a "release".

I have had quite a few stability problems with Camera II when using 1.25, beyond functions not working (eg the one discussed about the Extreme/Vision cards). Things like VidBlaster freezing when adding a third Camera II (same setup with Camera I modules work fine), not everyting loaded in the profile when loading it on a different PC than where it was created, and more.

In sum, I do not trust Camera II (yet). Therefore everything after 1.21 is in my view not a candidate for release.

Personally I would like to see a major quality fix on the latest beta, resulting in a new "release" (cleaned from bugs and all modules stable) before any new features are added (even though I love new features and wish for many that are in the pipe and mind).

[Immediate update: note that I am using 1.25, but don't trust Camera II and annoyed by quite a few bugs and other things that cause me extra work)

[Mike]

Thanks Richard. And what would your reply be if I remind you that Camera II is clearly marked as "under development" in the help, so you can always choose not to use it?

[weconverse]

I would say: (short version) such marking is not sufficient. If that kind of "under dev" stuff is included in the release, there should be a global setting "turn unstable functions on/off". I can't recall any other software that has released non-beta versions, with functions known to cause major problems and just a warning not to use them.
And again, there are so many "under dev" functions in the most recent versions, it's hard to know what works and what might not (TCP, Replay, Vamera II, PIP-cropping, etc). Hence my above "fix what is, add more later".

Longer version (with love and admiration):
Gee, VidBlaster is slowly becoming an enterprise growing out of a true entreprenerial spirit. The user base is growing, the product line (with different editions) seems to be really competitive. One might even say ground braking in many senses. Hopefully the revenue stream and profits are in line with these developments.

As things are growing it sooner or later becomes necessary to assure a high quality of both product development and customer support. The latter implies making sure that operations keep on running, even though key staff might leave the company. Otherwise come customers might not be willing to invest in a platform without longer term usability guaranteed.

It is perhaps too early to implement project management tools like Scrum. But some measures has to be taken so that sub-projects not become too many, complex, and interrelated that there is no longer any overview of what works and does not.

[EdEstes]

These are good points Richard. As the installation base continues to grow, stability has to take precedence over new features. The topic of this thread points to the fact that it's unclear where that stable product is, which is the way Mike has managed the development in the past, but that might not be the best way to continue with growth.

I personally like the three point release system that many products use:

x.x.x

The first number point (X.x.x) is for major releases, the second point (x.X.x) is for functional improvements and the third point (x.x.X) is for bug fixes only.

So with VIDBlaster, we might be on 1.27.0 which would be the first official release of the product with the new audio and other features. Subsequent releases would only be bug fixes to quickly address issues that come up. 1.27.1, 1.27.2, etc. (the idea being that each subsequent release is more stable than the last)

Only after the product is rock solution, would the next significant release of 1.28 BETA 1 be posted. This would indicate that the product is not considered stable for live production but open to the community for testing. (feature sets would be locked and focus would strictly be on stability) Once the bugs have been addressed by those willing to beta test the product, the official 1.28.0 release would be posted for every to use. Subsequent releases would come out that would address bugs found by the larger audience. (1.28.1, 1.28.2, etc)

Then there is no question about what is the most stable product.

Ideally, second point releases would come out every 2-3 months with follow up bug fixes coming out every 2-3 weeks, depending on the severity of the bug and how many customers are effected by it.

Major releases would be every 18-24 months, with significant functionality being introduced. (and license upgrades expected by current users, which would significantly help with Mike's cash flow)

Obviously this is just one way to approach development but one that I personally like, both from a customer as well as a business trying to increase revenues and grow as a company.

--Ed

[QuinnQuality]

@Mike, please beware of the mistake Microsoft made, make more and more applications but forget about reliability. I would be very sad if a program like VidBlaster would head this way. I am not saying that i am not happy with the added modules, like the RMTP module in v.1.27, It is our savior, but try now to stay in focus for the flaws and hick-ups in your beautiful software and make them work as expected and wished for. Blast us away in v1.28 with what you achieved until now and please fix the discussed modules.

[weconverse]

Well, from a number of recently "fixed" threads, it's seems Mike is in the process of killing bugs :) Perhaps 1.28 BETA 1 will really be the next version?

[Mike]

As you've already gathered I've work hard to get a new release version ready. How about v1.36? I desperately need a new release version as I have a number of fixes/features waiting that require some major rewrites in VidBlaster's core, and thus the risk of new bugs. Interesting things coming, but may be a while before we have a new release version.

Who's using v1.36?

[wiav8r]

My production machine has v1.36 loaded . I plan first broadcast on Thursday and Sunday. But, so far I think 1.36 is a go. I tested it on Test Rig and all looks good for me.

[Mike]

Thanks Allan. Say hi to your buddy Test there from me, or is it Mr. Rig? :)

[wiav8r]

Thanks Allan. Say hi to your buddy Test there from me, or is it Mr. Rig? :)
LOL

I will do that and give a pat on top of the case too! (better than the kick in the hard drive that he usually gets ;P)

[QuinnQuality]

I just finished building my new PC and i have installed 1.36 today. I hope to do the first test tomorrow.

[QuinnQuality]

Here are my system settings

[weconverse]

I have used 1.36 quite extensively without any problems. Mark, not with any Camera II (which I don't trust) or Replay modules loaded. So 1.36 is good for a RC (with a warning on Cam II).

[edit: added I haven't used Replay module, and a notion that I still don't trust 1.36 because I have not tried it yet (in 1.36 that is)].

[greenidge]

I am still using 1.19 ! Had some trouble with the 1.2x versions and when I realized they were beta I went back to the released v1.19. I took the safe route!

[Mike]

Thanks all. Looking good..

[wiav8r]

Mike

I can confirm v1.36 stable. Using 4 Cam II, 2 Overlay, 2 VE, 2 Player, 1 Recorder and Streamer.

I am now able to run Frame Rate 29.97 setting, Streaming and Recording and EXT Mon out to DVD recorder all at same time, Resolution 640x480(SD NTSC) and Program info measured fps averaged 27 to 29 fps during 1 hour broadcast with all of that running! This uses to be set at 25 fps and best average I could get before was 20fps! Same hardware as listed in signature. Same profile used with previous versions.

UPDATE!!! Click here to see a 12 minute sermon excerpt (http://1goodshepherd.org/sermon-video-know-who-jesus-is-know-what-jesus-did/)

Also CPU usage averaged 40-45%, same as before versions running 25 FPS, Recorded WMV audio sync much much better too!

Still running Windows Vista 32 bit. ( I cant wait to try with Win 7 64 bit!. Just waiting for budget to upgrade and I am sure will be much better!)

Mike, I have to say I am very pleased with v 1.36 in Studio version and look forward to it as the release version!

[Mike]

Thanks Allan!

[Rafal Oramus]

After this weekend I can strongly recommend v1.36.

My project was 640x360@25fps and it was 25fps all the time. With recording (uncompressed). With 2 replay modules. With few PIP's and overlays.

The CPU (i7-950) usage was never bigger then 35%. Stability was never a problem during 6 hours of broadcast.

[Mike]

Thanks Rafal.

[Sinc747]

I will be testing 1.36 in real time on Friday when we stream a local all star soccer match. For the first time will try wide screen at 640x360 with three cameras, two replays, scads of overlays and effects modules, streaming to FMLE and recording local and remote. Ought to be a good test. I'll let you know how it goes.

BTW, my son regrets he was not able to get over to Middleburg for a visit. Something about a girl... ;) He heads back to the States this week.

[Johan Lundberg]

So far I have not had the time to play around with the new 1.36 version, but I will give it a real run, and push it hard(!) as soon as time permits! :)

[Sinc747]

Ran into a glitch with 1.36 this weekend. A flickering in the Program module when a Replay module was selected and the Replay module was connected to an Effect module. See post here (http://forum.vidblaster.com/showpost.php?p=14127&postcount=4).

Also ran into a freeze frame in camera modules, but that may be a capture card issue. I'm tracking it down now.