Allow QU-Drive playback routing

Forums › Forums › Qu Forums › Qu feature suggestions › Allow QU-Drive playback routing

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • 2015/10/27 at 10:12 am #51701
    Profile photo of ZueriZueri
    Participant

    Right now it is not possible to change to routing of QU-Drive playbacks to other inputs than 1-18. To use it for virtual soundchecks with other QUs than 16 this would be really useful. This feature would allow us to train our volunteers letting them to use a Virtual Sound Check mode to mix where the channel setup would be identical to our LIVE setup.

    And to make it even more useful it would be perfect if there is a way the recording would remember the source channel.

    I think @tjmcsorley would also be happy with such a feature. Maybe others to?

    2015/10/27 at 1:47 pm #51703
    Profile photo of Anonymous
    Inactive

    Whilst we’re at it…

    Grabbing a time stamp from a QuPad for recordings.
    Naming files per channel name (Maybe 01Kick etc.)
    Naming projects

    2015/10/27 at 3:39 pm #51704
    Profile photo of Anonymous
    Inactive

    Oh, and allow fewer than 18 channels to be recorded/played 😉

    2015/10/27 at 4:07 pm #51705
    Profile photo of AndreasAndreas
    Moderator

    Oh, and allow more than 18 channels to be recorded/played (if technically possible) 😉

    2015/10/27 at 4:48 pm #51709
    Profile photo of Anonymous
    Inactive

    Lol – yes, that too, but at least not having to duplicate tracks to lay them down onto a QuDrive would be a benefit – and is pretty clearly technically possible. I can’t imagine that laying down more than 18 tracks is impossible – it does up the ante on the device characteristics AND simultaneously reduce the available buffer duration on the QU – double whammy there…

    2015/10/27 at 4:59 pm #51715
    Profile photo of AndreasAndreas
    Moderator

    Sure, I’ve added that primarily for rhetorical purposes… 😉
    Not sure where the 18 track limit originates from and how the QuDrive is implemented. Maybe its based on ICE-16, maybe 18 channels because it started on Qu16, maybe a physical limit of the used USB implemetation, maybe its completely hardcoded into some FPGA.
    My guess is, that if it would be easy to simply skip channels which do not exist as WAV file, it already had been implemented.

    2015/10/27 at 5:12 pm #51716
    Profile photo of Anonymous
    Inactive

    If it was writing a single 18 track wav then I’d agree, but I can’t imagine it being too hard to read from /dev/null if a file isn’t there (yes, I know it’s not *nix, but the concept is the same)

    2015/10/28 at 11:23 am #51738
    Profile photo of ZueriZueri
    Participant

    Agree, fewer than 18 channels for record/playback would also be useful (but only together with the changed source / destination routing).

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.