-
Posts
9,681 -
Joined
-
Last visited
-
Days Won
27
Posts posted by scook
-
-
Keyboard shortcut J toggles the scrub tool
With the scrub tool enabled, click-drag plays notes in the PRV
- 3
-
similar thread
- 1
-
From https://www.cakewalk.com/Support/Knowledge-Base/2007013355/SONAR-X3d-Update
QuoteAs of SONAR X3d, SONAR’s video engine defaults to using Microsoft’s Media Foundation framework, rather than DirectShow. This fundamentally improves the way video files are loaded, played, edited and exported in SONAR. Media Foundation generally supports most older formats supported by DirectShow as well as many newer formats such as H264 video. A full list of media formats supported by Media Foundation can be found here.
As a result of this change, a large number of long-standing bugs and limitations with importing videos and video playback have been resolved. For backwards compatibility, SONAR's video engine can still be switched to use the DirectShow engine. More information on switching SONAR's video engine can be found here.
With X3e and newer (including CbB) the VideoEngine sets the default engine but when DirectShow encounters an unsupported format the DAW falls back to the Media Foundation engine.
-
unsupported format
-
4 minutes ago, winkpain said:
I too would love to see the video aspect functioning better. I can't even get the default engine change outlined here - https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Troubleshooting.08.html to take hold (changing to Direct Show) in order to deal with Trim In-Out changes.
Chances are the file being loaded cannot use the DirectShow engine. If this is the case rather than error, CbB automatically switches to the Media Foundation engine.
-
The position in the ini file should not matter.
When VideoEngine is set to 0 CbB tries using the DirectShow engine but if it cannot load the file it will automatically fall back to the Media Foundation engine.
-
4 hours ago, locrian said:
However I prefer to apply it to a VI in realtime on an instrument track (in Cubase) but have not been able to get it to work. Stutter Edit responds to the data on the midi track, but it does not modulate the audio on the instrument track.
Has anyone been able to do this?
I do not have Cubase to test but to make this work in CbB, the transport must be running.
-
13 minutes ago, jonathan boose said:
Should I start a project without plugs and add plugins until one of them causes a crash?
That is a way. Consider saving incrementally.
13 minutes ago, jonathan boose said:And why would a plugin cause a problem now but not the last time I successfully opened CbB?
As mentioned in the OP
On 2/11/2020 at 12:12 AM, jonathan boose said:I haven't used it in a while.
Possibly the machine was used for some other purpose and something changed to cause the failure. Maybe some other software was installed or updated (including the OS). I have no idea how the machine is used or maintained. Of course, we are not sure if the problem is plug-in related but it appears to be a good candidate ATM.
-
In CbB to send the same MIDI data to multiple targets either
- Clone the instrument/MIDI tracks and use linked clips or
- Use one MIDI track and a virtual MIDI cable (LoopBe1 is the best free choice for this) to drive multiple instrument/MIDI tracks.
- 1
-
Large projects with lots of plug-ins are certainly more challenging that small projects.
Again if projects load in safe-mode with no plug-ins and fail to load with some or all plug-ins, the problem is likely with the plug-ins. Determining which ones can be time consuming. If there is a common plug-in or set of plug-ins used in a collection of failing projects, those would be the first to suspect.
-
If a project loads without plug-ins in safe-mode, it becomes a process of elimination to determine which plug-in(s) if any are the problem. It could be any one or a combination of plug-ins. Even if the project appears to get past a plug-in when loaded in safe-mode, it does not exclude that plug-in from being a problem.
Still there are a finite number of combinations and it appears that loading without plug-ins gets past the error message so this may be a good way to work the issue.
-
You are welcome.
Glad it worked for you.
At some point consider playing around with buses. They can be very useful for a variety of tasks.
-
Start with no to all plug-ins
If that works then it is likely one or more plug-ins causing the problem.
If not, it is likely something else.
-
It appears that CbB does not see any ASIO driver.
Usually ASIO drivers are supplied by the hardware manufacturer and must be installed before using the audio interface.
When using a device without an ASIO driver such as the internal sound chip in the PC (n.b. the RealTek ASIO driver is buggy and should be avoided) a differenT driver mode must be selected. This is set on in Audio > Playback and Recording preferences shown in the image above. For Win10, the WASAPI modes are best choice. For other OSes try WDM then MME.
-
Craig Anderton did a review of an older Anthology release which included the H3000 Factory and H910.
- 1
-
When Melodyne Region FX sections are rendered references to the Melodyne plug-in are removed from the project.
AFAIK, any plug-ins in frozen/archived tracks are not accessed with a project is loaded.
Uninstalling a plug-in is functionally the same as running in safe mode, skipping offending plug-ins then deleting them. Of course, safe-mode is per-project solution where uninstall may be less work if there are many projects involved.
Either should allow the project to open if the problem is related to the plug-in.
-
The H3000 Factory does not include all the algorithms from the hardware unit. Eventide broke out the algorithms into several of their plug-ins including the H910, H949, Octavox and Quadravox (and probably the H3000 delay, IDK my H3000 did not have multi-band delay but it was an older unit). The H3000 Factory is OK but of the plug-ins currently on sale I use the H910 most often.
- 4
-
There were reports of un-rendered Melodyne 2 parts crashing SONAR when Melodyne 4 was released.
This could be the problem. If it is, the original clips should still be in the project but the Melodyne affects clips may be unavailable.
-
One should avoid posting in the early release thread after the production version is released.
It is better to post in the production release thread. For 2020.01 it is
There was a hot fix released for 2020.01.
The announcement thread has been updated
along with https://www.bandlab.com/products/cakewalk/whats-new
-
It is a hot fix for 2020.01 see the announcement post for details
-
OK
Based on what has been reported -
There is a problem in a project.
It occurs at or before loading Melodyne.
There are "many" plug-ins that load before Melodyne.
Does this
35 minutes ago, jonathan boose said:I'll try skipping the last instance of Melodyne. I don't know why there is more than one shown, except that I think Sonar X3 Producer came bundled with Melodyne Le and I guess I was prompted to update since it says Melodyne 4.
mean the project created prior to upgrading to Melodyne?
-
No, they are two different programs.
BandLab runs in Chrome and Edge. It stores its projects on the BandLab servers.
Cakewalk by BandLab is a Windows program that stores its projects on your PC.
-
14 minutes ago, Robert Bone said:
use the VST2 version of Melodyne
This is only an option if the plug-in is used in the FX Rack. Region FX clips require the VST3 plug-in.
While the project stops when loading an instance of Melodyne, it may be a symptom and not the cause. It will take more experimentation with safe-mode to rule out a previously loaded plug-in as the cause of the problem.
-
given
11 hours ago, jonathan boose said:I opened a simple 2 track template I had saved from the desktop icon. It loaded instantly. There are no plugins or recorded tracks on it. But CbB opened the last time I used it with actual projects.
opening an existing project in safe-mode may be instructive (once the OS is finished updating).
Session drummer, Melodyne
in Q&A
Posted
Most of this applies to your question