MUFF WIGGLER Forum Index
 FAQ & Terms of UseFAQ & Terms Of Use   Wiggler RadioMW Radio   Muff Wiggler TwitterTwitter   Support the site @ PatreonPatreon 
 SearchSearch   RegisterSign up   Log inLog in 
WIGGLING 'LITE' IN GUEST MODE

ADDAC207 - New Firmware: Issues / Reports
MUFF WIGGLER Forum Index -> ADDAC System  
Author ADDAC207 - New Firmware: Issues / Reports
ADDAC System
Dear all,

hope everyone is well. Following up the ADDAC207 threads we decided to create 2 threads for these matters!

This thread will be used to Report issues with the latest Firmware released. In order to avoid already known issues, please read through the comments and make sure you have the latest firmware installed before posting any reports.

For any Firmware upgrades related issues: errors, problems, connections, etc, please go to this thread instead:
https://www.muffwiggler.com/forum/viewtopic.php?p=1689582#1689582

With these 2 threads we can separate any issues that may arise from these processes.


RELATED LINKS (edited August 9th):
ADDAC System
Thought of also posting a list of what has been done in terms of corrections to the initial released firmware:

. Several minor details have been polished
. Greatly improved CV inputs detection
. Corrected all issues with gates in detection
. Corrected all issues with Trigger Repeat function
. Automatic CV input recognition on channels 2,3,4 now will only track Channel1 after 10seconds of 0v is received
. Added a button to disable the Channel1 control over other Channels
- This can be accessed from the "Trig.R." Menu (Button7)
- Toggling button 2 on/off: On (track Ch1), Off (no tracking)
meatbeatz
Going by the log above, if the most recent update address the triggering and channel interaction issues I will be one happy chap. I have a show coming up and I'd be stoked to be rocking the 207! Thanks for taking the time to look at this.
Hirsbro
with the latest firmware (I believe?) this: ADDAC207_FIRMWARE_HEX_J3.hex
I am getting some timing issues, sound almost like shuffle some times


this is "bypass" straight from the trigger source (trigger riot) straight to the env



both wave files have been moved in order to make the first note start at the same point
__ag
Hello,
Thanks for the report, will look into it in the next days!
all the very best
andre
__ag
Hello all,

Just updated the Firmware to version J_5, this will correct the timing issues reported by Hirsbro.

The reaction time between gate in and output is now about 1 millisecond.

all the very best
andre
Paranormal Patroler
That's great news Andre. Looking forward to checking it out! Will this also fix the multiple triggers issue?
Hirsbro
__ag wrote:
Hello all,

Just updated the Firmware to version J_5, this will correct the timing issues reported by Hirsbro.

The reaction time between gate in and output is now about 1 millisecond.

all the very best
andre


thumbs up
meatbeatz
Hirsbro, I haven't had a chance to upgrade yet but can you tell me whether triggering s&h style with CV's (LFO's for example) on multiple channels is working without interaction between channels?
__ag
Hello,

I read through the last comments in the other thread and made a new update (J_6) to save the CH234 slave to 1 setting in overall memory, so now it should keep your pre-defined setting after startup.

And yes with this new setting channels 234 will never be listening to channel one!

all the very best
andre
Fastus
Is there any chance there will be a definitive, fully tested update rather than these ad hoc releases? I was going to pickup my unit from Control last Saturday after they installed the j_3 release, but then there was a j_5 update. Now there's a j_6.

Kind of makes it difficult to know when the unit really is ready to go...
Paranormal Patroler
__ag wrote:
And yes with this new setting channels 234 will never be listening to channel one!


But we still get the chord production working, right? I mean when nothing is plugged on inputs 2,3,4.
Hirsbro
Fastus wrote:
Is there any chance there will be a definitive, fully tested update rather than these ad hoc releases? I was going to pickup my unit from Control last Saturday after they installed the j_3 release, but then there was a j_5 update. Now there's a j_6.

Kind of makes it difficult to know when the unit really is ready to go...


I suppose there will be at some point, when ppl seas to report issues, I'm happy to help getting there if I can, testing the new firmware releases, (when I got the time confused )
Hirsbro
meatbeatz wrote:
Hirsbro, I haven't had a chance to upgrade yet but can you tell me whether triggering s&h style with CV's (LFO's for example) on multiple channels is working without interaction between channels?


Will test this, I do not have a s/h option atm but I suppose I can use mt Z8000 and/or a-149.. will report back
Refund
the updating process is pretty painless once you've got the serial adapter
Hirsbro
Made a test of the j_6 firmware today
Had all 4 quantizers going each with different clocks (1/1, 1/2, 1/3 and 1/4)
Ant tbh its been the best performances so far I could not spot any interactions between channels and did not notice timing issues (well my ear did not so did not test further)
BUT when each channel had rested for some time strange things started to happen, seems like its become far more sensitive to voltage changes or something because all the channels started to fire of gates randomly as the video show.
That said it was by far the best and virtually perfect performances form the 207
flo
So probably you had it rest for more than the specified 10 seconds?

Anyways, this is great news! Will look into buying one of these bad boys soon hihi
Hirsbro
flo wrote:
So probably you had it rest for more than the specified 10 seconds?

Anyways, this is great news! Will look into buying one of these bad boys soon hihi


Yes that's my theory, it was still registering voltage changes it seems, even from the precision adder without any attenuation, perhaps its a good thing I dunno suppose I could increase the idle time, sometimes you need all or some of the channels to be quiet for much longer than 10 sec
Fastus
Refund wrote:
the updating process is pretty painless once you've got the serial adapter


OK - so I have to buy an FTDI board so I can be an unpaid beta tester for an expensive & complex module. Whole point of modular for me was to get away from this computer/software BS... very frustrating
meatbeatz
Hirsbro wrote:
meatbeatz wrote:
Hirsbro, I haven't had a chance to upgrade yet but can you tell me whether triggering s&h style with CV's (LFO's for example) on multiple channels is working without interaction between channels?


Will test this, I do not have a s/h option atm but I suppose I can use mt Z8000 and/or a-149.. will report back


By S&H I mean feeding each CV input a different CV source then trigger each of the 4 gate inputs with a different clock source (div/mult or euclidian etc.) That way the quantizer will sample each incoming voltage upon receipt of a trigger pulse and at that moment quantize the voltage to the nearest note in the selected scale. So in essence you are S&Hing incoming voltages (except the output voltage is quantized). This is how I use my A-156 most the time.
Refund
Fastus wrote:
Refund wrote:
the updating process is pretty painless once you've got the serial adapter


OK - so I have to buy an FTDI board so I can be an unpaid beta tester for an expensive & complex module.


I feel your pain, If this wasn't such a richly featured module that no other quantizer comes close to, I probably would have just returned it myself.

the FTDI adapter costed me about $20, the postage to send it back to addac from australia probably would have cost about that, but this way *I* have control over the module maintenance, and can update it as further revisions and fixes come out.

For me, being able to do the process myself has alleviated about 99% of the fears I have about this module glitching out on me in particular useage cases, since now I can do something about it.

edit: just for the benefit of any other australians out there, I got this adapter from jaycar and it worked just fine, also I had to google to find drivers for it.

http://www.jaycar.com.au/productView.asp?ID=XC4241
ben_hex
Are you offering the option to return units for firmware upgrades?
NS4W
Beware that the related links section above is not reflecting the latest firmware! Version J9 can be accessed here: https://www.muffwiggler.com/forum/viewtopic.php?p=1830712#1830712

(Kinda messy with all these different threads and pieces of information scattered all over the place)
overjoid
Hello - I love my ADDAC case and these quantizers. I did the J9 update, but there is still an accidental gatemode switching that can occur after 60 seconds.

__ag wrote:
Hello,

I read through the last comments and made a new update (J_6) to save the CH234 slave to 1 setting in overall memory, so now it should keep your pre-defined setting after startup.

So with that setting off channels 234 will never be listening to channel one, with this long intervals between gates will not be a problem.

all the very best
andre


From the manual (last updated July 2013):

"This Gate in ON/OFF detection is made in software.
After the detection goes On, and if the user removes
the gate in jack it will automatically goes to Off after
60 seconds. If the user want to reset voices before the
60 seconds period Button 6 (Gate L) can be pressed at
the same time as the voice number button (1 to 4).
For example to Reset voice 2 Gate In, the user needs to
press button 2 and 6 at the same time.
This will resume the behavior without regarding the
Gate In until a new jack is plugged in."
______________________________________________________________________ ______________________________________

OK ---- So, the interval creation and gate detection are different things.

As of the current OS, the "CH234 slave to 1 setting" has only taken care of the accidental mode switching that happens when sending 0V CV to "in" 2, 3, or 4.
The "no-gate-in-patched"-detection is still on a 60 second timer, so "gate detection" issues have not been resolved for anyone who wants their input gates to be spaced wider than 60 seconds.

I did a simple test:
Medium slow LFO into CV "in" (set the speed so you can kind of see it moving up and down on the quantizers LEDs);
make a single trigger pulse happen into "gate in" (start a stopwatch now if you'd like);
This trigger switches the quantizer into triggered operation and stops the quantizing of every step of the lfo and holds the value from the triggered moment;
now wait. . . . . . . . . at 60 seconds the quantizer "goes crazy" (switches back to untriggered mode of operation) . . . .
it stops thinking that I have a cable plugged into "gate in", but the cable is still plugged in.

Doesn't work for slow music (you won't make it past the 15th bar at 60bpm); I think it's why random outputs are sometimes happening for some people; this situation can definitely interrupt any nice long drone note.

It would be very very helpful to have another "Trig.R." Menu item to declare "I will be using gates", or "auto detect" (which already works for "I won't be using gates").

please,
thank you,
all the very best,
Roy
freq_divider
Just did the firmware update K 3 via windows using the update kit that's available now on the ADDAC website. The very modestly priced kit got shipped in no time at all, updating was smooth, everything fine, thanx Andre!
anosou
I don't know if I'm just stupid or something's wrong... I just got the ADDAC207, straight from ADDAC. E-mailed beforehand to ask if the units have the latest firmware (they did!) and if there still were a lot of known bugs (there wasn't!).

I just got it, plugged it in, started following the manual. Connect the oscillators, tune them, go to keyboard mode, play—all fine.

And then the punchline: I try putting some CV in the IN. Nothing happens. I try 9 different other CV sources. Nothing happens. I try different IN/OUT combos, using Gate IN and everything else I can think of but ADDAC207 does not care about incoming voltages.

Keyboard mode still works fine, the module seems fully functional with all menus working and so on but it simply does not quantize the input at all. I have no idea what to do. Anyone know of typical pitfalls or secret settings where this could happen? Anyone had a similar problem..?
ben_hex
Try putting a fast gate pattern into the right hand gate input and your CV into the left and gate input anosou. See if that way you can get it to quantise. Bear in mind that's a period of time after having a gate signal plugged in where it WILL NOT quantise anything as it's waiting on a gate still. I think this is 30-60 seconds off the top of my head.
anosou
ben_hex wrote:
Try putting a fast gate pattern into the right hand gate input and your CV into the left and gate input anosou. See if that way you can get it to quantise. Bear in mind that's a period of time after having a gate signal plugged in where it WILL NOT quantise anything as it's waiting on a gate still. I think this is 30-60 seconds off the top of my head.


Yeah, I read about the wait time. And also Andre responded to my e-mail (in record time I might add, very impressed!) so we're checking it out now. It seems like a freak occurence as everyone I know with ADDAC207 from the new batch are super happy with it. smile
ben_hex
ah ok, hopefully just an odd occurrence sorted soon. I really like my 207 and it's my main quantiser (only one I use really) for everything.
anosou
ben_hex wrote:
ah ok, hopefully just an odd occurrence sorted soon. I really like my 207 and it's my main quantiser (only one I use really) for everything.


Found it! One of the male connectors between boards had slipped out of the connection when mounting. A quick screwing off the board and re-aligning sorted it out.

Andre was enormously helpful, and fast. Gave me good step-by-step things to check and offered to send a new one right away if this didn't solve it. Great customer service!
ben_hex
Nice! smile
Hirsbro
ADDAC System wrote:
Dear all,
Hope everyone is well.

Following up the 207 threads we decided to create 2 threads for these matters!

This thread will be used to Report issues with the latest Firmware released.
In order to avoid already known issues, please read through the comments and make sure you have the latest firmware installed before posting any reports.


For any Firmware upgrades related issues: errors, problems, connections, etc.
Please check this thread instead:
https://www.muffwiggler.com/forum/viewtopic.php?p=1689582#1689582

With these 2 threads we can separate any issues that may arise from these processes.


RELATED LINKS (edited October 27th):

Here's the direct link for our Firmware Upgrade Guide:
http://addacsystem.com/firmwares/ADDAC207_FirmwareGuide.pdf

Here's the direct link to our latest Firmware .hex file for Windows users (vs: J6 ) - last update October 27th:
http://addacsystem.com/firmwares/ADDAC207_FIRMWARE_HEX.zip

Here's the direct link to our Firmware Upgrade OSX App (vs: J6) - last update October 27th:
http://addacsystem.com/firmwares/ADDAC207_FIRMWARE.zip


all the very best
andre


Dead links... please update
Hirsbro


Anyone know where I can get a link for that firmware? there is only a link for the firmware upgrade guide not the firmware itself
cry

http://addacsystem.com/product/addac200-series/addac207
lohacker
Hirsbro wrote:


Anyone know where I can get a link for that firmware? there is only a link for the firmware upgrade guide not the firmware itself
cry

http://addacsystem.com/product/addac200-series/addac207


http://media.addacsystem.com/firmwares/ADDAC207_FIRMWARE_OSX.zip
lohacker
double
Hirsbro
lohacker wrote:
Hirsbro wrote:


Anyone know where I can get a link for that firmware? there is only a link for the firmware upgrade guide not the firmware itself
cry

http://addacsystem.com/product/addac200-series/addac207


http://media.addacsystem.com/firmwares/ADDAC207_FIRMWARE_OSX.zip


Chugging Beers

I see it was missing the "media" paret
ADDAC System
Updated the first post so that it has the "media" part. Thanks for pointing it out!
h1d3m3
So, after reading about all of the problems / resolutions / upgrading / complaining and complimenting on various threads, what is the general verdict on this module? I'm on the fence between an O&C and this and it seems to me that:

ADDAC207
+ More musical, immediate, less menus
+ Has become more stable (?)
+ Microtonal
- More expensive
- History of Gliches
- Need to buy updater hardware

O&C
+ Independent scales per output
+ Cheaper
+ Tons of other functions
- Menus (I do dislike menus)

Any other opinions or points worth noting? I'd like to be off the fence
seriously, i just don't get it

EDIT : Holy crap, great quantizer reference : https://docs.google.com/spreadsheets/d/1yicqvGRRJMIAFFNAcgZb9jM9_Y94KP uKuFmQIJ3AbSg/edit#gid=0
SlyFrank
h1d3m3 wrote:
So, after reading about all of the problems / resolutions / upgrading / complaining and complimenting on various threads, what is the general verdict on this module? I'm on the fence between an O&C and this and it seems to me that:

ADDAC207
+ More musical, immediate, less menus
+ Has become more stable (?)
+ Microtonal
- More expensive
- History of Gliches
- Need to buy updater hardware

O&C
+ Independent scales per output
+ Cheaper
+ Tons of other functions
- Menus (I do dislike menus)

Any other opinions or points worth noting? I'd like to be off the fence


I own both and you've summed it up pretty well. They're both fantastic modules. Two things I'd like to add to your list:

1) the 207 does not glitch at all so long as gate ins are used. And to correct an earlier post by me saying that the transpose in on the 207 was very fiddly, I was doing that with no gate ins. Again, if you use gate ins, there is absolutely no issue with glitching.

2) You mention the 207 as being microtonal, and that is true - it has a few preset microtonal scales, including La Monte Young's scale. But if microtonality is important to you, the O&C is amazing. It comes with tons of preset microtonal scales, and since I'm really into microtonality I added about 20 more scales of my own to the code. You have to recompile the code if you add your own, but you can put in any scale you want, if it's not already in there.

Not advocating one over the other - they are different beasts, with different UIs and capabilities/functions.
anosou
h1d3m3 wrote:
So, after reading about all of the problems / resolutions / upgrading / complaining and complimenting on various threads, what is the general verdict on this module? I'm on the fence between an O&C and this and it seems to me that:

ADDAC207
+ More musical, immediate, less menus
+ Has become more stable (?)
+ Microtonal
- More expensive
- History of Gliches
- Need to buy updater hardware

O&C
+ Independent scales per output
+ Cheaper
+ Tons of other functions
- Menus (I do dislike menus)

Any other opinions or points worth noting? I'd like to be off the fence
seriously, i just don't get it

EDIT : Holy crap, great quantizer reference : https://docs.google.com/spreadsheets/d/1yicqvGRRJMIAFFNAcgZb9jM9_Y94KP uKuFmQIJ3AbSg/edit#gid=0


If you buy direct from ADDAC (which I recommend highly!) you can simply ask them to make sure the latest firmware is installed.

I find O&C incredibly annoying to use and ended up selling mine. If you always have one setting (one scale, one type of quantizing) then I guess you can set and forget but the menu diving is not very nice. One upside is the trigger delay on the O&C which can help make up for latency from digital modules sending triggers.

I find the keyboard buttons invaluable on the 207, makes quickly altering a scale live a breeze. I've not experienced any major glitches and what I posted previously in this thread was due to a miss in assembling that was easily fixed and compensated for.

The only thing I've noticed recently is that sometimes ADDAC207 is a bit trigger happy with the note changes and the gate in doesn't always lock quantizing to only when there's a trigger. I haven't sat down to properly investigate when/why this happens and it mostly doesn't. I think it's a case of my gates not being recognized, maybe they're too weak or similar, but I'm pretty sure it's user error. smile
SlyFrank
anosou wrote:
The only thing I've noticed recently is that sometimes ADDAC207 is a bit trigger happy with the note changes and the gate in doesn't always lock quantizing to only when there's a trigger. I haven't sat down to properly investigate when/why this happens and it mostly doesn't. I think it's a case of my gates not being recognized, maybe they're too weak or similar, but I'm pretty sure it's user error. smile


I experienced a bit of this a while back. I fixed it by making sure that my gates were long enough. If the gate is too short, it will fall to 0V before the note is over, and the glitching can kick in. Not sure if that's the issue you're experiencing, but I manually adjust my gate lengths to taste and all is good. w00t
anosou
SlyFrank wrote:
anosou wrote:
The only thing I've noticed recently is that sometimes ADDAC207 is a bit trigger happy with the note changes and the gate in doesn't always lock quantizing to only when there's a trigger. I haven't sat down to properly investigate when/why this happens and it mostly doesn't. I think it's a case of my gates not being recognized, maybe they're too weak or similar, but I'm pretty sure it's user error. smile


I experienced a bit of this a while back. I fixed it by making sure that my gates were long enough. If the gate is too short, it will fall to 0V before the note is over, and the glitching can kick in. Not sure if that's the issue you're experiencing, but I manually adjust my gate lengths to taste and all is good. w00t


That's probably it! I mostly sent short triggers and didn't change ADDAC's internal gate length setting—neat feature by the way.
SlyFrank
anosou wrote:
That's probably it! I mostly sent short triggers and didn't change ADDAC's internal gate length setting—neat feature by the way.


Ah yes, I forgot about that internal gate length setting, despite having read about it in the manual. Very useful! Although in my case, I'll probably continue to run my gate source(s) through my QCD + Exp, which allows instant fine-tuning of the gate lengths with a knob. But, yeah, that setting could be very useful too/instead of. Cheers Guinness ftw!
h1d3m3
Thanks for the comments. I'm probably going to pull the trigger...Was hoping someone who has been through this update process before can confirm these are the necessary tools to order:

Maybe one of these boards?

https://www.amazon.com/XCSOURCE-FT232RL-Adapter-Arduino-TE203/dp/B00HS X3CXE

or

https://www.amazon.com/FT232RL-Serial-Converter-Adapter-Arduino/dp/B06 XDH2VK9

and then the cables:

https://www.amazon.com/dp/B00PBZMN7C?psc=1

But I'm not sure what this is (and if I even need it): 0.1uF Capacitor
The manual says "If you have no Capacitor you can still complete the update process.", so maybe I don't need it?

Thanks.
SlyFrank
Both of those look correct to me, but I can't say for sure. All I can say for certain is that this is what I ordered from Amazon and it works perfectly:

https://www.amazon.com/gp/product/B00TNI2MQ0/ref=oh_aui_detailpage_o06 _s00?ie=UTF8&psc=1

And same goes for the wires - these are the ones I ordered from Amazon, and they work perfectly:

https://www.amazon.com/gp/product/B00RMB91J6/ref=oh_aui_detailpage_o06 _s00?ie=UTF8&psc=1

As for the capacitor, I started the upgrades before the capacitor option was available, so I'm used to not using it. And I still prefer not to use it, but on paper it is easier to use it. Here's the deal - if you use the capacitor you don't have to _time_ when you start the upgrade process and when you turn on the 207 - the 207 has to be turned on about 1 second after you hit upgrade (or vice versa, can't remember off the top of my head, but it's outlined in the docs). Some people had issues with that, but I never did. And if you do, just try again. But it's up to you, either way will work.

In the end it's really easy. I never had a problem, and I'm no expert in these things. Also, the last update to the 207 was just last July. I kinda doubt there will be any more since it works just fine as it is now, so if there are updates in the future you can always wait if/until then to order the upgrade stuff. As mentioned, if you order direct from ADDAC, and ask for the latest July 2017 firmware, you're good-to-go.

Cheers Guinness ftw!
flo
You guys are aware that Addac is selling a kit now for the updates? That should be a safe option.

http://addacsystem.com/product/addac-accessories/addac0016

You only need a USB Mini-B cable.

Otherwise, yes, order directly from them and tell them to make sure that the latest firmware is installed.

Cheers Guinness ftw!
h1d3m3
flo wrote:
You guys are aware that Addac is selling a kit now for the updates? That should be a safe option.

http://addacsystem.com/product/addac-accessories/addac0016

You only need a USB Mini-B cable.

Otherwise, yes, order directly from them and tell them to make sure that the latest firmware is installed.

Cheers Guinness ftw!


Normally, yes that would be the best option...but...

Unfortunately, in my experience anyway, it takes around 3+ weeks to get anything to the US directly from ADDAC. I ordered my beloved 802 and it got held up somewhere at US customs for like 4 or 5 days. The amazon order will take 2 days for roughly the same price.

Also, considering an early rev module on BS/T so it likely has not been updated.
Paranormal Patroler
SlyFrank wrote:
As mentioned, if you order direct from ADDAC, and ask for the latest July 2017 firmware, you're good-to-go.


As far as I know all 207s directly from ADDAC have the latest firmware. I would assume the same goes if you buy through a retailer, don't they update the modules they have? hmmm..... I never thought of this before.

In any case, update process for the 207 is easy.
MUFF WIGGLER Forum Index -> ADDAC System  
Page 1 of 2
Powered by phpBB © phpBB Group