Jump to content

newdreamstudio

Members
  • Posts

    37
  • Joined

  • Last visited

Posts posted by newdreamstudio

  1. just an FYI to anyone doing this....

                my Frontier 1.3 Windows installer for AlphaTrack  actually creates this dll :        AlphaTrack.dll

                                       ... not     alphatrack.dll

    Once I sorted that out then the .dll registered fine

    yay

    Rusty

    • Like 1
  2. (SOLVED)    OK... I've been digging into online info about alphatrack and CbB.....  seems like I'd be successful installing

    the 1.3 driver using compatibility mode for Windows 7 (I have Win 10 Pro)....  and if needed I could drag the alphatrack.dll

    into the Shared Surfaces folder....      I'll probably also include the optional SONAR alphatrack  plugin in the install....

    It seems like the AZ Controller is  the most functional way to go but seems a little 'hairy' for me to wrap my head around....

    Who here is using Alphatrack with CbB and how did you go about the install?

    Rusty

  3. Hi folks....  my buddy is several states away and we're wanting to at least converse about a CW project (by phone and headset)

    AND have him be able to hear the output of my MOTU card that's carrying the CWalk out audio.

    Jim Roseberry told me that ASIO isn't really gonna work with Zoom and to try WDM or WASAPI.

    So far no luck....      can anyone help?

    Rusty

  4. sorry .. .we didn't do a screenshot of the error message....

         AFAIK, there are not specific minilab mkii drivers...   I think that windows installs

    drivers when the hardware is first connected.   Sort of corroborating that is that Device Manager sees the unit fine,

    no exclamation mark.    Our plan  is to use Craig Anderton's batch file that enables Device Manager to REALLY show all the devices,

    hidden or not.   We think we'll see a redundant entry.   I know that my friend initially connected the minilab to a hub and subsequently

    connected the unit to a non-hub usb port.           Will report back in a day or two.

    Rusty

  5. Midi device issue: trying to help a friend with this: new Arturia minilab mkii is being seen fine by Device Manager, is registered and activated with Arturia.

    ... in CbB Preferences it shows up as "Arturia minilab mkii (1)

    note the (1)

    when clicking Apply he gets a midi device error. ??

    can't say that I've seen that before...

    Thoughts?

  6. Edit: SOLVED  ... senior moment on my part!   I posted about this on Oct. 23, 2021 and msmcleod answered it:

    Hi folks... my CbB version is a couple of versions back, everything's fine.

    Just enabled my Tranzport after a couple of years of no use, altered the surface config file for Tranzport, named it and saved it.

    Question:  where are the control surface config files saved?      I can't find the file.

    Rusty

  7. Here's what I've done:

             Selected (split) a track

              Did  Region FX>Melodyne>Create Region FX

              Altered the pitch of some notes

               Rendered the Region FX

                               now, on playback, I hear the original notes and the adjusted notes....

            Thoughts?

    Rusty

  8. after uninstalling/reinstalling CbB (wish I hadn't done that!)  the problem persisted...

    so with some googling this morning and seeing that this issue has shown up in the forum several times, 

    I tried 2 things that were recommended:

    1)  unselected my Arturia kybd in preferences/midi devices, closed CbB, re-opened CbB and re-selected it....   didn't seem to work..

    2) with no project open I went into preferences and changed the midi 'driver' to UWP....

    BINGO!     and Yay

    • Like 1
  9. Stylus RMX midi issue:

    Hi !

    My issue: I use an Arturia minilab mkII unit (pads and keys)

    I've had an Stylus RMX template (.ctl_rmx ) for that for a year or two, has worked fine (using the minilab pads for RMX parts)....

    But now:         I can open RMX standalone, choose a multi, load the template, everything works FINE with the Arturia and the standalone RMX.

    But if I close that, then open Cakewalk by Bandlab, new project, insert Stylus, load the same multi, load the template:   I get nothing, even on Arturia Omni setting.

    Interestingly the midi activity light in the system tray blinks when I strike a pad on the Arturia but the midi track (echo on) in Cakewalk shows No midi input when I strike a pad...

    There are no Control Surface conflicts...

    In midi-OX all looks fine with the minilab cc outs

    ??

    Rusty Kirkland

  10. My GUI for standalone Nolly and Plini are fine but my vst versions in CbB have a truncated GUI... not showing all of the right side or the bottom side.

    Minimizing/maximizing the GUI window doesn't cure that.      I don't have any scaling in my Windows 10 Pro 64 bit OS display settings...   thoughts???

    also:   neuraldsp.com site is down?

    Rusty

  11. I requested the 4.1 installer this morning from Celemony and they sent it to me (and asked me to not distribute it)...

    here was Ulf's comment about 4.2:

                 "thanks for your mail. There are indeed a few systems that have an issue with Cakewalk by Bandlab and Melodyne. We’re still investigating this.

    However, the workaround is simply:

    If you come across undetected blobs, simply select all blobs and manually chose the algorithm desired. This should do it for the rest of your session."

     

    Rusty

     

×
×
  • Create New...