Harley Dear

I have just downloaded the new version to two laptops at the bottom end of the world. Both went seamlessly.
Harley

11 hours ago, Noel Borthwick said:

My only request is that rather than making new threads, any EA related issues should always be reported in the main EA thread. Otherwise we risk not seeing it.

Oh, I didn't know that sorry. I didn't even realise I'd updated with an 'early version' and just thought it was something stupid I'd done to one of my settings.
Glad it helped though 😁

On 9/3/2023 at 4:31 AM, OutrageProductions said:

Reading is hard, Comprehension even more so.

21 hours ago, msmcleod said:

This isn't a beta version, it's an early access.

If this bug wasn't found, it's likely this version would have been released as the final version.  So far we're not aware of any other specific issues in this release, but we'll keep an eye out for any reports over the next couple of days.

 

Touché  😁

On 8/30/2023 at 2:44 AM, JohnnyV said:

There might be a situation where an ASIO driver is very poorly written and the WASAPI driver seemed more stable. But that seems like a rare off chance.  You're lucky the Soundcraft works with WASAPI, mine doesn't.  I've often connected it to other computers and couldn't get it to be recognized by windows until I installed the ASIO driver. 

 

I have two Ui24Rs and both have worked well with both ASIO and ( now ) WASAPI. Plus we have three laptops in our band, all as backups of each other or so someone can makes changes on the MIDI files and if it turns out an improvement, then we copy that to the other two machines.

So I am unsure why you've had trouble. We installed Soundcraft's UI24r USB driver in the first instance and both machines worked fine from the very start. One Ui24R was even second had ( risky I know and yes it did have one problem but $60 with the licensed agent fix  that - loose re-set cable ) but with little effort, it works fine.

The sound quality is outstanding. We tried the Behringer option, but that came a poor second.

Anyhow, now we've solved the patching problem I made changes to all our 250 odd projects ( took about 2 minutes a project ) and WASAPI turns out to be the best for us now in terms of using files from one machine to the other.

1 minute ago, Will. said:

Strange, mine wasn't in the toast at all. That could also been that I literally checked the DAW 9mins after the EA dropped. Didn't see it so, i downloaded it from the google drive link that was attached in announcements. 

Same. 

Despite the moments of despair, for me the silver lining is that a glitch has been alerted to The Bakers 😁
 

6 hours ago, msmcleod said:

wow, this one was a tricky one to track down!

Ok - here's the cause:

You've got MIDI strips unchecked in the console view, but also you've got "Keep track/console visibility states in sync" checked:
To fix this:
1.  Ensure MIDI is checked
2.  Open the track manager from the console view, and unhide the tracks (with the sync still on).

There have been some bug fixes in this area, as sync wasn't working properly... but this looks like a regression.  We'll look into it further.


 

Thanks so much Mark. I appreciate the time you have put into this to help.

Harley

@msmcleod Changing 'Workpaces' to 'None' doesn't make any difference sorry

Video removed

*** Don't worry - FOUND it *****
Where do I find 'Workspace settings' please?

Harley

20 minutes ago, msmcleod said:

Did you save the project after unhiding them?  The hidden state is saved with the project.

Yes I did. It still came up with the tracks hidden when re-opening.

Well, things get more weird.

I re-installed as you recommended Will. I still get the MIDI tracks not showing

I then press H as Bristol-Jonesy said and I get this 

After checking all the tracks, the MIDI tracks finally show up. I save the file ( I have master back-ups elsewhere ), close it down.

However, when I re-open it , the MIDI files do not show again AArhghhhh! What a nuisance.

Hi all

I just updated Cakewalk and now I can't see the top tracks at all ( along with the MIDI data ) , plus can't see tracks 10 and 11 which also have the midi data.

In addition, if I try and display MIDI in the strips command on the Console, the MIDI consoles don't show either.

The file plays fine so all the data is there. It just seems that any track with MIDI data can't display.

Is this a bug or do I have to do something to get the MIDI track views back?

Well, another interesting thing that I should have noticed but went blindly past.

Somehow, without me knowing, the system driver changed from ASIO to WASAPI!

Actually WASAPI gives me better patching options to the Ui24R for some reason, and now that explains why the two other laptop files ( running ASIO ) did not compute on the main laptop all that well.

Is WASAPI as good as ASIO in this instance? What's the cons of WASAPI vs ASIO? ( I see another post regarding this  @JohnnyV you contributed to and your video is great BUT in windows 11, managing the sound settings seems more obscure )

OK, I labelled the AUD.IN file AUD.INI-OLD and started up Cakewalk with the Ui24R connected.  Nothing worked unfortunately.

So I renamed the previous AUD.IN-OLD back to AUD.INI ( after changing the name of the AUD.INI that was automatically written ) and now when I start all my files, I get this message

If I click OK, then things work fine, but I must save the file fresh so that I don't get this message again plus the patching assignments are all skewiff again ( see below ). I have to do this with every existing file!

I'm probably doing something wrong, but can't understand why CbB didn't write the new AUD.INI file and function well like Lord Tim and msmcleod said it would?

In addition, why do I have to click OK and save each existing file now so it works again? Clearly, there's something I am not understanding about the ASIO set up to our Ui24R.

As mentioned above, after going back to the original AUD.INI, when I open the CWP files, I have to re-assign all the outputs again!  Grrhhh!  What's going wrong here?

Sorry to be a pain.

Harley

Jeepers! I've got 4 of them! Should I disable all 4?

6 hours ago, Lord Tim said:

Yeah, if you delete it (or rename it to aud.OLD so you have it there as a backup) it'll automatically be rebuilt when you start CbB next. You might need to go back and double check your preferences in places in case something you customised was changed back to default but it won't break anything if you do this.

Thanks Lord Tim

1 hour ago, JohnnyV said:

I'm no expert but I've read here a lot that you can completely nuke everything in there and Cakewalk will simply rebuild as needed automatically. 

@msmcleod Is that correct?. Just get rid of everything, and start CbB up again and it will rebuild?

Thanks @JohnnyV for that info.

Harley

@msmcleodCompare Aud.ini ( in %APPDATA%\Cakewalk\Cakewalk Core\ )  between the machines.  This file specifies the order, indexing, and naming of the device's input and output ports.

You may find that one port is either in a different order, or disabled on one machine.

Thanks - I have looked into the ini file and really don't know exactly what to look for but I'll load the other machines' ini files and see what the difference is

Meanwhile I found literally hundreds of listings for reaper ( I tried reaper a few years ago and gave up in favour of CbB )

This can't be doing the system any good I figure. How do I get rid of all these Reaper references or won't it matter?

AUD.INI

Thanks msmcleod and JohnnyV

Hi all,

This isn't one of the 'the sky is falling in' moments but  I'd just like to understand why when I open a CWP file that's been processed in one of our band member's PCs, I get a different patching assignment when I load it onto each of my laptops I use for gigs ( on is a back-up ).

We use CWP files in conjunction with our Soundcraft Ui24R as backing tracks for drums, keys and brass. The drum vst we use is SSD5 Sampler. I know it's not everyone's cup of tea, but is suits our band's style very well. When the other band member makes change to the tracks, has also has a Ui24R which has an identical set-up. All laptops with CbB have same version software and identical VSTs ( same releases )

So when I open one of these files in the ASUS laptop, the assignment for Kick is 'none' as seen below

To make this work, I have to re-assign the patching to 27Out/28in 

When I bring the same file into my MSI laptop, the assignment is fine - need no adjusting

So why does it work fine on one laptop, but need changing on the other?

Thanks,

Harley

*** UPDATE ***

I took my laptop into a tech expert. He couldn't see too much wrong with it, so he updated the BIOS, Nvidia and Internet drivers.

That seems to have fixed the problem as CbB is running like it did prior to that Wii update.

Whilst we don't know which of those updates did the trick, it least it's working and gigable now.

Thanks everyone for your detailed help - it really was appreciated and something I can store for any future problem/s I might have.

Harley

Thanks JohnnyV

Thanks Metelus and Larioso.

@msmcleod

 the resultant audio file is written to either to the project audio folder

How do I check/influence that please?

Perfect! Thanks MS McCleod. That's very helpful - just what I was after.

Thanks Johny V. Yes I did read that thanks.

This is actually on the other laptop which is running Windows 10 and is functioning well with CbB.

I'd just like to know the destination of where those files get written to on my C drive when I freeze tracks. My D drive has HEAPS of space, so it would make sense for those 'freeze files' to be written there. Is it possible to direct them to the D Drive.

Harley