Xoo

I do too...that doesn't mean I can remember the name of it 🙂

And attached are my 3 updated FX images. To "fix" the red issue I see, all I did was change the "Bypassed FX Name" coluur value to be the same as the "FX Name" colour you'd already chosen (C7CDDC). Looks perfect to me now.

This is what PRV looks like when white (all other things being equal): The grid lines are the same colours and look "balanced" for want of a better word.

I did wonder if they were non-theme but didn't have time to check. On a white background, they look good, on a dark one, not so much. Very annoying that some things aren't themed (the track colours being the most annoying!). What I've done for the FX widgets is to export your images as png's and drop their transparency to about 60%. The green then looks marvelous, the red doesn't, so I need to look at that. When I've got some that work, I'll pop them on this thread so you can take a look and see what you think.

Thanks - I couldn't remember which MFX it was!

Can you not make use of one of the MIDI FX {MFX) to compress the MIDI velocity data (non-destructively too)?

I love this too with 2 exceptions: - The PRV (and you're not alone with this - most PRVs seem to be dark) is unusable in my opinion - too many lines, too many colours!!!! Do a pale/white PRV background and it'd be great. - The colours for the mouseover and disabled settings on FX bins are too saturated given the text colour making the text hard to read:

Assuming you have a multicore CPU, do check that the following setting in aud.ini is set to 1: AllowOfflineRenderMixThreads=1 The help file has this the wrong way round, so if you've set it to 0 (intentionally or otherwise), you'll be using just one core for exports.

Possible failing drive (or cable)?

Likely because of a Workspace (the feature formerly known as Lenses).

That's the scook quantum effect - it doesn't work until you've read his reply 🙂

Quick'n'dirty response: these are all software protocols that layer above your network protocol (eg. TCP/IP) driver for Wide Area Network support (eg. PPTP = Point-to-point tunneling protocol). This could route through your wi-fi interface, but could also through a wired ethernet adapter. They're not loaded if not used (and most are probably are very rarely used nowadays).

Z-drag and Alt-Z to undo zoom all the way...

Ditto - GT610 IIRC which isn't supported by the latest nVidia drivers. I don't want to have to drop £40+ to replace a video card which is more than adequate just to update Windows...I think it'll probably get resolved but I'm in no rush 🙂

None of those WAN* drivers are wifi.

Annoyingly not mentioned in the key bindings dialog...wish I'd known about this! Note also that "=" on this key works, so you don't actually need to press shift.

Captain Codpiece (double pun there)?

It's not but I'd support this - it slows down workflow too much now.

There's no obvious Leslie FX in Dim Pro, but a lot of the organ patches I have seem to have the element FX set to Autopan. Disabling that makes it less Leslie-y, but doesn't seem to eliminate it completely.

There are a few of them that I use regularly: Valve Driver (really good for dirtying up a guitar sound and giving it a bit of bite), Tempo Delay (not that I'm short of delays otherwise, but it's different enough), the Analog Phaser (ditto) and the PEQ2B Equaliser (a great Pultec emulator).

Ctrl-D for duplicate.

Can't repro here either. Are you applying during playback or when playback is stopped?

Might be nice if they gave you a clue which device(s)...

Mine's turned off as well, but I took an image before manually trying this (I've been bitten too!).

I get this error (0xc1900223) on trying to run the update - after running through the "getting ready" phase, which seems to mean "nothing wrong, try again later". Helpful, eh? But on re-opening the Update settings tab, I now get the same as Erik above with a nice little picture. How cute.