-
Posts
3,958 -
Joined
-
Last visited
-
Days Won
9
Everything posted by Promidi
-
I can confirm this. I attempted to open many projects done in a previous build. Many would not open in CbB 2019.7 Build 70. The way it manifests is as follows: The project attempts the open but eventually CbB stops responding with the mouse displaying an hour glass. No error messages were displayed. Eventully I got the Program has stopped responding. I had to end the process using Task Manager. No dump file was generated. The Application event viewer yeilded an Exception code: 0xc0000005 error, Faulting module name: Cakewalk.exe, version: 25.7.0.70 I reverted to 2019.7 Early Release 2 (CbB 2019.7 Build 65 )and the projects were able to be opened. The way I reverted was as followed. I restored the C:\Program Files\Cakewalk\Cakewalk Core contents to the state in was Last Friday from my backup. After doing this, I ran CbB to confirm the actual resultant version in Help | About. For me this was now Early Release 1 (build 55) I edited the Windows registry at HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Core and changed the ProductVersion value to 25.07.0.55. You need to do this, otherwise, the ER2 installer will not update. I am now on 2019.7 Early Release 2 and can open all previous projects. I am going to have to concur with the OP and hold off Build 70 until this can be resolved.
-
[CLOSED] Cakewalk 2019.07 Early Access 2
Promidi replied to Jesse Jost's topic in Early Access Program
I am not experiencing this with 2019.7 ER2 Does this happen with any instrument or a particular one? -
Do you have the version of Cakewalk by Bandlab that has a ripple edit on/off indicator on the CbB gui?
-
That's strange. I have never had that happen. Are you able to try with a different mouse? Or maybe adjust the mouse settings in Control Panel | Mouse to increase the double speed
-
Turn core parking off. Go to advanced power settings and set CPU min and max to 100%. Install all windows 10 and driver updates. With drivers, go to the manufacturer's websites rather than letting Windows do it. Also, tell Windows updates to leave drivers alone. Check which programs start when you start the PC (and therefore running in the background.
-
I am not sure why downloading this file resulted in that filename. This is actually an MP3 file without the .mp3 extension. Simply rename the file to "Traxx Magnific - XXX-ten (mastered).mp3" and you should be able to play it or import it into Cakewalk
-
I can also confirm the dropping of notes issue. It only occurs when notes of the same value in a row overlap. That is, the next note triggers before the previous note ends. The issue does not occur if the note values are different. I have to ask, has anyone logged a support ticket with IKM for this particular issue yet? As others have reported this issue before me, I am hoping someone has logged a support ticket with IKM by now.
-
I got another reply from IKM support. They have acknowledged my issue and they are going to fix it.
-
I got a reply from IKM support and they asked me for screenshots or a video (obviously my detailed explanation was not enough). I just created a detailed video showing the issue. I showed the workflow using Sampletank 4.04 were the edited patch loaded successfully. I repeated the same workflow with Sampletank 4.05 (same patch and everything) and the error appeared. I am hoping this will be enough to get them to reproduce the issue and come up with a fix in the form of an update. Until this is resolved, I am staying with Sampletank 4.04
-
I can't say I have noticed dropping notes with 4.05, but that does not say that I won't. because of the saving custom patch issue and now potentially this, I also have reverted to 4.04. Looks like version 4.05 might have tanked.... Roll on 4.06 eh....
-
I left a post on the IK Multimedia Sampletank forums and the moderator there has confirmed he was able reproduce this issue. I am going to lodge a support ticket at IK Multimedia.
-
Just a note that I think I may have found an issue with Sampletank 4.05. Saving instruments appears to be broken. It creates files that cannot be subsequently reloaded on the next session. Instruments saved with 4.04 load ok, just not ones saved with 4.05. Can anyone with Sampletank 4.05 verify this?
-
Shift + Z
-
Feature req: Ability to rename MIDI CC in automation envelopes and PRV
Promidi replied to GreenLight's topic in Feedback Loop
This can be done globally. Under "Controller names", "Standard" in Define instruments and Names, you can customise the list as shown below. It would be nice if this can be done per VST synth, however. -
Note: Requires Kontakt version 5.8 or higher (full version)
- 1 reply
-
- 1
-
-
One thing you might like to check is head to Device Manager and expand "Universal serial bus controllers". Right click on all devices that has "Root Hub" and then select properties. Head to the power management tab deselect "Allow the computer to turn off this device to save power" Do this for all devices that has "Root Hub" in the devices name. This may help.
-
The folder tree looks fine. Maybe try going through all your IK products and reactivate them using IK Multimedia Auth Manager.....
-
Remember, with ST3 you could only specify one location for the content. With ST4 you can specify multiple locations. I have the content for ST4 and ST3 (Though I uninstalled the ST3 player) and can see all the content from both products (as well as IK add ons). I have two locations for the sound content specified, one for where the ST3 content resides and another for where the ST4 content resides. They are on 2 physical drives. Go into the Settings and head to the Sound Content tab and make sure any folders that contain Sampletank content (which ever version) are listed there. Then perform a "Rescan Instruments"
-
I have to wonder the same thing. I know I already have plugins that do (or can be configured to) the same as what these are offering.
-
This video explains a bit more https://www.youtube.com/watch?v=iuoTmNLlZk0
-
Yes.
-
Yes, I also have a blank measure. Some synths or effects need time to initialise. If a note sounds before the synths or effects has fully initialised, the note may sound strange.
-
First open (don't import ) your MIDI file in CbB. Make sure the MIDI tracks are configured to sent MIDI to the port that your Roland - JUNO-Di is physically connected to. Then add your session drummer as either a simple instrument or even with multi outs. Load your drum patterns or program the pattern as you usually do. Then create an audio track. Make sure you set the levels so it does not clip anywhere Then, while your MIDI data is being played, record your Roland - JUNO-Di performance onto that audio track. Preferably you would want to use ASIO driver mode to minimise latency. Note: While recording your Roland - JUNO-Di performance, you might with to mute your audio track that you're recording onto. I have done this a few times, but I use a Yamaha module and recorded its performance from MIDI files but the workflow is pretty much the same.. Hope this helps.
-
I never use the Matrix view, Loop construction, Video when I am programming MIDI files. Nor do I need to even see the virtual keyboard. I also wish to have my personal key bindings available in all lenses - so this is deselected in my all of my custom lenses. This is the reason I find Lenses useful. They enable me to hide these functions and elements that I do not use and therefore do not need to even see. Of course, as mentioned, because I have deselected Windows layouts in my lenses, only screensets saves the various Windows layouts for my various projects. I usually have about 4 - Track View, PRV, lyrics and drums. I have also key bound these screensets to CTRL-Numpad 1 to 4 respectively. I have written a small VB2010 program that automatically changes my default CbB lense to "MIDI sequencing" and then opens my MIDI project in CbB. The project opens, the correct lense is set, and project's screenset is also loaded according to what was saved in the project ready for me to resume.
-
Within CbB, If you hold CTRL while dragging a window, the snap window feature (with the corresponding blue overlay) will be temporarily disabled.