Forum Replies Created
-
AuthorPosts
-
June 7, 2016 at 8:58 am #4829
Hi Jorge,
can you please go more into detail, what did you mean by “when I linked the drum instruments”? What is the Zaquencer version you´re using?
What is your setup? Especially, how is the Vermona connected to the BCR? Directly or with another Synth or Midi-Through box inbetween? Is it the only device connected to the Zaq?
Can you try replacing the Vermona and check if it also happens with a different drummachine or PC connection?Do you have a USB interface? Can you please look at the note data that is being created by the Zaq to get more hints on what´s happening?
May 12, 2016 at 7:57 am #4789Hi Jacobo,
thanks for your message and sorry to hear about your problem.
It looks a lot like the dreaded BCR2000 hardware bug, described here:
https://zaqaudio.com/forums/topic/sticky-hardware-issues
and here:
http://ricardo-dias.com/2013/07/19/repairing-a-behringer-bcf2000/In the second link contains hints on how to repair it. I have personally gotten a BCR with the same error to work with these instructions. You need some electronics knowledge to do it though.
Your other option is to get a new BCR and transfer your Zaquencer license (please write to support@zaqaudio.com for a license transfer request). The old BCR can be kept for parts or sold. They still have value even broken.
Best,
ChristianMay 10, 2016 at 3:49 pm #4782Ok, that´s already some hints to go by. It would be awesome if you could export the pattern and global data as sysex and mail it to support@zaqaudio.com
B, can you please describe in detail how the connections are going in/out from the Zaquencer?
May 10, 2016 at 7:22 am #4774I´m afraid I cannot be of much help here, as I have 0 experience with bitwig. Any other guys?
Edit: Ah it seems in the other thread that you were already able to solve this?
May 10, 2016 at 7:20 am #4773When you say high pitched noise you mean tonal note noise, right (as opposed to white/pink noise)? Are you guys using the scale feature when this happens?
May 4, 2016 at 7:28 pm #4758Thanks J.A.B. and Nathaniel for your comments! Can you all who experienced this with a thru box please mention the brand&type of the box like J.A.B. did? I´d like to see if there´s a pattern. Also, please holler if you haven´t used a thru box (and no other midi through path – synth directly connected to the Zaquencer) and still experienced this. Thanks!
Edit: I just realized that the Miditech Midi Thru has a panic button. That seems an odd thing to incorporate into a through box, except you´re expecting anomalities?
May 4, 2016 at 7:58 am #4755Hi Flavio,
thanks for sharing the feature request!
While I understand the idea behind it, I had thought about it before and back then had decided against it. The reason was that I wanted the Store/Load pages to look distinctly different from the Main/Mixer/Global pages so you do not accidentally trigger a load or sometimes even worse, a store, thinking you´re in a different menu. This is why all the LEDs light up. Also to have an indicator for empty/used is not so trivial to do and either requires additional flash memory or a routine that checks all the patterns on entering a menu.Regarding your other question about emptying all the patterns, you can re-initialize the Zaquencer by holding “Page<” and “Stop/Play” at startup. This will reset all flash memory (= all the patterns and the global settings). For single patterns you could always record an empty pattern via SysEx and then just send it back to clear a single pattern, or copy it from an empty slot.
May 3, 2016 at 7:46 am #4749Ok, great to hear! Thanks for reporting back here. Cheers!
May 2, 2016 at 11:02 am #4742Hi chnouf,
thanks for submitting your bug report!
Is this happening especially when you make a lot of use of the ratcheting/delay feature?
You write that you´re using 1.04, but there have been two follow-up bugfixing updates. The most recent version is 1.042. You should be able go back to a previous version (1.03 or earlier) without problems, just download them from your account and send them via sysex to the BCR. I always advise to backup existing patterns via SysEx first, just to make sure.May 2, 2016 at 7:33 am #4737Updated, thanks!
May 2, 2016 at 7:31 am #4736Hi Pierre,
thanks for your message!
To answer your question, the notes will not be cut off by the next step.
So, yes you can create polyphony by overlapping notes of different steps
(of course it also depends on the synth if it can handle polyphony).Best,
ChristianApril 16, 2016 at 8:40 am #4711Thanks for that, added!
April 13, 2016 at 4:47 pm #4706Ah ok, thanks for editing your post with more data! From the first post and yours, it sounds like this might have something to do with the thru+filter settings. Will look into that next.
April 13, 2016 at 4:22 pm #4705Thanks for chiming in! It seems that this affects more people.
Do you have a feeling when it might occur? Like, are you using the scale feature? A lot of chords? How high or low are the notes of your sequence?I have already looked into the issue here, but was not able to produce it so far. I have also looked into the code creating noteOn/noteOffs but for now it seems solid. From looking at the code I could not imagine a scenario where there is a noteOn created, but no appropriate noteOff following.
I would be very grateful about more information or data about this. I will continue to look into it myself as well.
I´m thinking of including a panic function as an intermediate remedy (sending noteOff on all notes when pressing a button).
April 13, 2016 at 8:32 am #4689Started a sticky thread about the interfaces:
https://zaqaudio.com/forums/topic/midi-usb-interfaces-for-zaquencer-installationPlease keep posting your experiences to this thread here and I will transfer your infos to the mentioned sticky thread.
-
AuthorPosts