Milton Sica

4 hours ago, David Baay said:

If clips are completely missing, I think the most likely explanation is they were inadvertently deleted from the project at some point and it was saved in that state. Or the project crashed before saving the session in which the recordings were made. If the project had been closed without saving the recording session, the audio files would not have been preserved. And any corruption of the project or audio files after the fact that could cause loading to fail would almost certainly result in an error of some sort. 20-20 hindsight: using Save As or the built-in File Versioning feature helps avoid this.

This would be a good explanation to clear up the error if, in fact, it had happened. What didn't happen.
Even so, under such a hypothesis, both my backup file and the versioning ones would have kept track information.

This loss of references to wavs files without their inclusion in the project is something that, I think, deserves to be evaluated by the developers.

On 10/1/2020 at 3:03 PM, jono grant said:

No, it won't rebuild or play. I have to physically go to the audio folder, retrieve the audio and snap it to the empty clips so it lines up.

Hello
I'm facing the same issues currently on versap 2022.02
Did you get the explanation for this problem?

2 hours ago, David Baay said:

I still don't fully understand what the exact symptoms of "not loaded" are. Is it that tracks that formerly contained audio clips are empty or the clips are present but are empty? I did a quick search and found one  report of empty clips disassociated from their audio files, but it was never resolved and I don't recall seeing any other reports of this. Is this what you're seeing?

If this is it, you should send the project to the Bakers so they might have a chance of finding and fixing the root cause.

I explain:

The audio files are present in the audio folder, but they are not included in their places on the tracks where they should be.

The track is empty.

14 hours ago, David Baay said:

 

What I'm saying is that recording, though one of the most fundamental things, is  also one of the most trivial and version-independent things that CbB does, and not likely to contribute to any issue opening old projects. In other words, I think you're 'barking up the wrong tree' as we say over here.

When you say, "some files in wav format are not loaded in the open project",  is there an error that files aren't found or do you get empty clips with no audio file associated or no clip at all or...  something else?

 

Thank you for your help.
In Brazil "barking at the wrong tree" is "praying to the wrong saint".
I understand that the version information is a minimum detail in the universe that the application does, of course!
Precisely because it is so simple that I think it would be quite possible to have this information more accessible.

CWAF has already helped me a lot and the calculation presented by @tparker24..... is very interesting.

In my case, there are projects that wavs files are not loaded after opening. MIDI registers only.

There is no error information.

Frozen instruments are loaded as frozen, but without the respective wav track.

It is only by defrosting the instrument and freezing it again that the normal situation is recovered.

2 hours ago, David Baay said:

I believe the version reported in File Stats int he browser and CWAF Tool is the version in which a project was originally created (i.e. saved for the first time). This is useful, but not necessarily the same as 'last recorded', obviously. But this seems like a case where the desired feature would be useful in only in this particular circumstance and not often at any other time. To really be helpful in troubleshooting version-related issues CbB would need to record the version  under which every significant edit was made to a project - not just recording -  and even then, going back to that version might not help.

CW is very good about maintaining compatibility across versions in both directions. I've had very few issues opening old projects in newer versions or even opening current projects in the last release of SONAR to confirm suspected regressions. And I've never had a problem opening audio files in any version that I can recall. Given the stability of the .WAV file format, I wouldn't expect otherwise, understanding that all the metadata related to clip editing, Audiosnap, Melodyne, etc is stored in the project, not in the .WAV file, with the exception of looping metadata in a Groove Clip which should follow a standard format. 

 

Thanks.

What I think would be important to have is, at least, the information of which version was the last recording of the project.
As a verification facilitator and support for the improvement of the tool, because in some cases I have gotten errors in projects recorded in older versions that, when opened in the most updated version, do not bring the wav files corresponding to the track and timestamp into the project from the project.

I think that this information, if it does not yet exist, being registered after recording the project, it could be registered and informed to the user.

On the other hand, one can also see the issue of VERSIONING.

Perhaps, in this case too, it would be possible to register the version that was recorded and, who knows, in the future, even be able to open the project with the version to which it corresponds.

They are evaluations and reflections that came from these errors that I saw in some projects.

21 hours ago, tparker24 said:

One way would be to run the CWAF (Cakewalk Audio Finder) tool, which reports (among many other things) the Cakewalk version.  For example, the latest version of Cakewalk is 28.02.0.039.

You can find the CWAF tool in Cakewlk in the Utilities menu.

You can click Help in CWAF for the documentation.

Excellent way. It is possible to check the recording version of the project.

However, the code used is not the same as what we currently see.

I think it would be the case that there is more equal information between the column shown in the CWAF and the help screen of the current version.

Application help screen.

And even, if possible, some message that guides the user like:

Attention this project was last recorded in a previous version of the DAW. There may be issues upgrading to this version.

Or something similar.

14 minutes ago, John Vere said:

Windows explorer can display different date formats including last modification. This is very accurate for when you wish to compare files. 
A great way to avoid future confusion is to simply include the date in the titles of “save as” backup copies.  

Thank you for your help.
Your suggestion is very good.
Even so, I think it would be interesting for the application itself to record this information.

I believe that this registry could help developers to understand some kind of error presented, especially when we know that many users do not always migrate to the latest versions.

WHICH VERSION WAS THE PROJECT RECORDED?

My question is if there is any way to identify, before opening the project, the version in which it was last recorded.

Something in the configs, some XML tags or something?

I ask why I am seeing some problems when I reopen some projects that had been finished in other versions and when opening with newer versions some files in wav format are not loaded in the open project.

21 hours ago, Kurre said:

You'll need this:

https://www.amazon.com/Digital-Optical-Analog-audio-converter/dp/B004C4WPXA

Yup. That's right ! I use it very well with my historic TASCAM US 600 connected to my mixer.

It works perfectly for me.

When saving Project Model, the project is only being saved after the operation is commanded a second time.

I have no way to confirm if the first operation is still being performed in the background.

Steps used to replicate the problem with me:

1) Save as Project Template.
2) Close model.
3) Open new project using the previously saved template.

Note: The model is not saved on the first save operation. Just look at the MODIFICATION DATE list field.

9 hours ago, Lord Tim said:

Looking at the other thread you made, it's not clear if you've reported any crash reports to the Devs.

Us users can't help you because you're unwilling to tell us anything about your problems or your system. 

If this crashing was as bad and as widespread as you're saying, the forum would be up in arms about it, which it's not, so it's clearly something that's either constrained to or exposed by your environment.

It could well be a CbB bug that your environment is exposing. If you don't report it, unless someone at Bandlab is a clairvoyant, nobody will know if there's a problem at all, let alone trying to solve it.

We *all* benefit from people reporting bugs that get fixed. These EA builds especially are here for us to give it a good test before the public release - this is the time to bring up problems, document them and report them.

Hello. I know my answer in this thread at the moment is out of focus which is: THOSE USERS INTERESTED AND WILLING TO HELP DEVELOPERS IMPROVE THE FINAL VERSION is to download the EA version and be collaborative, polite and detailed in their feedback on the version.

Personally, for some versions I only participate in the EA by downloading, testing, etc. when one of the implementations, improvements or bug fixes focus on difficulties that I go through in the production version I use.

If not, I don't participate anymore, keeping my version in production and stable in full use.

In this way I think I help more than hinder. So I have avoided at times, including, for sure there are, some forum members who are not very kind in their approaches to what is brought by other users.

It's my vision. I leave the topic moderators free to delete this comment of mine if they consider it inappropriate and without focus on the topic.

However, I want to register my perception and it's just a perception, nothing quantitative or statistical, that, for some time now, I don't know exactly which EA, the participation of users in EA versions has been getting smaller and smaller.

Therefore, I believe it is up to the team to identify why this happens. If not, then let's move on.

I'll be waiting for the public version.

Hug to everyone.

On 1/9/2021 at 2:10 PM, scook said:

It depends on the plug-in developer.

A few support VST3 migration.

Some update their plug-ins such that even in same format appears to the DAW as a different product.

Hello, something that was not clear to me in the documentation is, if it is possible to migrate VST2 -> VST3 in this configuration, the presets or parameterization until then existing in the plugin is maintained or only the replacement of VST2 -> VST3 is made, being included in the plugin's default parameterization as if included for the first time.

2 hours ago, User 905133 said:

I select the take lane and double click on the text field.  See this to expand the take lanes.

In fact, I didn't see any reference in the documentation to this field that is not hidden, but exists in a line of type TAKE.

I'll try to improve my view of it working on the Model.

46 minutes ago, Starship Krupa said:

 

I can see on clicking that there is a "Box", but I can't get into the edit.

How to enter the editing/inclusion of information in this "hidden field"?

On 5/5/2022 at 4:28 AM, Starship Krupa said:

I use the notepads in the track lane header:

 

How to access this box to enter information?

I get good results when "EXPORTING TO CLIPS".
In the new generated clip/track the pops disappear for me.

1 hour ago, Milton Sica said:

@msmcleod

Hi,
Has anyone managed to use MIDICHOIR in Cakewalk Bandlab?

I managed to do it as follows.
For basic use I used 3 tracks, one with the audio of the original voice, another with the audio of the duplicated voice and a third MIDI.
1) Insert the MIDICHOIR in the second audio track. (track 1 and 2 have the same WAV content)
2) Enable MIDI Input/Output Plugin.
3) I created the MIDI content by copying it with CTRL - SHIFT and dragging the audio file to the MIDI track, transforming its content into MIDI.
4) I set the MIDI output to MIDCHOIR.

It worked.

Detail > Only works if the track has the same recorded audio content as the track where the MIDICHOIR was inserted

I got good results from multiple voices doing only the sung melodic sequence (Song Chords)

On 10/14/2020 at 1:43 AM, Matthew Sorrels said:

The deals forum isn't the best for this (you might want to open a thread in Instruments & Effects).  In order to be able to send MIDI to the MIDI Chorus plugin you have to enable MIDI Input to it using the drop down above the plugin in Cakewalk

So basically put it on a audio track.  Enable the MIDI input.  Add a MIDI track and route it to the MIDI Choir (which will now be a choice in the MIDI track's output drop down).

 

@msmcleod

Hi,
Has anyone managed to use MIDICHOIR in Cakewalk Bandlab?

1 hour ago, John Vere said:

The above statement doesn't really explain what you are facing .  It could imply a few different scenarios. 

But if you read my question you'll see I wanted to actually know what you where seeing when you open the project.  

 

Thank you for your help.
I answer your question.

1) WAV files with data that should be on the respective tracks in the project are not present at their place/time.
2) WAV files are in the AUDIO folder.

7 hours ago, msmcleod said:

To be honest, I'm sceptical about relying on such information in this particular use-case.  

The fact that Cakewalk is saying that the files are missing even though they're not, would indicate the part of project that stores information about the clips has been corrupted, so there's a very good chance you couldn't rely on any other clip information as this may well be corrupted too.

A better question would be how it got corrupted in the first place.  Although it's possible it could be a Cakewalk bug, I suspect it's more likely to be a plugin overwriting memory it shouldn't be - else we'd be seeing reports of this all the time. 

If you want a bullet-proof backup of your audio files, maybe consider exporting the clips as broadcast waves using the Export Dialog, and using a filename such as

{projectname}-{tracknumber}-{laneindex}-{clipindex}-{trackname}-{clipname}

  It should then be easier to drag these back into the project if necessary.

Thank you for your help.
I understand that if there was this loss of references, the project itself would not have them in an intelligible listing of these references.

Do you find it very difficult for the DAW to provide an intelligible listing of the insert time references for each wav?

I ask why I have the configuration for generating project versioning.

If the DAW had this listing in some of the saved versions, this information could be retrieved more easily.

7 hours ago, Bill Phillips said:

My theory is, the clip properties meta data including start time is in the individual clip files not the project file. But I've never needed to test or prove it. If so the clips know where they belong on the time line. 

Thanks a lot for the feedback.

It is a theory to be tested.

I've done several tests to reinsert the files. By his theory there would be an identification by the DAW where they should be inserted and it would put each WAV in "its place".

Unfortunately I didn't get that result.

When multiple files are imported, as many new tracks are created as there are files.

When importing WAVs one by one in sequence, the DAW appends them to the end of each one without retrieving any reference to the timestamp at which it would be inserted.

As a result, this information is only available in the project file.

Therefore, if the project has this information that is used to reinsert or reference the files at their correct times, it would be very good to be able to generate a listing with these settings.

@msmcleod

What do you think about this ?

11 hours ago, John Vere said:

Question? are the original audio tracks all there? As in there are tracks for the missing audio but they contain no data. Or are the complete tracks totally missing? 

If the tracks are still there but empty of data my approach would be to open the audio folder in the browser and using the audio file track names drag them into a lane for that track. Use as many lanes as needed.  I would guess that using the numbers assigned  and the time stamp as shown in my screen shot would tell me what order they were originally in. Then soloing each lane along with the rest of the music to slowly figure out were they belong in time. 

Thanks a lot for the feedback.
Yes ! The wavs are all there intact.
There is a sequence of takes and the modification date/time is a step towards recovery.
I can do this on tracks that start from team 0:00:00.
The problem is in inserting those WAVs from several outlets.

15 minutes ago, John Vere said:

Well Cakewalk would naturally know all that information otherwise the audio would not play in sync. But that information will be imbedded in the CWP files data code as zero's and ones. One would have to somehow read the data inside the CWP files.

The scary mess found in an audio folder is one reason I have taken to exporting all my broken up audio tracks as stems and then bring them back in as one whole track that always starts at zero. At first I did this to convert projects from 44.1 to 48hz but then I also found that this was the best way to have audio for doing other things like slowing down or speeding up a song.  I use save as to have a fresh copy and when done you look in my audio folder and there is only 1 file per track now. 

This is very good as it is a big step towards recovery in cases like the one I described.

In these cases, unfortunately, I have not found a solution.

It's too bad, because ALL WAVS are there in their own folder and without possibility of insertion in their correct times.

12 minutes ago, Bill Phillips said:

Doesn't clip properties provide the start time and length for each clip? Also you may be able to load clips at their original start time.

This information only exists when the wav (clip) is in the project.

The problem is when, as I described, the file disappears from the project.