kdjensen
Max Output Level: -90 dBFS
- Total Posts : 5
- Joined: 2015/02/18 19:16:18
- Status: offline
Internal error occurred while processing the mixdown
I received the following error message when exporting audio: "An internal error occurred while processing the mixdown. The operation was unsuccessful." I've used Sonar for years, and I have never encountered this error message. Likewise, I can't find a fix for the problem either. I'm stuck. Can someone help?
|
tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
Re: Internal error occurred while processing the mixdown
2016/10/23 10:48:57
(permalink)
Welcome to the forum!
I had an issue with disc write permissions when attempting to export audio to a flash drive that caused this error (which may or may not be anything to do with your problem as it seems to be a fairly broad description). Have you tried running Sonar as administrator and/or writing to a different HDD?
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|
kdjensen
Max Output Level: -90 dBFS
- Total Posts : 5
- Joined: 2015/02/18 19:16:18
- Status: offline
Re: Internal error occurred while processing the mixdown
2016/10/23 14:33:48
(permalink)
Thanks for your answer. I tried to write to a different HD, but got the same result. The funny thing is that I had already exported this file a couple of times already, but I didn't like the result, to I made some minor changes and that's when the problems surfaced. I'm going to try exporting by not selecting different individual tracks to see if that's the problem.
|
Cactus Music
Max Output Level: 0 dBFS
- Total Posts : 8424
- Joined: 2004/02/09 21:34:04
- Status: offline
Re: Internal error occurred while processing the mixdown
2016/10/23 16:13:17
(permalink)
Try "select none" before exporting. I've always used this as I found "select all" iffy.
Did you add any weird plug ins on this attempt
|
kdjensen
Max Output Level: -90 dBFS
- Total Posts : 5
- Joined: 2015/02/18 19:16:18
- Status: offline
Re: Internal error occurred while processing the mixdown
2016/10/23 19:02:55
(permalink)
I'll try your suggestion. No unusual plug ins added. However, I discovered that the problem is being created by one track. I'm going to copy and paste it into another track without any effects and see if I can mix down everything. Its very odd, I've used Sonar for a long, long time and this type of problem has never surfaced. Oh well, live and learn. Thanks
|
kdjensen
Max Output Level: -90 dBFS
- Total Posts : 5
- Joined: 2015/02/18 19:16:18
- Status: offline
Re: Internal error occurred while processing the mixdown
2016/10/23 20:54:30
(permalink)
Problem has been solved. I used Melodyne to correct the pitch on a vocal tract. Melodyne requested that I increase the size of the cache. I did. However, once I brought the range of the cache down to prior levels, the problem went away.
|
tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
Re: Internal error occurred while processing the mixdown
2016/10/23 23:47:38
(permalink)
Great work! Melodyne is a great tool but can be a little flakey. I find it best to clone the track to be adjusted before adding melodyne then render the changes as soon as possible.
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|
kdjensen
Max Output Level: -90 dBFS
- Total Posts : 5
- Joined: 2015/02/18 19:16:18
- Status: offline
Re: Internal error occurred while processing the mixdown
2016/10/24 12:34:21
(permalink)
Good suggestion, I'll try it. Melodyne is a good tool for limited circumstances, in other words I try to get the takes in tune rather than relying on Melodyne. It takes a lot of memory and it taxes computer resources. I will note that I should have said buffer instead of cache in my response yesterday. Oh well, it was a long day.
|
slyman
Max Output Level: -87 dBFS
- Total Posts : 194
- Joined: 2015/08/31 13:55:12
- Location: Montreal, QC
- Status: offline
Re: Internal error occurred while processing the mixdown
2016/10/24 13:50:16
(permalink)
kdjensen
Melodyne is a good tool for limited circumstances, in other words I try to get the takes in tune rather than relying on Melodyne.
Lol....without Melodyne, I'm a mediocre singer.....with Melodyne, I'm just a bad singer. 
Sonar Platinum, Gigabyte H87-HD3, Intel 4770k, 16Mb Ram, Win 10 Pro, RME Babyface Pro, Roland A-Pro 800, Presonus Studio Channel, Kemper Profiling Amp, Strat/Tele/LesPaul/Taylor 214ce/Dean Cadillac/P-Bass
|
reginaldStjohn
Max Output Level: -81 dBFS
- Total Posts : 485
- Joined: 2011/01/15 23:42:50
- Status: offline
Re: Internal error occurred while processing the mixdown
2016/10/24 15:03:50
(permalink)
I have had this issue and it has always come down to having to bounce some clips before the export. I would bet that if you had bounced the melodyne clips down first it might have worked. I have seen the error without Melodyne clips but there must be something with some clip data that it doesn't like that bouncing them down fixes?
Just my experience
AMD Phenom II x6, 8 GB Ram, 2 Internal SATA III HD Windows 10 Presonus Studio Live 16.0.2 Interface/Mixer Cakewalk Sonar Platinum Line6 Helix Guitar Processor Custom Made (El Bandito) Telecaster LTD ESP EC-1000 PRS El Torrero SE
|