I will possibly add a small back plate glued to the cardboard to give the Dino’s output sockets more stability.
If you use the USB bus master to connect to a powered hub, you could use a Lightning cable to charge the iPad while playing. (Well, technically you could also solder aforementioned cable to the +5V supply on the board, but is it really worth doing that?)
I DO like the TB Midi Stuff app, but as of this time of writing, it is almost abandonware. The author promised to do an iOS12/13 update, but I would not blame him if he didn’t.
Modstep is a great sequencer and beatbox with a more than passing resemblance to Live, but like Live, it is no simple tool. And there have been no updates for a while – once again, I do not blame the programmer. Do people realise that it is impossible to survive on writing special-interest apps?
A Minimoog, a Prophet and an Odyssey enter a bar… and it’s only 200 Euros. — I know, if you don’t understand German, there is not much the last post can offer you but that is where I collected the first batch of info on the DinoPark VA PCB synth. In the meantime, controller panels have been programmed with the TB Midi Stuff app for iPad, and it works.
A Novation SL MKII controller keyboard connected via a USB printer cable to the DinoPark board; the Dino is the USB master, and the power supply for the keyboard.
The DinoPark’s USB Slave connector – the Micro USB socket – is used to connect an iPad via the Camera Connection Kit. It runs TB MIDI Stuff; the panels enable me to change the settings, and show me the parameter settings for the actual sound.
It would be possible to use the Novation controller only; this just about works for the Minimoog emulation as a Minimoog has not got that many dials to turn; for the Prophet clone, the 24 dials and faders of the SL are simple not enough; you would need two templates and would have to jump between them. Moreover, the Novation controller does not evaluate the board’s CC messages and is thus unable to show the actual values for a parameter. Nothing new for VA synths.
Dino Park is switched to OMNI mode, receiving on all channels.
Switching between the synth models is by doing a full MIDI Bank Select: CC#0, model #, CC#32, Preset Bank (0 = Presets, 1 = User). BTW: This is wrong in MPA’s MIDI documentation for the Dino Park.
These models are included:
Bank 0: Minimoog model, „Minimax“
Bank 1: Prophet-5 model, „Pro-12“
Bank 2: ARP Odyssey model, „Prodyssey“
More models available for the Creamware technology: Bank 3 – “B4000” organ emulation closely related to Ferrofish’s tech, a VS-inspired synth called Lightwave, the “Vocodizer”, a FM/PD synthesizer called FMAGIA, and a „Drums ’n‘ Bass“ model.
Saving a preset is done by sending CC#111 followed by the preset to save to.
MIDI implementation is documented for the four first models on the DINOPARK-Support page. Some small errors and omissions: The CC#0, CC#32 sequence for model switching is mixed up, Prodyssey model VCA Mod is CC#11 (not CC#51), VCA Gain is missing from doc but can be reached by CC#51.
Rediscovering an old love of mine, for a simple reason: The R3 is an ideal piece of gear to take on a holiday – compact yet with a full-sized 3-octave keyboard, extremely versatile, powerful sound – and really good fun.
The setup: The R3, vocoder mic inserted, my Volca Beats drum machine synched to the R3 via a sparkling blue MIDI cable, and inserted with another audio cable into the R3’s two audio inputs, and optionally, the ModStep sequencer app on my iPad as a phrase recorder, connected via the new Camera Connection Kit and an USB cable. Apart from my headphones, there is even a small autonomous Bluetooth speaker that can be wired to the R3’s output, via another audio cable. As the R3 is a full-blown synth rather a sound toy (also known as “Tischhupe”), and everything mentioned fits effortlessly into a small gig bag, and thus in my overstuffed car, I conclude that the R3 is ideal travel gear, and suitable even for camping holidays.
Yet the R3 is so much more.
Bass and melody tracks in Modstep, you can even override the Volca Beat‘s patterns and control the sounds directly from a Modstep grid
Came as a substitute, stayed as a champion
Many, many years ago, I was looking for a small beginners’ synth to get back into music. I had been looking for a MicroKorg but without the MK’s obvious limitations – four-voice, monotimbral, small keys simply not suited for my clumsy fingers. I realized that there was a MK XL, and then I realized that there was a slightly larger version of the same engine packaged with full-size keys, more FX, the capability to produce two different sounds at once, and a slightly better user interface, called R3. Which was to be had cheap. So I bought a second-hand one on eBay.
It was a good choice for getting back into music. The same qualities that make it a good holiday companion made it a good choice for jamming: It’s portable, it’s playable, and it’s capable. And gradually I started falling in love with the R3. Let me tell you why.
Genesis fans from the Prog-Rock as well as the „Mama“ factions hate it. Well, „Duke“ it‘s not, but it contains some truly unique pieces of music.
For one, I do love underdogs. And the R3 is an underdog synth. You see, the R3 is a bit like Genesis’ “abacab” album. Prog-Rock Fans hate this record for, well, Phil Collins, you know. Pop fans hate it for its handful of admittedly truly horrible songs. Just like Microkorg enthusiasts hate the R3 for sounding cleaner than a first-gen MK or an MS-2000; VA enthusiasts hate it for not sounding like an analog. I love “abacab” for its unique, electronic, Prophet-5-heavy sound, and for showing off what a terrific musician Phil Collins actually is, whatever you think of his songwriting.
Well, the analogy stops here – as I have mentioned the magic word “Prophet-5”, let’s be honest: The R3 is not a good VA to replicate vintage P5 sounds. In case you should be desperate to replicate the sound from Genesis’ “Lonely Man At the Corner”, better known as the sound from PC’s “In The Air Tonight”: There are much, much better VAs for that – please do look at Creamware’s Pro-12. So let me break down what I like – and dislike – about the R3.
The depth of the Radias engine
The R3’s basic layout is a traditional substractive synthesis setup, with two oscillators, two multimode filters, 3 EGs, 2 LFOs. The first oscillator features classical as well as sampled wave forms. The filters are not too bad for digital filters. A small mod matrix complements a couple of hard-wired modulations such as velocity/EG and LFO2/pitch. Some extensions and variations on the classic theme, under Korg’s “MMT” label from the Oasis line.
Some of that stuff is weird – Format wave forms, anybody? – some is really good. I love switching OSC1 to VPM – this is Korg’s variant of Casio’s Phase Distortion synthesis from the 80s, which was Casio’s variant of DX7-like FM synthesis for normal humans without a second brain or PhDs in acoustic physics. A wave shaper, technically a lookup table but very versatile. Filter2 working as a comb filter, i.e. a resonator for Karplus-Strong type string plucking sounds. And up to three independent effects per sound, including another bit crusher as well as a ring modulator.
The best thing of the R3’s mod matrix may be the feature that is not part of it: a sixteen-step modulation sequencer. Apart from sequencing, well, pitch, it can animate parameters like OSC1’s harmonics in VPM mode, which you cannot reach from the mod matrix. It can even modulate the mod matrix’s modulation depths. I would wish that the mod matrix could reach all the targets the mod sequencer can reach, but it is unfortunately much more limited. They fixed that in the Radias – a Radias is two R3s packaged with an Electribe and many, many knobs – but the software update enabling the additional targets never was back-ported to the R3. Underdog indeed.
I do own a Radias, by the way. It understands R3 sounds, and they are among the best for this synth.
Let’s face it: in terms of digital technology, the R3 is old. 8 voices – 4 per split – are not enough. (Still, its even more limited Microkorg brethren are sold to this day.) There are fresher VA alternatives that are just as cheap, like Novation’s Mininova. And there are some things to hate about this small machine.
The plastic housing is cheap. The full-size keybed is playable but nasty. (Take my word for it: the keys don’t feature the usual metal springs but are attached by flexible plastic working as a spring load – ewww!) They tend do turn yellow over the years as well. Really, really nasty. They could also do with an aftertouch, but even if the R3 HAD aftertouch, the limitations of the mod matrix would mean that you could not program it to control vibrato independently of the mod wheel.
In summary: Rational causes for a a love affair
Full-sized, 37-key keyboard
Light and compact
Deep VA engine capable of some unique sounds
While not knobby, it is still easy to program without an editor
Incidentally, Jenny had to vanish in her new flightcase due to a broken keyboard frame – I had patched this several times before, but until I can manufacture a new part to fix this once and for all, she will have to stay put.
I figured out that I have reached the point where the unpleasantness of having to buy, install and maintain a proper web shop has dropped below the unpleasantness of having to do everything by hand. (I am sure there is an XKCD cartoon for this.)
And there is also the fact that the many buyers of Bob’s firmware deserve professional handling of their inquiry. A machine is much, much better at this than me.
So this little blog is running WPShopGermany now – although I am not at all happy with their multiple documentation, things look reasonably well so far.
A German shop – for English speakers?
The WPShopGermany is fantastically well adapted to German laws and regulations, but not quite as well to speakers of other languages. To offer foreign language support, the makers recommend using the commercial WPML plugin – for which a license comes in at impressive 79 dollars, much more than I paid for the shop plugin. Which is all the more infuriating as the language files for US-English are all there (wp-content/plugins/wpshopgermany-free/lang/). And no, I am not using the free version.
Luckily, I discovered that there is a newly developed free alternative to WPML, WP Multilang. Installing and activating the plugin made the shop run fine, with German and English texts – but I have not come round to translating every important title and page into two languages, so you might still have to employ GTranslate at some point or another.
To err is human. To blunder spectacularly is untergeeky.
I tell myself that this is the downside (backside?) of serendipity, but I tend to overlook things and produce errors. If you should serendipously stumble upon one of those – a missing translation, a missing order form, something running wild – drop me a line, will you? Cheers!
…as I am installing proper shop software after all. Safer and faster for you, easier for me.
Might take a couple of days though until the webshop plugin is running and properly translated.
If you are about to lose patience, or would like to contact me about any issue or question, please use the contact form. (Yes, I DO know that it stubbornly mistakes some people for spammers but please stick with me; there is also a mail address on that site.)
Natürlich lief die Installation nicht rund, und das hat in diesem Fall mit einigen Eigenheiten von Strato zu tun, meinem sonst durchaus geschätztenund geliebten Provider.
Der erste Schritt war einfach: Das OpenAtrium-Installationspaket heruntergeladen und in ein Verzeichnis auf dem Server geschoben, die install.php aufgerufen – und die Installation läuft los. Leider läuft sie nicht durch, sondern bricht am immer gleichen Punkt ab mit der Fehlermeldung, der Speicher sei aufgebraucht. 32MB würden nicht reichen, sagt die PHP-Installation
Jetzt ist das mit dem Speicher für PHP so eine Sache. An die Datei php.ini, die globale Einstellungen festlegt, kommt man bei Strato nicht heran; dort kann man den Speicher also nicht hochsetzen. Ich wundere mich, dass das nötig ist – laut einem Hinweis von Strato bietet mein Hosting-Paket beim Einsatz von PHP5 maximal 64MB, was dicke reichen müsste. Und ich habe den OpenAtrium-Ordner im “Webkonfigurator” zum Einsatz von PHP5 gezwungen. Ist das Paket mit sich selbst zu geizig?
Wie kann man sich mehr Speicher verschaffen? Neben der – wie gesagt: nicht zugänglichen – Konfigurationsdatei php.ini besteht die Möglichkeit, in der versteckten Datei .htaccess Anpassungen vorzunehmen. Zu der kursieren einige Tipps im Netz; man solle Verschiedenes auskommentieren oder sie ganz löschen. Dass das nötig ist, kann ich nicht bestätigen; Fakt ist aber: Trage ich in die .htaccess-Datei die Anweisung “memory_limit = ’64M’;” ein, produziert der PHP-Interpreter nur noch Fehler.
Der nächste Schritt war, dem Programm selbst mehr Speicher zu geben: Die OpenAtrium/Drupal-Installation hat in einem Unterordner eine “settings.php”; dort kann man das memory_limit auf 48MB setzen. Nicht schlecht, nützt aber nichts für die Installation. Moppelkotze.
Obwohl ich – spürst Du’s, Leser? – nur noch einen Schritt von der Lösung entfernt war, habe ich mich an diesem Punkt entschlossen, die Installation nochmal zu radieren und von vorn anzufangen. Nanu, ehemals schreibgeschützte Dateien lassen sich immer noch nicht löschen? Auch auf der ssh-Kommandozeile nicht? Kein Wunder, wenn der Ordner noch schreibgeschützt ist, du hohle Nuss. Und nein, bei Unix gibt’s kein chown und kein chgrp, sondern nur den Befehl chmod; Linux ist nicht Unix.
Vor der Neuinstallation habe ich das memory_limit in install.php UND in settings.php auf 48M gesetzt. Und siehe da: jetzt lief die Installation durch.
Gut, nun läuft OpenAtrium also, sieht gut aus, erst einmal aber auch nicht viel mehr. Komme mir ein wenig vor wie der Mann, der sich einen teuren Flügel kauft und ins Wohnzimmer stellt und dann allmählich darüber nachzudenken beginnt, ob es nicht doch mal hilfreich sein könnte, Klavierunterricht zu nehmen. Ob ich nicht doch lieber beim Wiki bleibe?