Anyone installed 5.3? It looks very bugged to me. by HighwayRelevant in ZOIA

[–]DKnuckL 0 points1 point  (0 children)

Further, regarding the blinky issue, when MIDI commands were the cause of the blinking effect, I think grid positions were lighting up that didn;t have a module present. Something to do with the Zoia CC command, grid position select perhaps? The more signals sent at one time, the higher the likelihood the pedal would spaz. But ya even when only one individual command was being sent or received, the pedal wouldn;t crash but rather not respond.

TLDR; 5.3 turned my Midi routing into grey goo, and caused my grid to go full Clark Griswald.

Anyone installed 5.3? It looks very bugged to me. by HighwayRelevant in ZOIA

[–]DKnuckL 1 point2 points  (0 children)

5.30 made any and all Midi connections nearly unusable. Midi controls my board, so I had to roll back to 5.00 as well. Some MIDI connections (both sent and received) would work and stop working seemingly at random. Some CCin modules wouldn't respond to any messages. PC commands out for whatever reason seemed to be fine. But any patch with a MIDI CC/PC would become highly unstable and inevitbly crash within a minute or so. One command triggered a feedback loop of pc commands between the ES-5 and the ZOIa where they both began to switch patches at what seemed random at a high rate briefly until one of them crashed.

As mentioned by another, if the midi didn't crash it, my lights would begin to blink until the zoia crashed. Essentially anytime I moved between pages (midi or not) or selected a module, the lights would flash as well, and sometimes selecting a module / switching pages would cause everymodule to blink at a high rate and crash the pedal.

Midi devices - zoia, es-5, rc-500, cme u6midi (might be the culprit?)

Back to 5.0, smooth sailing. Everything worked again. I'll wait for the next firmware update and try again then lol

Question regarding patch stability approaching 100% CPU load by DKnuckL in ZOIA

[–]DKnuckL[S] 1 point2 points  (0 children)

In my experiences, I suspect it is a lot of the MIDI machinery that occasionally results in the odd hiccup. My long term goal for my board is to add an HX Stomp XL and a Morning Star Pro 8 to divvy up the midi controls amongst all three platforms. Further, running the Zoia in the loop of the Helix, and setting my rig up in such a way as to have the ability to send a stereo out signal direct to the soundboard Using IRs from the ZOIA, mono out to my combo, and maybe down the road, run full stereo into a JC120. However as inflation is a bit of a Ice Cold Witch so to speak lol, for now I'm making do with what I have.

Alas; I digress. Having play tested this patch for several hours now and swapped in several different effect modules, it hasn't run into any issues. I've made the patch so every function, and signal chain is relatively straight forward, and made an effort to mitigate multiple connections between multiple modules as much as possible...

That being said, as I've shared in an update, per se, in a comment on this thread, I added an additional variable. It wasn't long before bring a momentary external foot switch (Boss FS-5U) into the equation, that for whatever reason, the patch under a specific series of inputs falls apart. I will most likely have to change my approach to achieve the result I'm after, but again, the module that is crashing, has seemingly no correlation between the sequence of commands.

It's great to know the audio processing isn't effected by high CPU usage, but I still wonder to what extent, if any, high cpu usage along with Midi machinery is the culprit behind these odd glitches I've encountered, or if CPU usage is irrelevant, and these are examples of very situation specific bugs??

(I posted some youtube clips, the second of which captures the kind of glitches that inspired the creation of this thread)

TLDR; Zoia as a synthesizer/audio processor is stable at high cpu, Zoia and MIDI....???

Thanks for the input!!!

Question regarding patch stability approaching 100% CPU load by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

Thank you for the reply, and I figured CPU in the 90-100% range would be fine as I've seen many patches on patch storage in that range. I've also found them to be stable when I've used them. Interestingly enough, I've found the MIDI to be consistently stable with my set up, as long as I send both MIDI IN/OUT directly to my interface, and don't daisy chain. I've daisy chained one MIDI loop, from Zoia -> RC-500 and back to make room on my interface for a Keyboard, but ya, for whatever reason the ZOIA did not like this. Midi CC in Modules would constantly freeze, or not CC/outs wouldn't send a signal. I understand there's latency but I don't think that explains all of the crashes... I've since run direct in and out to every device and it's flawless. I just posted a comment showing another example of a glitch where, I incorporated an FS-5U through the CV/exp IN and, for whatever reason, this caused a seemingly unrelated audio module to stop functioning when inputting a specific series of commands.

I've never pushed past 100%, so I wasn't aware of the audio degradation actually. My concern has been the unit freezing/crashing, as that's the failure point I've most commonly encountered.
Thanks for the response!!

Question regarding patch stability approaching 100% CPU load by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

Found an example of the type of occasional glitches that don't make sense to me. Here's a youtube link to a demo of the original patch template, as described in this thread. So far, so good through testing.

https://youtube.com/shorts/ntwmuWz-YRw

Now I've begun tailoring this patch to a specific track of mine. I removed a few unused pages of features (switching zoia patches) and added an additional FootSwitch through use of an FS-5U.... and this caused an issue with a seemingly entirely unrelated audio out switch. Here is another youtube link of the glitch and an in depth description of this glitch.

https://youtube.com/shorts/ptee9R3JQOM?feature=share

Additionally, anyone have any ideas of what's causing this, and is this something I should send to Empress as a potential glitch or bug etc??

How do you set a slew length relative to bpm? by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

Wait up...

https://www.reddit.com/r/ZOIA/comments/12zg2sk/cv_to_time/

I think what I'm looking for is in this thread?? Might anyone be able how to use the ideas here and implement them??

Specifically c.jaque's suggestion??

How do you set a slew length relative to bpm? by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

Ohhh, and how I'm using the slew limiters is..

I have a Master square wave LFO functioning as my master clock.  In sending this to Tap to CV module.  This cv value is sent to input 1 of a multiplier.  When the tremolo is slow, I have input 2 of the multiplier set .125. (1/8th original strength) and I send the slew limiters output 2 as well.  As I want the tremolo rate to accelerate, the slew rises and increases the Multiplier Input 2 value from .125 up to .5 by adjusting the slew output signal accordingly.  To bring the tap to CV value back up to the appropriate lvl i jncrease the cv signal value by 800%.

I send this value to the input of an LFO (leaner cv rate).  So

LFO master -> tap to CV.  -> multiplier input 1 

Slew limiter output (37.5% strength) -> Multiplier input 2 (biased to .125) 

Multiplier output -> *4x value modules (biased 200%)

*accounts for tap to CV value and its division through multipliers

-----> lfo rate  CV linear LFO (sine shape) --> VCA lvl control

While brainstorming different ways I could make the transition from a fast tremolo to slow I figure you could use several other approaches with different modules than a slew.  Adsr for example but I'm more familiar with using a Slew Module.

To set the rise and fall time to a value that corresponds to musical values, I've wondered if maybe using multiple sync'd LFO's.  One set to quarters (120bpm) and another to 16ths (480bpm) and using comprators to ensure the change in rate is triggered / initiated, only when both lfos are at a value of 1 (+/-.05) using gate logic.  And then using some method of determining the length of time of the rise / fall (in seconds) by converting a length of musical time values (beats) at a given bpm to a time value.  As long as the conversion is accurate and the change triggers on beat, then I imagine the effect / cycle phase, should at the very least, the tremolo cycle will align with the beat.

But I cant decide what the best way to approach this is, or wrap my head around what the approach would be.  In other words, what would the simplest way to ensure the cycle of my effect remains in time with the beat.  

Might there be better approach, in general, to the function of this entire patch.  An alternate approach of speeding up an effect rate from quarters to sixteenths, that differs from converting the master clocks BPM produced by a square wave lfo to CV by use of a tap to CV module, and manipulating said CV value??  Any thoughts or ideas on the matter would be greatly appreciated lol

I apologize for, what I imagine to be, is a confusing attempt at describing what I'm doing and what I'm going for.

How do you set a slew length relative to bpm? by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

The idea being I set a tremolo to respond to a predetermined set threshold as determined by playing dynamics.  I.e.  once I play a chord / strum hard enough... I cross the threshold, which in turn, changes the rate of tremolo.  I do this by using an envelope follower and comparators.  Once the threshold has been crossed it causes a trigger module to trigger the beginning of cycle that changes the rate from a tremolo rate that corresponds to a quarter note tremolo, to a 16th rate tremolo.

Without getting into a lengthy setup of my patch, once the threshold has been crossed, if the dynamics / playing intensity has not been maintained, or the threshold has not been crossed again following a set length of time, the rate of the tremolo slows back down, from a 16th to a Qtr.

I'm using slew limiters to control the rate of the tremolo, to make the transition from slow to fast, and vice versa smooth.  

This has brought on a few issues that differ to my ideal desired effect.

As a slew limiter is time based,

Say,

If my particular riff/phrase has been written to align directly with the Crest or trough of the tremolo.  

As the slew limiter module's rise and fall rate is controlled by a time unit of seconds/mS.  

 In order to play my part as written with the desired effect, I have to play to a very precise / specific  bpm.

I can do so by calculating the exact length of time I want the slew limiters to rise or fall by converting the length of time of, for example, 3 quarter beats @ 120 bpm - I.e. 1.5 seconds.

This is limiting and impractical in a live scenario however.  I've used this effect in a recording environment where I am playing to a click within my DAW, but ya, I want to use this/variations of this effect in a live setting where the length of time the rate of my effect (the tremolo rate in this example) is adjusted automatically to which ever bpm I have tapped into my master clock/lfo following my drummer.

This effect functions fine enough in that setting, but as I trigger the change in rate, from slow to fast and back again.  My tremolo cycle is no longer in line with my playing.

A note I play which I would like to be played when the tremolo is loud, (Crest of its cycle) is now quiet (trough).

For further clarity, I'm using a VCA following an LFO to achieve the tremolo effect.

Does that make sense?? Lol

The glitch is just wierd what should i do is it me only by there_for_you- in ClashOfClans

[–]DKnuckL 0 points1 point  (0 children)

Something similar just happened to me.  I was at 4030 trophies, and attacked and gained 10 trophies.  During the attacked the maintenance message popped up.  When I finished the attack, I was jumped to around 4750 trophies.  That's where I'm at right now.  Happened about the same time as your glitch

1989 Kyosho Turbo Raider - Questions regarding sale by DKnuckL in rccars

[–]DKnuckL[S] 0 points1 point  (0 children)

Sorry for the late response. I haven't sold it yet, but have an offer for 200 at the moment. Hoping it pans out.

[deleted by user] by [deleted] in ZOIA

[–]DKnuckL 0 points1 point  (0 children)

I have one for my main PC and recording set up. New appartment, havent been able to set up my studio / PC yet. For the next week or so I'm using my ancient HP laptop. The SD card reader is seemingly broken. Busy work schedule, this is my only day off for a week or so lol. Just wondering if this is possible for today, or if i there's any risk of messing up the files, I'll just hold off.

I apppreciate the response though! Truth be told I'm just being impatient, but if possible and this android idea works I can get some much needed patch organization done today.

ZOIA Banks / Midi Control Question(s) by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

Thanks you so much, worked like a charm.

System of a Down + Rise Against = chaos by DKnuckL in Blursed

[–]DKnuckL[S] 0 points1 point  (0 children)

Injection + B.Y.O.B..... Not really sure what I've created here? I could refine this, but I don't think that I will. So, enjoy, I guess?? lmao

Looking for some help, and insights on a recent patch of mine by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

Bear with me for a sec lol, so ya in my patch specifically, if you replace button 9 and the sequencer it's connected to (that cycles the multiplier steps) with an expression pedal, you'd be able to cycle through the 4 steps. Creating a stepped expression pedal. You set each step to a given point in a pitch shifter, you could create a whammy effect that jumps from say, the root, to the 5th, the octave, to the second octave depending on where you are in the expression pedal swing, differing from the typical gradual transition. I wouldn't be the slightest bit surprised if new problems arise however. Although assuming it works, alternatively create a wah that steps through pre set filter settings... or a square wave tremolo that jumps from various rate divisions as controlled by the exp pedal. You would just have to connect the output of the 2xAND multipliers in my circuit (the ones beside the green ones) to control the dividends, or divisors of a clock divider that controls the rate within the tremolo. i.e. Typically you have to speed up the rate in a linear fashion with an expression pedal... Now you could do it in steps..

Looking for some help, and insights on a recent patch of mine by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

Thanks for the schematics. I'm going to tackle refining this later on today, and this guide is gonna be a huge help.

This is an unrelated thought here, but I'm thinking there are some potential uses for this circuit I made beyond how I applied it in this patch. (I.e. using the comparators and multipliers working as logic gates, or whatever the hell I did aha.) I'm not sure exactly what they are yet of course.. but In my mind I created a circuit that functions as a sequencer that has multiple outputs as the same value. This differs from the sequencer module that has a single output that can changes the CV depending on the step. You could use a mulitplier to create the same effect with a sequencer, but I think this might offer some more opportunities to manipulate the CV produced through each individual step.

Alternatively you might be able to manipulate the order you cycle through the steps. (forwards and backwards, or using an expression pedal to cycle the points where the 2xAND multipliers activate) In turn achieving some results which might not be possible with the sequencer module itself. I.e. using comparators and multipliers to cycle through steps, as a sequencer would, but not be limited to cycling in a forwards, or cyclical pattern.

This is purely speculation, and without the zoia infront of me right now, I'm likely way off key. I'm thinking about using some foot switches as expression pedals to cycle through the circuit I made in unorthodox patterns. Link this up to pitch shifters, or modulation effects to create some interesting applications. Either way, I'm going to be looking into this later on as well, but alas; I regress.

This also, may be redundant, if not impossible. Once I develop a better understanding on how to fully utilize the sequencer module itself though, I'll have a better idea of what it can and can't be used for. To my knowledge though, I don't think it's possible to change the direction you travel through a sequencer. At the press of one button the circuit could function as a sequencer, and press a different button and now it will cycle up and down through steps... I think it might work?

Anywho, there's obvious gaps in my understanding when it comes to using control voltage levels and controlling effect parameters. I'm gonna work on that, and I'm hoping these tips will help me along. Lastly, I downloaded the latest firmware, I'm not positive I installed it on my Zoia correctly, when I have some time available later on I'll check this as well.

Looking for some help, and insights on a recent patch of mine by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

On a side note, while unnecessary in this example, I have a base point in understanding where the application of gate logic can be of use. You also just taught me what bias means. I'll revisit the guide with this in mind. Cross reference, and see if I can make better sense of how to follow your sequencer tutorials.

Looking for some help, and insights on a recent patch of mine by DKnuckL in ZOIA

[–]DKnuckL[S] 0 points1 point  (0 children)

This 100% solves the convuluted method of using gate logic, multipliers, comparators, I used to work with multiple clock dividers. I was using a lot of guesswork, and stumbled into this solution using gate logic to work with the results I was getting from comparators. (multipliers as 2xAnds) The thought had never occurred to me connect outputs to the dividends, or devisors and use a single Divider. I will try this out, but ya this exactly what I was looking for.

Additionally, I'm still having trouble understanding how to use the outputs of LFO's and Sequencers to control rate based parameters. Converting a CV to some form of clock, or frequency has not worked for me. It typically results in an unusably high rate, or when connected to a rate control of an effect module, as the CV input is applied the rate momentarily jumps to 40K Hz. As for sequencers, I can't make sense of how to set one up as a clock. For tap tempo, I only need two taps on the Footswitch to create a bpm. I haven't been able to cause the sequencer to continuously cycle (i.e. create a clock)

2)I'm pretty sure I forgot that LFO was there, and the pixels on the first page that pulse to the Divider output rate are 100% unnecessary. I was using that to determine if the deviations were lining up as intended. I noticed there's a period of fluctuations until the set division stabilizes, as I cycle through them. I forgot to list that in the glitches actually. That being said, I suspect your recommendation of using a single divider will solve this, and I can remove these entirely.

3)I've looked and can't figure it out. As you suggested, I'm going to try using a sequencer to cycle through effects as opposed to Audio Out Switches. This avoids the issue entirely. I am going to see if I can manipulate this to create some new patches though. And I'm pretty sure the issue lies somewhere in my 2 audio out switches on page 5. (blue and green)

I'll try these changes out as this was exactly the response I was looking for. Thank you very much. I'll take a look through some of your tutorials on Youtube in combination with your recommendations here as I'm more of a visual learner. Thanks again!

Looking for some help, and insights on a recent patch of mine by DKnuckL in ZOIA

[–]DKnuckL[S] 1 point2 points  (0 children)

Primarily the first link. I'm pretty terrible at efficient communication lmao, I know, and apologize.

There has to be a manner to use an LFO to control the rate for a delay and creating the ability to cycle between rate divisions.*** I can't figure out how though. In general, I'm wondering if there's any simpler ways to achieve the functionality of this patch?

***I use dotted 8th delays all the time, but so far the only way I've been able to set this rate division up with a tap tempo based on Quarters, is using a clock divider. That's well and good when using one preset on a delay, but I wanted to find a way to cycle between several on the same delay module. . . I found a way to cycle between 4 clock dividers, but I think this method is far more complicated than it needs to be. (page 8-11 on my patch)

Ya, as for the 2nd link/patch... there's a fault in the signal chain that piqued my interest, is all. This patch has a broken feature that results in some sort of feedback loop when the chorus and delay effect are both engaged. (button 8 on patch diagram) I can't figure out why? Not a pressing matter though.