msmcleod

I would second this. I've got both Focusrite Scarlett and Behringer interfaces, and the mic pre-amps (and as a result, the guitar input) is much better on the Scarlett. The Behringer pre-amps sound very harsh to my ears in comparison to the Focusrite.

We did see a case where this was happening when there was a zip file in the same directory as the .cwp that couldn't be opened by Windows explorer. Either moving the zip file, or moving the cwp file to a different folder fixed the issue. Unfortunately the media browser within Cakewalk is basically a Windows Explorer shell component (i.e. it's Microsoft's). When it's first constructed, it looks at the current directory - so if there's zip file that it can't deal with, it gets upset.

You have to ensure you've used each plugin at least once within Cakewalk since enabling the MackieControl surface. When a plugin is inserted into an effects bin, its parameters are remembered and written out to genericSurfaceParameters.xml when you shutdown Cakewalk. It's this file that C4Mapper reads to get the list of plugin parameters.

@Patrick Azzarello - can you send the file you're trying to import to @Jonathan Sasor so we can take a look at what is going wrong here? Cakewalk should support this file format.

I use the Studioworks Reference 4 as a plugin, alongside IK ARC 2.5. I put both on my master bus and only one is active at a time, with the other one bypassed (i.e. I use ARC 2.5 for speakers, and SWR4 for headphones). My Windows audio device is set to the onboard device, not my audio interface. I really only use it for YouTube / Groove3 tutorials. Also, I use other audio outputs other than those going to speakers/headphones, so I don't want either ARC 2.5 or SWR4 on anything but my master bus.

Yeah, a breve is 2 whole notes. A semibreve is a whole note, and a minim is a half note. I don't think I've ever seen a breve in any sheet music... maybe it's reserved for orchestral triangle players!

Back in the old days, I used Music-X on the amiga, and I used to manually insert my program changes & CC events ( normally volume, pan, expression, pitch bend & modulation & sustain pedal ) at the start of every "section" (e.g. intro, verse, chorus etc). I'd bounce the whole sequence down to an Alesis DataDisk, and then take it to the studio and plug it into the ADAT BRC. Because the program changes / CC events were specified at each section, I could start the ADAT at any point within a song and it would correctly pick it up and start playing in sync almost immediately using the correct sounds / CC settings. For me this just became a necessary part of my workflow with MIDI. It's not something I worry about as much nowadays with VSTi's, as they tend to have their own track and pan/volume are generally controlled on the audio track. But if I'm using some Kontakt instruments, I still put pitch bend/modulation events at the beginning if necessary, and I'm extra careful about sustain pedal events in piano parts when cutting / pasting.

According to the MIDI Spec: Start Byte Hex Binary Description 1 FA 111 1010 Status This message is transmitted when the Play or Start button of the master sequencer or drum machine is pushed. Once the message is received, the device resets its internal song position to 0 and begins to play at the reception of the next Timing Clock message. There should be a delay of at least one millisecond between the transmission of the Start message and the Timing Clock message to give the receiver time to respond. The receiver, however, should be able to start immediately, even if the delay is less than one millisecond. This is exactly what Cakewalk is doing. The drum machine should not be starting until it receives the Timing Clock message, which isn't sent by Cakewalk until the count-in has finished.

Cakewalk is Windows only.

This should work, but not quite exactly the same as in the PRV due to the Arranger/Articulations using a different UI technology to the rest of CbB. The trick is to stop short of the edge, and it'll scroll:

Eli Krantzberg has a great tutorial on using BIAB for Songwriting on Groove 3. I loved the different methods he showed of generating ideas, and using parts from what might seem disparate styles in your existing session. To be honest, I've never been that into the middle-of-the-road styles that BIAB generally has, but it's amazing what you can do by using just one part out of context. Here's the course overview: Tutorial 1 - Creating a Melody (7:25) In this first video, use the Band-in-a-Box Melodist function to create a melodic idea for a chord progression and arrangement in a DAW. Tutorial 2 - Exploring the Melodist Maker (10:26) Learn to use the Melodist Maker to create a custom Melodist and hear how it interacts with different styles. Three separate melodies are generated and brought into the DAW, where they're edited together to create a single, unified melody that matches the chords and arrangement. Tutorial 3 - Using the Chord Wizard (7:31) Next, discover the Band-in-a-Box Audio Chord Wizard and hear how it's used to generate chords and tracks supporting a melodic vocal idea for a song chorus. Tutorial 4 - Creating Harmonies (7:15) Explore Band-in-a-Box's ability to generate doubling and harmony parts from existing audio. Hear examples on vocals and guitar! Tutorial 5 - Creating a Guitar Part (7:27) Learn how the Band-in-a-Box MultiRiff feature is used to create multiple variations of a guitar part - based on your chord progression and rhythms - with custom shots and pushes. Tutorial 6 - Creating Better Harmonies (7:40) In this video, discover Band-in-a-Box's advanced harmonizing options, including the ability to export MIDI conversions alongside the generated audio. Tutorial 7 - Creating a Piano Part (8:19) Learn how to have Band-in-a-Box create a fully fleshed out piano part based on your original simple chords, in your choice of musical styles, using RealTracks. Tutorial 8 - Creating an Arrangement (10:36) See how the Auto Generate Chord Substitutions and Auto Generate Chord Reharmonization functions can be used to reinvigorate a simple melody, with examples in various styles. Tutorial 9 - Creating a Solo (11:24) Next, explore the Band-in-a-Box Soloist Maker and its ability to custom design solos and fill lines. Tutorial 10 - Creating an Intro (8:50) Hear the Band-in-a-Box's intro generating feature in action as it's used to create inspiring intros to match specific styles and chord progressions. Tutorial 11 - Creating a Chorus (6:31) In this video, see the Band-in-a-Box automatic generation feature in action, creating a chorus that harmonically and stylistically matches the preceding verses. Tutorial 12 - Generating Random Ideas (5:47) Finally, learn how Band-in-a-Box is used to generate random ideas based on your user input. Individual parts from multiple ideas can be used either independently or in combination as the basis for songwriting inspiration!

This isn't a bug - Zero All Controllers is the MIDI standard for dealing with this. The only reason people have started disabling this is due to Native Instruments hijacking CC #1 (modulation) for things like cut-off freq / volume. Why they did this, who knows, but it was a very bad idea. I've just got used to pressing and releasing my sustain pedal when this happens, or hitting the panic button.

FYI... Crotchet = 1/4th note Quaver = 1/8th note Semi-Quaver = 1/16th note Demi-Semi-Quaver = 1/32nd note Hemi-Demi-Semi-Quaver = 1/64th note. I could go on... but it gets silly!

Once or twice, although only when discussing sheet music. Demisemiquavers are far more common.

As a user, my #1 reason for using CbB is its support for the Mackie C4, which is a major part of my workflow. Most other DAW's don't support it, and those that do don't support it properly - i.e. you have to turn the pots several times to go from min to max, whereas within CbB you just turn it quickly for big increments and slowly for small ones. In fact, this bad implementation on other DAW's was the #1 reason for people not buying the C4, leading to Mackie eventually discontinuing it.

I used to use the Yamaha MT1X, then the Yamaha MT8X. I found the best cassette for these was the Maxell XLIIS. I did use the Maxell UDII for general listening though. It was a really good cassette. In fact my only reason for not getting a replacement cassette based portastudio was because you just can't get the cassettes any more.

We've had this issue reported before through BandLab support, again with a TR-8S. From what I can tell, from Cakewalk's point of view it's sending out the correct MIDI messages as per the MIDI specification, and certainly with my Alesis SR-16, it's behaving exactly as it should with count-ins. Unfortunately I've not got a TR-8S to play with, but it does look like the TR-8S is not adhering to the MIDI spec in this case.

1. You can only do this from the FX Browser, not the console view. 2. You can't, although I'm sceptical as to the usefulness of this in practice. It's unlikely you'd use exactly the same fx preset for any significant number of tracks. If you do want this, you can CTRL + drag the effect from one track fx bin to another track's fx bin.

You can also put an effect on multiple tracks by dragging from the browser, then holding down CTRL before you drop. Just remember to press CTRL after you've started dragging:

It might work, but bear in mind a virtual machine will be significantly slower, and there's no guarantee that USB emulation will work. A dual boot might be a better solution... although good luck with getting Windows 7 to actually install. The last time I tried to install Windows 7, it wouldn't activate due to Microsoft retiring telephone activation for Windows 7.

Just a heads up - I'm getting a lot of crashes with the BIAB 2022 plugin. This doesn't seem to be a CbB issue, as it crashes Reaper too. Studio One 5 doesn't crash, but frequently pops up error dialogs. I've raised a support ticket with PG Music. The crash only seems to happen when the UI is open, so you can mitigate the issue for now by turning off the audio engine before opening the plugin UI. You can switch off the engine by clicking this button: If it's white as shown above, this means the engine is running... so just click it to turn it off before opening the BIAB plugin UI.

This was reported a few days ago - it has been fixed for the next drop.

Export presets are meant to be global and don't save any project specific information, so anything to do with selection or specific category items aren't saved as part of the preset.

Apologies... it was Reastream I was using. I'm not sure what the best solution here is. You could try using Reaper as a bridge between CbB and Jamulus via Reastream. Other alternatives could be VB Audio ASIO Bridge, or ASIOLink. Any solution is going to introduce extra latency though.

But before that it was called Byzantium...