Jump to content
Morten Saether

2021.09 Feedback

Recommended Posts

Just now, Kevin Perry said:

My memory may be failing (no comment :-)) but doesn't some of that pull from the Info tab in the browser?

Yes.

The Title and Album are taken from the Name & Album fields from the Notes tab. 

If you're doing a tracks export, the Title field is replaced by the track name.

Share this post


Link to post
Share on other sites

Fantastic update, the new export system rocks!

Didn't have time to participate in the early access, but one thing that would seem more logical to me is to automatically recall the task settings in the dialog when a task is selected (or have a checkbox somewhere that enables this behaviour), and also a prompt to save changes when selecting a different a task (if the current task is has been changed)

The whole recall task settings / update task settings seems a bit cludgy to me - perhaps it'll be refined in a later update? Can appreciate the line would need to be drawn somewhere on this new dialog, as it's already got soo much functionality.

Share this post


Link to post
Share on other sites
2 hours ago, msmcleod said:

If you specify MP3 as an output format, the MP3 Export Options dialog will appear either when clicking Export or clicking the "Add Task" button.

When the MP3 Export Options dialog appears, make sure you check the "Encode ID3 info" checkbox:image.thumb.png.2d57aaeae6d20374bbccd272e8cc96e0.png


 

I may be missing something in the operation, but the only information that is transferred from the project to the MP's ID3 is the song name and artist name.
The album name is not filled in and comments are created automatically by the program itself.

 

image.png.8c40933c9ab49286d66e6d3fc042467f.png

  • Thanks 1

Share this post


Link to post
Share on other sites
3 hours ago, Matthew Carr said:

Fantastic update, the new export system rocks!

Didn't have time to participate in the early access, but one thing that would seem more logical to me is to automatically recall the task settings in the dialog when a task is selected (or have a checkbox somewhere that enables this behaviour), and also a prompt to save changes when selecting a different a task (if the current task is has been changed)

The whole recall task settings / update task settings seems a bit cludgy to me - perhaps it'll be refined in a later update? Can appreciate the line would need to be drawn somewhere on this new dialog, as it's already got soo much functionality.

You can double click any task to recall its settings. Recalling automatically would have been potentially annoying if someone just clicked a task.
To save new settings to an existing task you can do it from the drop down menu for the task (button to the right of the task)

  • Like 3

Share this post


Link to post
Share on other sites
5 hours ago, msmcleod said:

Yes.

The Title and Album are taken from the Name & Album fields from the Notes tab. 

If you're doing a tracks export, the Title field is replaced by the track name.

There is another problem with the generation of MP3 file ID3s.

I use a project that serves to master several exported files from their original projects.

By checking the option to generate MP3 with ID3 the current project values are not transferred to the ID3 information.

There is really no exchange between the DAW and the MP3 parameterizer.

 

In the image:
The first exported file with settings in the task.
The second file exported only running the tasks.

It is verified that the ID3 tag, instead of bringing the current information of the project, kept the ones from the moment of recording.

Symptom: the programs only interact when the task is generated.

 

image.png.d3dc783e752ce33104112a2e9d4241e5.png

In export

image.png.5810af10bdd7e665aeaf09a7ce54b748.png

Edited by Milton Sica

Share this post


Link to post
Share on other sites

This is as expected. The content of the MP3 export dialogs is captured at the time that the tasks are created allowing the user to change the default ID3 info.
If you change the project settings after the fact it won't pick it up. You will need to update the tasks manually if you do that.

  • Like 1

Share this post


Link to post
Share on other sites
7 minutes ago, Noel Borthwick said:

You can double click any task to recall its settings. Recalling automatically would have been potentially annoying if someone just clicked a task.
To save new settings to an existing task you can do it from the drop down menu for the task (button to the right of the task)

Yes, I can see that the automatic recall might be annoying,  but at the moment it's hard to see many other reasons for clicking on a task, other than to delete it, rename it, or open the output folder , which could all be handled by the task drop down menu - meaning the default action of clicking on a task line would be a more natural paradigm of form and sub-form. As long there's a prompt to save or cancel any changes (if dirty) before any new task is recalled, then the  recall / save could be automatic, and the options removed from the drop down menu.

 The double click is a handy shortcut, but perhaps not be best UI wise

1. Double clicking the task is a 'magic' action -  you wouldn't know to do it unless you've been told
2. If you've double clicked the task, there is nothing to tell you that the dialog is now showing the details of the task that's been double clicked

Not trying to rain on the parade - the new export dialog is a massive step forward and I'm stoked! Just from my perspective it could be slightly more consistent with the way other UIs work.

Cheers,

Matt

Share this post


Link to post
Share on other sites
43 minutes ago, Noel Borthwick said:

This is as expected. The content of the MP3 export dialogs is captured at the time that the tasks are created allowing the user to change the default ID3 info.
If you change the project settings after the fact it won't pick it up. You will need to update the tasks manually if you do that.

From what I understand then this ID3 parameterization is global for the entire Cakewalk session and not by project, ie:

From the first parameterization and while Cakewalk is open, no matter how many projects are opened, the ID3 data will be kept as of the first parameterization, forcing me to re-inform the data in each export.

There is a very strange behavior in this parameterization with the data.

My wish is that this ID3 data would also be automatically updated per project and that the tasks would do the same when using the other fields.

Is this possible?

Share this post


Link to post
Share on other sites
25 minutes ago, Milton Sica said:

From what I understand then this ID3 parameterization is global for the entire Cakewalk session and not by project, ie:

From the first parameterization and while Cakewalk is open, no matter how many projects are opened, the ID3 data will be kept as of the first parameterization, forcing me to re-inform the data in each export.

There is a very strange behavior in this parameterization with the data.

My wish is that this ID3 data would also be automatically updated per project and that the tasks would do the same when using the other fields.

Is this possible?

The ID3 data is populated at the time the dialog is opened, based on the current project, and current export criteria.

If you do a track export for example, it will use the track name as the name, and takes the rest from the browser notes tab. It will show a different name for each and every track. 

If you check "Use same settings for all", then it will automatically populate each "name" field with the track name.

For entire mix exports, it'll use the project name.

Whatever is chosen within the dialog will be saved in the task.  It does not get updated if you subsequently change the project name / track name / artist etc.

Share this post


Link to post
Share on other sites
34 minutes ago, msmcleod said:

The ID3 data is populated at the time the dialog is opened, based on the current project, and current export criteria.

If you do a track export for example, it will use the track name as the name, and takes the rest from the browser notes tab. It will show a different name for each and every track. 

If you check "Use same settings for all", then it will automatically populate each "name" field with the track name.

For entire mix exports, it'll use the project name.

Whatever is chosen within the dialog will be saved in the task.  It does not get updated if you subsequently change the project name / track name / artist etc.

Excuse me. I also thought this would be the correct procedure.

But that's not how it happens.

If you parameterize ID3 and record in a task, this data is not recorded as a task parameter.

If I record a task with ID3 song name as TEST this name will be perpetuated for all other files I export. There is no update of information.

My operation uses a project to master several songs.
I import the WAV file, make the final mastering edits and perform 2 tasks that generate a WAV file and an MP3 file.
For every mastering I make I change the song name.
Both WAV and MP3 tasks recognize the song name TAG of the project notes, but the MP3 ID3 does not, keeping the settings used from the first mastered project.

 

Two projects open in a Cakewalk session

Project 1 - Test

image.png.0c9a37b0c7ec02fd7b5b2fac21c90ef2.png

Project 2 - Test 2

image.png.9e0c6c6efabe5e7ba05d13e8bcc820a7.png

In summary: in the same Cakewalk session the ID3 parameters are kept for the first export and are not written to the task.

 

Where this ? "If you check "Use same settings for all", then it will automatically populate each "name" field with the track name."

Edited by Milton Sica

Share this post


Link to post
Share on other sites
1 hour ago, Milton Sica said:

Excuse me. I also thought this would be the correct procedure.

But that's not how it happens.

If you parameterize ID3 and record in a task, this data is not recorded as a task parameter.

If I record a task with ID3 song name as TEST this name will be perpetuated for all other files I export. There is no update of information.

My operation uses a project to master several songs.
I import the WAV file, make the final mastering edits and perform 2 tasks that generate a WAV file and an MP3 file.
For every mastering I make I change the song name.
Both WAV and MP3 tasks recognize the song name TAG of the project notes, but the MP3 ID3 does not, keeping the settings used from the first mastered project.

 

Two projects open in a Cakewalk session

Project 1 - Test

image.png.0c9a37b0c7ec02fd7b5b2fac21c90ef2.png

Project 2 - Test 2

image.png.9e0c6c6efabe5e7ba05d13e8bcc820a7.png

In summary: in the same Cakewalk session the ID3 parameters are kept for the first export and are not written to the task.

 

Where this ? "If you check "Use same settings for all", then it will automatically populate each "name" field with the track name."

I get what you're saying/asking/requesting. 

In other words: The Mp3 ID3 option can just as well be added to the new EXPORT window and remove this final window entirely. So that means, if you choose any mp3 track tags it will automatically be added to these fields/columns? Make sense to have one window for this. 

Share this post


Link to post
Share on other sites
3 hours ago, Will_Kaydo said:

I get what you're saying/asking/requesting. 

In other words: The Mp3 ID3 option can just as well be added to the new EXPORT window and remove this final window entirely. So that means, if you choose any mp3 track tags it will automatically be added to these fields/columns? Make sense to have one window for this. 

Thanks for your response.

Exactly.
I think both possibilities would be better.

When we recorded the tasks and, when exporting to MP3 we received some more options to be completed, I think it would be much better if this information not only came from what is in the Project Notes, as well as being recorded in the tasks.

I think this implementation would be better operationalized.

Share this post


Link to post
Share on other sites
7 hours ago, Noel Borthwick said:

This is as expected. The content of the MP3 export dialogs is captured at the time that the tasks are created allowing the user to change the default ID3 info.
If you change the project settings after the fact it won't pick it up. You will need to update the tasks manually if you do that.

Unfortunately this is not what is happening, even in the existing specification.

I retrieved the task information and when saving again, the ID3 information remains the same as the first run.

 

image.png.693ef9e83dd0d2fb294b0da5441eee47.png

Even when another project is open in another window.

image.png.4479f1311e485c86bd4a6e4e6ee6397a.png

My tests confirm that ID3 parameters are only changed/updated once per CAKEWALK session.

If you open several projects, even keeping only one in the application in a single window, the ID3 information remains the same as the first exported project.

And are not updated in the task.

 

I opened and closed several projects commanding the export to MP3 and ID3 parameterization was always the same. In other words: that of the first project worked on in the cakewalk session.

image.png.aa9819ed1135bae68e5e9fbba6406ce4.png

I don't believe this is expected behavior.

Could it be related to my LAME 3.100 encoder version?

image.png

Edited by Milton Sica

Share this post


Link to post
Share on other sites

Hi @Noel Borthwick,

As requested, reporting a Cakewalk fault on this thread.

I'm a pro user who is a hybrid mixer (a digital/analog integrated setup) and make use of the 'external insert' function within Cakewalk.

The first problem I'd like to report, which I know you're aware of, is the external insert only allows two mono returns, but, does not allow two mono sends (and, when assigning analog outboard in the input and output drivers in Cakewalk preferences, we only have the option to label things in stereo pairs).  This is a major functional flaw for a hybrid mixer, as, it means we can't  send two mono analog returns to two consecutive analog inputs as Cakewalk will route a stereo signal through to them from one channel, thus, making the second channel unusable.  So, for example, I have an 1176 compressor and an LA2A compressor  in my rack, routed to inputs 1 and 2 consecutively, and routed to outputs 1 and 2 consecutively.  I would like to insert the 1176 to a mono bass track in channel 1 on cakewalk, and, insert the LA2A to a vocal track in channel 2 on cakewalk.  This is not possible: I have to assign the mono compressor across a stereo channel send and both mono compressors can only be used in the one track.  For me to get two usable mono analog units inserted into Cakewalk, I have to route to two stereo sends on Cakewalk (so, one mono compressor will send to track 1-2 and the other mono compressor will send to tracks 3-4, even though, I only want them sending to one track), thus, wasting away precious DA converters that I've spent an enormous amount of money on.  

The second problem, which has only just started occuring since I updated to Build 120, 64 Bit, is when soloing a track with an external insert in the Cakewalk FX rack, the audio stops (while the session is still playing).  This has been the case for a long time when soloing a buss with an external insert in the FX rack, but now, the same problem occurs when soloing a single track. 

I understand your priority is to not service your pro users who are hybrid mixers, but, this approach to mixing is becoming more common now, and, I'm sad to see Cakewalk getting behind with basic hybrid functionality.  I've been using Cakewalk (as a pro) for over 15 years now, but, if a fix isn't offered soon, I'll be forced to start learning a new DAW, as, I've invested too much in my ADDA conversion to just waste channels with the multiple mono units I'd like to use.  I really don't want to do this; I've been very loyal to Cakewalk and would consider myself an expert user, and, to relearn all the intricacies I know on Cakewalk, would be a massive pain, but, as hybrid mixing is a must in my studio, I have to use what works.  I look forward to hearing from you (and happy to provide more information or conduct tests if necessary).

regards,

Adam Casey

The True Vine Recording Studio

Melbourne, Australia

Edited by Adam
  • Thanks 1

Share this post


Link to post
Share on other sites

After updating to 141, the export function didn't work for almost 2 days. It either exported silence, or exported the song with no effects at all - including guitar amps, etc. - or with only some of the tracks audible, some of the tracks coming in and out. This was for both the new menu and for exporting from from the control bar. It just started reworking by itself.

Yesterday, a spontaneous Waves Element failure - which never caused any problems - completely disabled the master bus, and both sound interfaces made weird fax like crackes/pops/buzzes on opening the project or toggling plugins on/off. Element was on a previously frozen and unfrozen track.

Share this post


Link to post
Share on other sites

Not mission critical, but upon export of a single project file on my desktop, I get the toast popup.

On my laptop, similar function, I DO NOT get the toast popup.

Let me know if there are any specific settings that I've missed

Share this post


Link to post
Share on other sites
5 minutes ago, OutrageProductions said:

Not mission critical, but upon export of a single project file on my desktop, I get the toast popup.

On my laptop, similar function, I DO NOT get the toast popup.

Let me know if there are any specific settings that I've missed

The toast is not shown when executing export tasks in the queue because tasks can create multiple files in different locations. Its only shown when doing a single export.

Share this post


Link to post
Share on other sites
20 minutes ago, Olaf said:

After updating to 141, the export function didn't work for almost 2 days. It either exported silence, or exported the song with no effects at all - including guitar amps, etc. - or with only some of the tracks audible, some of the tracks coming in and out. This was for both the new menu and for exporting from from the control bar. It just started reworking by itself.

Yesterday, a spontaneous Waves Element failure - which never caused any problems - completely disabled the master bus, and both sound interfaces made weird fax like crackes/pops/buzzes on opening the project or toggling plugins on/off. Element was on a previously frozen and unfrozen track.

@Olaf if you have any project that exhibits this we'd like to see it. To rule out any of the new stuff did you try turning off effects tails flushing and are you exporting with the buffer size set to "follow playback"? Does this problem still persist?

Share this post


Link to post
Share on other sites
3 minutes ago, Noel Borthwick said:

did you try turning off effects tails flushing

no, i haven't. i didn't know about the option. but ALL effects were disabled, not just the reverbs.

 

4 minutes ago, Noel Borthwick said:

are you exporting with the buffer size set to "follow playback"?

yes, that was the setting.

 

4 minutes ago, Noel Borthwick said:

Does this problem still persist?

no, it restarted working by itself. for now i am using a 140 buffer, and it's working.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...