Messages

31

miniAtmegatron / Re: Is Miniatmegatron open source?

« on: December 28, 2017, 01:26:36 PM »

Wow I didn't even know about that setting - that's bonkers!  I've located it and updated it to a luxurious 1Mb per pic!

Nice PCB - that's got me think about the possibility of an expander board that allows CV control over the parameters. I'd be tempted to put the Arduino serial pins (digital 0 and 1) on a 2 pin header that can be added as an option. This would then allow an expander unit to be connected which would provide more modular friendly inputs.  Use the 6 analogue inputs for CV and some of the free digital inputs for gates.  Then convert them to MIDI CCs which is transmitted over serial to the Euro-Mini.

I might even be tempted to develop that next year if there was a demand for Eurorack miniAtmegatrons! Def worth sticking 2 pads on the PCB for pins 0 and 1 (on a standard 2.54mm 2-way header).

Anyway, just a thought!
Paul

32

miniAtmegatron / Re: Is Miniatmegatron open source?

« on: December 07, 2017, 06:20:39 PM »

Yes, that's work in-progress.  Still trying to find a way to publish it properly.  Also, I think there's possibly too many diagrams, it makes it look more complex than it is!
Start with the Min class.  That contains a hardware class and engine class. The hardware class handles the electronics, the engine is the processing for the generating audio.  Both of those classes generate events.  The job of the Min class is to pass events between the hardware and engine class.  The idea is that the hardware and engine can be totally independent, so you can port different audio engines to different hardware interfaces really easily.
R.e. your customisations.
a)  Yes totally possible. Even can use a Sparkfun MIDI shield (don't connect the buttons or pots though)
b)  You'll need to remove pots on A4 & A5 as they use the I2C bus.  Then add an external I2C ADC chip.  If you look at the code for the Oscitron Hardware, you'll see how to do this with a Microchip MCP3208 ADC.  So 8 of the pots will come off the MCP3208 and 4 off the Atmega328.  That frees up A4 & A5 to use for the I2C to drive the ADC.
c)  See above.  Just free up A4 & A5 and use the I2C bus.  Then adding an I2C screen at a later date is easy too!

Hope this helps as a starting point!

33

Atmegatron / Re: Any more Atmegatrons?

« on: December 05, 2017, 01:53:49 PM »

If you haven't already, join the mailing list for info on a very small number of Atmegatrons which will be available in a couple of weeks.  Info will only be available on the mailing list: http://eepurl.com/FQIYL
After they've gone, it's eBay only!!  There'll be more info on the new range of Atmegatrons in the new year. Aiming for launch at Superbooth.

34

miniAtmegatron / Re: Is Miniatmegatron open source?

« on: December 03, 2017, 11:13:27 PM »

Hi - I'll do a little chart showing how the classes all interact with each other.  It's pretty easy once you know this.  The .ino file is just a holder for uploading the project.  All the work is done in the classes now.   Will hopefully add the diagram tomorrow.

35

Software announcement / Libraries v2.9 released + other updates

« on: December 02, 2017, 05:14:13 PM »

Here's the other updates:
* Libraries v2.9 is released and on Github: https://github.com/soulsbysynths/libraries This is for Arduino 1.8.5 (and Atmel 7 + Visual Micro should you desire!)
* miniAtmegatron and miniOdytron now have CC 7 for volume added to latest version
* miniAtmegatron and miniOdytron now have separate versions for issue 2 and 3 kits.  Unfortunately the issue 3 kits have different LED pinouts which require different software. You can see your issue number below the value inc button on the pCB

36

Software announcement / Strings v1.3 released!

« on: December 02, 2017, 05:05:27 PM »

Strings v1.3 has all parameters controllable via MIDI CCs:
1: LFO modulation depth
16: Phaser LFO waveform
18: Arpeggiator pattern
19: Arpeggiator clock division
20: Waveform 1
21: Waveform 2
22: Waveform 3
23: Waveform 4
24: Pitch envelope depth
25: Phaser source mix
38: Gate on/off
39: Pitch LFO invert
40: Arpeggiator ping pong
41: Phaser LFO invert
42: Tie waveforms on/off
43: Waveform cycler on/off
72: Env Release
73: Env Attack
75: Env Decay
78: Pitch LFO waveform
79: Pitch LFO clock division
80: Env Sustain
81: Phaser LFO clock division
82: Sine Phaser frequency
82: Cycler clock division
94: Osc detune
95: Phaser depth
123: All notes off

37

Software announcement / Odytron v1.3 released

« on: December 02, 2017, 04:51:50 PM »

All parameters are now controllable via MIDI CCs.  Here's the list:
1: FMA for Osc 1 & 2 (for vibrato effect)
5: Portamento
16: Filter mod B amount
17: Filter mod B source
20: Osc 1 mod A amount
21: Osc 1 mod B amount
22: Osc 2 mod A amount
23: Osc 2 mod B amount
24: Noise/Ring mod level
25: Osc 1 level
26: Osc 2 level
30: Noise / Ring mod source
31: Oscillator 1 source
32: Oscillator 2 source
33: Filter type
34: Osc 1 mod A source
35: Osc 1 mod B source
36: Osc 2 mod A source
37: Osc 2 mod B source
40: Keyboard tracking on/off
41: DCA source
71: Filter resonance
72: ADSR env R
73: ADSR env A
74: Filter cutoff
75: ADSR env D
77: Filter mod A amount
78: Filter mod A source
79: LFO frequency
80: ADSR env S
81: AR env A
82: AR env R
91: Pulse width
92: PWM amount
93: Osc 1 frequency
94: Osc 2 frequenct
95: HPF cutoff
123: All notes off

38

miniAtmegatron / Re: Is Miniatmegatron open source?

« on: November 25, 2017, 04:35:37 PM »

and pots turn clockwise! So fully clockwise will be read as 255 and fully anticlockwise is 0.

39

miniAtmegatron / Re: Is Miniatmegatron open source?

« on: November 25, 2017, 04:33:46 PM »

Hi yes all code  is open source and on github: https://github.com/soulsbysynths
However someone has just alerted me that there is an issue with latest mini libraries.  If you download v2.6 you'll be OK.  Will hope to have working libraries up to date by next week.
thanks
Paul

40

Odytron / Re: Odytron updates

« on: November 09, 2017, 03:25:30 PM »

Yes - will hopefully get the Odytron and Strings done this month.  The others will have to wait a bit as they need converting to the C++ classes.  Should have an Atmegadrum II ready by end of year though.

41

Software announcement / Atmegatron v2.5 released

« on: October 31, 2017, 02:15:57 AM »

V2.5 is released!  It's available here: http://soulsbysynths.com/wp-content/uploads/2017/10/AtmegatronV2-5.hex

new features are:

* Global settings reorganised. Function dial still does MIDI channel. Value dial does multiple on/off parameters. These currently are:
0 = Enable MIDI thru
1 = Enable MIDI program change
Red knob = parameter on
Yellow knob = parameter off

To access the global settings, power the Atmegatron on while holding down the function knob.  Cycle power to leave global settings

* The test button works again with Arpeggiator patches

* Fixed a couple of warnings when compiling in the Arduino IDE

* Add MIDI CCs for all parameters.  These are:
1   Pitch LFO (small range)
5   Portamento
16 Filter env amount
17 Distortion amount
18 Arpeggio type
19 Arpeggio clock div
20 Wave crush preset
32 Waveform
33 Filter Type
37 Filter normalise mode
38 Filter envelope invert
39 LFO invert
40 Arpeggiator PingPong
41 Proportional Portamento
42 Wavecrush pre-filter
71 Filter resonance
72 Amp envelope release
73 Amp envelope attack
74 Filter cutoff
75 Amp envelope decay
77 Pitch LFO (full range)
78 LFO shape
79 LFO clock div
80 Amp envelope sustain
81 Filter envelope attack
82 Filter envelope decay/release
83 Filter envelope sustain
91 PWM amount
92 Amplitude LFO
93 Filter LFO
94 Pitch envelope
95 Phaser amount
123 All notes off

42

Atmegatron/Odytron Hardware technical support / Re: MIDI Program Changes (changing patch via MIDI)

« on: October 12, 2017, 09:22:00 PM »

Thanks very much for doing this!  I'll add this as a setting for the next software update.

43

Everything else / Re: Feature Requests

« on: October 12, 2017, 09:20:53 PM »

1) yes - I have been wondering about this for a while. A knock-on issue will be Easy Uploader.  I'd need to reserve more of the EEPROM for storing extra universal settings. That can be done though.  If I put MIDI program change in, it'd def be via a setting that can be enabled/disabled. I hate MIDI program change - the number of awesome synth sounds I've lost because of it!!

2) Ah that'd require an external flash chip.  Thinking of doing something like this via a flash card for the next Atmegatron.  Sadly not possible for the first one. Nearly all software versions use up the entire 32kB!

3) Def yes for the next atmegatron. Had a few requests for this!

44

Software technical support / Re: Compiling Sources - Arduino IDE

« on: October 12, 2017, 09:15:52 PM »

a) Neither of those warnings will cause you issues. Although technically the first one is a bug - should be

Code: [Select]

#if EXP_ENVELOPES==1 . But the result is the same, so won't cause you issues.

b) Definitely *.ino.standard.hex  .  Are you building the project with Arduino IDE and then uploading with Easy Uploader?  Obviously for easy debugging, it's fine to upload with Arduino IDE.

c) I compile using Atmel Studio + Visual Micro.  The compiler settings may be different with Arduino IDE.  This would explain  differences in size. I'd be tempted to use Atmel Studio if you want to do major hacking to the code - it's a lot friendlier!

d) Ah yes I'd forgotten about this.  It's a knock-on effect when I fixed one problem, I created another!!  It's going to take a bit of tracking to find out exactly what happened.  It looks like it should work from browsing the code.  So I'll have to put some time aside to sort it out.  At the moment I can't even tell you where the bug is.  It's either in

Code: [Select]

void AtmEngine::midiNoteOnReceived(unsigned char note, unsigned char velocity)  or possibly in the Arpeggiator class itself.

45

Atmegatron Librarian / Re: Atmegatron librarian CPU usage

« on: October 11, 2017, 12:23:59 PM »

Hmm - I'll investigate.  I haven't updated Librarian for a long time.  My suspicion is that they've changed the Java runtime and it's no longer compatible.  If it's just a case of recompiling it in Netbeans I'll do it.  If it requires a massive rewrite, I'd be tempted to do it in Qt. I've kinda given up on Java!