Reply To: Date and Time

[Anonymous]

Apologies in advance if the below reads in a disjointed fashion – I’ve ended up with far too much copy and paste to rearrange the order of things…

There is an OS of some sort. IIRC @Nicola has confirmed that it is ground up built by A&H…
It might be custom, it will almost certainly be an RTOS,,,

Qu runs embedded software written in-house by our R&D team in Cornwall, UK.
It is not based on any third party operating system.

At the moment all the files from QuDrive end up with the same name, in the same directory (since I clean and reformat regularly, as recommended) and with the same timestamp. That’s a pretty good combination to ensure data loss IMHO.

To be honest there are various things I’d like to change about the QU handling of QUDrive. Don’t get me wrong – it’s absolutely brilliant, but there alternatives to the timestamp which would do the same/better job….

I’d like to be able to name sessions and tracks (e.g. …/BobWedding/QU01.Bass.wav). (Tracks could even take their name from the channel name, and give their name to the channel when played back?)
I’d like to be able to do seamless splits (maybe in one session we could have QU01.01.Bass.wav, then QU01.02.Bass.wav would take over without a dropped sample when a softkey was hit – allowing songs to be split, at the moment the reloading of the last recorded session and subsequent re-arm takes far too long).

I’d like to be able to record fewer than 18 channels, and play back fewer than 18 channels.
I’d also like to be able to control QuDrive from the QuPad.

Don’t get me wrong – QuDrive is absolutely brilliant, but there is always margin for improvement, and as a software engineer by trade (OK, an ex software engineer, although I still get dragged back) the above don’t *feel* like huge changes – although this is a custom embedded system, so all bets are off as to the actual complexity 😉