[ChristianKeymaster]

Sounds like it might have been switched to “external clock” in Global Menu (Encoder 2).
When it´s on external it does not react to the stop/play button because it waits for an external start message.

[ChristianKeymaster]

Hi Flavio,
happy 2016 to you too!

Behaviours like what you describe that only turn up sporadically are generally quite difficult to find.
I can only advise you again to switch around components, like alien suggested, and try a different clock, different combinations of devices, etc. You can also try to re-upload the Zaquencer firmware just to make sure. In theory this should work perfectly every time (it´s doing checksum tests etc), but if you experience funky behaviour I´d try anyway.

Also what I did before to find errors was to hook up a USB Midi Interface inbetween the Zaquencer and the receiving device, so that I could see the Midi data on the PC (hook up the interface input to the Zaquencer output and the interface output to the sound generator (DRM, MoFx) input). Now when you observe a misbehaviour you can check the Midi data and see if there are bytes missing etc.

I am very interested in what you find. I would really like to be able to help you more, but other than I wrote here and in my post above I can´t think of many more things to do.
Please keep us updated on your progress, maybe I can think of more things then…

[ChristianKeymaster]

Ah good to know, thanks for posting back here! Great that it could be solved that quickly.

[ChristianKeymaster]

Hi Paul,

thanks for submitting the support request. From your description you´re talking about the SysEx export/import functionality and I´ve edited the thread title to reflect this.

Which Zaquencer version are you using?
Can you please send the preset in a mail to support@zaqaudio.com so that I can try ro replicate the behaviour?

I´m not sure if you´re doing anything wrong, sounds like you´re using the correct procedure.

The LCD should display a moving “8″ on the very left side when transmitting back the preset. If that stops somewhere (could look like the – 1 you´re referring to) that would mean that not all packages are transmitted correctly. Do you have the possibility to receive the packages you´re sending with the same pc and compare sent/received data? Maybe with a midi loopback cable? A preset consists of 8 SysEx messages.

For furhter tests it would be good if you could mix up your Midi chain somehow, try a different interface, different OS etc. I don´t really think that´s the cause of the problem because you´ve transferred the firmware OK, but it can never hurt to try different things (if you have the option).

[ChristianKeymaster]

Hi Flavio,
this is strange, it´s the first time I hear something like it.
I definitely want to get to the bottom of this with you.

some thoughts off the top of my head:
- can you please send me the global and preset data that you experience the error with? I can then try to reproduce it here
- what is your setup? do the two devices with hiccups connect directly to the Zaquencer or is there any other device in the middle? for testing, can you get rid of all other devices except the Zaquencer, the DRM-1 and the Mo-FX?
- can you try switching out the devices? the DRM-1 for another drummachine and the Mo-FX for another device that likes to have clock sync? First order of business would be to determine if the behaviour originates in the Zaquencer or in the devices receiving the midi data.
- can you reproduce the behaviour (like: whenever I do this and that it happens) or is it completely random?
- it would be very interesting to see in a midi monitor if a note that hasn´t been played by the DRM-1 has been sent correctly. can you hook up a computer with a midi monitor inbetween the Zaquencer and the DRM-1?

[ChristianKeymaster]

Alien is right, we are not interested in hacking the BCR´s hardware for a larger flash rom. This would mean a quite a bit of non-trivial work to adapt and maintain the firmware and would splinter our user base. We´d rather focus on working on features to cram into the existing hardware for the moment.

[ChristianKeymaster]

Ok I understand. It seems you want to select the sound also from the sequencer.
I can confirm what Tommy said. The Zaquencer is able to set the program with the Midi Control Alpha/Beta messages (to send Midi Program Change). This is being done repeatedly, when the step is being played, so it might not be optimal.

I would also recommend to set the program on the synth directly and use the sequencer to play notes etc.
They way I see it it should be possible to setup the Chroma to “Whatever you receive on Midi Channel 1, use it to play a bass sound, Channel 2 lead etc…”, and then have the Zaquencer send the 4 tracks on the different Midi Channels (can be set in the Global Menu).

[ChristianKeymaster]

Hi Diego,
please make sure that the Zaquencer is running in internal clock mode (Global Menu, Encoder 2), so the Start/Stop Key is active. It´s not active by design if you run on external clock.

If you want to start the Zaq individually on external clock, please load an empty pattern or mute all the tracks in the Mixer so it doesn´t play. When you want it to play, load the full pattern or unmute the tracks.

Cheers!
Christian

[ChristianKeymaster]

Hi zip,
I think the assignement you ask for would have to be done in the synth, no?
Which synths are you using with the Zaquencer? Do you have a link to the manual?

Best,
Christian

[ChristianKeymaster]

Hi there,

thanks for the kind words!
Regarding your questions, yes installing the Zaquencer firmware meakse the BCR become exclusively a sequencer and removes all original controller functionality.
You can re-install the original firmware to make it work as a controller again, but this will get rid of the flash content (controller mappings/sequences) in both directions, and it will either have to be restored via SysEx dump, or by reprogramming.

The 4 tracks, or sequencers as you call it, can be freely assigned to a Midi channel. Even drums are not fixed to 10 (but can be of course), and can be assigned any Midi channel.

Yes the BCR can still be used with an iPad after installing the Zaquencer, but as a sequencer of course. Also bear in mind that installing the Zaquencer gets rid of the USB function of the BCR, so you need a Midi USB interface that works with the iPad.

[ChristianKeymaster]

Hi Drox,
yes there is the Tap Write function that allows to input notes in real time.
It´s reached through the Instrument select menu and it´s described in the manual in that chapter, on page 26.

It´s monophonic only, notes will be quantized to the step grid, and note length is not being recorded. All these parameters (chords, note delay, note length) can of course be adjusted after recording.

[ChristianKeymaster]

Awesome, thanks for posting back here!

Cheers,
Christian

[ChristianKeymaster]

Hi erwan,
thanks for your contribution!
I really thought a lot about the chord function lately and how to expand it/make it better.
I would like to include inversions as well, but haven´t found a use concept yet (that I could add to the existing one) that makes sense.

To anyone reading this, I would love to hear your thoughts about a restructuring of the chord function. Would you like a rework that would utltimately give you more possibilites, but would mess up your existing sequences chord-wise in the short run? What dou you think about the existing chords that add the octave below/above? Do you use them a lot? Could they be sacrificed for inversions?

[ChristianKeymaster]

Hi guys,
again, thanks for sharing your ideas!! I love seeing your enthusiasm talking about new gear/functions

In this case though I´m afraid it´s out of scope of what I do.
The whole idea behind the Zaquencer was to be able to get all these hardware-sequencing features into the hands of many. Take an inexpensive, widely available device and upgrade it with software to something much more valuable. I´m very happy to see that this concept works and that you guys generally enjoy the Zaquencer.

As Tommy wrote, first of all there would be much more competition if ventured into 400 Euro territory. Also, it really is a lot of work to develop a whole new device with the features you wish for. You can argue that the firmware is already finished, but adapting it to a new hardware is no small feat either. There is a reason why many devices with a lot of functions cost around 1000 Euro, and it´s not the price of parts alone.

While I understand the wish for sturdier, nicer hardware, I personally don´t have any problems with the BCR2000. As I wrote in some places before, I have a device from 2004 here that is still working great. I have opened up several other BCRs, exchanging the display and encoders and it´s been great to fix/work with underneath. I generally really like the device. Also as I wrote before, the LED rings around the encoders are a luxury. I believe they contribute a lot to what makes the Zaquencer great. Even in 2015, adding LED rings to a new device needs a lot of real estate on the device and makes it very expensive (check out Arduino boards and you´ll see).

[ChristianKeymaster]

Hi Lowcase,

the first thing to check is which mode the MIDI through on the Zaquencer is set to.
There is a filtered mode (that filters out all data which is relevant for the Zaquencer) and an unfiltered mode, that just sends everything to the output.
Filtered mode is depicted with an “F” (plus output A/B)in the display, unfiltered does only show the output A/B. I would recommend for testing to make sure it´s set to unfiltered mode.

I was not able to find the manual for the Panorama.
Can you be more specific what sort of MIDI message the sustain pedal information is?

Do you have the possibility to look at the MIDI data after the Zaq with a MIDI monitor software running on a computer? I´m sure you can see quite nicely what happens to the messages.

Cheers,
Christian

[Author]

Posts