Milton Sica

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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"?

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.

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)

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

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.

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.

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 ?

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.

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.

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.