Will report back when I get time but wanted to give the Bakers a heads up.
 
I'm a sound designer. I am working on a film.
 
I have a project, 70 tracks, 1 Kontakt synth, the rest audio. Film is 20 mins.
 
I have a track group for score which is just imported pre recorded audio that I make edits on for cues and fades.
I had made everything perfect but wanted to make one last change at a WAV that has been repeated before in the film but near the end.
I made some adjustments. (fades and gains) All good.
 
Export the wav.
 
Delivered to the director.
 
To my utter dismay Sonar had made weird in point and outpoint changes to the previous repetitions of the wavs. The wavs are not linked and were imported separately. But it made me look like I had missed all my cues.
 
Also the change that I made in the last wav (although independently imported and should therefore be its own file within my project) made no sense to the changes that Sonar made with the previous two????
 
Not cool.
 
I explained this to the Director on User error (which it wasnt) but from now on I am going to be uber careful.
 
Film if anyone is interested is this. http://www.imdb.com/title...04/?ref_=nm_flmg_snd_1

I don't think I quite understand the description of the bug here.
 
I will say this. I never ever ever ever ever send an export out without listening to it first.

I'm not understanding the OP either. A clear description of the problem would be very useful.  

Forget the OP then.
 
I dont understand the bug either, isnt that the point of them?
 
1. Import a wav file (previously bounced from Sonar) and insert it at 1m 47
2. work on a 70 track project during which are 1000's of changes, consisting of one Kontakt folder with 8 midi tracks, the rest are audio imports derived from AAF's exported to OMF's via PT 10.6.8.
3. Import the same bounced wav file, import it at 17. 72
4. Make a cue change i.e the timeline
5. export project
 
Expected results. Wav files are independent and have been edited as exptected
 
Bug. Changes in the 17.72 file have made bizarre changes to the the 1m 47 file in that its cue point (i.e start) is completely different and also has introduced a fade in point irrelevant to changes made to the latter file.
 
Is that better for you John? (sometimes I find your style of moderation extremely frustrating, not with me but deffo with others, there are alot of people on here who are experienced and professional and would sometimes like a bit of a rant. This is a community, not a concentration tech camp arena)
 

John T
I don't think I quite understand the description of the bug here.
 
I will say this. I never ever ever ever ever send an export out without listening to it first.

 
In my experience normally I would say the same. But I was pushed for time on a first pass.
 
This isnt the first time I have been let down by weird annoyances. 
 
Also, please, I am a professional and this is NOT human error.
 
Can I reproduce it? 
Probably not as there were hundreds of edit snapshots and possibilities in between the error so I cant pin point.
 
Have I got time to reproduce the error?
No.
 
How do I know its a Sonar thing?
Because I have been using Cakewalk for about 20 years meaning that I am experienced and do this process day to day, but i can 100% identify that we have bugs in this software.....Sonar.exe crashing and not releasing drivers, weird happenings with Win10 drivers and the sharing of said drivers, mad crashing on exporting of projects at clip point edits, OMF's crashing on importing...
I find these things well annoying. I have done for some time.
 
Do I want to move from Sonar?
No.
 
Why?
Because I love Cakewalk.
 
Am I annoyed?
Yes
 
This is a slight rant but I would hope my fellow community will understand the frustrations of glitches. I dont need help with it, its merely to highlight that even us experienced folk get them too.

markyzno
 
 
Bug. Changes in the 17.72 file have made bizarre changes to the the 1m 47 file in that its cue point (i.e start) is completely different and also has introduced a fade in point irrelevant to changes made to the latter file.

So the unintended changes to the first clip are different from the changes you made to the second one?

I feel better for that. Thanks.
 
Still. Problems remain as with any software I understand that.
 
But I have been banging on about OMF's and weird edit point crashes in exports and the like for years and nobody seems to listen.
 
How many hours do I have to waste on these things?
 
But The amount of hours I gain in amazing software seems to almost way up and balance it out, but when its old problems you have reported time and time again and nothing gets fixed addressing your issue and new features are introduced for bringing in new clients makes me frustrated....
 
At work, often, I in criticize our client configuration team for focusing on "Shiny new toys" and I really feel that Cakewalk do this sometimes, especially with all the change and various takeovers. I just wish they would focus on the product IN HAND as well as moving forwards. A natural harmony.
 
 

John T

markyzno
 
 
Bug. Changes in the 17.72 file have made bizarre changes to the the 1m 47 file in that its cue point (i.e start) is completely different and also has introduced a fade in point irrelevant to changes made to the latter file.

So the unintended changes to the first clip are different from the changes you made to the second one?

The intended changes on the latter clip forced unintended changes on the first clip.
The only logical explanation I can give is that they are of the same source.
 
But I have the option of copying all clips on import...So, In theory they should be entirely independent.

markyzno
 
The intended changes on the latter clip forced unintended changes on the first clip.

The thing is, I can't work out how, just based on what you've said in this thread, you can be so sure about that.
 
Not saying you're wrong, I'm just interested in diagnosing it.

I mean, you're definitely right that if you exported them separately, Sonar wouldn't even know that the source was the same.