OldTom
So I'm seeing a bunch of forum messages regarding this or that update and how a perfectly good setup starts acting wonky after build Number this and that. Makes me wonder how long I can go without accepting updates. What I'm trying to ask is how many updates can I skip before I should go ahead and accept one?
I'm running VDJ8 under the Pro license on two MacBook Pros and as a rule never accept an update just ahead of a gig.
I don't do video and don't use a customized skin.
Now, I'm wondering if I have a great build working for me, can I ignore or skip build updates for say ten or more occasions? Why get them when everything is working just fine at the time?
When I get the update notice screen I read the list of improvements and most of the time they have zero to do with me and my workflow or my needs.
As an example, last week I accepted an update (Build 2821.1097 ) and during my gig I noticed the live feedback function came on and started giving me outrageous song suggestions (like it did before I turned it off the last time).
Not a big deal overall, but I'm seeing posts where members describe sudden audio glitches --- and for me-- that's a big deal.
Call me a worry-wart or paranoid, but I come from the old school of "If it ain't broke—don't fix it."
How long can I go without taking a risk on blowing my setup to smithereens between update acceptance?
My question relates to the mechanics of an update in this case. So I skip the next update-- the one after that-- the one after that and so on. Eight or nine months later when I have a total month of downtime ahead of me, can I accept a current build update without having problems from not having accepted the ones before it? I'm assuming that update in the future will be an all-inclusive build that has everything I skipped in previous months already included. Am I making sense?
Is anyone else standing firm with older 8.1 build versions they know from experience delivers consistent results.
I'm running VDJ8 under the Pro license on two MacBook Pros and as a rule never accept an update just ahead of a gig.
I don't do video and don't use a customized skin.
Now, I'm wondering if I have a great build working for me, can I ignore or skip build updates for say ten or more occasions? Why get them when everything is working just fine at the time?
When I get the update notice screen I read the list of improvements and most of the time they have zero to do with me and my workflow or my needs.
As an example, last week I accepted an update (Build 2821.1097 ) and during my gig I noticed the live feedback function came on and started giving me outrageous song suggestions (like it did before I turned it off the last time).
Not a big deal overall, but I'm seeing posts where members describe sudden audio glitches --- and for me-- that's a big deal.
Call me a worry-wart or paranoid, but I come from the old school of "If it ain't broke—don't fix it."
How long can I go without taking a risk on blowing my setup to smithereens between update acceptance?
My question relates to the mechanics of an update in this case. So I skip the next update-- the one after that-- the one after that and so on. Eight or nine months later when I have a total month of downtime ahead of me, can I accept a current build update without having problems from not having accepted the ones before it? I'm assuming that update in the future will be an all-inclusive build that has everything I skipped in previous months already included. Am I making sense?
Is anyone else standing firm with older 8.1 build versions they know from experience delivers consistent results.
Posté Tue 02 Feb 16 @ 1:08 pm
PhantomDeejay
You can skip as many updates as you like.
When you decide to accept an update this is always gonna be the latest update. So, if you skip 10 builds and you decide to update on 11th, you will get the 11th build (which of course includes all fixes from previous builds)
As for how long you can go without updates:
It's up to you. We DO suggest our users to always update to the latest PUBLIC build. These builds have been tested thoroughly and usually they don't produce any issues. Instead they fix various other issues.
As a quick note: The fact that a build is stable for you is good, but it doesn't mean this build is not possible to produce issues if you stumble upon an issue that we discovered and fixed on a later build.
Usually we don't release new builds before the weekend just as a pre-caution measure.
We DO suggest our users to do the same. We advise our users to update right after the weekend and any important gig they may have.
As for what you read:
There are 3 phases of development: Beta builds that are accessible only to beta testers, Early Access builds that are accessible only on users that wish to get them (in other words power users that like to have the latest build regardless of the risk of a regression bug) and the PUBLIC builds which are accessible to everyone.
Most of the issues you read about are from "Early Access" builds and they are fixed (in other words not present) on Public Builds.
When you decide to accept an update this is always gonna be the latest update. So, if you skip 10 builds and you decide to update on 11th, you will get the 11th build (which of course includes all fixes from previous builds)
As for how long you can go without updates:
It's up to you. We DO suggest our users to always update to the latest PUBLIC build. These builds have been tested thoroughly and usually they don't produce any issues. Instead they fix various other issues.
As a quick note: The fact that a build is stable for you is good, but it doesn't mean this build is not possible to produce issues if you stumble upon an issue that we discovered and fixed on a later build.
Usually we don't release new builds before the weekend just as a pre-caution measure.
We DO suggest our users to do the same. We advise our users to update right after the weekend and any important gig they may have.
As for what you read:
There are 3 phases of development: Beta builds that are accessible only to beta testers, Early Access builds that are accessible only on users that wish to get them (in other words power users that like to have the latest build regardless of the risk of a regression bug) and the PUBLIC builds which are accessible to everyone.
Most of the issues you read about are from "Early Access" builds and they are fixed (in other words not present) on Public Builds.
Posté Tue 02 Feb 16 @ 1:28 pm
kradcliffe
There have been a few regression bugs lately because beta testing is now in-house rather than going out to the masses, but these are usually caught in the early release versions. The recent scroll display bug sneaked through to a public build but it wasn't a biggie.
Generally on my gig machine I install the latest public release and on my home machine I install the early release.
The V8 code is now mature and nothing is going to go badly enough wrong to crash a gig if you stick to the latest public release. When you do update all the previous releases are rolled in to it. That's it.
Generally on my gig machine I install the latest public release and on my home machine I install the early release.
The V8 code is now mature and nothing is going to go badly enough wrong to crash a gig if you stick to the latest public release. When you do update all the previous releases are rolled in to it. That's it.
Posté Tue 02 Feb 16 @ 1:31 pm
OldTom
Thanks all for your speedy replies!
Anyone care to give me a jump start on how to set my preferences to accept only public release updates?
I'll let the brave souls who know how to deal with Betas be the test subjects.
Or-- am I correct in guessing all the updates I am receiving for acceptance are public releases in the first place? -- Meaning the Beta folks are going to specific download site and intentionally downloading?
Als0-- I've mentioned this before-- prior to 8.1 you used to post dates next to the Build Numbers -- Now we don't see the dates -- Can you put the dates back in again?
Anyone care to give me a jump start on how to set my preferences to accept only public release updates?
I'll let the brave souls who know how to deal with Betas be the test subjects.
Or-- am I correct in guessing all the updates I am receiving for acceptance are public releases in the first place? -- Meaning the Beta folks are going to specific download site and intentionally downloading?
Als0-- I've mentioned this before-- prior to 8.1 you used to post dates next to the Build Numbers -- Now we don't see the dates -- Can you put the dates back in again?
Posté Tue 02 Feb 16 @ 1:46 pm
kradcliffe
Options (advanced) earlyAccessUpdates to no
Posté Tue 02 Feb 16 @ 1:55 pm
PhantomDeejay
Unless you manually changed your settings to get "Early Access" builds then you should get only public builds.
Open VirtualDj config, go on preferences and search for the "earlyAccessUpdates" option. Make sure it's set to "no" and you should only get public builds.
Open VirtualDj config, go on preferences and search for the "earlyAccessUpdates" option. Make sure it's set to "no" and you should only get public builds.
Posté Tue 02 Feb 16 @ 1:57 pm
OldTom
Once again-- Thanks everyone!
Posté Tue 02 Feb 16 @ 2:12 pm