Announcement

Collapse
No announcement yet.

Weird sample behaviour - after a while

Collapse
This topic has been answered.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Sending too many MIDI messages (e.g. LFO generated ccs) still results in bitcrushing after 15-30 minutes.

    Comment


      #17
      Originally posted by Marfusio View Post
      Sending too many MIDI messages (e.g. LFO generated ccs) still results in bitcrushing after 15-30 minutes.
      Interesting. I was not aware that "excessive" CC data results in bitcrushing - I was under the impression it was a time oriented thing.

      Do you find lots of CC msgs triggers the bitcrushing, and then it continues even if you solo that channel and/or send basic Note On/Off info only?
      It seems only time oriented in my case

      Comment


        #18
        Originally posted by Satans Squidnipple View Post

        Interesting. I was not aware that "excessive" CC data results in bitcrushing - I was under the impression it was a time oriented thing.

        Do you find lots of CC msgs triggers the bitcrushing, and then it continues even if you solo that channel and/or send basic Note On/Off info only?
        It seems only time oriented in my case
        I guess it was a kind of buffer/memory overflow. It needs time to fill the buffer and or the memory gets fragmented which reduces the performance gradually. I don‘t know … but it seems to be corrected meanwhile.

        Comment


          #19
          I also noticed the bit crushing on 2.2.4. Took me a while to wonder what had changed as I was mangled the sound to death anyway. A power cycle cleared it though.

          Comment

          Working...
          X