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.


Messages - paulsoulsby

Pages: [1] 2 3 ... 12
1
Atmegatron / Re: What about the Atpolytron
« on: July 13, 2017, 07:39:04 AM »
It turned into Strings.  It had some big bugs and needed such a major rewrite, that I decided to rename it. 

2
Software technical support / Re: Atmegadrum MIDI note nums
« on: May 22, 2017, 02:50:58 PM »
Excellent - glad you got it sorted.  Yes will hopefully get the Oscidrum ported back to the Atmegatron in the next few months.  Fewer drum sounds, but higher sample rate and longer samples, plus other added features.

3
Atmegatron / Re: ATmegadrum
« on: May 02, 2017, 11:16:53 AM »
Yes - eventually I'm gonna port the new Oscidrum back to the Atmegatron as Atmegadrum MkII.  It'll still be only 8 sounds of the Oscidrum, but using the higher sample rate, the new sound sets and the "per instrument" volume/pitch/length/delay. 

4
Odytron / Re: Odytron bulk export/import patches?
« on: May 01, 2017, 12:52:26 PM »
It'll be totally fine to do that. Won't harm it at all. The only thing you may find is that the synth resets itself when the computer resets or if you pull the usb in and out.

5
Odytron / Re: Odytron bulk export/import patches?
« on: April 30, 2017, 10:57:39 AM »
Hi,
You can save and load patches using the Easy Uploader (on the downloads page).  There's no sysex implementation for the Odytron software (or anything other than Atmegatron in fact).  The code for it eats up too much precious memory!
Was planning on phasing out the Librarian (especially as the OSX MIDI drivers don't support sysex), although I could potentially make it work with Easy Uploader instead of sysex....I'll have a think about that!

6
Software technical support / Re: Flashing from Linux
« on: April 22, 2017, 06:15:39 AM »
Yes, the 5V rail from the FTDI to the Atmegatron is cut.  I didn't fancy the USB cable trying to power all those LEDs!!  It might draw too much current from the USB.

AVRDUDE command line looks correct.  That's all Easy Uploader is doing via a graphical interface.

The EEPROM read and writes is harder.  The Atmegatron uses the Arduino Optiboot bootloader. This has no implementation for those AVRDUDE EEPROM commands to save space.  So the way that Easy Uploader does it is to:
  • Read a copy of the flash and save to a temp .hex
  • Write a serial->Eeprom .hex application
  • Receive the Eeprom data via serial and write to Eeprom
  • Write the original software from the temp .hex file back into flash
So quite a process!! 
I will look into compiling Easy Uploader for Linux once I'm back from Superbooth.

7
Software technical support / Re: Flashing from Linux
« on: April 19, 2017, 09:59:04 PM »
Ooh you're the first person to ask about Linux! Easy Uploader is written in Qt and I know that can create Linux executables.  I just don't have a Linux boot to install Qt onto to create the file. I'll look into it once I'm back from Superbooth.
Paul

8
Hi,
It's a problem with Safari.  It converts unknown file types to .txt.  You can fix this by either:
  • Select file
  • Command + I
  • goto File and Extension
  • uncheck Hide Extension
  • change StringsV1-2.hex.txt to StringsV1-2.hex and enter
  • click OK to change file type

or just download with a different browser.

9
Odytron / Re: glitchy response when sending MODULATION messages
« on: April 06, 2017, 11:26:24 AM »
Awesome - I'll add 1.2 to the downloads page and make it official!

10
Odytron / Re: glitchy response when sending MODULATION messages
« on: April 01, 2017, 11:10:51 PM »
ooh yeah - sorry been away but back now.  give me a day or so to double check that it all compiles and works on my machine and then I'll send you a .hex over.
Paul

11
miniAtmegatron / Re: Odytron for miniAtmeagtron
« on: March 27, 2017, 08:14:28 AM »
Hi,
Yes you can find the code that does that at the bottom of MinOdyEngine.cpp (v2.6). Just delete the following:

Code: [Select]
if(sequencer_->getStep()==15 && sequencer_->getPattern()!=0)
{
if(sequencer_->getPattern()==15)
{
patch_->setFunctionValue(FUNC_PATTERN,0);
}
else
{
patch_->setFunctionValue(FUNC_PATTERN,sequencer_->getPattern()+1);
}
}
I should have really wrapped that in the conditional if for Xmas code!

You'll need to use all the V2.6 libs together, replacing just one lib will probably not compile. Let me know if you still get any compile errors.

The pots control identical functions to the normal miniAtmegatron software apart from:  Distortion controls Osc 1 pitch offset and Phaser controls Osc 2 pitch offset.

The functions are also mapped to identical features in the Ody engine ( I think cyan only only controls portamento, as there is no wave crusher).

I'll definitely have the final version of Odytron for mini uploaded by the end of this month, with all the Xmas stuff removed and extra MIDI CCs added.

12
Odytron / Re: glitchy response when sending MODULATION messages
« on: March 21, 2017, 11:33:13 PM »
I've made some updates to the MIDI handling since the official version of the Odytron.  Would you like to try a new .hex file if I email it to you?  If it fixes the issue, I'll release it as a new version.

Alternatively, you can use Easy Uploader to save the patches, and let me know which one is causing the issues and I'll try and recreate the issue.

cheers
Paul

13
Oscitron / Re: pitch calibration question
« on: March 10, 2017, 06:15:43 PM »
Hi,
Did you check the voltage with a volt meter, or did you work it out via the CV.OCD manual?  It sounds like there's a discrepancy somewhere and the CV.OCD is an octave out.  Coarse = 9, should def produce 440Hz. 
Can I also check you're using a square or other basic wave on the Osci, not one of the waves with harmonics that can sound like it's an octave up.  Captured waves can also sound like they're an octave up (depending on settings and audio source).
It's not a disaster if it's an octave out anyway.  As you have done, you can use the coarse pitch to correct. It will mean the CV range is only 4 octaves rather than 5 though.

14
Oscitron / Re: pitch calibration question
« on: March 02, 2017, 11:45:32 PM »
Just added tutorial video: https://youtu.be/s6l-9iKFtDo

To confirm a Doepfer A-190-2 by default sets MIDI note 36 = C2 = 0V.  Therefore the notes required for calibration are 51 (Eb oct 3)  and 81 (A oct 5).

A Beat Step Pro requires the  0V MIDI Note setting (in Device Settings) to be set to C1.   

15
Oscitron / Re: pitch calibration question
« on: March 01, 2017, 10:14:05 AM »
Hi,
I think I am correct here and the manual is wrong  :-[  Just checked notes with MIDI Ox and it is def Oct 3 E flat and Oct 5 A natural when using a Doepfer A-190-2 (with default settings). Means I'll have to update the manual for next batch!  Basically with Coarse Pitch set to 9, A 4 on your keyboard should = 440Hz.  If not, then the keyboard is an octave out or MIDI to CV has different offset.  Only just discovering that there are numerous standards for MIDI to CV converter offsets!!

Just updated instructions.  I missed a little bit.  It's hold function and value knob, not just function knob.

 

Pages: [1] 2 3 ... 12