Andres Medina
-
Posts
653 -
Joined
-
Last visited
Posts posted by Andres Medina
-
-
Bonus: if a combine this with the new tempo track, I can visually align arranger sections of the music to landmarks on the video by changing the tempo map...! wow. What a time saving tool! Thanks again -
-
18 minutes ago, msmcleod said:
You can change the time base to Absolute time on an arranger track by track basis. So all sections within an absolute time track will keep their absolute time position and length regardless of tempo changes.
To change the time base of an arranger track, either use the arranger track context menu, or click the time base icon in the arranger track header:
Whatt!? just what I was dreaming of - Thanks Scook!
This is extra useful for composing music for video (now I can mark sections on one arranger track dedicated to video marking, and keep them locked regardless of the tempo changes I make on the music). And keep the arranger sections of the music unlocked in a different track.
- Fantastic.
-
Sorry! what a mess -
I avoided inserting Soft Synths as Simple Instruments tracks for that reason. I like to have access for midi and audio inputs+outputs as independent tracks, so there's room for reassigning / rerouting as needed.
Have you tried to inserting your VST's that way? each midi and audio tracks are independent, and easily configurable, and accesible via the console view as well.
My troubles with Omnisphere assignments were solved by re-assigning the inputs of the audio tracks directly on each audio track. Midi tracks were not affected, nor audio outs. Lost half an hour but it was done!
Check images attached.
-
1
-
-
5 minutes ago, Olaf said:
Nevermind, I've solved it. Lost an hour of my life. Maybe the problem would get solved in the near future.
If you use Spectrasonics soft synths, there was a recent update on their part that messed up the audio inputs of the synth audio tracks inside Cakewalk.
Check this thread:
But, fortunately, It was solved recently by the Cakewalk team, in the latest update:
-
Hi!
Didn't find anything related to this: is currently any way to lock the position of an Arranger Section to a specific SMPTE position, same as you do with clips?
Would be very useful in a music for video scenario.
-
34 minutes ago, msmcleod said:
@Noel Borthwick's fix was a generic one for both extra ports appearing, and ports being missing from updated VSTi's, so the fix in EA should equally apply to those as well.
wow - and it gets even better!
Thanks!
-
12 hours ago, bitflipper said:
The reason this doesn't affect RMX, Trilian and Keyscape is that the root cause of the problem was a change made only to Omnisphere, in which a 9th output was added. I have no idea why they did that, since you can have at most 8 individual voices in a Multi.
It means that when you created your project prior to the Omnisphere update, CW saw that it had 8 outputs and calculated all the other instruments' input source offsets accordingly (think of them as being numbered 1...N internally; inserting a new one throws the whole list off). Then, when you subsequently re-open that same project all the offsets are thrown off by 1 (or the number of Omnisphere instances).
Kudos to Noel for figuring out a fix quickly. Know that this was not an easy fix to implement. As a fellow coder, I can testify that our Noel is a frickin' bit-ninja.
Agree!
Have no idea what the purpose of the 9th out is for...
BTW, I double checked Trilian and Stylus, and it seems to me that there are 9 outs now... see the images.
-
13 hours ago, Noel Borthwick said:
We posted a new early access installer that includes a fix for this issue. @bitflipper @Andres Medina please try this out and let me know if this addresses the issues with I/O's getting changed unexpectedly.
AFIK the problem was only localized to track inputs when loading a synth that changes its outputs. Let me know if you still see problems with this fix.I'm confused by the statement that inputs and outputs were mismatched. Are you referring to the outputs to buses from tracks? Those should have been unchanged. Anyway let me know how it works in this release.
Wow - fast and efficient!! Thanks Noel.
Yes, it's working just fine!
I opened an old project and there were not mismatched audio input assignment on Omnisphere.
About: "I'm confused by the statement that inputs and outputs were mismatched. Are you referring to the outputs to buses from tracks? Those should have been unchanged. Anyway let me know how it works in this release." - :
You are right. The problem only affects the audio inputs on the Omnisphere audio tracks.
Thanks again!
---
UPDATE: I already checked with Stylus RMX and Trilian, the other two Spectrasonics products that were updated along with Omnisphere, and they are working fine too. Fantastic!
-
1
-
-
12 hours ago, Noel Borthwick said:
We posted a new early access installer that includes a fix for this issue. @bitflipper @Andres Medina please try this out and let me know if this addresses the issues with I/O's getting changed unexpectedly.
AFIK the problem was only localized to track inputs when loading a synth that changes its outputs. Let me know if you still see problems with this fix.I'm confused by the statement that inputs and outputs were mismatched. Are you referring to the outputs to buses from tracks? Those should have been unchanged. Anyway let me know how it works in this release.
Wow - fast and efficient!! Thanks Noel.
Yes, it's working just fine!
I opened an old project and there were not mismatched audio input assignment on Omnisphere.
About: "I'm confused by the statement that inputs and outputs were mismatched. Are you referring to the outputs to buses from tracks? Those should have been unchanged. Anyway let me know how it works in this release." - :
You are right. The problem only affects the audio inputs on the Omnisphere audio tracks.
Thanks again!
-
That would be great - Thanks Noel.
-
Thanks for the research!
Now it all makes sense (kind of..!).
And yes, the only way to restore the project is to manually assign each audio input all over. For one instance, it's just 8 outputs to go. But for multiple instances, well... hard work.
-
Same here: I opened a project containing Omnisphere, and all the inputs+outputs of the audio tracks of the plugin were completely mismatched. Only happened with Omnisphere. Not sure, but perhaps the last time I opened the project was before updating Cakewalk.
-
I wonder if anyone is experiencing trouble using Vienna Synchron Strings after this update.
I'm having severe glitches when hitting stop, while playing Synchron Strings, and only with this plugin.
Vienna Instruments working fine.
---
UPDATE: In fact the glitches are present after stop with every Virtual Instrument, but were more noticeable in one particularVienna Synchron Patch.
I found out that the configuration of Audio/Playback and Recording/ Fade On Start+Fade On Stop must be at least 10 ms, at least in my system; otherwise there are very noticeable glitches on Stop.
This solved the problem completely.
-
Worth to check: when opening an OMF file, you are asked to locate the audio of the OMF, which is contained in the OMF folder.
It's working just fine.
BUT, when closing this project and opening another one, this time a regular one (a project file), it seems that Cakewalk reverts the Audio Data folder to the factory location, and erases the user defined location. May be the reason why some threads report missing audio when opening a file, referenced to the Audio data folder.
-
I found out that in this version the configuration of Customization/Display options in Preferences is not retained after closing Cakewalk.
The option "display all times as SMPTE" reverts to unchecked every time.
-
1
-
-
1 hour ago, 4th Eden said:
Its 2.7.0f now...youll be fine! This is only a problem 1. if you have installed the June Omnisphere patch and 2. gone back to older project using prior to 2.7.0f
Thanks.. I´ll do it - I work a lot with Spectrasonics plugins.
-
1
-
-
Trilian (1.6.0f*) and Stylus (1.10.0f*) working fine here.
Omnisphere I working here (1.5.8.d 64 bits). But this version was not updated.
-
4 hours ago, msmcleod said:
This feature creates a new arrangement based on the selected arrangement sections within an existing Arrangement.
You don't have any arrangement sections, so that's why its greyed out.
In the above scenario, just add the arranger sections using the add-sections-to-arrangement button.Got it. Thanks! Works nice -
-
The "Create new arrangement based on existing arrangement" new feature is not working, at least in my system. (Build 2021.06 - built 041, 64 bit).
After selecting sections on the Arranger pane, the context menu when right clicking the arrangements pane is greyed out.
-
Update: in order to be able to see/edit the notes corresponding to a clip in the melodyne track - one at a time - you must select a clip in CW and then select clip mode inside melodyne.
Anyway, at the moment, even in this scenario, the changes in selected clips inside the comp track are not reflected in melodyne.
-
1
-
-
Thanks!
I did some additional tests, and found out a way to work it out, with some limitations. Not sure how melodyne is applied in Cubase to composite tracks, so here is a way to use inside Cakewalk:
When applying melodyne to take lanes:
- All takes must be active before applying melodyne. Otherwise, Melodyne renders the muted clips as silence.
- Each lane must be selected independently to select and apply the melodyne region (otherwise melodyne renders the whole comp track to one single melodyne composite take)
- Once this is done, you can select and edit the comp takes as always, and melodyne reflects your selection in its own screen (the selection must be done in the cakewalk lane, not inside melodyne).
- For been able to see the different selected clips independently inside melodyne, I think you need the studio version, which provides multitrack editing, otherwise all the clips that has melodyne applied inside the comp track are displayed together in a single window, and this makes pointless the use of this comp+melodyne tool.
So, I guess that to really use the comp track with melodyne, you need to have the studio version.
-
Hi - I'm struggling to make it work too. - I'm using latest Cakewalk (2021.04 build 175) and Melodyne Assistant version (no multitrack editor, no polyphonic capabilities)
Here are my findings:
- If I apply Melodyne to the whole track (comp lanes inside), Melodyne renders whatever clips are active into a single clip, losing the ability to work the individual clips again.
- If I apply Melodyne one by one on the individual takes of the comp track, I can work and hear the edits made on the comp tracks, but Melodyne displays all the blops of the clips stuck together - not useful at all.
Not sure if this is a limitation on my Melodyne version, or a malfunction on the integration of Melodyne with Cakewalk ...
I wonder if any of you are using Melodyne Studio+Cakewalk to check?
(in the meanwhile I think I'll try the 30 day test drive for Melodyne Editor or Studio to see how it behaves)
-
1
-
1 hour ago, Noel Borthwick said:
@Andres Medina thanks we'll investigate it. did you hit the delete key after selecting all? If you can share the project file before the crash.
Thanks Noel -
No, I used a shortcut for "wipe tracks", not delete.
I'll send you a copy of the project as soon as I can.
-
Hi,
Just got a weird crash, doing the following, when rewriting the music in a project:
- Select All
- Wipe
- Crash
Weird part: the tempo of the project was changed to 8 bps prior to the crash. Before this update, when you selected all and then wiped, the tempo remained unchanged. Am I missing something?
Enclosed the minidump.
Locking Arranger Sections to SMPTE
in Cakewalk by BandLab
Posted