williamcopper
Max Output Level: -68 dBFS
- Total Posts : 1120
- Joined: 2014/11/03 09:22:03
- Location: Virginia, USA
- Status: offline
Warning sign that a cut & paste midi crash is due
At some point in working on projects, "cut special" stops working. The dialog no longer pops up, the action happens immediately as if it is a simple cut. I've noticed this for a long time, but only recently realized it is a warning sign that if ignored indicates a crash is coming. Saving project, restarting sonar with exactly the same project somehow re-energizes "cut special" so it works again.
|
mettelus
Max Output Level: -22 dBFS
- Total Posts : 5321
- Joined: 2005/08/05 03:19:25
- Location: Maryland, USA
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 08:20:12
(permalink)
There was a thread a few years ago about SONAR running best when saved frequently, and the speculation has long been that being related to the size/complexity of the undo history. This observation has merit, as most editing programs have a preference option of "# of undos to keep in history," especially when those undo's can be massive. I never went searching for such a setting in SONAR (so not sure if such exists). I have not had SONAR ever belly up during a save, but the new SONAR has a "File->Save Copy As" as well. I have never used that, so not sure if it actually resets undo history or not.
ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
|
jatoth
Max Output Level: -83 dBFS
- Total Posts : 363
- Joined: 2009/08/12 06:31:35
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 08:27:22
(permalink)
The setting is in the "Edit-History" option from the menu. You have to have made at least one edit for "History" to be available. It seems we are getting close to finding the source of "random" crashes while editing. I have had several crashed while doing a lot of copy and paste in staff view, I just changed the undo history settings. Let's see if that helps. But, being random in nature, it may be a while before I realize the crashes are gone.
John X3e Producer, Sonar Platinum, Sweetwater CreationStation i5 3.1gHz, 12 GB RAM, 500GB SSD OS drive, 1TB SSD audio drive, 1TB archive/misc drive, dual 22" monitors, Windows 7x64, SaffirePro40 (firewire), MOTU MIDI Express XT, Behringer BCF2000, dbx 586, Samson Servo 120a, Yamaha HS80M, Auratone 5c Cubes, Sennheiser HD650, Sony MDR 7509HD, Sony MDR 7506, Kurzweil K2500XS, Roland XP-30, Proteus 2000.
|
williamcopper
Max Output Level: -68 dBFS
- Total Posts : 1120
- Joined: 2014/11/03 09:22:03
- Location: Virginia, USA
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 08:30:29
(permalink)
good reminder of history, Mettelus -- maybe, in fact, the two are related -- a project that has become fragmented into many many clips could possibly take up a great deal more space in the undo stack.
|
mettelus
Max Output Level: -22 dBFS
- Total Posts : 5321
- Joined: 2005/08/05 03:19:25
- Location: Maryland, USA
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 08:39:44
(permalink)
jatoth The setting is in the "Edit-History" option from the menu. You have to have made at least one edit for "History" to be available.
Thank you for that! I just opened a project and changed that # from 128->10, requiring an edit to do so. Closed without save, then opened another project to do a quick edit and check again, and the value was still at 10, so it is global (I hope, I didn't reboot the machine to test). 128 was a default I would never have expected, but that is indeed a massive number. Most graphical programs would belly up before ever hitting that one, but I am not sure of what SONAR considers an "undo" either. When I undo is usually the "last 3 things" max. I will have to check out that undo history when I think of it sometime, as I can hardly envision a scenario of "Damn, I need to undo the last 73 items!" For me, I would just close it and revert to the last save from <10 minutes ago. Edit: I did just get around to rebooting the machine to check the "Maximum Undo History" and it is indeed a global (and remembered) setting.
post edited by mettelus - 2016/01/31 12:59:49
ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
|
williamcopper
Max Output Level: -68 dBFS
- Total Posts : 1120
- Joined: 2014/11/03 09:22:03
- Location: Virginia, USA
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 08:51:57
(permalink)
Things to undo can build up quickly --- I frequently undo maybe 30-40 little edits, which only took 30-40 seconds to make.
|
Skyline_UK
Max Output Level: -54 dBFS
- Total Posts : 2133
- Joined: 2004/04/15 17:55:09
- Location: Midlands, UK
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 09:32:59
(permalink)
Very interesting, I must have a look at that. It may be what's causing a regular irritant. When cutting or copying I sometimes find the paste doesn't work, for no apparent reason. I always check that I haven't somehow changed the track focus, making the paste turn up in the wrong track, but invariably find it's just failed. I try the copy/paste again only to find the paste just won't happen. I then save, close Sonar, re-open and all works as expected.
My stuff Intel Sandy Bridge i7 2600 @ 3.4GHz, 4 cores, 8 threads, 16GB RAM.OS & Programs drive: 240GB SSD Data drives: 1 x 1TB drive RAID mirrored, plus extra 1TB data drive Windows 10 Home 64 bit Cakewalk by BandLab 64 bit, Studio One 3, Band In A Box 2016, Ozone 8+ too many other pluginsBandLab page
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 09:42:11
(permalink)
|
jimkleban
Max Output Level: -64 dBFS
- Total Posts : 1319
- Joined: 2008/11/09 09:42:45
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 09:52:58
(permalink)
Yes sir, I believe that the CNRL S thing/large edit sessions was my observation a few years ago (or at least someone else had the observation as myself and posted it) and I am happy to report that it still works today. During editing MIDI tracks, adding the keystrokes of CNTL S (save) and doing it often, resets something avoiding the crash and a SONAR restart and all the editing tools work again as they should instantly. Never got it confirmed that it was related to large UNDO buffers but I am still sticking with that theory until or if the bakers confirm. If it is a large BUFFER, it would appear to be something that can be fixed in SONAR with larger allocations of memory for these sessions. Just to add another behavior that gets fixed with frequent CNTL S is that the SPACE BAR stops acting as the START/STOP playback of your project... here to, CNTL S and the space bar works again. So, just remember that CNTL S is your friend while doing MIDI editing and all will be OK. Jim
post edited by jimkleban - 2016/01/31 10:11:31
The Lamb Laid Down on MIDI www.lldom.com Studio Cat Custom i7 with Thunderbolt (wonderful system built and configured by our own Jim R) Apollo Duo (via TB) UAD Quad UAD Duo WIN 8.1 x64 with 32 GB Ram 4 SSD for programs and sample libraries Splat (latest version)
|
stevec
Max Output Level: 0 dBFS
- Total Posts : 11546
- Joined: 2003/11/04 15:05:54
- Location: Parkesburg, PA
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 17:03:33
(permalink)
Interesting... I Ctrl+S fairly often out of sheer habit, and I rarely have many of the oddball issues experienced by others. In hindsight, perhaps the connections being made in this thread are more than just coincidental...
SteveC https://soundcloud.com/steve-cocchi http://www.soundclick.com/bands/pagemusic.cfm?bandID=39163 SONAR Platinum x64, Intel Q9300 (2.5Ghz), Asus P5N-D, Win7 x64 SP1, 8GB RAM, 1TB internal + ESATA + USB Backup HDDs, ATI Radeon HD5450 1GB RAM + dual ViewSonic VA2431wm Monitors; Focusrite 18i6 (ASIO); Komplete 9, Melodyne Studio 4, Ozone 7 Advanced, Rapture Pro, GPO5, Valhalla Plate, MJUC comp, MDynamic EQ, lots of other freebie VST plugins, synths and Kontakt libraries
|
vanceen
Max Output Level: -74 dBFS
- Total Posts : 814
- Joined: 2003/11/08 08:55:56
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 18:40:13
(permalink)
I get similar problems working with audio. For me, the signal is that the Split command stops working. I always use Alt - click, but S and the menu also refuse to split clips. This seems to happen when I'm doing lots of splitting and moving things around to get audio timing right. I was excited about the History depth suggestion, and I reduced it from 128 to 32. The problems (and the whitescreen crash) seemed to start sooner than before. I tried increasing the Undo depth to 256, since I've got plenty of memory. It took longer, but I eventually got a Not Responding whitescreen crash.
SONAR Platinum Windows 10 ASUS X99E WE Core i7 5960X 32 GB Corsair DDR4 2133 C13 Fireface UFX USB driver 1.098 GeForce GTX 950
|
gustabo
Max Output Level: -49.5 dBFS
- Total Posts : 2591
- Joined: 2009/01/05 17:32:38
- Status: offline
Re: Warning sign that a cut & paste midi crash is due
2016/01/31 20:04:58
(permalink)
Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3 M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad Adam A7X - Behritone C50A PreSonus Monitor Station v2 (controlling the mons) https://www.facebook.com/groups/sonarusergroup/
|