[TheodorParticipant]

Being typically used to firmware updates not being able to roll back, somehow it slipped my mind that you CAN roll back to a previous Zaquencer firmware if something happens to go wrong.

Thanks once more, and a big respect for seeing Zaqaudio refining what was already to begin with, a superb product.

Needless to say Im posting around Zaquencer to anyone I know that might be interested! You deserve it!

[TheodorParticipant]

Hello Zaq and congrats for the continuous development of Zaquencer.

Small question based on this issue: provided that one is lucky enough to have a BCR which does not display the ghost encoder problem. I hope the new filtering feature does not give any sort of “overhead” of the processing or anything like that…correct?

(btw I have bumped indeed on that wrongly blinking LED on loading/storing even when it was on a different page)

In simple words, those who do not have the ghost encoder problem are they advised to still update the firmware? I guess so, because of the rest of bug fixes, but just making sure.

Thanks!

[TheodorParticipant]

Ok so I found out WHICH exact step was messing the procedure up. Im typing here the explanation in case anyone else bumps into the same problem – which is not really a problem, I figured it out due to your explanation above on how the whole thing works with the ‘flash” memory.

So….Lets say we have pattern1 loaded (after having been saved to flash of course). Lets also say we want to copy the sequence of track2 over to track1 – always in the same pattern1.

1.We have pattern1 loaded and we go into load mode.
1. We press and keep pressed, track1 button (destination)
2.We press the track2 button and release both – now the track2 pattern is indeed copied into track1 – BUT, remember it is not yet saved into “flash”.

Here is the tricky part – if you press the “load” button to “exit” load mode, patttern1 is recalled FROM the “flash”, essentially messing up our “copy” and reloading the “old” track1 pattern so step 3 is:

3. press EXIT button to exit the “load” menu – now you can see that track1 sequence has been succesfully copied from track2.

OR

3, “Jump” from “load” menu to “store” menu, and store the pattern1. Yet again, you can see that now whichever way you use to exit the mode, the “copied” sequence has been indeed pasted into track1 from track2.z

The tip that the “copy” is not saved to flash made me realize the correct procedure.
Thanks!

• This reply was modified 9 years, 9 months ago by  Theodor.

[TheodorParticipant]

Thanks for the help, Zaq. Im not currently in front of my Zaquencer, But I remember trying:

1. Performing the copy function, as per instructions, and exiting load mode – track1 did not have the “desired” source pattern (of track2).
What I actually observe:
I have pattern1 track 1 sequence all set to the same midi note 63, and all notes unmuted. Pattern1 – track2 is saved and has variable notes, variable note mutes and seq shift.

I thought well perhaps it is stored in flash but not recalled.

2. I proceeded in actually going into load mode again and load pattern1.

About step2 – I realize after your reply above, that doing step2 reloads the “initial” pattern – not the one that I copied. So, tonight I’ll try the following:

Go into load menu, keep track1 pressed and then press track2 to copy track’s 2 content into track 1. Then I’ll hit save to be sure the “copied” sequence is stored into flash and try it out. I’ll get back to you with the results.

• This reply was modified 9 years, 9 months ago by  Theodor.

[TheodorParticipant]

Yeah kinda like performing “solos”. Nice one!

[TheodorParticipant]

Aaaah thanks a bunch! I know its not of your responsibility, but if you or any other member has any recommendations for a reliable one, Im all ears. Truth is, I have 2 BCR units, and one of em has the built-in USB to midi interface broken so I am already using the cheapo one I have with my “factory” BCR so I was planning on getting a second one for the ZAQ BCR anyway. So, a recommendation will come in handy!

Thanks again!

[TheodorParticipant]

On the same subject, and forgive my hi-jacking of the OP….

@Andrew: Are you experiencing a bit of jittering (loose timing) when Zaquencer is “slaved” to Ableton Live. Here, internal clock seems to be “tighter” than the external one with a clock division of 16steps and all steps active.

Perhaps my cheapo USB-to-MIDI interface is the culprit?

ALSO: specifically, for Ableton Live compensation of the natural “latency” can be achieved by setting a negative delay value in the settings of Ableton Live’s midi clock output. Hope this helps anyone else dealing with the same set up.

• This reply was modified 10 years, 1 month ago by  Theodor.

[TheodorParticipant]

OK Thanks! In the meantime I figured as much! Already got my Zaquencer up and running!

[Author]

Posts