yep nothing important at end,qtheerearranger wrote:your video goes black at the end.
Bitwig Studio 1.3.8 RC-1
-
- Banned
- 1601 posts since 29 Sep, 2014 from Halmstad, Sweden
desktop: windows 10 x64, i5 4690k, 32gb ram 1600mhz, 2x ssd 128 gb +2x3 tb, asus gtx 970, asus proz gamer motherboard, no external audiocard
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750
-
- KVRAF
- 1551 posts since 14 Feb, 2010
Ah nice that,s nice to read.volker@bitwig wrote:Push4Bitwig crashes are fixed for the next update, was technically all the same issue.codec17 wrote:And another push thing.
When load VSTi on track, and switch to drumview on push, press octave up/down and slap a pad BOEM. crash.
Includes also the "(getting out of a FX\drumlayer)" fix maybe?
-
- KVRian
- 510 posts since 5 Apr, 2014
i noticed a great thing at least for me,
if i double click project files now, it does open Bitwig.
This hasn´t been the case in versions before.
if i double click project files now, it does open Bitwig.
This hasn´t been the case in versions before.
-
- KVRist
- 130 posts since 2 Mar, 2015
I'm just now noticing what I believe to be a bug. I use a lot of SoundToys plugins which require an iLok. I have a session with a couple instances of Decapitator. I left my iLok at my studio last night and tried to open the same session without it. The session will open but the audio engine will continuously say all of the plugins in the session have crashed and gives me the option to reload the plugins as normal. The problem is none of the plugins will actually reload successfully so I can't play any audio in Bitwig. I figured it was because of the Decapitators so I removed them, saved the session, closed Bitwig, then reopened it. The session now runs like normal. No plugin crashes. Can anyone that uses iLok for any plugins try the same process to see if this is reproducible? I'm submitting it to Tech Support now.
I've also been having the audio engine constantly spinning and not actually activating. This just started to happen recently as well. Most of the time Bitwig has run pretty well.
I've also been having the audio engine constantly spinning and not actually activating. This just started to happen recently as well. Most of the time Bitwig has run pretty well.
Mid 2012 Macbook Pro OSX 10.9.5
www.WeAreMadHouse.com
www.WeAreMadHouse.com
-
- KVRian
- 844 posts since 6 Nov, 2004 from UK
i reported a bug today not sure if it's specific to me. Can't believe i didn't notice it before.
When overdub-recording notes in clip launcher with the arrangement panel hidden, it doesn't work properly - pressing a midi key will result in a 'machine gun' triggering affect. Ie the sample will play like 20000 times per second!! aghhhh
If i open the arrangement page so it's in view, the bug vanishes (or at least improves)
Trying exactly the same thing in 1.3.8 has no problems at all. So something with this Rc
Best
DALE
When overdub-recording notes in clip launcher with the arrangement panel hidden, it doesn't work properly - pressing a midi key will result in a 'machine gun' triggering affect. Ie the sample will play like 20000 times per second!! aghhhh
If i open the arrangement page so it's in view, the bug vanishes (or at least improves)
Trying exactly the same thing in 1.3.8 has no problems at all. So something with this Rc
Best
DALE
- KVRian
- 1353 posts since 31 Mar, 2014
Can confirm. Also got these machine guns when overdubbing in clip launcher.askewd wrote:When overdub-recording notes in clip launcher with the arrangement panel hidden, it doesn't work properly - pressing a midi key will result in a 'machine gun' triggering affect. Ie the sample will play like 20000 times per second!! aghhhh
If i open the arrangement page so it's in view, the bug vanishes (or at least improves)
I played on the Surface in 'Play' mode (tablet display profile). But didn't took the time for investigating further. I thought that some irregularities with the the touch input might be the reason but doesn't seem so.
And sometimes it works fine and sometimes these stutters happen. Couldn't find a way to reproduce it consistently yet...
- KVRist
- 364 posts since 13 Nov, 2010
Yep... Either Machine gun or silent... I hate this one sooooooo much!!!askewd wrote:i reported a bug today not sure if it's specific to me. Can't believe i didn't notice it before.
When overdub-recording notes in clip launcher with the arrangement panel hidden, it doesn't work properly - pressing a midi key will result in a 'machine gun' triggering affect. Ie the sample will play like 20000 times per second!! aghhhh
If i open the arrangement page so it's in view, the bug vanishes (or at least improves)
Trying exactly the same thing in 1.3.8 has no problems at all. So something with this Rc
Best
DALE
V.
- KVRian
- 598 posts since 18 Dec, 2014
I think this is a false positive
this happened on the last version
just click ok and install it
Important note for Windows users:
Windows might show a warning during installation about the installer not being trusted software. This is only a temporary issue and should disappear soon. In case you see such a message, you can still install the software by clicking "install anyway" (or something similar).
Best wishes from the Bitwig team!
cheers
kev
this happened on the last version
just click ok and install it
Important note for Windows users:
Windows might show a warning during installation about the installer not being trusted software. This is only a temporary issue and should disappear soon. In case you see such a message, you can still install the software by clicking "install anyway" (or something similar).
Best wishes from the Bitwig team!
cheers
kev
BWS 5.0.6,Spark LE, V Collection 9.2 BS1 & BS PRO, KS & KS pro keylab 25, Axiom pro 49,Behringer UMC1820,LPP ProFx8 v2 Icon m+, KRK 10/3,win 10 pro,i7 5820k 4ghz ,16G ddr 4 1TB NVMe.M2 msi x99a sli + NV GF Gt710, Matrix Brute Roland TR8S
-
- KVRer
- 18 posts since 29 Jul, 2005
OK! After reboot windows something changes and i have installed 1.3.8 RC-1
All version 1.0.1 - 1.3.8 the same reports
#:engine-x64.exe
Detected instruction set: AVX
Exception throw: Could not open shared memory with name "bitwig-meter-mem" and size of 8
388608
All version 1.0.1 - 1.3.8 the same reports
#:engine-x64.exe
Detected instruction set: AVX
Exception throw: Could not open shared memory with name "bitwig-meter-mem" and size of 8
388608
- KVRian
- 1353 posts since 31 Mar, 2014
+1Ogopogo wrote:Can you guys please fix double contents? So that it doesn't stop the clip from playing when you use it?
- KVRAF
- 4805 posts since 21 Jan, 2008 from oO
what is that about? Double contents? Where do you have that?Ogopogo wrote:Can you guys please fix double contents? So that it doesn't stop the clip from playing when you use it?
JamWide - a cross-platform Ninjam client for DAWs
- KVRAF
- 2562 posts since 1 Oct, 2013
"Content x2" in the clip inspector. It doubles the length of a clip and duplicates the contents of the clip to fill it. So if you have a 2 bar drum pattern and you use "double contents" you now have a 4 bar pattern that consists of those 2 bars twice. It's great for if you decide you want to switch the pattern up or add a fill after a few bars. Or if you want a chord progression to play twice with a some variation the second time. But if you use it on a launcher clip, it stops playing and you have to restart it.Suloo wrote:what is that about? Double contents? Where do you have that?Ogopogo wrote:Can you guys please fix double contents? So that it doesn't stop the clip from playing when you use it?

