Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Mystery dropout due to mystery MIDI drum clip
Okay... I have no idea what would do this. There is this one little tiny clip that has consistently caused problems in this X2 project. It was, IIRC, a bad MIDI drum take that refused to let me remove it. Any time I zoomed in on it or tried to do anything with it like delete it it would crash Sonar. There was nothing I could do so I just cropped it down to nothing. When I returned to remix this project I had the same problem. Now though I've bounced all the clips into a new track and archived the original. Now anytime the song gets to that exact point I get an audio engine drop out. Doesn't matter if I am using the new bounced clip or pull the original clips out of the archive and archive the bounced clip and any combination between the two. This is feeding BFD Eco. I do not know what the heck to do with this now and was wondering if anyone has encountered something like this before. Is there any know reason why one tiny, essentially non existent, segment of MIDI data could cause so many problems? This is really holding me up here. Thanks.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/10/31 14:43:50
(permalink)
Okay, I just figured out a workaround and the specific details to some of the nuances will have to be dealt with by a baker, if at all but if anyone has any idea about how a MIDI clip could cause so much chaos or have experienced this behavior before I'm all ears because I would like to avoid this in the future. I really have no idea what, if anything, is special about this clip. It was just a drum take I made with my padKontrol, one of many in that session in that exact same spot, that just refuses to be moved, removed or even looked at without causing all sorts of wacky stuff. :-/
|
dwardzala
Max Output Level: -61 dBFS
- Total Posts : 1470
- Joined: 2008/05/26 19:18:33
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 12:28:49
(permalink)
Can you copy the good data to another track and delete the whole track with the bad clip?
DaveMain Studio- Core i5 @2.67GHz, 16Gb Ram, (2) 500Gb HDs, (1) 360 Gb HD MotU Ultralite AVB, Axiom 49 Midi Controller, Akai MPD18 Midi Controller Win10 x64 Home Sonar 2017.06 Platinum (and X3e, X2c, X1d) Mobile Studio - Sager NP8677 (i7-6700HQ @2.67MHz, 16G Ram, 250G SSD, 1T HD) M-Box Mini v. 2 Win 10 x64 Home Sonar 2016.10 Platinum Check out my original music: https://soundcloud.com/d-wardzala/sets/d-wardzala-original-music
|
Grem
Max Output Level: -19.5 dBFS
- Total Posts : 5562
- Joined: 2005/06/28 09:26:32
- Location: Baton Rouge Area
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 12:52:47
(permalink)
Try: Export the midi clip and then try to import it back in. Just mute the clip with out cropping it at all. Lasso each small section of the clip and copy past to another clip, using a new clip/trk each time until you come to the info that is giving the trouble. The only reason I can think of is that you might have cropped the clip at one time and the extra info that Sonar is trying to keep is preventing the delte and such. IDK. Just guessing.
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 PCAMD FX 6300; 8gb Ram; 256 SSD sys; 2TB audio/samples; Realtek WASAPI; Win 10 Home 64; CWbBL 64 Surface Pro 3Win 10 i7 8gb RAM; CWbBL 64
|
Taurean Mixing
Max Output Level: -84 dBFS
- Total Posts : 312
- Joined: 2006/05/20 12:15:19
- Location: NY
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 12:54:22
(permalink)
highlight the entire track and right click in the track pane and chose bounce to clip. See if that resolves it.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 13:06:10
(permalink)
I've tried a bunch of different stuff and it won't even let me get near it without causing weird behavior or crashes so I've just left it where it is and have been working around it. I managed to get the clips I want bounce/comped together and I've successfully edited that to my liking and it will now all be bounced to audio (fingers crossed). Then if need be I'll use Save As then delete the offending material so it is gone. If I'm still having problems then I'll simply start a new project and import all the audio waves into that and let the MIDI version rot where it is unless I decide to go back and redo it. However with this song if I do decide to redo it I will start from scratch because it was one of my first projects and it's a little wonked so I know I can do much better now. The thing I'm mostly curious about is how the heck a tiny little MIDI clip can cause so much chaos within a project? I experience very few full on crashes with X2 but any time I fiddle with this one clip too much totally craps the bed. It is very odd.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 13:10:07
(permalink)
It should be noted, in case it wasn't already apparent, that this clip isn't even audible. It was slip edited to nothing because I originally couldn't remove it. I can't even remember what it is and it won't let me slip edit it back without crashing. As I said I seem to have been able to do what I need to with this project but it is extremely bizarre behavior and I have never seen this type of behavior nor seen anything like this posted on the forum. Maybe my pK tossed a corrupt note to the program?
|
Taurean Mixing
Max Output Level: -84 dBFS
- Total Posts : 312
- Joined: 2006/05/20 12:15:19
- Location: NY
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 13:22:45
(permalink)
Beepster if you tried the bounce to clip to no avail how about this, did you try to delete the clip through the events list?
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 13:27:42
(permalink)
I actually haven't tried to bounce (to audio) that specific clip. Only delete it, remove the lane, try to drag it elsewhere, try to unslip it, etc... Like I said it is hurting anything right now and when I was originally working on this song I managed to get it mixed and exported. I just can't get near that clip. Even just clicking to select it for a bounce would likely cause a crash. Maybe it's haunted. Spooky.
|
Grem
Max Output Level: -19.5 dBFS
- Total Posts : 5562
- Joined: 2005/06/28 09:26:32
- Location: Baton Rouge Area
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 13:56:55
(permalink)
I'm thinking beep that if you need anything further from this project, you should just bite the bullet and start a new one. Sometimes, for what ever reason, things get corrupted. Seen it before. And it's just best to start over instead of trying to tip-toe around something.
If it were me I'd export all my takes and then import back in the new project.
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 PCAMD FX 6300; 8gb Ram; 256 SSD sys; 2TB audio/samples; Realtek WASAPI; Win 10 Home 64; CWbBL 64 Surface Pro 3Win 10 i7 8gb RAM; CWbBL 64
|
Taurean Mixing
Max Output Level: -84 dBFS
- Total Posts : 312
- Joined: 2006/05/20 12:15:19
- Location: NY
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 13:57:17
(permalink)
Ah ok, I actually mean right-click, "bounce to clip" command not anything like bounce to audio. MIDI tends to get fragmented over time while you work on it and bouncing all of the bits and pieces of a MIDI track to a cohesive clip often fixes issues. Just highlight all the pieces of that track, then right click any where on a clip and choose bounce to clip. It's worth a try.
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 14:08:25
(permalink)
Thanks for the tips guys. They will be noted for future needs. I was trying to do something kind of fancy in this case that seemed to irritate that clip. Normally that wouldn't happen (I hope) but because of that nasty little thingie I just had to fall back on what worked before. I just hope it doesn't give me a hard time while I bounce all the tracks to audio... which if I can get my arse in gear I will be doing this afternoon. Thanks again for pontificating on such a weird and presumably rare (if not completely isolated) happenstance. I always seem to find the fun stuff, eh? ;-)
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 14:14:42
(permalink)
And just to clarify the bounce to clip I did a few days ago did indeed behave but that was using multi selection methods and even deleting the lane the offending clip occupied. The bounced clip still caused the issue at that spot when I tried to do my fancy footwork which is what prompted the thread. Somehow even though it was deleted it wormed it's way into the bounce. I even tried deleting the original track (I bounced it all to a new MIDI track to preserve the fragmented one) but it still caused the dropout. Extremely weird behavior. I'd send the project to Cake to see what's up but a) I've got my workaround and b) it would be pointless because this is an X2 project. More of a curiosity than anything. I'm still thinking the padKontrol sent a wonky message. I don't know if that can happen but it's the only explanation I can come up with.
|
Taurean Mixing
Max Output Level: -84 dBFS
- Total Posts : 312
- Joined: 2006/05/20 12:15:19
- Location: NY
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/03 14:16:40
(permalink)
weird! definitely post any updates
|
Grem
Max Output Level: -19.5 dBFS
- Total Posts : 5562
- Joined: 2005/06/28 09:26:32
- Location: Baton Rouge Area
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/04 00:48:17
(permalink)
Transcending Music weird! definitely post any updates
+1
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 PCAMD FX 6300; 8gb Ram; 256 SSD sys; 2TB audio/samples; Realtek WASAPI; Win 10 Home 64; CWbBL 64 Surface Pro 3Win 10 i7 8gb RAM; CWbBL 64
|
chuckebaby
Max Output Level: 0 dBFS
- Total Posts : 13146
- Joined: 2011/01/04 14:55:28
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/04 01:29:03
(permalink)
I would look close at the midi data itself, is it at all possible the midi is triggering a hidden note that is not applicable ? IE-its triggering something that is causing the crash.
Windows 8.1 X64 Sonar Platinum x64 Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GBFocusrite Saffire 18I8 - Mackie Control
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/04 01:33:08
(permalink)
Anything in the Event List?
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
Beepster
Max Output Level: 0 dBFS
- Total Posts : 18001
- Joined: 2012/05/11 19:11:24
- Status: offline
Re: Mystery dropout due to mystery MIDI drum clip
2013/11/04 08:08:55
(permalink)
chuckebaby I would look close at the midi data itself, is it at all possible the midi is triggering a hidden note that is not applicable ? IE-its triggering something that is causing the crash.
hmm... not sure how it would do that unless, as I was wondering about earlier, the pK sent a bad note. IIRC I had the entire controller mapped (as in all the pads were going to notes used in the project all of which were successfully triggered before and after without causing problems) so anything that got inputted SHOULD have been a valid entry. I guess maybe there is a bad velocity layer in there somewhere but this is the Rock Legends kit for BFD from Platinum Samples. It should be pretty solid. Also... hi, Chuck. Don't see you around much anymore. Hope everything's alright. Cheers. :-) brundlefly Anything in the Event List?
This is something I hadn't thought of mainly because I've never used the EL before. It confused the heck out of me but I know enough about MIDI now to at least read and understand the data. I'll try this after I safely get what I need to move on to the mixing phase before I fiddle with that though because I don't want to tempt fate and end up with an unusable project because I was curious. But... does the EL show ALL MIDI data in the project or is it clip specific? Will it show archived data? Layered clips (takes)? Will I have to select the problem clip to see what's there or expand it? If the EL doesn't show anything other than currently selected or audible/active data then I doubt it'll show anything because I can't actually get the data displayed. It's just a vertical line left after slip editing it down to nothing and as I said it won't let me near it. Good suggestion though. I should start looking at the Event List in general anyway just to gain a better grasp on MIDI stuff. Cheers.
|