Helix JCM800 2203 Request Thread (FW 3.70 new Brit 2203)!

[mikah912]

If you think they couldn’t release faster you are factually wrong. Your own explanation shows it. I appreciate their release schedule, but it can certainly be released faster.

There are a lot of different philosophies regarding this stuff. At one extreme end you have reaper where all development is public and pretty much every test build is released immediately to the public while the official releases come out much slower and thru the official update channel. At the other end you have more of this secret squirrel stuff, very limited or no public betas, no public alphas at all, etc.

It's a part of a publicly traded company, with regulatory disclosures and fiduciary duties to stockholders, so no....they cannot release faster just because smaller companies with less requirements and stakeholders can.

Tell me this: If you're so sure that they can go faster, what would be the benefit to throttling their firmware releases?

 

[pipelineaudio]

Of course they can release faster. What force in the universe could be stopping them? The corporate stuff is just a red herring or at best a reason why they WANT to release on a different schedule, but the hard fact is this:

As soon as the software is made, it can be made available.

Full stop.

No amount of obfuscation can change this

For your question "Tell me this: If you're so sure that they can go faster, what would be the benefit to throttling their firmware releases?"

There are a million reasons, and very good ones

• Getting the release as stable as possible before releasing to the public (while this can do wonders, its not like there haven't been some pretty well known bugs in the official releases, as long as they took. Auto engage bugs in 3.15? for example)
• Scheduling a release for strategically appropriate times regarding other press releases and product launches/updates/trade shows
• Heavy alpha use for deciding on feature freezes (and this can be a HUGE one) before getting to the beta team who likely will ask for those same features

 

[pipelineaudio]

I'd rather wait until most of bugs were squished rather than releasing stuff that hasn't been properly tested. If that means I wait a few extra weeks then fine.

This is a false dichotomy, and I agree with you and Line 6 here. But that wasn't the claim

I was objecting to the claim that they CAN'T release faster. Of course they can

 

[pipelineaudio]

Agreed. I mean, having the option could be cool, but.. releasing public betas etc for hardware like this (very different from software and from hardware aimed chiefly at more DIY or technical users) can be a support and PR nightmare when a product is popular and widespread.

It can also be the best possible thing you can do for stability and not end up nailed to a buggy feature set that would have been caught if there were more beta testers...See the auto engage bugs for example

 

[mikah912]

This is a false dichotomy, and I agree with you and Line 6 here. But that wasn't the claim

I was objecting to the claim that they CAN'T release faster. Of course they can

Err....ok. Yes, if they threw all caution to the wind and set fire to their reputation, a tiny vocal minority of Helix/HX users could have new amps/fx a bit sooner. Cool, cool.....

 

[SillyOctpuss]

This is a false dichotomy, and I agree with you and Line 6 here. But that wasn't the claim

I was objecting to the claim that they CAN'T release faster. Of course they can

Ok we're just going to disagree on this one then. I could retort but we'd be going round in circles and honestly I can't be bothered or care enough to continue.

 

[pipelineaudio]

Err....ok. Yes, if they threw all caution to the wind and set fire to their reputation, a tiny vocal minority of Helix/HX users could have new amps/fx a bit sooner. Cool, cool.....

That would be a strawman, and still just a red herring dodging the factual inaccuracy of the original claim which is what I was responding to

 

[pipelineaudio]

Let me repeat the original claim

I'm pretty sure they release stuff as quick as they can with the resources they have.

This CANNOT be true the instant they have software that can be installed

a) The law of (non-)contradiction: A cannot be A and not-A at the same time. What this means is that a statement cannot be true and false at the same time. For instance, it cannot be raining and not raining at the same time.
b) The law of identity: everything is what it is. A is A, that is, identical with A. A=A. If any statement is true, then it is true.
c) The law of the excluded middle: A is either A or not A. A cannot equal non A or be non A.

 

[Mooselake]

Depends on how one defines 'ready' I suppose. Software dev is a slow grind often with dozens of interim/engineering or development releases (almost always internal). I'd guess both Line 6 and Fractal have their own criteria for "ready". I'm glad Honda decided to inflate the tires and put the engine in my vehicle before they released it. Similarly, I'm glad Line 6 puts out releases with very few major bugs. No experience with Fractal, but it is kind of neat they let interested users check out betas.

 

[SillyOctpuss]

Let me repeat the original claim

This CANNOT be true the instant they have software that can be installed

a) The law of (non-)contradiction: A cannot be A and not-A at the same time. What this means is that a statement cannot be true and false at the same time. For instance, it cannot be raining and not raining at the same time.
b) The law of identity: everything is what it is. A is A, that is, identical with A. A=A. If any statement is true, then it is true.
c) The law of the excluded middle: A is either A or not A. A cannot equal non A or be non A.

Seriously dude we disagree it's totally fine just let it go.

You can go over and over your same points all you want but I respectfully disagree.

You believe that as soon as they have software they should release it. Fine that's totally cool. I personally don't class software which isn't finished as ready to install. All of the features and models might be there but if there's a bunch of bugs then IMO it's not finished and therefore not ready for the general users to install. Again IMO. If you disagree that's totally fine.

I'll refer you back to my last post we're going round in circles and I'm out because

A - we're not going to agree
B - I don't really care
C - it's a really really petty point to argue.

 

[pipelineaudio]

You believe that as soon as they have software they should release it.

Show me where I said that

In fact I said exactly the opposite

 

[SillyOctpuss]

Show me where I said that

In fact I said exactly the opposite


View attachment 13577

FFS I actually started typing a response to this but man this is the pettiest most pointless argument I've been involved in on the Internet in a long time. Let it go man seriously. Just accept we either disagree or going back over our posts we seem to agree about most of it except for a really small point. It's late over here, I've logged in to look at some guitar porn and maybe have a laugh. I don't care about this, I'm quite happy to say we disagree and it's not big deal if you are? If not then that's cool too but I'm done now.

 

[norminal]

 

[the-trooper]

Just accept we either disagree

There is nothing to agree or disagree here. His point is literal and theoretical, and as such he is correct. They could publish alphas, betas, they maybe could like Mozilla have "nightly" channel and publish daily! They could publish each model the moment its finished and not wait for bundled update. Hell, they could abandon all other projects and work just on Helix updates. They could hire more people...
You get the point. None of that makes sense in the real world, but could it be done? Like you said, a pointless argument, but yes, it could be done.

Now, can we travel faster than light and how would that affect latency?

 

[Orvillain]

They could publish every single commit they ever make to their repositories.

It would be fucking stupid. But they could do it.

Or they could just continue to be professionals.

 

[Foxmeister]

Not sure why you mean? Do you mean holding a firmware update until a new product that uses it is launched?

If you are referring to the HX One, they already said that it would release with 3.60, and 3.70 might actually drop before the HX One becomes readily available.

 

[SillyOctpuss]

If you are referring to the HX One, they already said that it would release with 3.60, and 3.70 might actually drop before the HX One becomes readily available.

No I was thinking about the cab update. Wasn't it delayed because of something else?

 

[Lele]

Not gigging much at this point, it's really more about the scribble strips and having 10 stomp switches (and an expression pedal) available without adding any third party gadgets.

By a lucky "accident" I was upgraded from LT to Floor.
In the beginning I missed the display arrangement of the LT, but soon I found out that (apart from the small or big hardware differences) there were two major advantages in my opinion with the Floor version:
- the small displays on each switch are very bright and practical
- the user interface is even better and faster (to adjust any effect parameter) because you don't have to switch between the different views on the main display since you always have also the information available on each switch display at the same time: this is a very nice improvement imho.

 

[Lele]

Back to the original post topic.
When are we getting the Magnatone M80 amp sim for our Helix?!?
Now with Slash developing a signature amp with Magnatone, we don't care for JCM800 any longer!
But... does Magnatone M80 have the bright cap?!?

 

[Foxmeister]

No I was thinking about the cab update. Wasn't it delayed because of something else?

3.50 was "delayed" because it wasn't ready, but Line 6 released an interim update, 3.15, because of this.

(Note, there were no Helix 3.20 or 3.30 updates - they went straight to 3.50)