msmcleod

JBridge can be useful for 64 bit plugins if there's a compatibility problem between CbB and the plugin, or the plugin is unstable and has a habit of crashing the host. For example, the UJAM virtual guitarist seems to produce clicks & pops even with an ASIO buffer of 1024. The plugins are obviously doing something it shouldn't be doing with one of Cakewalk's threads. Wrapping in it JBridge solves the issue - I can comfortably run them with a buffer of 64, or 32 in a small project. For plugins that have a habit of crashing CbB, JBridge can sometimes help. JBridge may access the plugin in a slightly different way, which may mitigate the issue. And even if it doesn't, at least it will only crash that JBridge process and not CbB itself.

Click on the number of a MIDI track or Instrument Track, then go to Views->Staff View.

Actually, that's interesting... so it might well be worth sending a minidump to @Jonathan Sasor just in case it is something Cakewalk's side. If nothing else, it might point Garritan in the right direction.

This is most probably down to the polarity of your sustain pedal. Most sustain pedals have a polarity switch on the bottom - try switching it.

No, I think the fact it's happening with a particular plugin put it firmly in the plugin's court. Unfortunately plugins are in-process DLL's, so they run in the same process space as the host (CbB). This means any plugin has the potential to crash CbB. In the meantime, if you've got JBridge you could try enabling the "Load using JBridge Wrapper" option (you'll need to reload all instances of the plugin after changing this). This will force the plugin to run in a separate JBridge process. It may behave better there, or at worst, it'll crash JBridge and not CbB.

ok - everything looks ok there. I think the best thing is to get a crash dump from when CbB crashes, and send it to @Jonathan Sasor. We can then look at exactly what is happening. Try to do it with the smallest project possible. Details on getting a crash dump are here:

That error message means something else has the device open.

Can you post a screen shot (ALT + PrtSc) of these dialogs in preferences?

If you take rewire & Finale out of the equation, and just use CbB on its own, does it still crash?

Goto Insert->Rewire Device from the main menu. You should see Finale listed there if you're running v25 or later. When you select it, you'll get what looks like the insert synth dialog - just select it as a simple instrument track for now. Once that's done, making the Finale track the active track (with echo on) should send all MIDI data to Finale from CbB. The transports of both Finale and CbB should be in sync as well - i.e. when you press play in CbB, Finale will follow. I don't use rewire myself, but other users are using it for Sibelius and Notion, so it might be worth asking some of those users how they have things set up. When using rewire, you shouldn't need any other loopback devices. Some of them have commented in this thread:

Have you tried connecting CbB to Finale using rewire?

Why do you need loopMIDI / midiOX out of interest? Can't you just have CbB record the pedal directly from the MAudio keyboard?

It does sound like a MIDI feedback loop to me. I'd double check your configuration with both loopMIDI and MidiOX. Remember that whatever appears on loopMIDI's MIDI output will also appear on its MIDI input (and vice versa). So it's important you don't have Cakewalk listening to both. I tend to create two separate loopMIDI ports, and use one for input and one for output. Also check the echo settings in Midi-OX - even now that confuses me, so it's easy to get it into a feedback loop and especially when you're already using a loopback MIDI device.

Try this: If you're still getting issues, check that you've not got a MIDI feedback loop going on, e.g.: - Check which tracks are echoing MIDI data - Disable MIDI output for synths you're not using MIDI output on - Check the MIDI input filter for MIDI tracks (e.g. are you receiving MIDI from a synth on other tracks?)

You need to make sure "Display Ghosted Data" is checked to see envelopes in the background of clips:

A Delicate Sound of Thunder is one seriously good album (although the use of the Roland JX-8P does kind of date it) - but if there was a "best of" album for Pink Floyd, that would be it.

These are artists I'm pretty sure have influenced me (as opposed to ones I just like): Genesis (and solos - mainly Hackett/Collins/Banks) Rush Yes It Bites Camel ELO Pat Metheny Group / Lyle Mays Pink Floyd Bruce Hornsby The Eagles / Don Henley Chet Atkins Marillion Spock's Beard

I highly recommend these ones - the 8x8 has been rock solid for me: https://www.thomann.de/gb/miditech_midiface_8x8.htm https://www.thomann.de/gb/miditech_midiface_4x4.htm The M-Audio MidiSport range are also good, but seem to be discontinued. Personally, I've not had much joy with ESI MIDI interfaces.

There's a couple of important differences between USB and MIDI 5pin DIN: - USB runs at full USB speed, whereas MIDI 5pin DIN runs at 31250 Baud. This isn't normally a problem for using USB as a MIDI In, but when using it as a MIDI out, it can cause a bottle-neck as it is receiving data from your DAW at full speed but pumping data back out at 31250. This requires it to be stored in a buffer while it's waiting in the queue. Cheaper USB interfaces have a very small buffer, which typically leads to loss of MIDI messages. - USB MIDI interfaces require a driver... and yes, even if you're using a DIN socket, it's probably going to be connected to a USB MIDI interface, but the difference is that dedicated MIDI interfaces (e.g. M-Audio MidiSport, MidiTech, MOTU etc - or the MIDI interface on your audio interface) have drivers that tend to work for a long time. Drivers that come with keyboards or keyboard controllers do not tend to get updated when Windows goes to a new version, as those keyboards get replaced by newer models far more often.

Make sure Mackie Control is the first device in you Control Surfaces list - it sounds like it might be the 3rd in the list. Alternatively, go to the Mackie Control panel (Utilities menu->Mackie Control) and click the "Configure Layout" button on the bottom right. Then turn the v-pot on channel 1 to the right until the tracks show 1-9. Then click the button again, and save your preset.

Notion 6, Finale (v25 and above) and Sibelius all support Rewire, which I think are the top 3 scoring packages out there.

SHIFT-clicking the envelope activates it in the track filter so you can right click and delete. If you've more than one ghosted enveloped, you want to make sure you've picked the right one.

I tend to keep sound design & mixing separate. Get your guitar sound sorted first. TH3 is certainly good enough to get a good guitar sound - part of that chain within TH3 may well include a compressor. Concentrate on getting your guitar track down with a sound you're happy with; worry about channel strips etc once all your tracks are down and you're ready for mixing. There's a good reason for this: You may find that at the mixing stage, the EQ'ing / compression / etc you apply to make your guitar fit in the mix, may make it sound completely awful if you solo it. This is perfectly normal - at this stage it only matters how it sounds in the mix. Most of the time you shouldn't need to go back to TH3 (i.e. try to avoid that). Just do what needs done to the track afterwards to get it to fit in the mix.

All the snap values are key bind-able, so you could easily bind a key to switch between them, or add it to the custom module.

I guess you could do a CTRL + A to select all, right click on a clip then Lock Position/Lock Data to lock all the clips. But to be honest, the easiest way would be to just make a backup copy of your project. Another way would be to take a mix snapshot so you could always go back to the original.