-
Posts
9,681 -
Joined
-
Last visited
-
Days Won
27
Everything posted by scook
-
Quality has a cost. If sampled acoustic instruments are what you are in the market for look to Kontakt. There is a free player with a few instruments. Since you are using soundfonts now there are a couple of free solutions TX16Wx and sforzando that may work. While not dedicated sf2 players they claim to load/play the format. Here is a thread about free instrument plug-ins
-
Looks better than the first image. Select the tracks, CTRL+SHIFT while dragging the edge of one of the selected tracks
-
To create an effect bus and send several tracks to it, try selecting the tracks, hold down the CTRL key and right-click one of the selected tracks and open the Send Assistant, in the Send Assistant, create a new bus and add the effect Using the CTRL key creates a quick group which allows an action to happen to selected tracks. Still may want to open the bus area to see what is going on there.
-
The track inspector shows a track strip and a strip for the track output. In the image above there is a reverb plug-in on the master bus and a send to another bus in audio track 1. Not sure that is what you want to do. It might be useful to display buses. To do this, click the button near the bottom of the image pointed to by the red arrow Any number of tracks may be sent the same bus/ Once a bus is created, it will be available in audio/instrument track send and output drop downs.
-
While I have not seen this particular failure point or any scan load errors in some time, when ever I had an error scanning a commercial plug-ins there was never a problem taking the "Enable Plug-in" option. If the "Disable Plug-in" option was selected, to re-scan the plug-by open VST Settings in preferences and select "Manual Scan" from the scan options drop down check "Re-scan Failed Plug-ins" option, click the Scan button once the scan is complete uncheck "Rescan Failed Plug-ins" reset the scan options drop down to your preferred setting. While in preferences make sure the "Scan in Sandbox" is enabled. IIRC, it is the default.
-
Try saving the project as a MIDI file. IOW, from the main menu use File > Save setting the file save as type.
-
To insure projects may be opened with SONAR older than Oct 2015 avoid using patch points and aux tracks.
-
From the media browser drag and drop the original project cwm file into the radio edit project. Mix scenes (cwm extension) are stored in a MixScenes folder where the project is stored.
-
From the description above it may be too small an audio I/O buffer setting. I did not listen to the audio in the OP. If running ASIO driver mode use the software supplied by the company providing the driver to adjust the buffer setting. All other driver modes use the buffer size slider in the Mixing Latency section in preferences.
- 10 replies
-
- sound trouble
- sound problems
-
(and 2 more)
Tagged with:
-
Anything You Find Confusing About CbB?
scook replied to Craig Anderton's topic in Cakewalk by BandLab
Either I misunderstood your question or you misread my post. It would be nice if note name assignments made in the PRV Notes Pane were persistent but AFAIK, they are not. I filed a feature request some time ago about this. -
VirtualMIDISynth is a replacement for the MS GS Wavetable synth. To a DAW this is an external device. It may be used but is not nearly as convenient as working with softsynths. It is difficult to work with the audio generated by VirtualMIDISynth and the MS GS Wavetable synth. This is why most use either external hardware synths when wanting to use external audio sources or soft synths when working all in the PC. IOW for the best DAW experience avoid using VirtualMIDISynth or the MS GS Wavetable synth
-
Blue button: 'Input echo auto thru' - what is it?
scook replied to Skyline_UK's topic in Cakewalk by BandLab
actually IRTFM but RTFM is good advice -
Replacing/augmenting bass tracks etc using /Audio Snap/Drum Replacer
scook replied to Gary Shore's question in Q&A
Yes, drag and drop audio to MIDI conversion uses the Melodyne VST3 plug-in. The same plug-in supports audio drag and drop to the timeline to create a tempo map and the Region FX implementation of Melodyne. SONAR X3 came with a license for Melodyne Essential. CbB, being a free product, does not include a license for Melodyne, instead; it includes a trial copy. To see the current help page substitute Cakewalk for SONAR X3 as the product in the url like this https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Region_FX.04.html#1679092. This substitution works for most of the Cakewalk help pages. -
Replacing/augmenting bass tracks etc using /Audio Snap/Drum Replacer
scook replied to Gary Shore's question in Q&A
I believe so, it uses the same mono algorithm. -
Replacing/augmenting bass tracks etc using /Audio Snap/Drum Replacer
scook replied to Gary Shore's question in Q&A
AFAIK, monophonic audio to MIDI conversion continues to work after the trial expires. Other Melodyne features such as the Melodyne edit screen stop working when the trial expires. -
Blue button: 'Input echo auto thru' - what is it?
scook replied to Skyline_UK's topic in Cakewalk by BandLab
Yeah, I like to look up the help before posting even when I know the answer. It's a pretty good resource. -
Blue button: 'Input echo auto thru' - what is it?
scook replied to Skyline_UK's topic in Cakewalk by BandLab
The three states of the input echo button are explained here To suppress "Auto" disable "Always Echo Current MIDI Track" in preferences -
Replacing/augmenting bass tracks etc using /Audio Snap/Drum Replacer
scook replied to Gary Shore's question in Q&A
A 30 day trial version of Melodyne (Editor?) is available as an optional add-on. Monophonic audio to MIDI conversion still works after the demo expires. Add-ons are found on the BA menu shown below -
^^^ This is a better solution. Then both the original and radio edit may be versioned separately.
-
From http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=DrumEditor.05.html
-
This would be my guess. Chances are Guitar Pro 7 is adding setup information to the exported files. This should be dealt with by modifying the program's export options. Cakewalk sfz engine synths shut down when encountering unexpected data. Once the data is sent to the synth, it will make no sound until the project is shutdown and restarted. There are two ways to deal with the unexpected data in MIDI clips - Open the clips in the Event List View and remove the offending data. Often the data is at the beginning of the clip. Deleting everything up to the first note may be enough or Enable "Don Not Intercept NRPNs" in the VST plug-in properties page for the synth
-
The .asset files were used with Gobbler. They are no longer needed. Gobbler changed it line of business and the feature that relied on the .asset files is no more. It is safe to delete or skip copying asset files.
-
To add a drum map preset to a MIDI track use the MIDI output drop down to select a new drum map. If using an instrument track, the click on the MIDI tab in the inspector to gain access to the MIDI output drop down. To populate the presets drop down in the drum map manager, click New to create a new drum map for the current project.
-
The XLN "wrong computer ID" error often happens as a result of updating Win10. See https://www.xlnaudio.com/support/my-product-is-suddenly-not-authorized-wrong-computer-id-or-this-instrument-is-in-trial-mode
-
Check the exclude list by clicking "Show Excluded" while "VST3 Audio FX (VST3)" If the plug-in is there, try a manual scan from preferences with "Rescan Failed Plug-ins," "Scan in Sandbox" and "Generate Scan Log" enabled. After scanning, disabled "Rescan Failed Plug-ins." If this does not fix the problem review the scan log. There should be some entries about the plug-in. If the plug-in is not there, running a VST Reset from preferences with "Scan in Sandbox" and "Generate Scan Log" enabled. Depending on how many plug-ins are installed, the scan log may be huge but searching the log for the VST3 file name should narrow down the search for the appropriate entries. An alternative to running a VST Reset is uninstall the plug-in, run a manual scan, re-install the plug-in then run a manual scan with "Scan in Sandbox" and "Generate Scan Log" enabled. This will generate a much smaller log because only the newly adding plug-ins get scanned.