When I went to sleep around midnight it was still working, when I woke up it continues to work. Be smart - live in Poland
This is not funny, Bitwig
-
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
Why are you people using Bitwig in the middle of the night
When I went to sleep around midnight it was still working, when I woke up it continues to work. Be smart - live in Poland
When I went to sleep around midnight it was still working, when I woke up it continues to work. Be smart - live in Poland
-
- KVRian
- 1386 posts since 7 Dec, 2017
Nodp93 wrote: Wed Jun 09, 2021 4:03 amAH ! & so u are culpabilizing me (or others stupids?) to not do so & go offline like you...JHernandez wrote: Wed Jun 09, 2021 3:57 amYeah, and others may need to go online to work. I understand.dp93 wrote: Wed Jun 09, 2021 3:44 ammaybe people, i mean Adults does not use 2 computers...JHernandez wrote: Wed Jun 09, 2021 3:24 am I don't understand. People are dong serious work in a beta while online too? Or is it happening to just any version of Bitwig while online? I haven't gone through the whole thread.
I was just using Bitwig right before I came on the forum, offline.
Edit: Just saw another thread. dif ver while online. Sucks.
I never have the internet going while working as a rule. Shit happens.
(editos: or can't cause they are beggars, like they have not HO-HO-HO setup for free... xD .....
Even If I'm going to open Bitwig for a second, I turn the wifi off, do what I got to do, quit, and then turn the wifi back on. I do this because in the past (years ago) I've had a few issues with plugins becoming unauthorized which sometimes took hours to resolve. Now I'll quickly authorize online if I need to and immediately disconnect all paranoid like.
=> i just had a RealStrat update on-the-fly while i was rocking the dancefloors LOL... in my bitwig headphones...
-JH
-
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
We need more to extrapolate from. For example if your livelihood depends on Bitwig, then you could become homeless & die from heroine overdose. But I'm just guessing, so help me help you!Nemirov wrote: Wed Jun 09, 2021 7:45 amFirst there is 4th version with no significant improvements and annoying bugs fixed for years, then loosing projects because of internet things, what next?
-
- KVRian
- 600 posts since 1 Jul, 2009
sebastian_blu wrote: Wed Jun 09, 2021 4:00 am I was just going to use bitwig to prank my wife and yell into a delay unit. so im gonna have to do that with logic now....
-
- KVRist
- 430 posts since 4 Jun, 2018 from The UK
If Bitwig is going to invalidate our license, I would much rather it does it at the beginning of my session - not when I'm already 3 hours in! This sort of licensing copy-protection only hurts the paying users. Honestly I'm thinking of going back to FL Studio or maybe trying Reaper.
If I was at Bitwig I would change how the licensing check works so it doesn't lock paying users out mid-way through a session if there's some down-time in their licensing backend. At least let us save if for some reason it's switching from registered mode to demo suddenly during the session.
Not great for PR and trust building for their brand.
If I was at Bitwig I would change how the licensing check works so it doesn't lock paying users out mid-way through a session if there's some down-time in their licensing backend. At least let us save if for some reason it's switching from registered mode to demo suddenly during the session.
Not great for PR and trust building for their brand.
-
- KVRist
- 178 posts since 26 Apr, 2018
Hopefully they'll learn from it to make sure it can't happen again for users. But no-one in this thread has mentioned it happening before, so once in what, 5-6 years (not been here since it's early release so I'm not sure of exact time-frame) it may just not be something that occurred to them that it may be a problem. What is probably less likely would be releasing updates for V1 and V2, and maybe even V3 that changes this behaviour, but hopefully for users of V4 (and hopefully V3 as I have not moved over yet) can have this changed so it doesn't prevent people from working should it happen again.
I totally understand anger from people affected yesterday who ned it for work, but so long as Bitwig learn from it and publically announce a change to the process a lot of the panic saying "we'll never use it again" can be calmed down.
I totally understand anger from people affected yesterday who ned it for work, but so long as Bitwig learn from it and publically announce a change to the process a lot of the panic saying "we'll never use it again" can be calmed down.
Last edited by sbmongoose on Wed Jun 09, 2021 9:14 am, edited 1 time in total.
-
- KVRist
- 430 posts since 4 Jun, 2018 from The UK
This kicking back to demo mid-session thing has happened to one of my friends before, it's definitely something that has happened in the past to users but this is the only big time it happened to everyone at the same time that I'm aware of.
-
- KVRian
- 887 posts since 29 Jan, 2017
Agreed - I had no idea their CP is so invasive. IMO they should issue some sort of statement what and why it happened and prevent this happening in the futureRanoka wrote: Wed Jun 09, 2021 8:47 am If Bitwig is going to invalidate our license, I would much rather it does it at the beginning of my session - not when I'm already 3 hours in! This sort of licensing copy-protection only hurts the paying users. Honestly I'm thinking of going back to FL Studio or maybe trying Reaper.
If I was at Bitwig I would change how the licensing check works so it doesn't lock paying users out mid-way through a session if there's some down-time in their licensing backend. At least let us save if for some reason it's switching from registered mode to demo suddenly during the session.
Not great for PR and trust building for their brand.
-
- KVRAF
- 2296 posts since 23 May, 2012 from London
Luckily I wasn't affected at the time, but this sort of thing is concerning. Having a plugin crap out on you mid-session is one thing, but the entire DAW... 
Always Read the Manual!
-
- KVRAF
- 1596 posts since 19 Aug, 2009
-
- KVRist
- 451 posts since 8 Dec, 2014
I agree they should refrain from doing mid sessions lockout. There should be auto-saves tho, so no actual hours of work should be lost.
-
- KVRAF
- 3729 posts since 3 Nov, 2015
Just want to add, before I actually read the whole thread, this also happened here with version 2.4.3.
Suddenly while editing a song, Bitwig announces that it's now running in demo mode.
Not understanding why (and suspecting file corruption or hardware failure), I nevertheless tried to log in using the prompt offered by Bitwig. Did not work. I then made sure I can log in to the bitwig dot com web page and that was successful. But still no access to the software.
I planned to put out some new music this week. I sent an email to Bitwig, with 'URGENT' in the subject line, got a ticket number.
Seems to affect all versions of the software. It means that the software always maintains contact with a server during normal use. Not always but periodically, you know what I mean. I can understand server failure. That might be the case.
If there's a solution mentioned within this thread, I'll see it as I'm now going through.
If there's such a possibility, I'll use offline registration or any mechanism that decouples from the need of reaching a server to function properly. I do not want this to happen again.
EDIT: Tried it this morning, was able to log in, everything seems to be back.
Q: Will the offline activation remove the need to have a link to a server ? If so, how is it enabled from a running Bitwig session ?
Suddenly while editing a song, Bitwig announces that it's now running in demo mode.
Not understanding why (and suspecting file corruption or hardware failure), I nevertheless tried to log in using the prompt offered by Bitwig. Did not work. I then made sure I can log in to the bitwig dot com web page and that was successful. But still no access to the software.
I planned to put out some new music this week. I sent an email to Bitwig, with 'URGENT' in the subject line, got a ticket number.
Seems to affect all versions of the software. It means that the software always maintains contact with a server during normal use. Not always but periodically, you know what I mean. I can understand server failure. That might be the case.
If there's a solution mentioned within this thread, I'll see it as I'm now going through.
If there's such a possibility, I'll use offline registration or any mechanism that decouples from the need of reaching a server to function properly. I do not want this to happen again.
EDIT: Tried it this morning, was able to log in, everything seems to be back.
Q: Will the offline activation remove the need to have a link to a server ? If so, how is it enabled from a running Bitwig session ?
Last edited by mevla on Wed Jun 09, 2021 12:21 pm, edited 2 times in total.