Andrew Posted January 5, 2012 Report Share Posted January 5, 2012 Hello all~ I using 'sensor in a box' on behalf of midi controller. (accent sensor in a box -> Pysical computing with Micro process. similar 'Arduino' http://www.arduino.cc/ ) This device connect at WO5, occur ERROR message. 'midi i/o errir : buffer overflow' What is meant this error message? 0 Quote Link to comment Share on other sites More sharing options...
altar Posted February 16, 2012 Report Share Posted February 16, 2012 Hello, Watchout V.5.1 Midi Controller: KorgNaNO2 as soon as I raise a fader too fast,or more faders simultaneously,I get a message: "Error:Midi I/O buffer overflow" Do you know how to solve this problem? Thanks Regards JP 0 Quote Link to comment Share on other sites More sharing options...
Luca Posted February 20, 2012 Report Share Posted February 20, 2012 with the same controller i also cannot use the first slider: an I/O error appear. from the slider number 2 to the last one everything works fine. 0 Quote Link to comment Share on other sites More sharing options...
kFrogStudio Posted February 22, 2012 Report Share Posted February 22, 2012 I am getting the same error with WO4.3 and Korg Nano Kontrol. There is no information about this error on the support documentation. Does anyone know what is this about and how to solve it? Thanks 0 Quote Link to comment Share on other sites More sharing options...
altar Posted February 23, 2012 Report Share Posted February 23, 2012 Me too kFrogStudio 0 Quote Link to comment Share on other sites More sharing options...
artwhaley Posted March 22, 2012 Report Share Posted March 22, 2012 I'm having the buffer overrun problems with this Korg Nano 2 controller and Watchout, though I've seen it work perfectly with other software. If I move one fader at a time I don't have any problems, but if I move two faders quickly to full travel in either direction the 'status bar' in the input window stops moving at a random number (OTHER than 1 or 0) in the middle of the travel and I get the buffer overrun error. The problem Luca mentioned is based on the fact that the controller identifies the first fader as control '0' and Watchout will only recognize Midi channels starting with 1. This seems like a simple thing that could be corrected in the next version of watchout? The buffer overrun thing may be specific to our Korg controllers... though the fact that other software (I've got it working in Resolume Avenue at the moment) responds perfectly makes it sound like there's something up with the midi implementation in Watchout? Is there more info I can provide that will make tracking these issues down easier? 0 Quote Link to comment Share on other sites More sharing options...
ARTABASE Posted March 23, 2012 Report Share Posted March 23, 2012 With a KontrolEditor software you can change your controller setup, patch ... 0 Quote Link to comment Share on other sites More sharing options...
Moderator jfk Posted March 24, 2012 Moderator Report Share Posted March 24, 2012 ...The problem Luca mentioned is based on the fact that the controller identifies the first fader as control '0' and Watchout will only recognize Midi channels starting with 1. This seems like a simple thing that could be corrected in the next version of watchout? ... I think that my be a difference in the implementation of the MIDI standard. If you read the published protocol, there is no MIDI Channel 0, they start at 1. The published protocol states that MIDI channel 1 has a hex value of 0, so Korg may be interpreting things a bit differently. There are sixteen MIDI channels available. Some vendors choose to incorrectly label them 0-15 while others choose to correctly label them 1-16. So if your Korg offers 0-15, then likely Dataton MIDI channel 1 = Korg MIDI channel 0, etc. 0 Quote Link to comment Share on other sites More sharing options...
Natalia Posted May 25, 2012 Report Share Posted May 25, 2012 There are good articles about buffer overflow in the May issue of Exploiting Software Hakin9. You can read the teaser here http://hakin9.org/wp-content/uploads/downloads/2012/05/HES_05_2012_Teasers1.pdf 0 Quote Link to comment Share on other sites More sharing options...
ThomasL Posted May 25, 2012 Report Share Posted May 25, 2012 The article is irrelevant to the above problems. I had a buffer overflow error message once when i was testing out a borrowed Behringer BCF 2000 with Watchout 5.x. I can't recall exactly but I think the error message is due either to a connection error between Watchout and the MIDI controller or a wrong setting on the Controller such that it is sending something that overloads the MIDI inputs on the WO computer. I solved it then but can't remember what I did exactly. Check all your inputs and output connections between MIDI Controller and Watchout PC (should be simple basic stuff), and read the manual of the MIDI Controller. 0 Quote Link to comment Share on other sites More sharing options...
antonioscreenmaster Posted August 18, 2012 Report Share Posted August 18, 2012 Hi! How to overcome the next problem "error: MIDI I/O: Buffer overflow"? Midi controller nanoKontrol2 works good with another programs: Resolume Arena, VDMX etc 0 Quote Link to comment Share on other sites More sharing options...
Luxav Daniel Posted October 20, 2012 Report Share Posted October 20, 2012 Hi Same Problem with my new Korg! Using 4.51... Whats that? Greetinx Daniel 0 Quote Link to comment Share on other sites More sharing options...
Luxav Daniel Posted October 20, 2012 Report Share Posted October 20, 2012 Hi Problem Solved? Watchout didnt find my BCF...My Nano work :-/ Greetinx Daniel 0 Quote Link to comment Share on other sites More sharing options...
Jonas Dannert Posted October 20, 2012 Report Share Posted October 20, 2012 This will be fixed in the upcoming 5.3 release. Not in version 4 though. /jonas 0 Quote Link to comment Share on other sites More sharing options...
Luxav Daniel Posted October 22, 2012 Report Share Posted October 22, 2012 OK... Uncool to hear that, because we are Using 4.51 Keys...hmpf The Korg Nano Key version 1 is doing fine...but its damaged :-( Greetings Daniel 0 Quote Link to comment Share on other sites More sharing options...
Moderator jfk Posted October 27, 2012 Moderator Report Share Posted October 27, 2012 MIDI I/O errors were addressed with improvements in the MIDI support of WATCHOUT 5.3. 0 Quote Link to comment Share on other sites More sharing options...
Luca Posted April 5, 2013 Report Share Posted April 5, 2013 in 5.3 it is not solved. any news? 0 Quote Link to comment Share on other sites More sharing options...
Jonas Dannert Posted April 5, 2013 Report Share Posted April 5, 2013 It should be. /jonas 0 Quote Link to comment Share on other sites More sharing options...
DavidPatrick Posted May 8, 2014 Report Share Posted May 8, 2014 Error: Buffer Overflow Anyone know what this error means? Doesn't seem to affect anything...show still performs fine. Can't seem to replicate it consistently either. dp 0 Quote Link to comment Share on other sites More sharing options...
Moderator jfk Posted May 8, 2014 Moderator Report Share Posted May 8, 2014 In what context are you encountering this error? We would see errors like that with MIDI in older versions, what version are you using? 0 Quote Link to comment Share on other sites More sharing options...
DavidPatrick Posted May 9, 2014 Report Share Posted May 9, 2014 v 5.5.1 No MIDI (Error only said "Buffer Overflow" - no mention of anything else. No inputs or outputs. No external control. Only two outs from a single machine. Got a couple Aux timelines, but they aren't doing much. Almost all the show is in the Main Timeline. A couple comps, but I can't isolate it to that. Message would pop up while I'm sitting paused in the timeline...I don't recall it happening while I was playing anything. Also popped up once after I refreshed changed media. Like I said, hasn't affected anything. Just curious what it means so I can avoid...that box popping up always makes me a touch nervous. 0 Quote Link to comment Share on other sites More sharing options...
limeworks Posted May 9, 2014 Report Share Posted May 9, 2014 I received this message recently (5.5.1). But it was because i was switching between different MIDI monitoring tools / USB midi vs standard MIDI etc, when using a combination of controllers together. I haven't had the same problem using standard MIDI devices via a PCI-E Midi port. It seems to be much more stable than connecting via USB (it also means watchout can see more than one controller). Rob 0 Quote Link to comment Share on other sites More sharing options...
Jonas Dannert Posted May 9, 2014 Report Share Posted May 9, 2014 WATCHOUT can only use 1 (one) MIDI-device. /jonas 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.