http://www.elektron.se/news/announcing-overbridge-computer-integration-for-analog
I had money on the beta coming out Mar 12th 2015!
http://www.elektron.se/news/announcing-overbridge-computer-integration-for-analog
I had money on the beta coming out Mar 12th 2015!
Let’s just wait. We’ve had our fill of stirring in other threads. It’s later than we’d all like and the lack of info likely means it’ll be a while?! It will come when it’s ready…
whilst they play ducks and drakes…they are fair game…afaic!
Sure I’m very patient, but what I really don’t like that Overbridge takes all time and energy, so no attention on the Machines OS’s…
You know for a fact how Elektron divides up their workload between their employees?
whilst they play ducks and drakes…they are fair game…afaic!
[/quote]
to clarify,
[i]Around the same time, the use of ‘ducks and drakes’ to refer to idly throwing something away or squandering resources came into use. That usage was recorded in James Cooke’s Tu Quoque, 1614:
[/i]
The adoption of ‘play ducks and drakes’ meaning to throw away money seems to have come directly from the throwing of stones in the waterside game.
The meaning now seems to have wandered closer toward the ‘unreliable and reckless’ and away from the original ‘idly squandering’. This may be a simple migration of meaning over time, or it may be due to a confusion between ‘playing ducks and drakes’ and ‘playing fast and loose’.
thanks to
phrases.org.uk
I do think we should be kept better informed, to be honest. No probs if there’s a delay, but it would be nice to have an explanation.
agreed, if you announce a date, you should announce a delay of date
otherwise, you should just say it will be done when it’s done
It was a communications failure. It would’ve been better to say nothing until OB was close to public beta.
They did this with the Rytm as well as the “hidden” +Drive in the A4. No one knew about these things until they were just about ready for the public.
But with that said, at this point, I’m fine with waiting until OB is in a stable place. No need to rush something that doesn’t work.
Overbridge …? tricksy trade of the year 2014-2015
It is time to repair my MOTU 828 Mk3 (burned) if I want to re-start with my productions .
If they were so kind in Elektron to say something we would all be happier , think
Peace
ah well, another thread full of pointless fecking words and anger - pointless why ? because it’s done to death elsewhere and it makes no difference except to stir up all this ill-feeling - way to go OP, yay
.
i agree that communication has been sketchy - but they did say recently they were a bit behind, OFFICIALLY, so WTF is the point of stirring this up again …
.
this boring naive tosh is far more annoying than a delay imho !
yay, angry is good, grr, let’s squabble about something we have jack control over
Looks like you’re the angry one in this thread!
I understand people’s frustration but do we really need yet another thread?
TBH the shear lack of any listenable material in the Science lab competition showcased just how important OB is! How can I possibly be creative without it?
what would be cool is if they announced the beta AND firmware update for the Rytm heheh
Still waiting on that ring mod kick drum machine for the Analog Rytm… I’m more concerned that Overbridge development is eating up resources from Elektron. Get back to updating the Rytm FFS!
agreed, if you announce a date, you should announce a delay of date
otherwise, you should just say it will be done when it’s done :)[/quote]
I’m definitely not an Elektron apologist, and while I can’t recall the company saying this formally, I do remember Cenk saying it’ll be done when it is done and that it’ll be as soon as possible but it won’t be released until it’s stable.
I’d like it today as I’ve got three recording projects happening this year and it would help me IMMENSELY, but hey.
I do think they dropped the ball in the sense that there has been no apology, no explanation, and no official word, and no sense of respect communicated to their disappointed customers. That’s a big no-no in my world and gives out a funny message.
Elektron made a mistake with announcing. Two mistakes really. But that’s the wonderful thing about hindsight. I’m sure they would do things differently if they could time travel but as ground breaking as Elektron are, they haven’t yet mastered that.
Anyway, nothing to get knickers in a twist over. As has been said, it’ll be done when it’s done.
For what it’s worth, I posted this as I don’t spend much time looking for overbridge on this forum, I know that my looking won’t speed it up …I did a Google search for overbridge and it came up with ‘overbridge announced March 12th…’ I clicked the link with some excitement and found the original press release from March 12th 2014! (Which I had never seen as I bought my A4 and RYTM together in the sale in November…(newbie)
As a new user I haven’t been on the journey, take for granted all the new features (it came that way) and definitely only got on board with Electron based on the promised overbridge (Febuary) as I realy struggle with that small screen (I an the wrong side of 40), don’t play live and everything I do is computer based.
I don’t even care about the audio io, I have an x32 and will probably continue to route via the desk (I like to use my desk effects) but I realy need the on screen editor and librarian for workflow, I realy need to call up patches and patterns with DAW tracks etc. there are max patches for live that do some things, but I realy don’t think this aspect of the software should be too difficult for Electron, I wish they had done this first and added the audio io latter (I am sure that is what is holding things up)
Anyway - don’t get angry, espicialy if your eyes are still good enough to see a small LCD screen, I am sure they are not announcing further delays due to the imininent release just before Messe
Sean (OP)
It’s a shame that Elektron machines are totally useless without overbridge.
// Sarcasm note here just to be sure
We should all note that the release we are waiting for is going to be a beta too - buggy, occasionally project crippling, spend 5 hrs on a track to have it crash and corrupt so avoid doing proper work in it, beta software. I have a feeling some will be disappointed if they arent used to betaing/troubleshooting/helping with bug squishing. Prepare for the influx of lousy bug reports, vague ‘xyz doesnt work, fix it’ posts with no steps to reproduce, no list of hardware/software combinations etc XD