KVR Audio

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Oct 11, 2013 7:11 pm

[DELETED]

humanbeingbeing · Post by **humanbeingbeing** » Sat Oct 12, 2013 12:22 am

TheoM wrote:
humanbeingbeing wrote:
pdxindy wrote:
humanbeingbeing wrote:
pdxindy wrote: Bitwig has full PDC (so they say)
I've heard that, I was just wondering if it was confirmed in the beta.
Bitwig stated it specifically...
Yep I read that, what I'm asking more specifically, could a beta tester confirm it working in the beta? if it's an unfinished feature I'd be concerned I guess.
exactly. Example in case is Logic. it has automation pdc problems and apple claim full pdc. Same with (to a lesser extent though) Cubase. Sonar is the tightest in this regard, but it STILL faulters timing on automating effects with latency themselves.

It's a shame so many tools still have problems with this.... IMO it's the most important thing for a modern production app, Ableton not having full compensation in 9 was terrible, it made me stop using Ableton after almost 10 years... I think a lot of people gloss over the issue, maybe some people don't realize how serious the consequences are... anyways, I hope this is working with Bitwig, kinda waiting for it to replace live...

fluxmind · Post by **fluxmind** » Sat Oct 12, 2013 6:16 am

Anyways for some reason this must the most annoying thread title ever on KVR for me lol
maybe it's because it's allways on top and never the truth/ wet dream haha

hibidy · Post by **hibidy** » Sat Oct 12, 2013 6:33 am

Feel the pain!

It's worse for all of us who tried to get onto the beta 10-15 years ago, and never even got a thank you for signing up to the COMPLETELY fake newsletter!

wasi · Post by **wasi** » Sat Oct 12, 2013 11:56 am

hibidy wrote:[...]the COMPLETELY fake newsletter!

So true.

I recently actually tried to sign up again thinking maybe there was some glitch and it said "you're already signed up!

BMoore · Post by **BMoore** » Sat Oct 12, 2013 12:04 pm

So, what will "to do a BitWig" mean in the future?

krixa · Post by **krixa** » Sat Oct 12, 2013 12:05 pm

Screw this. I've just got Maschine.

humanbeingbeing · Post by **humanbeingbeing** » Sat Oct 12, 2013 1:20 pm

agreed on the beta signup, I think people who signed up years ago should be able to test an unfinished version, especially by now.. that was the expectation, and what happened is uncommon in computer software... but I do think they should wait to get it right before releasing proper, the time frames are too long tho, it's hard to stay patient for such a long time.

UncleAge · Post by **UncleAge** » Sat Oct 12, 2013 1:59 pm

hibidy wrote:Feel the pain!

It's worse for all of us who tried to get onto the beta 10-15 years ago, and never even got a thank you for signing up to the COMPLETELY fake newsletter!

True dat

Ogopogo · Post by **Ogopogo** » Sat Oct 12, 2013 2:34 pm

Their latest tweet is fairly relevant here

https://twitter.com/Bitwig/status/385444433874804737

we're very sorry for you feeling let down! but the beta is not a demo phase or there to please people, it is a pure technical tool..

humanbeingbeing · Post by **humanbeingbeing** » Sat Oct 12, 2013 3:09 pm

Ogopogo wrote:Their latest tweet is fairly relevant here

https://twitter.com/Bitwig/status/385444433874804737

we're very sorry for you feeling let down! but the beta is not a demo phase or there to please people, it is a pure technical tool..

I think Maddox's tweet made more sense, the reply tweet is relevant but a change in phrase, the original beta signup wasn't for a technical tool and some people have actually received beta signups, whether this is a "technical tool" or not... it looks like the app is going to be released possibly at 1.0 and a lot of people who signed up for the coming soon beta test aren't going to see a beta or a "technical tool"...also it's not good if Bitwig is just a tech tool right now, it kinda needs to be near completion at this stage... for me personally this is disappointing but I'm not too bothered, if it isn't released this year I will stop checking on it and adopt a different platform... I just hope when it's finally released that Bitwig can be more transparent with updates, I want the software to be everything I've imagined it to be, but also it's important that Bitwig as a company deliver things in a timely fashion and are able to communicate with customers... I think that's been one of Ableton's biggest mistakes...

Ogopogo · Post by **Ogopogo** » Sat Oct 12, 2013 3:56 pm

I think you are misunderstanding a few things. If I remember correctly, they said they were beta testing and let people send in applications. Then I guess they selected a group of people who they felt would be the best testers. Who you choose for the beta is important because you are looking for people with certain characteristics:

1. People who will communicate well and give good bug reports (Possibly a lot of germans like Thomas)

2. who possibly having coding experience to facilitate bug reports

3. who have experience in the industry and with other software so they know what they want and need and a bit about what is important to others, rather than just saying "oh! how can you not have thing a, b, and c, that I want, that's basic!"

4. who can keep tight lipped and not spread rumors based on their perceptions and put the company in an awkward position. For example, imagine if a beta tester had taken it upon themselves to run their mouth off without really knowing "yeah, I don't think they'll be finished within a year or two."

Since I'm not a tester or a Bitwig, I can't say that this was exactly their thought process, I'm just trying to illustrate that you want certain people, not everybody; as was said earlier in the thread, too many people just creates confusion. I don't think they ever promised that everybody who signed up would get in.

So they start doing this to catch bugs and to expand the amount of perspectives so that they can make sure it is stable for everyone with all their different systems, and to refine the features so that they are suitable to the public instead of the 10 or so minds working on the project. The beta process is the technical tool, not Bitwig. It's the technical tool they use to get Bitwig ready for release.

Maybe somebody who's more familiar with other daws can correct me, but I don't think the level of transparency they are showing is out of the ordinary, especially since they have now allowed beta testers to divulge every inch here in this thread.

humanbeingbeing · Post by **humanbeingbeing** » Sat Oct 12, 2013 3:57 pm

Ogopogo wrote:I think you are misunderstanding a few things. If I remember correctly, they said they were beta testing and let people send in applications. Then I guess they selected a group of people who they felt would be the best testers. Who you choose for the beta is important because you are looking for people with certain characteristics:

1. People who will communicate well and give good bug reports (Possibly a lot of germans like Thomas)

2. who possibly having coding experience to facilitate bug reports

3. who have experience in the industry and with other software so they know what they want and need and a bit about what is important to others, rather than just saying "oh! how can you not have thing a, b, and c, that I want, that's basic!"

4. who can keep tight lipped and not spread rumors based on their perceptions and put the company in an awkward position. For example, imagine if a beta tester had taken it upon themselves to run their mouth off without really knowing "yeah, I don't think they'll be finished within a year or two."

Since I'm not a tester or a Bitwig, I can't say that this was exactly their thought process, I'm just trying to illustrate that you want certain people, not everybody; as was said earlier in the thread, too many people just creates confusion. I don't think they every promised that everybody who signed up would get in.

So they start doing this to catch bugs and to expand the amount of perspectives so that they can make sure it is stable for everyone with all their different systems, and to refine the features so that they are suitable to the public instead of the 10 or so minds working on the project. The beta process is the technical tool, not Bitwig. It's the technical tool they use to get Bitwig ready for release.

Maybe somebody who's more familiar with other daws can correct me, but I don't think the level of transparency they are showing is out of the ordinary, especially since they have now allowed beta testers to divulge every inch here in this thread.

I think I understand the beta and beta software in general. I'll stick by what I said. The original beta signup was a simple email address, no questionnaire, they've clearly skipped the idea of a public beta test -- and it was Bitwig themselves who posted features, screen shots videos and the famous 'coming soon' message.

Ogopogo · Post by **Ogopogo** » Sat Oct 12, 2013 3:59 pm

Well this line of yours just seemed suspect to me:

also it's not good if Bitwig is just a tech tool right now

That's not what's going on.

humanbeingbeing · Post by **humanbeingbeing** » Sat Oct 12, 2013 4:00 pm

Ogopogo wrote:Well this line of yours just seemed suspect to me:
also it's not good if Bitwig is just a tech tool right now
That's not what's going on.

That line seems "suspect" to you?? yeah I think I'm going to stop discussing this with you.

The All In One Source Bitwig Information & Speculation Thread