Xoo

I remember this change - it feels like it's had unintended consequences and the Platinum method was preferable (personally, I don't like it and haven't since it was introduced) and should be rolled back.

The first is the final (ha!) version of Oumuamua Returning (thanks for the suggestions from people here): https://www.bandlab.com/xoospacemusic/oumuamua-returning-ab48d9d6?revId=9f1888c5-fa9e-ec11-a507-0050f280e91e It has remixed drums, more ear-candy synths and an OTT guitar outro. The second is a piece inspired by a conversation with @Lord Tim and @Wookiee and is called Last Orbit of Sol. It's a collaboration with Crater 93 (see https://cosmonauttransfer.bandcamp.com/music for more), who I think has done a cracking (re)mix of my original piece: https://www.bandlab.com/xoospacemusic/last-orbit-of-sol-c253a178?revId=1821a10e-70a9-ec11-a99b-501ac512ad32

I spent *way* too much time on these as a kid ?

Colossal Cave(s).

So a 128GB drive with 128GB free works fine; a 1 TB drive with the same free doesn't? That makes no sense, which is why talking in % free is illogical. And if your project needs to suddenly grab that much disk space on opening...something is screwy. It just doesn't happen.

% free is unhelpful. 15% on a 1TB drive is a lot of space; on an early 64GB SSD...not so much. I don't buy this anyway: if you have enough spare space, you have enough spare spare, whether what is needed is 1GB,1MB or 1 byte. Windows 10+CbB takes up a fairly small amount of disk space anyway if you're keeping temp folders etc clean: I have those plus other media apps and some Office components installed and it takes uo no more than 30GB. Just don't keep all your data on the Windows partition, not that we do that anyway, do we?

A tri(quad?) state for the FX button might be nice: all on, fx. bins off, pro channel off, all off.

Reminds me (and some of your other stuff) of "free festival" bands from the 90s like Senser. No bad thing in my book.

Devil's advocate question: if indeed the difficulty is caused by driver model support, would you prefer mono external support and dropping driver modes other than ASIO or not getting mono support and retaining other driver mode supoort (eg. WASAPI)?

My guess would be an overwrite of a core C++ library. There's a thread here where Noel posted a link to a consolidated C++ library download/install. I reckon that getting and running that after the driver update may well put things back working again.

Surely complex time would be 7i 8 ? With apologies for the maths joke.

Isn't this kind of situation exactly what cloud computing is for? Scale up when you need it, then down when you don't. Poor planning as this should have been expected.

@antler Thanks for that!

So thank you to everyone who listened and made suggestions, which I then proceeded to ignore ? But they did make me think about different options which I wouldn't have done otherwise. The final(?) version is here: https://www.bandlab.com/xoospacemusic/oumuamua-returning-ab48d9d6?revId=9f1888c5-fa9e-ec11-a507-0050f280e91e

Also check there isn't a highly latent plugin in the affected projects.

It's happened to anyone who's used a computer...bugs, hardware problems, power failing...

But automation can't (easily) do some of those things - try inverting one side of a stereo audio track/clip (you need a plug-in like Channel Tools). But I don't think that those should be split out into separate functions - I'd just rename the menu item to something more "obvious" (Channel Tools? :-)).

Does right clicking on the volume widget in the controlling MIDI track and choosing "Disable Control" not do this for CC 7? Ditto MIDI Pan for CC 10?

I love little anecdotes like this. I always find it quite amusing how even members of "big" bands have jobs like this (we used to share rehearsal space with Supergrass, and we found out that their drummer (I think) carried on with his previous job as a decorator/gardener (I forget which now - it was a long time ago!)...).

Just wanted to thank people for their feedback - I've added and tweaked quite a bit of it now. I need to redo the guitar part(s) so that it's right now, but I've hurt my wrist, so playing at the moment for any period of time is painful. Watch this, ahem, space ? UPDATE: Thanks to the wonders of ibuprofen (other painkillers are available), I have an updated version - hope you like it (I'm not sure about the outro guitar part to be honest): https://www.bandlab.com/xoospacemusic/oumuamua-returning-ab48d9d6?revId=b4a71e8b-bd99-ec11-a507-0050f280e91e

Annoyingly catchy ? The change in instrumentation both throws and intrigues at the same time.

It was indeed Transitions 5 Ultimate which I got "free" with MSP 16 - any reference to them in an existing project (in MSP) failed, as did trying to add them to a new project (even though they appeared in the transition menu in MSP). Even after a reinstall. Not sure what happened, but my drag and drop reinstated them, so all good in the end.

Not too bad. There are obviously some differences (that still get me a couple of years after getting MSP16!), but it's not a huge jump in how things work.

Good deal for NewBlueFX. Note that I already had NewBlueFX Transitions installed, and the new NewBlueFX install broke it. The solution here anyway was to drag the Transitions folder out of the Common Files\OFX folder, run MSP 16, close MSP 16, move the Transitions folder back into Common Files\OFX and re-run MSP 16. I'm getting a crash on close sometimes with MSP 16 now which I never did, but I'm not sure if it's related to the NewBlueFX installs.

They are in mine too ?