MarkP

I was surprised to get this message today while using Cakewalk 2024.02 build 098, 64-bit. It's all Dutch to me 🙂. My language settings are exclusively English as far as I know. The exact circumstances that trigger the surprise message seem to be: when trying to upload to Bandlab and choosing upload options that include audio tracks or mix-down, when neither are present.

I've never used it, but the Presonus Studio 24C does have loopback. At least, there are options: Virtual and Mix 1/2.

I think the biggest and most organised collection of ESQ-1 and SQ-80 programs is the database I published in 2022. It has 5,675* unique patches, categorised into three levels: Synth type: ESQ-1 or SQ-80 Instrument Family: for example, Bass, Strings... Instrument: for example, Trumpet, Trombone, Tuba... There is a table of contents to help you find the sound you might be looking for, and comprehensive instructions. And, yes, credit to Don Solaris and Rainer Buchty for collecting and sharing most of these patches. This collection is available at: https://app.box.com/s/odqcbczbs8xjhgw9k2v2bna0tcxyx1v7 Please read the file 'Ensoniq Programs.pdf' for more information. Incidentally, the SQL file I provided loads directly into KnobKraft Orm, a free open-source, cross-platform, multi-synth sysex librarian that works with the ESQ-1. A link to the Orm site is included in the notes. Using Orm bypasses any need to work with sysex files; just download and set-up the program, load the entire collection in a single .db3 file, and start sending programs to your synth. You could be up and running in under 20 minutes. * The notes mention 5,762 patches in places. This was before a last-minute discovery of 87 duplications, whose names are identified in the notes.

I've used Thunderbird since the 20th Century. Quite happy with it.

I've used the arranger on most of my recent songs, but I either didn't know or had forgotten a lot of ways to use it. I had no idea there could be more than one track, for instance. This is good stuff. Very succinct and instructive. As for the animations, I thought they were perfectly fit for purpose as the text explains what is happening and the animations just reinforce that.

Got a bit dazed, flummoxed and befuddled myself when I returned to Cakewalk earlier this year. Spent a few days using the online Bandlab DAW, all the while thinking 'Is this it? Really?' Great relief to discover that the real thing was all the time there in the thicket too! I think I downloaded and tried about four DAWs at the time. I wasn't in the mood for small print. Even now, I can still go astray in the array of Cakewalk-related support pages, and this is probably due to my habit of using search engines to get to what I want - a habit that I gather is quite widespread.

If hard disk space is really not the issue, have you thought about periodically creating complete disk images? If you keep just your music-related stuff on a relatively small SSD, you should have space for literally dozens of disk images on a regular hard disk or cloud repository. Having said that, I don't know whether what you seem to want is truly possible, seeing as neither VST copy-protection measures nor future operating system revisions are completely knowable. Last month I built some Cakewalk projects from scores I wrote out in a manuscript book in 1978-1981; good old paper and pencil saving the day. I might well have compact cassette recordings of the same material, but finding them and being able to play them might not be as simple as poring over the staves. The point is, if there really is a good reason to resurrect old material, you will do it regardless of the amount of work it takes - if the need is there, and OCD notwithstanding.

After having Read The Fulsome Manual and having poked at the software I conclude the only bulk action that can be applied to sysx banks is Send All. I would really like bulk Select, bulk Clear and bulk Open too. I get that this may be a minority interest. Using database software, I periodically generate 100+ ordered banks of programs (all basses together, all woodwinds together, all other families grouped in between, and each family sorted by instrument). Keeping programs in this order makes it easy to find the right sound but means new programs must always be inserted among old ones, which changes where the breaks between banks occur. So I would like to be able to bulk-select an old set of banks, bulk-clear them, and bulk-open a new set, ordered by filename. Instead, now I have to open a new project, manually load the new banks one at a time, then delete the old project. Failing any answers to my prayers, is there a way to get in under the hood and replace a set of banks without causing undue catastrophe?

I have been down this path with my ESQ-1 and CbB. I think there may be several ways to go about this, but here's mine. First a comment: MIDI-Ox didn't seem to be straighforward enough for me, but I found Send SX worked like a dream. I think both of them can slow down transmission speed, which may or may not be crucial. I know that CbB is pretty fast when it comes to MIDI, and if there are problems it could be that the cable you are using just doesn't have the buffer size to deal with CbB's firehose. Everyone suggests you either get a Roland USB-MIDI cable, or use a proper interface. Still, let's assume that there are no bandwidth problems and that you just need to know how to put the bits together. I store multiple banks of 40 Ensoniq programs in CbB. If I want to load a bank to the synth I do this... Set the synth into sysex mode (I think you know how to do this) Make sure that the MIDI channels of the synth and CbB match (I found that the defaults work for me) Set the synth to a program page (say, Internal 1) In CbB, open the sysex window by typing Alt-Shift-7 or selecting Views>Sysx from the main menu Select a program bank in the sysex window Click File>Send in the sysex menu After a few seconds the programs should all appear in the synth's display.

I've had a bit more time with the SQ80 V, and I can clear up a few open questions in my previous post. The duplication of programs is a recurring problem. It can always be overcome by deleting the db.db3 file as described, and reloading, but this is clearly a bug. No more crashes since using SQ80 V without also using SQ8L at the same time. And the crackling was, I think, something to do with my audio interface. I had the buffer set to 512, went to change it, got offered a driver upgrade and then a firmware upgrade for the audio interface, both of which I took, then experimented with a buffer size of 1024, then tried 512 again - no more crackling. The other issue was that imported LFO waveforms seemed messed up. I can confirm now that the only waveform that imports properly is TRI. The other three, SAW, SQR, NOI, are all mapped to the wrong settings. I've notified Arturia support of this. If they fix this, I presume it will mean having to reimport all old programs, which will be a pain.

Despite (or perhaps because of) owning a working Ensoniq ESQ-1 and copies of the now abandoned SQ8L and Krosswave software emulations of the ESQ-1’s successor, the SQ-80, this week I spent actual money on yet another emulation of the SQ-80, the Arturia SQ80 V. My first impression is that it is so much better all round to have graphical representations of synthesis parameters like envelopes and filters than just digital readouts. The SQ family were state of the art for ease of programming in the 1980s, but expectations and technology have changed since then. With their gains balanced, playing the same programs on the original 1986 hardware ESQ-1 and the new 2021 software SQ80 V, I am hard-pressed to tell them apart, so my verdict is that this is a faithful emulation. It should be though, as the old and free 32-bit SQ8L, which still works, is also close (even though it has some differences the developer deemed improvements). I ran into some odd behaviour when I imported a bank of ESQ-1 programs. Twice the Arturia software appeared to duplicate every program in the bank, telling me there were 80 when I had uploaded only 40, but this problem seems to have gone away. The first time it happened I deleted what appeared to be duplicates by hand, only to find that I had one by one deleted every program in the bank. The second time it happened I exported the bank to Arturia’s proprietary sysex format, deleted the offending bank, and reimported it without problems. Subsequent imports have behaved perfectly. Arturia support suggested deleting the temporary file C:\ProgramData\Arturia\Presets\db.db3, which apparently can obstruct program (Arturia call them presets) updates. So what I learnt from that was that once programs go into the SQ80 V, there is no getting them out again. Arturia’s proprietary file format is the only form of output I can see so far. The other thing is that it looks like Arturia re-encode most parameters in decimal form, whereas ESQ-1 and SQ80 programs used integer values. The range of a DCA was, and is, encoded as 0 to 63, in increments of 1, whereas Arturia expresses it as 0.00 to 1.00 in increments of 0.004 or thereabouts. For some reason, just to be different, the envelope parameters stick to Ensoniq’s integers. The recoding is understandable when you consider that the SQ80 V is much more than the SQ-80. It has a suite of effects, which can be saved as part of individual programs. It also incorporates elements of the VFX methods for sound engineering, that were not catered for in the early Ensoniq program sysex. There are three ways to set up envelopes in place of Ensoniq’s one, an arpeggiator, new unison settings, and so on. In other words, it is a superset of the old synths. Another way this manifests itself is that program names can now be long and in both upper and lower case. Amazing! Programs can be classified, tagged, favourited and generally made a lot easier to find, sort and reorganise than they ever were in the hardware (or on audio cassette or floppy disk). I am editing programs simultaneously in both the hardware and the software as I write this up, to see where, or if, sounds begin to diverge, so far the results are alike, even though the process and values are quite different. I’ve noticed that LFO waveforms might be ordered differently because a program that calls for noise is being assigned a saw wave. This requires investigation. I’ve had a couple of crashes within Cakewalk, and I have heard crackling, but I think this is due to my system being stretched to its limit already, or may be attributable to the less than solid SQ8L. Once I’ve got all the programs off that, I doubt I will use it again. Another quibble is that there are a fair few spelling errors in the in-app quick tutorials provided by Arturia. Nothing show-stopping of course, but I always find that a bit disappointing. On the other hand, the support team moved with alacrity when I emailed them about my program duplication issues. Another neat feature – a clipping warning light in the display. Why wasn’t that in the 1980s hardware? However, I wonder whether the clipping I am seeing is because there is no way to regulate the way the master envelope modulates the final output? In the hardware there is a way to scale this. Overall, I am happy with the Arturia SQ80 V and look forward to getting more out of it.

Thanks for this. I watched it last night (Sydney time); it must have been only minutes after you posted it.

Similar problem here; specialist left-handed luthier way too close: https://www.gaskellguitars.com.au/

That's the best guitar strumming I've ever heard. If only it came with an Auto Fretter too.

I am pleased that you've got a workaround. I suspect that you're still getting errors when dumping from Cakewalk, though. Working with sysex dumps over the last few days I've noticed that Cakewalk dumps a great deal faster than the default settings of SendSX, so your original suspicion that Cakewalk is too fast for your X3 could well be right. I don't have anything to offer on slowing down Cakewalk as I've not found it necessary, but if you figure it out I'd like to know.