Hello! I have the same exact issue and also on latest firmware and original SD card and power supply. I noticed the bitcrushing can get triggered when a signal comes in too hot for some reason. But I am now mainly experiencing a lot of artifacts that sound like xruns when listening back to recorded material. This seems to happen more when working in a 12 track session. Heat can't be the problem as it also happens when I just turned it on. I would hate to get rid of the bluebox as it is so perfect when it does work, but these problems make it way too unreliable for professional use. I have been experiencing this from the first firmware version to the latest. Also nothing else on the power strip. As this problem has been around for some years now, I would like to know what has solved it, as I assume it has not been totally fixed, because in some conditions it actually works just fine?
-
-
That is an incredibly useful clue. I think we may now have a fix for this problem. Look for it in version 1.2.13, which will be released in the next few days.Originally posted by JGardner View PostComment
-
Really hope the next update fixes it!
Happens every session, unuseable right now for live gigs.
Am using og powersupply+cable, 12 channels, launchcontrol xl midi controller per usb (maybe that draws too much power?)
no too hot signal coming in.
Comment
-
Installed 1.2.13 today and the bitcrushing is back. Hadn't had it for a long time and assumed it was fixed with the previous version. What's weird is it isn't happening on all tracks.Comment
-
We are looking at this. We believe it is related to overdriving the Compressor. Can you verify your Comp settings?Comment
-
Compressor is off. Just been thinking about this some more. I'm pretty certain it was channels with incoming audio that got bitcrushed for any subsequent audio. Channels that were silent at the time when the bitcrushing started continued to have no bitcrushing for subsequent audio.Comment
-
Please try version 1.2.14, which wav just released.
Comment
-
I already stated in my initial post that I tested the effect of the compressor on this issue without success. When the problem occurred I turned the compressor off but it had no effect. But of course there could be two distinct issues resulting in this behaviour.Originally posted by Steve View PostComment
-
I just tested latest firmware 1.2.14 and bitcrushing doesn't happen yet when I input a hot signal. If this firmware fixed it, that is great news in terms of reliability for live situations. If it does happen again at some point for another reason, I will report it here. Thanks!Comment
-
Had a pretty long, loud jam with both my Blueboxes being put through their paces tonight and no bitcrushing (using firmware 1.2.14)Comment
Comment