[CWBRN-28852] - Dimension Pro - Crash on cloning track

Author
Greeny
Max Output Level: -87 dBFS
  • Total Posts : 181
  • Joined: 2014/09/26 11:55:12
  • Status: offline
2014/10/01 07:17:26 (permalink)
0

[CWBRN-28852] - Dimension Pro - Crash on cloning track

Ok Alex ask me to post this here as I mentioned it in another thread.
I cannot clone a track that has FX in the bin without a crash, I tested with a bunch of VSTi/VST combos and it crashes literally every single time there is a vst fx in the bin.
 
To see if it just me or a cakewalk issue try this...
 


1. insert dim pro (or any other vsti), load a patch, play in a little midi clip.
2. Add ANY vst FX to the FX bin
3. Clone track, get ready for crash recovery.

Cheers, Greeny
 
EDIT: I forgot to mention that all my stuff is upto date, and I am using sonar x64 on windows 7.
post edited by CakeAlexS - 2014/10/06 18:14:53
#1
Splat
Max Output Level: 0 dBFS
  • Total Posts : 8672
  • Joined: 2010/12/29 15:28:29
  • Location: Mars.
  • Status: offline
Re: Crash on cloning track 2014/10/01 13:05:44 (permalink)
0
STEPS
1) New Project
2) Insert DP 1.5 simple instrument track.
3) Select a DP patch from the program browser.
4) Throw in bifilter into FX bin
5) Drag in and loop midi file.
6) Save
7) Select whole track
8) Right click clone track.
9) Select all tickboxes except "Link to original clips", reps = 1, starting track =3 10) Click OK.
 
EXPECTED
Cloned track

ACTUAL
A Sonar crash dump occurs, which generated CWBRN-28852.
 
So confirmed! Thanks for that...

Sell by date at 9000 posts. Do not feed.
@48/24 & 128 buffers latency is 367 with offset of 38.

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.4,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),4 x Seagate ST31500341AS (mirrored),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5.Maschine Studio+Komplete 9 Ultimate+Kontrol Z1.Addictive Keys,Izotope Nectar elements,Overloud Bundle,Geist.Acronis True Image 2014.
#2
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Crash on cloning track 2014/10/01 13:17:40 (permalink)
0
Ignoring for the moment the crash formula, cloning instrument tracks in general does not produce a useful result.
#3
Greeny
Max Output Level: -87 dBFS
  • Total Posts : 181
  • Joined: 2014/09/26 11:55:12
  • Status: offline
Re: Crash on cloning track 2014/10/02 01:28:56 (permalink)
0
It does if you for example want a filtered version of the same track for another part of the song, I dont use clone anymore because of this crash, but the fact that I found this bug suggests cloning a track is actually useful to me.
 
For now I shall stick to making a new track with the same instrument and copy dragging the FX over to the new track.
#4
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Crash on cloning track 2014/10/02 02:13:26 (permalink)
0
CakeAlexS
7) Select whole track

I believe if this step is skipped SONAR does not crash. There is no need to select a track to clone it. The track only needs focus.
 
Also another solution may be: split the instrument track and clone the audio track only.
#5
Greeny
Max Output Level: -87 dBFS
  • Total Posts : 181
  • Joined: 2014/09/26 11:55:12
  • Status: offline
Re: Crash on cloning track 2014/10/02 03:24:16 (permalink)
0
It still does it for me without selecting the whole track, I just right click the track and hit clone from there without highlighting the entire track and it still crashes. The only way I can have it work without crashing is to have absolutely nothing in the FX bin of the track I am cloning.
#6
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Crash on cloning track 2014/10/02 03:39:20 (permalink)
0
I followed the steps in #2 above. Without step 7, the track cloned OK. With step 7, the track fails after creating the cloned audio and MIDI tracks just before joining the clones back to an instrument track.
post edited by scook - 2015/03/07 10:50:29
#7
Greeny
Max Output Level: -87 dBFS
  • Total Posts : 181
  • Joined: 2014/09/26 11:55:12
  • Status: offline
Re: Crash on cloning track 2014/10/02 04:23:01 (permalink)
0
Tried again an no matter what it crashes, I haven't done step 7 the track I tried to clone wasn't even in focus I just used the right click menu on it, the blue highlight was on the track above the one I was cloning.
 
Also, the thread has been renamed to dimension pro for some reason, it happens will all vsti not just dimension I used dimension as an example since it is bundled.
#8
Grem
Max Output Level: -19.5 dBFS
  • Total Posts : 5562
  • Joined: 2005/06/28 09:26:32
  • Location: Baton Rouge Area
  • Status: offline
Re: Crash on cloning track 2014/10/02 06:46:18 (permalink)
0
I remember something about Simple Instrument trks causing a crash on cloneing. I think it was Sharke who was having trouble with it. But IIRC it was only SIT. I am wondering what's going on now.

Not at my computer to try this. But I clone guitar trks with FX in it. So I am wondering what changed. I won't be back home till Sunday.

Does it matter if FX is in the bin or PC FX rack?

Grem

Michael
 
Music PC
i7 2600K; 64gb Ram; 3 256gb SSD, System, Samples, Audio; 1TB & 2TB Project Storage; 2TB system BkUp; RME FireFace 400; Win 10 Pro 64; CWbBL 64, 
Home PC
AMD FX 6300; 8gb Ram; 256 SSD sys; 2TB audio/samples; Realtek WASAPI; Win 10 Home 64; CWbBL 64 
Surface Pro 3
Win 10  i7 8gb RAM; CWbBL 64
#9
Greeny
Max Output Level: -87 dBFS
  • Total Posts : 181
  • Joined: 2014/09/26 11:55:12
  • Status: offline
Re: Crash on cloning track 2014/10/02 07:31:09 (permalink)
0
I will test now. I have no issues with audio tracks btw only SIT.
 
 
EDIT: Done more testing, if I skip step 7 using boost11 as the vst I get no crash but with some vst I still do. PC makes no difference - no crashes for PC.
#10
Greeny
Max Output Level: -87 dBFS
  • Total Posts : 181
  • Joined: 2014/09/26 11:55:12
  • Status: offline
Re: Crash on cloning track 2014/10/02 07:51:38 (permalink)
0
My mistake, I have just cloned like 20 times with various vsts in the bin without the track highlighted and no crash, I must've had it highlighted and not realised before - Doh!
 
Would be cool to see this fixed properly but at least I can clone trcks in safety now - if I just remember to make sure the track aint selected.
 
 
 
#11
robert_e_bone
Moderator
  • Total Posts : 8968
  • Joined: 2007/12/26 22:09:28
  • Location: Palatine, IL
  • Status: offline
Re: Crash on cloning track 2014/10/02 09:35:06 (permalink)
+1 (1)
Glad you can at least continue to do your work.
 
I played around with Simple Instrument Tracks way back when, but never trusted them, and I cannot even recall how long it has been since I switched over to using separate audio and midi tracks for everything.  
 
I do think the bug should get fixed, seems pretty simple to identify the conditions that produce it, and then it would just be some code to do something different, but in any case it is indeed good news you can now keep on tracking til they DO fix it.
 
Bob Bone
 

Wisdom is a giant accumulation of "DOH!"
 
Sonar: Platinum (x64), X3 (x64) 
Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22
Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64
Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others
MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es
Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms  
#12
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
Re: Crash on cloning track 2014/10/02 12:31:35 (permalink)
0
SITs are fine for simple applications. I use them occasionally. Many of their issues have been addressed since their introduction. In the past, I used SITs only for testing issues like this one preferring to use separate audio+MIDI tracks exclusively. Anytime an SIT needs manipulation such as this, I still split the track. Manipulating SITs is too risky for me.
#13
Greeny
Max Output Level: -87 dBFS
  • Total Posts : 181
  • Joined: 2014/09/26 11:55:12
  • Status: offline
Re: Crash on cloning track 2014/10/02 14:39:37 (permalink)
0
I cant tell you how happy I was with the birth of SITs (and the same things in other daws too) so I pretty much use them unless there is a reason not to. Other than this cloning crash I have never had issues in x3e with them so I will probably continue to do so, I am glad we found a workaround that doesn't involve any interruption to my workflow though.
#14
Splat
Max Output Level: 0 dBFS
  • Total Posts : 8672
  • Joined: 2010/12/29 15:28:29
  • Location: Mars.
  • Status: offline
Re: Crash on cloning track 2015/02/10 17:00:10 (permalink)
0
Just following this up...
Is #2 reproducible in Platinum?
 
Thanks..
 

Sell by date at 9000 posts. Do not feed.
@48/24 & 128 buffers latency is 367 with offset of 38.

Sonar Platinum(64 bit),Win 8.1(64 bit),Saffire Pro 40(Firewire),Mix Control = 3.4,Firewire=VIA,Dell Studio XPS 8100(Intel Core i7 CPU 2.93 Ghz/16 Gb),4 x Seagate ST31500341AS (mirrored),GeForce GTX 460,Yamaha DGX-505 keyboard,Roland A-300PRO,Roland SPD-30 V2,FD-8,Triggera Krigg,Shure SM7B,Yamaha HS5.Maschine Studio+Komplete 9 Ultimate+Kontrol Z1.Addictive Keys,Izotope Nectar elements,Overloud Bundle,Geist.Acronis True Image 2014.
#15
Jump to:
© 2024 APG vNext Commercial Version 5.1