Noel Borthwick

Yes its just an installer change the app is the same.

@Home Studio Simplified thanks for checking out the arranger. A small tip - while you can certainly use the main sections pane to also audition arrangements its designed to primarily store and manipulate the master list of sections in the project. i.e. if you have 4 parts A-A-B-A for a song, you would only need 2 sections in the section list. Where you would create the repetitions would be in the arranger pane below by dragging 3 instances of A and one of B into it. IOW you do arrangements in the arrangements pane and manipulate blocks of data on the project timeline using the sections pane. Hope this clarifies the workflow. Also saving or making multiple arrangements in the arrangements pane has no effect on the sections pane itself. Its saving different variations or combinations of the sections themselves. You should normally not need to reorder sections in the sections pane unless of course you want to move the project data on the timeline. In any case everyone will have their own workflow to use this feature...

If you are running at 128 samples you likely won't notice any perceivable delays. Performance is project specific however.

Maybe you misunderstood. The arrangement can freely be modified during playback with no interruptions. You can add new sections, reorder, delete, duplicate, all on the fly during playback.

You don't need to use ripple edit. Just commit the arrangement to the project and it will automatically make all the edits for you. At that point you may just need to fine tune the edits with slip edits or other transitions as desired. While arrangement preview is a very useful way to audition and A/B multiple arrangements the intent of the arranger is primarily as an editing tool. In most cases preview works seamlessly and transitions are as fast as they would be when you seek to regions on the timeline. In more complex projects with lots of effects if you perceive any discontinuities bypassing effects or running at a smaller buffer size will normally alleviate this. Otherwise you can always commit the arrangement at which time it is "flattened" to the timeline with no jumps.

@Johnboy If you can send a link to the bundle I can take a look at it. Which version did you save it in? If It's from a recent version it's unlikely to be corrupted since we fixed many issues with reading and saving bundles.

Hello this was an installer problem. It has since been updated. If you are encountering this issue you can simply rollback and then reinstall the latest update again. This should fix the issue for you.

@HIBICan you send me your text file? It definitely worked with some Japanese text we tried. Are you running an English version of Windows with the language set or Japanese Windows?

@Percy Ferry that link isn't accessible. You should be able to zip the minidump and drop the size a bit. If you save from task manager for a hang the dump file will be big since its a memory snapshot.

Arrangement Preview will not be sample accurate - that's why its called preview. It will improve though if you run at low latency. Can you verify that it improves? Depending on project load seeking to far apart sections may cause small discontinuities. Crossfades won't solve all problems. In general arranger is a tool for editing, experimentation and composition but before getting ready for production you typically need to render it and do some clean up.

This issue should be fixed in the 2020.04 release that was posted earlier today. The issues below were related. Please verify that it is fixed and no longer occurs. Unexpected behavior with Instrument tracks when adding MIDI ports. Adding or removing MIDI devices can cause soft synths to be assigned to incorrect ports.

Just to clarify for this thread, the problem RBH was having has been resolved. He has a broken DirectX installation that causes even the Microsoft DirectX diagnostic tools (DXDiag) to crash. The new version of Cakewalk uses Direct2D for some drawing optimizations for the arranger UI and this is what triggers the problem on his PC. Normal Win7 systems are unaffected by this problem.

@Nicault what exactly is the problem you are having? If anyone on this thread is having a specific Win7 problem with the early access release please get in touch ASAP.

For the record Windows 7 is end of life and we do not have the resources to test or develop custom workarounds or hacks to keep CbB working on Win 7 anymore. Though we try to remain basically compatible, problems like this will continue to happen because nobody is testing it anymore. That said, if there is something fundamentally broken and we can find a cause we do try and address it when possible.

@Craig AndertonWhen you select entire mix, exports are captured from the hardware mains rather than the buses. There is no hardwired logic to favor the master bus - its all based on the signal flow. i.e. if your selection has tracks and buses that route to a specific set of mains by default they will be shown in the dialog. If there are multiple hardware mains selected when you export, then we internally create a bus to mix down all the mains selected and export that bus output.

@markrounds what specific issue are you referring to? I'm not aware of any Maschine problem that came my way. Do you have a case number for this?

No current plans to make Cakewalk itself cross platform. We're working on other cross platform apps and our efforts could ultimately help facilitate a full cross platform port but its very unlikely to happen in the near future. Staff view is a lower priority since it is one of the least used features. We try to make incremental updates to it but it was never intended to be a full blown score editor.

We just posted the 2020.04 early access release. Please post any comments or feedback directly in the linked thread. We're very excited to get this major update of Cakewalk out. We plan on releasing the final build next week which will include a few more tweaks.

I assure you it will be worth the wait

@HIBI this is fixed for next release.

Will look into it thanks for the heads up

Hi Folks, as mentioned in the prior release that model is considered "beta" since I still have to do more testing with it. The latency problem is due to a weird race condition leading to audio buffers being lost. I just havent had time to track it down yet but will get to it. For now don't use that model until further notice.

@Maxim Vasilyev the problem with track names displaying garbage has been fixed. As mentioned above its actually caused by the way the VST3 SDK reported this so technically could have been easily addressed from the plugin side (most other VST3 plugins handle it). However I have made a change to resolve it from our end. As far as VST2 goes there is no way for a host to report track names to the plugin via the standard VST protocol so this won't work with Relay in any host. You must use the VST3 version to get this functionality. Cakewalk has supported VST3 channel naming from the get go for many years now. With regard to track ordering in Neutron, this is a deficiency in the plugin since it it appears to be sorting the track names alphabetically and ignoring the host specified track order. There is a specific VST3 interface that can be used by the plugin to identify the order of tracks. If they use that the tracks will be sorted in the same way that they appear in the host. This is how it works with the Softube Console One. BTW the same track ordering problem can be observed in other VST3 hosts such as Reaper.

I've fixed this issue as well for the next release. It had to do with some peculiarities with how Relay requests the host to do resizing via VST3.

Oh well I managed to sort out the string garbage by fixing some code in the VST3 SDK . The SDK code was not copying over the null terminator for the string ? I'll submit my change to Steinberg as well since any app that uses that would be susceptible to the same problem.