News:

SMF - Just Installed!

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - paulsoulsby

#106
Hi,
Yes, just select pattern 0 in the sequencer (white mode).  That will stop the sequencer allowing you to play MIDI via USB. 
If you don't have a MIDI-hacked Arduino, you will need to hack it. Tutorial here:  http://soulsbysynths.com/tutorials/
Paul
#107
miniAtmegatron / Re: Incompatible Uno ??
June 07, 2016, 12:00:24 AM
Ah -but quite often the Atmega328P will actually be a clone, even though it looks totally genuine.  I've found this with quite a few cloned boards. If the software doesn't upload every time or the upload bombs out half way through, this can be because of a cloned Atmega.  Always worth having a genuine Uno at hand, to test for problems like this.
#108
Well I guess it's a matter of opinion, but I'd say:
Odytron for round warm basses
Atmegatron for brighter tougher basses
Atcyclotron for dub steppy super-bright glitchy basses

Be sure to have the bass boost up for bass lines.
#109
Atmegatron / Re: Factory patches
May 17, 2016, 09:33:50 AM
That new version of Easy Uploader with patch load/save is now on download page BTW.
#110
Fault report / Re: easy upload props
May 16, 2016, 05:04:40 PM
Ah this seems to be a browser related issue.  Not all of them understand the HTML5 code to force download.

Right click and download.  If it saves as a text file, rather than a hex file, take a look at this thread:  http://forums.soulsbysynths.com/index.php?topic=104.0
#111
miniAtmegatron / Re: Incompatible Uno ??
May 16, 2016, 04:45:29 PM
Thanks for the info.  That's very strange, considering the filter is digital and all processed within the Atmega.  My only explanation is that they haven't accurately cloned the ADC on the Atmega328P.  They've cloned enough of the parameters for the standard Arduino analog read to work, but not everything.  The Atmegatron libraries don't use Analog read and they scan the pots at a faster rate. 

Interesting to know that you've had this issue though.  I'll look out for this when I'm testing cloned Unos.

Paul
#112
Open finder window
Finder->Preferences...
Advanced tab
check Show all file name extensions
Change .txt or .text to .hex

that should be it! Paul
#113
Ah I think it may be an issue that has happened to someone else too.  Has the file saved as a text file rather than a .hex file?  If it has, you need to manually convert it's type to a hex file.  Are you using a Mac?
#114
Lookup tables are in MinEngineProgmem.h which is in the MinEngine Folder.
thanks, Paul
#115
Atmegatron / Re: Factory patches
April 12, 2016, 09:30:10 PM
I have tested 2.1 and it works fine.  Obviously you need to press more than one note for it to play an arpeggio!!  This can't be done with the test knob alone, you need to connect a MIDI keyboard.

Librarian is note compatible with Odytron.  There will be a system for loading and saving patches via the Easy Uploader in the near future.
#116
Atmegatron / Re: Factory patches
April 12, 2016, 03:23:02 PM
Hi,
I've just tried this and I can recreate the issue here.  The problem is to do with v2.4 libraries, not the Easy Uploader.  I had to make a few changes to the Arpeggiator library when I create Strings.  I think these changes have affected the main Atmegatron software.
I'll rectify this problem with the next update.
I'll also start to upload older software versions to the Downloads page, so that users have the option to use old versions until I have fixed the problem.
cheers
Paul
#117
Atmegatron / Re: Factory patches
April 12, 2016, 01:57:39 AM
Hi,

I've just added the Atmegatron factory presets .mem file on downloads page: http://soulsbysynths.com/wp-content/uploads/2016/04/FactoryPresets.mem

  • Can I confirm that you are using V2-0 of Librarian.
  • Make sure you have Atmegatron software loaded.  This is for Atmegatron only - not Odytron.
  • Don't forget to turn on Sysex Read mode (see quick ref card - press Amp Env Decay, so that it's green).
If this all fails, I'll send you a beta version of Easy Uploader and we'll upload the Factory Presets using that. 

We'll get the factory presets on there somehow!

Paul
#118
The waveforms aren't a 1 to 1 match with the Atmegatron.  They use the lookup table to pick a selection from bank a and b.  So via the lookup table the waves are:
0 = Pure Square
1 = Pure Saw
2 = Pure Sine
3 = Octave Square (Juno 60)
4 = Square Fifths
5 = Pulse Wave (RP2A07)
6 = Warped Sine
7 = Bass (Multivox)
8 = Metal 1
9 = Metal 2
10 = Vocal 1
11 = Brass (multivox)
12 = Reed organ (PPG)
13 = Bell (PPG)
14 = Chord
15 = Noise
#119
Atmegatron / Re: Factory patches
April 11, 2016, 10:33:09 PM
The original idea was to use the Atmegatron Librarian, but there's major issues with the OSX version (due to Java + Sysex not working).  If you've got a PC, that is available on the downloads page. It's also only for Atmegatron, not any other software verisons (e.g. Odytron).
So as an alternative I'm actually working on a new version of Easy Uploader that will allow you to load and save patches! Should be available in a couple of weeks.  Let me know if you'd like to beta test it.
Paul
#120
So the key bit of code is this:
All settings are selected from the main Atmegatron code.  If you download the manual from the Atmegatron Downloads page (not mini page) you can see a lot of the parameters at the back.

Filters are identical to the full Atmegatron (ie in manual).
LFO shapes and speeds are identical to the full Atmegatron (ie in manual).

Waveforms are selected via these tables:
static const unsigned char OSC_PRESET_TABLE[16] PROGMEM = { 0, 4, 9, 1, 2, 3,11,14, 0, 1, 4, 7, 8,12,13,15}; 
static const unsigned char OSC_PRESET_BANK[16] PROGMEM =  { 0, 0, 0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 1, 1, 0};

E.g. waveform 0 on the mini is Bank 0 (red) wave 0 (ie square).
waveform 15 on the mini is Bank 0 (red) wave 15 (ie noise)

Envelope presets are derived from these tables:

static const unsigned char ENV_A_PRESET[16] PROGMEM =  {0, 0, 0, 0, 0, 0, 0, 0, 3, 3, 5, 7, 7, 7,11,15};
static const unsigned char ENV_DR_PRESET[16] PROGMEM = {0, 3, 5, 5, 7, 7,11,11, 0, 5, 7, 0, 3, 7, 7,15};
static const unsigned char ENV_S_PRESET[16] PROGMEM =  {15,0, 0,15, 0, 7, 0,15, 0, 0, 0, 0, 0, 7, 7, 0};


E.g. envelope 0 is Attack = 0, Decay/release = 0, sustain = 15 (full)
envelope 15 is Attack = 15, Decay/release = 15, sustain = 0
Both envelopes use the same lookup tables.

Wavecrusher/Portamento is split into 8 wavecrusher presets (of increasing severity), followed by 8 portamento presets (of increasing time).  You can't have both at the same time.

Think that's everything!