Jump to content

Bill Campbell

Members
 View Profile  See their activity

  • Posts

    64

  • Joined

  • Last visited

 Content Type 

Posts posted by Bill Campbell

    2022.11 Feedback

    in Cakewalk by BandLab

    Posted · Edited by Bill Campbell

    Unfortunately SPP isn't helping with that.  But THANKS for the call out.....  CW now just ranks at 9.6 instead of 10.0 with that minor little niggle.   Of course if they could get that working it would easily be an 11.9 out of 10! 😉

    2022.11 Feedback

    in Cakewalk by BandLab

    Posted · Edited by Bill Campbell

    CW syncs incorrectly to external device.

    Go to Edit / Preferences / MIDI

    Set MIDI Sync to the device you want to send midi sync to...

    1553786539_SendMidiSyncPage.JPG.aedf46030137d331c97816e40d32887a.JPG

     

    Start CW.

    Result:  CW starts device and device and CW sync OK.  Now...

    Go to Edit / Preferences / Metronome

    Set the Record Count-in: to 2.

    728675786_SetMetronome.JPG.c3acc30c8da7d1c040d953253657b039.JPG

     

    Enable a track to record then start CW.

    Result:  CW delays start then sync the external device incorrectly.

     

     

    A little Cakewalk/Relab bug?

    in Cakewalk by BandLab

    Posted

    Just wanted to get you guys thoughts, opinions or advice on this little bug I found in Cakewalk when using the Relab LX480 plugin.   I really like the sound of this plugin but I hate the instability.   So who's a fault here is it Cakewalk, Relab or me.    I know probably me again!... Right?   🙂

    Cakewalk by Bandlab sync bug?

    in Cakewalk by BandLab

    Posted · Edited by Bill Campbell

    On 1/4/2022 at 6:13 AM, azslow3 said:

    To scope, you can use "MIDI loop" driver (so something which send output to input), f.e. loopMIDI, and scope itself which can display what is going on, f.e. MIDI-OX

     

    I guess Presonus developers used the same logic as you. Studio One sends "Start" after count-in, so from device perspective count-in does not exist. And they don't send clock when transport is stopped.

    REAPER sends "Start" at the beginning of count-in and immediately start sending clock, so from device perspective count-in is the same as recording start and so device will start playing in count-in. Clock is not sent when transport is stopped. So build-in clock logic  is troublesome, but there are "workarounds" with VST or script based plug-ins which can do things differently.

    Cakewalk follows MIDI specification with count-in. It sends clock when transport is stopped (but with previous active transport rate, possibly different from current project/position).

    I mean 3 different DAWs use 3 different approaches. And all of them are MIDI specification conform. But I think Presonus way is most "compatible", at least for this century  equipment.

     

    ---------------------------

    From device developers perspective it is unclear how to do things most user friendly way.

    MIDI specification does not help solving the issue:

    • master CAN send clock when transport is stopped, so some do (Cakewalk) and some don't (Studio One, REAPER). And so device, to be user friendly, should assume there are periods of time when there is no clock and switch to own clock (transport is stopped in some DAWs, DAW exits, DAW crash, etc.).
    • the specification has solution for that, Active Sense. When used, device at least knows when the master is still active. So many devices support it (Roland, Korg). Unfortunately that is an OPTIONAL feature, all mentioned DAWs does not support it (I am not 100% sure, but I have not found related options).
    • between "Start" and clock there can be significant time, as in case with Cakewalk. So, device has a choice. It can follow MIDI specification and "freeze" itself till clock is there or user explicitly reset synchronization or ignore the specification.

    So my whole original guess is that Roland has decided ignore the specification when Active Sense is not in use, to don't freeze the device.

     

     

    Tried setting to 5 measures pretty much the same result.   Still starts the TR8S before the count-in is complete.   Also found found a midi scope here...

    https://hautetechnique.com/midi/midiview/

    But I can't seem to get it working .  The app starts fine but it isn't capturing any data.   The quest continues.... 😉

    Update:   Found a strange work-around...    If I change the count it from measures to beats and the set it to 2 beats it counts in 2 beats and then works perfectly.    Go figure...  

    Also I've got the Roland D-05 which has a internal sequencer.    With the count-it set to 1 measure it also starts early just like the TR8s.  So at least that's consistently broken...

    Cakewalk by Bandlab sync bug?

    in Cakewalk by BandLab

    Posted

    No 'noise' at all.  Thanks for the thoughtful post.   I'll definitely try changing the count-in to 5 and see what we get there.  I wonder why Cakewalk would send a "Start" message before the count-in?   Shouldn't it just send nothing?  The receiving device wouldn't care about the 'count in'.  Right?  It would just need to know when to start the sync.  So CW should just do its count in and then send a 'Start' command.   I guess...

    Of course I guess all of this is just guess work without some sort of scope of the midi messages being sent.   Maybe there is some software out there that does that?.. Hmmm...  I'll look for that also...  Thanks a lot.   You've got me thinking about this differently.  🙂

    Cakewalk by Bandlab sync bug?

    in Cakewalk by BandLab

    Posted

    Thanks so much for your response.  I really wanted to know if these was a scenario where this worked as expected.  So I'm glad to hear that it works with the SR-16.  I might even consider picking up an SR-16 just to play.  😉 

    It does seem weird to me that the issue only seem to happen with the count in enabled.   I would think that the midi messages would be the same with that on or off.  So either it would always work or always fail.  At any rate its not the kiss of death for me just a minor irritant.

    I was at a friend studio last weekend and he uses Studio One and he enabled the count in there with the TR8S and that worked perfectly for him and of course he loves to poke fun at me for CW's little idiosyncrasies.   I still maintain its the best DAW though.

    Relab LX480 plugin locks up Cakewalk?

    in Cakewalk by BandLab

    Posted · Edited by Bill Campbell

    Thanks for the replies.   The issues seem to be intermittent.  But it's still good to hear that some are having success with it.   I did find something very strange if I initially insert the plugin into the Prochannel and then drag it from the the prochannel to the channel fx it work fine.

    Relab LX480 plugin locks up Cakewalk?

    in Cakewalk by BandLab

    Posted

    Just wondering if anyone else had experienced this issue.  I recently bought this Relab LX480 plugin and while it sounds great is occasionally will cause Cakewalk to freeze completely and I have to kill Cakewalk from task manager.   This seems to happen more often when its inserted into a tracks fx and less often when inserted into the Pro channel.

    I really like and I'd like to continue using it if I could figure this out.   Thanks all...

     

    image.thumb.png.e19689a88e151c28d2fc61ba732d66fc.png

×
×
  • Create New...