scook

In session drummer a preset (aka program, the files with prog extension) consist of

• kit files - sfz files
• pattern files - MIDI clips

sfz files contain information mostly about when to play what sample and where the samples are located. sfz files are plain text and may be viewed in any text editor.

The default location for SD3 samples are kit specific folders under C:\Program Files\Cakewalk\Vstplugins\Session Drummer 3\Contents\Kits

Addictive Drums uses proprietary file formats and has no facility to work with 3rd party files. It is their drum kits or nothing.

Installing Session Drummer depends on which DAW it came with. Through SONAR X3, the advanced install options permits installation of individual plug-ins. The last series of SONAR did not have an advanced install option instead opting for breaking the installer into smaller units. For most this means installing the DAW then running the individual installers as desired. There are some detailed discussions about legacy installs. Nothing has changed since thing forum was created. Here is a link to a legacy install thread

24 minutes ago, Shane Taylor said:

Is there somewhere else I need to enable them or make them shown?

Not that I know of.

I just checked tested with a wav adding markers in SoundForge.

Importing the file caused the markers to appear on the time line and in the marker view.

Allow importing of WAV File Cue Markers

1 minute ago, xtenkfarpl said:

Would be more of a 'request for enhancement' than an actual bug, I suppose.  It may 'work as designed' but the design is deficient IMHO.

But what the heck, life's too short.  I've got a workaround and songs to get down, I'm outta here.  Have a good day!

That's right

Looooong standing feature request with several workarounds

File a bug report if you wish.

Just know the current MIDI routing works as designed.

The traditional reply when wanting to use the same recorded data on multiple tracks is linked clips.

Then came routing solutions with virtual MIDI cables and plug-in exploits.

Here is an even more exotic routing example using the Step Sequencer to drive the Matrix view

When documented controls seem missing the first place to look is the workspace setting.

Either select a setting with the appropriate controls, create a new workspace or set workspaces to None to disable workspaces and see all the controls.

11 minutes ago, xtenkfarpl said:

I think, frankly, that this is a bug.  The 'option' to select the first synth as input to the second is bogus: it doesn't work.

Time for a bug report?   Meanwhile, I guess we are back to copying the MIDI track in as many versions as we want doubled synths, and re-copying any time we make a change.   Sigh....

There is no bug.

I do not recall if any of the synths bundled with CbB are capable of sending MIDI data (I don't believe there are any) but there are quite a few free and paid plug-ins that do.

Distributing MIDI data from instrument track to multiple instrument/MIDI tracks works when using one of them.

The method has been described on this and the old forum forum multiple times

Here is an example

While I prefer using a plug-in, a virtual MIDI cable such as LoopBE1 works too. Some virtual cables add too much latency though.

One does need to manage input echo so it may be easier to disable Always Echo Current MIDI Track and manually set input echo as needed.

According to the preset, the samples are from a TR808.

If you have

• a Cakewalk user account created during 2014 through 2017 and 
• purchased a version of a Cakewalk DAW with a downloadable installer containing Session Drummer 2/3

Download and use Session Drummer or at least grab the samples from the plug-in. 

Clip start and length are available in the clip properties inspector

Strum Session 2 was added to SONAR Platinum in Jun 2015. I believe it was added to the Platinum Instrument Collection installer.

GS-2, the full version was never bundled with SONAR

Strum Session 2 required no special activation. GS-2 activation information, if any, would be listed on your AAS account.

5 minutes ago, Hannah said:

@Mannymac ASIO drivers don't work with my version of cakewalk. It immediately freezes and crashes Cakewalk.

The RealTek ASIO driver is not suitable for DAW use.

Set CbB to use one of the WASAPI driver modes.

17 minutes ago, xtenkfarpl said:

Still not working for me.  I followed the steps exactly as far as I can tell, but I get no output from the second soft synth.  In fact if I select any track other than the first, nothing. 

Is there some "obvious" step that I'm missing?

Fancy routing usually means manually setting input echo on tracks (the button right of record on each track) in order to hear the incoming data.

Try disabling Always Echo Current MIDI Track in preferences and manually set as needed.

6 minutes ago, David Ageev said:

Enabling "Do Not Intercept NRPNs" setting didn't work for me. But thanks again for the tips about non-note data !!!

After changing this setting did you restart the project?

If the synth engine shuts down, usually at least the project must be restarted to get the synth playing again.

Problems with 3rd party MIDI files and Studio Instruments (or any Cakewalk sfz engine synths) almost always comes down to unexpected data shutting down the sfz engine.

IIRC, by default Guitar Pro adds some non-note data to its MIDI file exports that the Cakewalk sfz engine synths can't handle. There may be some configuration in Guitar Pro to skip this part of the export.

Otherwise, the fix in CbB is either clean up the data using the Event List View and/or enable "Do Not Intercept NRPNs" in the SI Plug-in properties shown below.  The data is most often at the beginning of the file before the first note.

Have not used the plug-in but here are some general comments about how to setup plug-ins that generate MIDI data

10 minutes ago, GreenLight said:

Are you sure it hangs on the load of project #2 - and not just after quitting project #1?

I've had some buggy plugins cause Cakewalk to crash just after the project has been closed. I'm thinking it might be possible that there's a buggy VST in the first project... just an idea.

 

Could be

32bit plug-ins should be at the top of the suspect list

If the device works on new projects and does not work on old projects, make sure the old projects were created at a sample rate the device supports.

Most audio interface support several sample rates but the GP-200 only support one sample rate - 44.1kHz. 

If the old projects were made at a different sample rate, they will either need to use different hardware or the project sample rate will need to change for the GP-200.

If there is no audio in the old projects, changing the sample rate is as simple as changing the Default Settings for New Projects in Preferences > Audio > Driver Settings.

If there is audio in the projects, see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.05.html#1117623

34 minutes ago, willem windig said:

Thanks. I will look into it. Since  XLR does not plug in computer I assume you need a cable to convert to headphone plug?

Most purpose-built audio interfaces (link provided to Sweetwater as an example of interfaces available) provide XLR or 1/4" connections suitable for microphone use.

In general, most users ultimately purchase at least two special pieces of hardware in addition to a computer for DAW use

1. an audio interface
2. a MIDI controller/keyboard, drum kit or other MIDI input device

Strictly speaking they are not absolutely necessary but really can make a difference in the DAW experience.

USB microphones are a combination of a microphone and audio interface in one. They are not a good choice for DAW use if one also needs to record physical instruments and MIDI. This is why most recommended purchasing microphones and audio interface separately. USB microphones when creating multi-track recordings from a variety of sources.

20 minutes ago, Gui Garibotti said:

Do you know how to display only the notes of the selected midi pattern in Cakewalk?

There is only one MIDI editor that works with a single clip at a time, the Step Sequencer view.

All of the other MIDI editors display data at the track or entire project level.

If working with multiple clips in the PRV is troubling enable "Show Clip Outlines" in the PRV View menu.

If that is not enough, here are a couple of ways to see only one MIDI clip at a time on the same track in the same project:

• mute all clips in the track except the one to edit and set Hide Muted Clips in the PRV View menu
• use the inline PRV and put each clip in its own take lane

If the program can with an installer, run the uninstaller. Note: Most Windows uninstallers leave user modified files behind. These will need to be removed manually. 

If the program did not have an installer, manually remove the plug-in binary from the VST scan path along with any associated files. 

After the plug-in is removed, the next time the CbB VST scanner runs the plug-in will be removed from the CbB VST plug-in inventory.

6 hours ago, Pete Ohlinger said:

You nailed it- the same file exported, when I import it back in, the stereo imaging is still there.

This is a good test.

6 hours ago, Pete Ohlinger said:

So... what the heck is happening to it when I play it from another source?

The two leading candidates are

• the playback is hyped some way (Windows enhanced audio, bass boost etc.) - adjust the playback software 
• the mix does not translate well - revisit the mix in the DAW and re-export.

1 hour ago, Gui Garibotti said:

In the "test2" pattern I am still seeing the notes from the "test1" pattern.

I can't speak FL Studio but maybe it would help to understand what you have from a CbB perspective.

The two images show two separate and independent MIDI clips in a parent track in the track and piano roll views respectively.

It looks like Show Clip Outlines is disabled in the PRV View menu so there is no indication in the PRV that the data are in two clips.

The only interaction between the two clips is that they are in the same track. Other than that, the two clips have nothing to do with each other. 

While all MIDI data is stored the projects, clips may be exported as standard MIDI files through either the menu options or dragging clips to Windows or the media browser. MIDI data may also be directly copied between projects.

Have you tried importing the exported wav file into Cakewalk and listening to it?

It might help to see an image of the export dialog for the wav file.