Korg Forums

Oh thank god, found a backup that I'd accidentally saved to the "wrong" place from last month.

Prologue Librarian seems to live or die by the Korg driver...

I uninstalled the Korg Driver because I was having problems with Logic. This fixed most of those problems. Then I used Prologue Sound Librarian while I had some synths connected and a track playing. It was taking longer than usual. My Sub 37 started to make weird sounds so I stopped the track and ...

Yeah, I literally finally got my studio together last week so suddenly the Prologue's being used kind of as a module. So doing stuff from an AT-enabled Nektar Panorama has revealed a few things about the AT: - it works kinda nicely on resonance - it works kinda nicely on anything that needs the ...

I tried this yesterday with firmware 2.00 and it seems to be the default behaviour. I can't remember how it used to be now...

Well that'd explain why we can't output the timbres separately...

(also I agree with RA here; this is not what "multitimbral" means)

What do you reckon MIDI AT foretells?

- A Prologue XD?
- A Prologue XD module?
- A programme of factory keyboard upgrades to enable AT in existing Prologues? (ok, I'm dreaming)

This wasn't in the release notes, but I'm very, very happy...

Nope. They're brilliant. Get them.

When I ran the 2.00 update on my Minilogue, the oscilloscope framerate went way down. Is that the case also here? EDIT: No. It is not. I'm just not that bothered about any of the updates except the asterisk showing previous values. Hey, great, aftertouch from an external keyboard and I still can't ...

You can always hit EXIT to show you the patch you're on.

I think one of the menus also has an option to turn off the oscilloscope but I don't recall if that has the effect you want. It might.

Local's permanently off

(I find that using the contact form is a better way to get in touch – they're normally pretty responsive that way, or for me in the UK emailing support@korg.co.uk)

Ah ok. I'm sorry, this sounds like a return to me. I guess you've been in touch with Korg?

Did you try just the voice update again? And can you re-flash with 1.32?

In my experience it's more likely to be the software side that's the issue. You don't say what software you're using, but a year or two ago I was where you are and these are the things that tripped me up with Logic Pro X: - Are the MIDI channel for the track and external instrument plugins the same ...