|
|
Post by thetechnobear on Oct 3, 2018 13:54:39 GMT
am I alone in having issues with this? my issue is ... I like to use other synths alongside AEM, and id like AEM to be 'in tune'. also importantly (as i think this is key to my issue) is I want to sequence with an external sequencer. Ive a squarp pyramid, so this has many more features then id get with the analog AEM sequencer... but also importantly, it means I can sequence both the AEM and other synths from one sequencer (I'm basically trying to sequence AEM by both midi and cv, in a couple of different ways, and also multiple AE voices ) my problem is pretty basic, I tend to find even though I've calibrated my oscillators , as described on the AEM website here , I still find I get a very restricted range anywhere near 'in tune', (2 octaves) , and even within this limited range its still off enough to hear it. now, I know the 2OSC has limited tracking, but I honestly dont even find the VCO modules that i have much better, I also know you need to wait for AEM to 'warm up' before using, and also before calibration (which i do allow 5-10+mins for) Ive done the calibration a number of times, and to be honest it doesn't really seem to make much of a difference... when Ive finished calibration Im kind of 'ok' with the results, and as good as they can be. (though honestly not very happy), but tend to find next time i come to play in melodies, I think 'meh', its too far out to be useful. I'll be honest, this is really the thing that has held me back from using the AEM considerably more... BUT this is not a moan, nor complaint, rather Id like to get some ideas from others, and also their experience. so the question is... Do you have issues with oscillator tuning (2OSC and VCO) , particularly with midi? How do you get around this? Have you calibrated the oscillators?
of course, we can also use this thread to talk about anything to do with tuning/calibration , both issues and suggestions, (I think its a pretty important topic, and im kind of surprised no one has mentioned it before... so do wonder if its 'only me'  ) also I have one question/request for robertlanger , what is the frequency suppose to be for OSC2/VCO when the course and fine tune/freq knobs are zero (and max) I do wonder if after calibration, I've gone outside your intended range, since Ive had trouble at times, getting the oscillator to go low enough. i.e. the freq knob with 1v cv is virtual at minimum....
here are a few of my slightly random thoughts/ observations... first, Ive seen many seem to use the AEM sequencer, which of course avoids oscillator calibration/midi mapping issues... since its all done with analog voltages directly. Im intrigued if this is because of issues with calibration, or just its nice to have 'all in one'. I did consider this approach, but really its not for me, as I dont want to not use the Pyramid. (and I dont currently have the case space ) CV vs MIDI, ok, this is quite interesting... Ive a theory (which could well be wrong) that perhaps there are two calibrations at play, one is CV->OSC pitch , the other in the master module midi -> CV I have a small suspicion when Ive been doing the oscillator calibration, that this midi cv is not 'perfect', in particular it seems that some notes(semitones) within the octave appear more 'out than others', so that all the calibration process gets you to tune an octave points, you still get some oddities within it. ( cant remember details for sure, but I seem to remember some of the #/b are out, but need to test again) calibration, ok, so as i said when I do it , it appears 'ok', and within I think what its capable of. (esp, since ive done it a few times now) but I do wonder if, partly the issue is unless you set up the oscillator *exactly* as it was when calibrating, it will always be slightly out. (theres an oddity in the calibration process, in that when you first set the freq knob, this is of course partially dependent on where the adjustment screw has currently been calibrated too!) does Eurorack provide an option? ok, so I have a Bela Salt (completely programmable) in my eurorack setup, which I sometimes use as a USB midi to CV module. so im wondering if we do midi to CV within eurorack, then transfer this via CV (4IO) , might we get better pitch conversion? ok, the above might feel a bit 'random' , but im interested to hear others thoughts. I've an idea for a new module that i think could solve this issue in an interesting way (and with some interesting other options) , but Id like to first understand if others have the issue (*)? and how they are resolving it? this will tell me if the module might be interesting to others, but also might help shape the way I approach the 'solution' thoughts? Mark (*) ok the issue is oscillator tuning, but i guess the key thing Im trying to solve is external sequencing with midi/eurorack. |
|
|
|
Post by robertlanger on Oct 3, 2018 19:08:36 GMT
Yes, this oscillator tracking thing... to be honest also, this is a point I'm not really satisfied too. One thing that might be confusing during the calibration is to use a CV of 0V at the lower end; due to the unipolar design of AE there is not really 0V but approx. 0.03V as lowest CV. So for calibration use better 1V and 4V as reference points. The MIDI to CV conversion in the MASTER module is linear enough to be not the source of the issues - most likely.
I want also give a short reminder that the 1V/octave oscillator characteristic was added during the kickstarter phase in a relatively short time (not to say "in a hurry"); initially there was no "official" CV tracking planned, at least not for the Kickstarter phase. But the backers urged me successfully ;-) I have learned that creating a reliable 1V/octave tracking is even more difficult in the 5V single supply environment (as 100% analog) than in the +/-12V range of eurorack; so for the future oscillators I will go the way of "digital controlled" oscillators. With these I expect a robust tracking over 4 octaves and this also in higher / lower ranges.
|
|
|
|
Post by thetechnobear on Oct 3, 2018 20:25:40 GMT
for sure , as I said was no complaint... rather more trying to understand how I can make this work for me, and how/if others were addressing the issue.
(as I said, Ive a feeling many are using the aem sequencer so its not an issue, as this is using fixed voltages)
Pretty sure I’m using note 24 so 1v for base calibration. But will check with oscilloscope next time.
When sending in midi note 24 , where approximately would you expect the freq/coarse tune knob to be positioned? 9 o’clock?
Digital oscillator, hmm that’s an interesting thought, once my Bela is back in place, i’ll see if I can get that to track properly - that’ll show me if the midi cv voltage is linear/accurate.
What’s your thoughts on using the 4io/master cv for eurorack 1v/oct do you think this should be working the same as midi cv in aem? or are there are possible issues?
(obviously the oscillator tracking is the same if it comes via midi or cv, but perhaps the 4io/cv might introduce other issues?)
Basically I’ve an idea to create a kind of ‘advanced’ quantizing module, that will basically allow me to map Input voltages to arbitrary output voltages, such that the relationship between notes is irrelevant, ie it will just supply the oscillator need to get to a known pitch. so basically build a full pitch map.
If I can get the micro controller to do fft, then there is even a chance I can get it to ‘auto tune’ which would be very cool.
(it be easy for me to prototype this concept on bela salt in eurorack, if you don't think the 4io would cause other 'artifacts', then I can build the aem module)
|
|
|
|
Post by Malibu Interface on Oct 4, 2018 11:09:23 GMT
I am really looking forward to the CV QUANTIZER module.
It is always tricky to play the AE VCOs in tune.
This may be part of the charm of the system : a little bit of an experimental approach.
But sometimes, it could really ease the composition process having a scaling module.
|
|
|
|
Post by thetechnobear on Oct 7, 2018 15:06:06 GMT
I am really looking forward to the CV QUANTIZER module. unfortunately a 'traditional' quantizer wont help the tuning, in fact it'll make the issue more noticeable (like midi) , since its the oscillator scaling thats the problem, not the input voltage  anyway, I can now reveal why I wanted to discuss this topic (and again, show that this was not a 'moan' thread, rather a request for ideas and thoughts!) Im creating a new module called ArdMod , whos primary purpose is to help me solve this issue with a patch called 'SOM' (Scale Offset Memory)theres more detail on the DIY thread, but the basic principle and how it relates to this topic are quite simple. assuming an oscillator (once warmed up) always gives the same frequency when supplied with a given voltage, then we can bypass the oscillator calibration/tuning, by simply proving the voltages it needs to produce the required pitch! i.e. we don't care if its v/oct or not, we just tune the oscillator in the SOM, and get the SOM to do the conversion from v/oct to oscillator cv. (the SOM has 4 independent I/O with 4 independent maps, so you can do this for 4 different oscillators) so whats quite interesting, is with my proof of concept, I walked thru the workflow of how to do this, using my pyramid (midi) sequencer , and it feels actually a bit like the analog sequencer (but with unlimited number of pitches) - basically, you use SOM to 'store' each of the pitches your interested in the sequence - then just sequence those notes. (of course, you can also 'store' entire scales if you want, but you this is a bit more effort that does not have to be done) and because these mappings can be stored to eeprom, once you have done this once, you do not have to redo it again (for that oscillator) (*1) anyway, proof of concepts seems to work, Im sure I'll be doing lots of tweaking to make the process quicker and easier. (*1) of course like oscillator calibration and the analog sequencer the notes will only be true IF the oscillator has warmed up, otherwise you might have some slight pitch variations! (*2) one thing that might be interesting is to determine if each oscillator has a tuning characteristic, such that I could produce a 'default' map, that could then just be tweaked. EDIT: so Ive been playing a bit more, and realised IF your oscillators are reasonably well calibrated the 'tuning/store' process is very quick, the reason is simple.. assuming you set scale to 1, then once you have tuned (via offset) your first note and stored it, then when you enter the next note the offset required will be very similar , so a tiny touch on the pot is all thats required, in other words, you end up just tuning out the inconsistencies in the scaling. I think once I have the other buttons/pots Im going to add a fine tune for both offset/scale, and probably a mode that allows you to force scale = 1, this should make this even quicker/easier. (and of course, once you have one oscillator tuned, its really easy to then use that oscillator as a reference oscillator for another) |
|
|
|
Post by robertlanger on Oct 7, 2018 16:26:50 GMT
This is a super exciting development; if this works it will be an official AE module very soon! Besides of this I'm just working on a digital controlled oscillator with the same goal to get a precise pitch over the full range. Anyway, I see this tuning issue to be solved soon! Thanks a lot, technobear!
|
|
|
|
Post by thetechnobear on Nov 3, 2018 17:55:04 GMT
ok, now finally ArdMod is complete and 'racked up', Ive been able to 'fine tune it' (pun intended) for its tuning role (SOM) and I can definitely say this approach works! I can reasonably quickly tune 4 oscillators for about 3.5 octaves, what Im labelling C2 to G5. (C0-G3 for AEM, but i auto pitch down when going to AEM ) the top end is a bit tricker than the bottom, G5 is alway spot on but A5-C6, is a bit variable. (you have to also wait a little while for the AE oscillators to warm up and stabilise) the process to tune is fairly simple (and similar to oscillator calibration) , if I'm trying to tune the whole 3.5 octave scale what i do is: set scaling to 1.0, offset to 0 (or as close as possible) , which means its should be not doing anything, then i tune from the lowest note up, trying to find the close scaling to put in tune. then it just a matter of tuning/store each C and perhaps each G (depending how close my scaling is) then often manually tuning the lower and higher notes (where the scaling seems most 'off') it a bit of a 'technique' but it's pretty quick once you've got used to it, as its all small adjustments. if your just after a few notes (from a sequence) , then you can alternatively just tune those specific ones (which is really quick to do), but i like to do the range, so I'm free to transpose. what's nice is I do it all by ear (initially against my external synth, which is also sending in midi to the AEM), so when I do 4 different oscillators, there is going to be tiny variations between the oscillators, so keeps its analog flavour so controls Ive got it down to are: Pot 1 - Coarse Scale Pot 2 - Fine Scale Pot 3 - Coarse Offset Pot 4 - Fine Offset (Ive added an LED confirmation for hitting the mid point on each of the pots as its so important) Button 1 & Led = Live/Recall mode (of current input/output pair) Button 2 & Led = Store scale/offset (in live mode only) Button 3 & Led = quantise input (per input) Button 4 & Led = Select input (live mode) Button 1 + Button2 (Live+Store) = clear mapping Button 1 + Button3 (Live+Quant) = toggle recall interpolation (per input) so basically: - You play a note on a keyboard, and tune it with Pots 1-4 - Hit store - repeat - test by switching to Recall mode, perhaps add more notes then you can switch which input/output pair your using with button 4, all others are in 'recall mode' settings: quantise input (default on) , 'rounds the voltage' of the input , makes it easier for note input where there can be voltage fluctuations... (turn off for continuous CV scale offset) interpolation toggle (default on), if an value has not been stored for an input voltage: on - linear interpolate between the stored voltage above and below (default) off - use the closest voltage. linear interpolation works well for notes, and means you don't have to store every note. though I designed if for tuning, its really useful for other stuff. - turn off interpolation, and you can use it as a mapping function for CV - linear interpolation works in reverse, so 0v = 5v, 5v = 0, it'll now invert voltages - scaling and offset (err, ok, implied by the name) but its useful to attenuate/amplify and offset (positive or negative) any cv. I currently have setup for storing up to 64 mappings (not a lot of memory on the Arduino) which seems plenty/overkill. anyway, perhaps a candidate for something similar as an AE modular. I guess I'll organise myself and chuck the code into GitHub, though pretty it is not... as its my first time playing with arduino code  thoughts for the future... - currently i dont store to eeprom,this would be trivial to do - partly because its quick to do - but also I think there are so many variables to the oscillators tuning, Im not sure how valid the map would be... say on a colder day , or a warmer environment or if you knock the oscillator tune. - but its probably worth a go, just to see how this assumption is true, and for sure helpful if you turn the rack on/off for the day - storing scale/offset so currently i store fixed points in the map (with linear interpolation optional) , but an interesting variation would be to store the scale/offsets, perhaps from these you could do a different interpolation (e.g. interpolate the scale factor) , which might give a closer setting. - differential tuning ok, so the 'pain' with the UI as it is, is finding the 'centre' points, and these are the most important points - as really what we want to do here, is do minor variations from this (assuming oscillator tuning is 'in the ball park' so a variation might be to rejig the UI so that the pots are normally at zero... so only increase values, but have a coarser (and stepped) control. the idea being the stepped control you know exactly where your at - and then the finer control you know where zero is. e.g. scale might have 0, 0.25, 0.5, 0.75, 1, 1.25, 1, 1.5, 1.75, 2.0 - then fine = 0 to 0.25 (with probably a small dead zone at the bottom, to really hit zero) currently both coarse and fine are floating +/- at 10 bit resolution so getting exactly 1.0 is difficult. this is definitely less useful if you dont care about exact values - as the +/- works really well, but perhaps the above for tuning might be more precise. anyway, now im using it regularly I'll see how these play out |
|
|
|
Post by thetechnobear on Nov 3, 2018 18:40:48 GMT
a small note on tuning in general so, this definitely is useful on the 2OSC oscillators - which i find usually i can only get about 1 octave of good tuning. but having played a lot more with tuning now, Im finding one of my VCO oscillators is actually pretty good, the funny thing is, Im not sure if this is the one i recalibrated or the 'newer' one which Ive not got around to re-calibrating so... actually, I think I probably can find a sweet spot on the VCO modules. - I think perhaps my frustration with the 2OSC clouded my judgement on the VCO. so I'll give the out of tune one a go at calibration... and also perhaps pop it out of the rack, and compare to the other to see if its the newer one or not... or to see if there is a pcb revision?!
EDIT: some calibration on the 2nd VCO ok, so I improved it... but now i remember what I came across last time... so you get about 2-2.5 octaves on the VCO, but they are dependent a bit on the base frequency (i.e. where the coarse dial is).. you get better tuning at the place where you have calibrated it (unsurprisingly) this means you can choose a little bit wear the 'good band' is (at least i found 2 good spots and octave apart) but what I found odd, and couldn't work out last time either was .... my two VCOs are different, one of them can go a lot lower in frequencies - down to clicks, whereas the other is never goes that low. (regardless of calibration) (this conversely means the top end is inaudible which is not much use ) )
EDT2: : my last observations on tuning and the VCO module I guess this can be summed up as 'its analog, so there are variations' but here is what I see. note: Ive not checked pcb (I'll do this next time Im reorganising the rack) , so dont know if theres any variation in boards between the 'new' and 'old', so this is just a label (as in new to me) a) old VCO (from KS) I could get it to tune pretty accurately over 2-2.5 octaves (SOM can fix the rest) its about 1 octave higher than new VCO ( Ive tried extremes of calibration, and just wont go down as low), (honestly I dont remember if it was like this when I first got it, I only really noticed after the first time I re-calibrated it, so perhaps i borked it) b) new VCO (bought a few months back) was tuned pretty well from "factory" again about 2-2.5 octaves, but I noticed it has a slight bump in the middle, where it was slightly flat so C1 was accurate, C3 was accurate, but C2 (and surrounding notes ) are slightly flat... and regardless of calibration this is the best i can get. so this means its response is not linear, its from C1 to C2 it goes increasing flat, then on C2 to C3 it becomes sharper. and the calibration knob seem to be linear scaling (or at least its not adjusting this curve much) to put things in perspective, its useable (and I can use SOM to fix) its just not as accurate at tracking at the old VCO, and honestly I prefer the fact it can go a little lower in frequency. Ive no idea if these two differences (range/linear freq response) are due to a change in design, or just tolerances in components, and they are no 'big deal', but just observations - that kind of confused me when I was looking at them, expecting to be able to tune them the same. the flip side, is having played so much with calibration - Im now very quick at it... and perhaps way too obsessed with tuning |
|
|
|
Post by spacedog on Jun 3, 2019 16:55:35 GMT
Using the search function I found this useful thread. I knew that I'd seen something, but couldn't remember where. I spent a long time yesterday trying to find a playable zone on my VCO module using both CV and MIDI inputs. I was trying to transpose externally-created sequences and because of the delays the tuning became noticeable very quickly. I then played quite widely across the keyboard just to hear where the sweet spot could be found. It was quite a narrow sweet spot, probably only an octave and I decided that couldn't be right so I remembered the calibration note on the website and off I went with my ears, a tuner and a screwdriver. After quite some work, I managed to get about 2 octaves in tune, but outside of that (higher) it went increasingly flat. Reading the thread above, my VCO does appear to go very low and I was trying to go down to 1V, which was basically clicking with the VCO. Having read the above thread it looks like I should start a little higher as the calibration zone - C1 to C3 (2V - 4V) was mentioned by robertlanger , rather than C0 to C2 (1V - 3V) as noted in the documentation. I am happy to upgrade to the digital version of the 2OSC if that is going to give me better tracking. Has anyone any experience of how well these track compared to the non-digital 2OSCs...? Of course, there is no digital VCO at the moment, so I would lose that fine tuning and it is noted as "... best if you need an oscillator for primary musical / melodic use". Like thetechnobear in the thread above, this is not a moan. It's more that I want to be able to sequence externally and play melodically across as wide a range as possible. I will try calibrating using the different range later this evening. |
|
|
|
Post by 101 on Jun 3, 2019 17:46:30 GMT
I've not had issue with the VCO module being out of tune with whatever I'm externally sequencing (from Renoise). I tune the VCO to middle C and it tracks very well with other synths. I know that's not the same as calibrating per se. But the end result is good. I wouldn't even attempt it on the the 2OSC module but for bass and modulation duties the 2OSC seems good enough.
|
|
|
|
Post by dmoney2000 on Jun 4, 2019 11:48:46 GMT
I’m able to get about 4 solid usable octaves when using CV from my Analog Keys to control the AE. The Analog Keys is able to do pretty fine calibration of pitch cv. Once it’s set, things are generally ok. As others have said, you have to make sure he lower value is set above 0v or the scaling will be all messed up. On a recent project, is set the lower value (C2) to 0.88v and the upper value two octaves up (C4) at 2.053v.
|
|
|
|
Post by thetechnobear on Jun 4, 2019 12:21:08 GMT
yeah, Id love to hear about experiences of the OSC2/d as well once the new cables are in stock ( ) , Im planning to put in a new order, which will include the OSC2/d amongst other things, and perhaps get the analog sequencer, as with that, tracking doesn't matter
on the VCO... interestingly, I later found that on my 2 VCO's seems to track better than the other (even though I calibrate in the same way) , it feels like on one of them, that the tracking is not as linear... so whilst I can tune the top and bottom nicely, I then find in the middle it goes out a little. but on the other its absolutely fine. I've been putting this down to one of the VCOs is much newer, as the other came from the original kickstarter batch - so perhaps they have been improved. (I don't know why is which ) - or perhaps its just within 'tolerances' edit: oops, actually just noticed, I already posted this observation before... oh well, perhaps useful reminder if others are using older VCOs (and as also noted, for some reason, they seem to have a slightly different range - which again perhaps shows some changes may have been made over time?) |
|
|
|
Post by gorkulus on Jun 18, 2019 21:50:45 GMT
I'm curious if anyone has tried using Ableton's new CV tools to get nice pitch tracking of AE's oscillators? Apparently it has nice calibration features that will create a custom CV curve for each oscillator for nice pitch tracking (sounds like along the lines of what you were trying to do with the module you're working on). I'd be really curious to know what the results are like. Still not a great solution if you're trying to sequence from anything other than the computer, but seems like potentially a game changer on this front if you're mostly sequencing with a computer and have a DC coupled interface (and I'm curious in general if anyone has worked with CV out of a computer / dc-coupled interface). cdm.link/2019/05/ableton-cv-tools-free-modular/ |
|
bahm
Full Member
Posts: 154
|
Post by bahm on Jun 19, 2019 6:10:54 GMT
Sorry, wanted to make that earlier but forgot about it.
The machine warmed up at least 20 minutes.
Midi in - 2osc/d - mixer - vca - out.
The tracking is not perfect but tuning the oscillators won't make it better I think because the detuning is not linear or exponential? Sometimes its a bit too high, other times too low as you see. But it's not bad I would say.
The guitar tuner is connected to the mixer. The app just uses the phones mic.
If there is anything else you want to see... Just tell me.
The video is only accessible via this link.
|
|
|
|
Post by gorkulus on Jun 24, 2019 23:48:55 GMT
I'm curious if anyone has tried using Ableton's new CV tools to get nice pitch tracking of AE's oscillators? Apparently it has nice calibration features that will create a custom CV curve for each oscillator for nice pitch tracking (sounds like along the lines of what you were trying to do with the module you're working on). I'd be really curious to know what the results are like. Still not a great solution if you're trying to sequence from anything other than the computer, but seems like potentially a game changer on this front if you're mostly sequencing with a computer and have a DC coupled interface (and I'm curious in general if anyone has worked with CV out of a computer / dc-coupled interface). cdm.link/2019/05/ableton-cv-tools-free-modular/Or has anyone used Expert Sleepers calibration? Or any other computer based calibration tools? |
|
|
|
Post by thetechnobear on Jun 25, 2019 18:54:37 GMT
yeah, I recently bought an ES-8 , so was keen to try it... it does a very good job , nicely accommodates the drift that occurs, and so you get a nice range with all notes in tuned with +/- a few cents. the results of the calibration are quite interesting, as they show the tuning curve  so Plaits in Eurorack (simple waveform) is completely flat , as expected  the AE OSC2 is pretty flat initially, but then you can see the tuning rises.  this AE VCO again pretty flat initially, then drops. however, another VCO I have, actually is flat then rises I think what we are seeing in both cases is its flat in the octave range we tune them for, but outside of this they then move a bit. but Ableton/ES-8 can nicely compensate for this. this is basically what I was doing with the ArdCode scaling project i did... but I found it a bit of a pain to do each time, as it didnt have the auto calibrate mode found in ableton. technical notes: - the AE oscillators Ive calibrated to as good as i can get... i think , and I waited for them to stabilise - I haven't yet run for a long time to see how long they are stable at the given calibration, or if they frequently drift. - I didn't test, but my assumption is Bitwig will be the same - similarly I guess silent way will do the same thing (but I don't have to test) |
|
|
|
Post by bleepbox on Jun 29, 2019 21:03:24 GMT
Really interesting to see these calibration plots, thanks thetechnobear. I've got an ES3 and Ableton/CV Tools and was wondering whether it would be possible to use these with AEM. Did you just run cables through a 4I/O to your AEM? Will CV Tools work effectively with AEM beyond calibration? I wasn't sure if there were any potential issues related to voltage levels, but don't have much knowledge about how this side of things works. |
|
|
|
Post by thetechnobear on Jun 30, 2019 18:19:15 GMT
this will work with either 4IO or the 2cv IO on the master module. voltage levels are not an issue, the 4IO and master module will simply clamp it between 0 and 5v, so that means you get potentially 5 octaves. (as shown in calibration) what nice about doing this is I get nearly 5v octaves that are useable... rather than the usual 3-3.5 that i usually get. I'm looking forward to trying the 2OSC/d which I'll be putting on my next order ... once the new patch cables are in stock |
|
|
|
Post by spacedog on Jul 16, 2019 11:45:48 GMT
An advert for these people just popped up on YouTube (whilst I was watching the piece by thetechnobear on the new Organelle, funnily enough). I'm not sure if it is "old" news or not, but just in case here is a link to a blog piece by TA Programming, advertising their product, which appears to play into this space. It's not cheap (to my thinking), but it might be a decent piece of kit for those that use these things. |
|
|
|
Post by spacedog on Jul 16, 2019 12:08:01 GMT
An advert for these people just popped up on YouTube (whilst I was watching the piece by thetechnobear on the new Organelle, funnily enough). I'm not sure if it is "old" news or not, but just in case here is a link to a blog piece by TA Programming, advertising their product, which appears to play into this space. It's not cheap (to my thinking), but it might be a decent piece of kit for those that use these things. I have now realised that I am a total (and old) nerd... looking at the picture on the product page, I spotted the magazine under the interface and I thought, " I have that magazine, it's the one with Klaus Schulze on the cover". Lo and behold, it was from March 1982 and I do indeed have that magazine I saw Klaus a few months later in London, he wasn't wearing the welding gear though. For that, go here or here (slightly longer with a Moog solo) for some crazy footage from Linz in 1980 - here is some detail for those who have stayed with me this far...!!!  |
|
Lugia
Wiki Editors
Ridiculously busy...ish.
Posts: 556 
|
Post by Lugia on Jul 16, 2019 12:16:58 GMT
I dunno...UKP 199 doesn't seem all that out of line when you consider that a Kenton USB Solo runs only about $10 less (US price) than this TA Programming device.
The EM&M cover was amusing, tho...I noted the Firstman Sequencer (also badged as a Multivox product in the USA) in amongst the pre-MIDI fun. Those had about a one year run, because the MIDI spec was just about to hit and that would blow that niche-y device into pre-MIDI oblivion, along with the CV/gate interfacing protocols in general for about a decade or so. The Firstman was definitely not anywhere as capable as something like the Kenton or, for that matter, the TA Programming converter...in fact, one might be tempted to slap a "Mattel" logo on it instead!
|
|
pol
Wiki Editors
Posts: 1,349
Member is Online
|
Post by pol on Jul 19, 2019 20:39:47 GMT
An advert for these people just popped up on YouTube (whilst I was watching the piece by thetechnobear on the new Organelle, funnily enough). I'm not sure if it is "old" news or not, but just in case here is a link to a blog piece by TA Programming, advertising their product, which appears to play into this space. It's not cheap (to my thinking), but it might be a decent piece of kit for those that use these things. I have now realised that I am a total (and old) nerd... looking at the picture on the product page, I spotted the magazine under the interface and I thought, " I have that magazine, it's the one with Klaus Schulze on the cover". Low and behold, it was from March 1982 and I do indeed have that magazine I saw Klaus a few months later in London, he wasn't wearing the welding gear though. For that, go here or here (slightly longer with a Moog solo) for some crazy footage from Linz in 1980 - here is some detail for those who have stayed with me this far...!!! Used to love E&MM, bought it from the first magazine to the last... Combined with another which I forget what that was (Computer Musician?) and became less interesting for me so switched to Sound on Sound Magazine until that became too full of computer stuff, and bugger all hardware discussion/review. |
|
|
|
Post by thetechnobear on Jul 20, 2019 15:59:50 GMT
An advert for these people just popped up on YouTube (whilst I was watching the piece by thetechnobear on the new Organelle, funnily enough). I'm not sure if it is "old" news or not, but just in case here is a link to a blog piece by TA Programming, advertising their product, which appears to play into this space. shouldn't have popped up whilst watching my videos - as Ive not monetized my channel  +1 Sound on Sound, I never bought it but their Synth Secrets is still one of the best resources available! |
|
ean
New Member
Posts: 34
|
Post by ean on Feb 21, 2021 1:13:16 GMT
I just tuned both of my VCOs using MIDI notes from C1 to C4. C0 did not register a MIDI note. C2 and C3 seem off by 10 to 19 cents. This is as close as I could get them in tune. Analogue VCO behaviour is new to me. I can imagine designing an analogue VCO to stay in tune using 5 volts as a range is extremely difficult. I sometimes have trouble using the AE with other instruments via midi but the sequencer will hopefully make it easier.
|
|
frndo
Full Member
Posts: 110
|
Post by frndo on Feb 5, 2023 7:46:39 GMT
Hello! I revive this post, since recently I have an interface that I modified to be dc coupled and I can't calibrate the oscillators in Ableton CV Tools. Did someone make it?
|
|
) 
