Bug reports & end-user support for Akai's MPC Software 'controllers' including the new MPC Studio 2, the MPC Touch, MPC Renaissance & original MPC Studio and MPC StudioB lack.
By Italian Beats Mon Apr 27, 2015 8:11 am
I don't know whether it is 1.8.2 related, but I experienced some trouble for the first time yesterday.
I was working on an 8-bar sample in manual chop mode. As I knew from the beginning that the sample would have 8 bars, I set the number of total bars in my project to 8.
Then after chopping I wanted to convert the slices to a new program and check marked "Create Events". Back in main mode I saw that only four bars had been converted into events and appr 2 bars of the following material had been placed on the 1st bar as well. So I had slices from the first 4 bars starting on the 1 and parallel to that slices from the following 2 bars on the same count. It looked as if the software just recognized 4 bars and put the following slices at the beginning on bar 1. Tried to hit play and I had a total crash, nothing responding anymore. Got a message "Audio not being processed" and a sound like a damaged CD playing. I had to close the software via task manager.
Tried everything from the beginning in a new project, same result. Tried to move the "double" slices to where they belong (starting at bar 5) manually and hit play again, same total crash. Screamed shit, threw my headphones to the side… :vomit:
Then I deleted the whole project once again, started new and worked on the same sample material, but divided the sample, so that I worked on two 4-bar samples. Everything worked flawlessly. Maybe I just overlooked something, but I cannot figure out what the hell it could have been. :hmmm:

By the way, I run a MacBook Pro mid 2013 on 10.8.5.
User avatar
By pspsounds Mon Apr 27, 2015 12:08 pm
While a track was playing I was scrolling thru a plugin (very fast) from the hardware and the software froze in a loop.
By tonemelle Mon Apr 27, 2015 6:18 pm
yea I've been experiencing a few laggy issues.. just making sure whether or not they're 3rd party plugin related
By SSS Mon Apr 27, 2015 8:01 pm
Italian Beats wrote:I don't know whether it is 1.8.2 related, but I experienced some trouble for the first time yesterday.
I was working on an 8-bar sample in manual chop mode. As I knew from the beginning that the sample would have 8 bars, I set the number of total bars in my project to 8.
Then after chopping I wanted to convert the slices to a new program and check marked "Create Events". Back in main mode I saw that only four bars had been converted into events and appr 2 bars of the following material had been placed on the 1st bar as well. So I had slices from the first 4 bars starting on the 1 and parallel to that slices from the following 2 bars on the same count. It looked as if the software just recognized 4 bars and put the following slices at the beginning on bar 1. Tried to hit play and I had a total crash, nothing responding anymore. Got a message "Audio not being processed" and a sound like a damaged CD playing. I had to close the software via task manager.
Tried everything from the beginning in a new project, same result. Tried to move the "double" slices to where they belong (starting at bar 5) manually and hit play again, same total crash. Screamed ****, threw my headphones to the side… :vomit:
Then I deleted the whole project once again, started new and worked on the same sample material, but divided the sample, so that I worked on two 4-bar samples. Everything worked flawlessly. Maybe I just overlooked something, but I cannot figure out what the hell it could have been. :hmmm:

By the way, I run a MacBook Pro mid 2013 on 10.8.5.



^^^
When in the Convert or Assign Slice window - converting slices to a new program - there is a "Number Of Bars" field that defaults to 2 bars. This could be the reason why the created events are only spanning over a 2 bar section.
I'm not sure why you are getting a crash when hitting Play after the events have been created; I cannot confirm the crash on my set up, unless I am misunderstanding your process.
By Italian Beats Mon Apr 27, 2015 8:29 pm
SSS wrote:
Italian Beats wrote:I don't know whether it is 1.8.2 related, but I experienced some trouble for the first time yesterday.
I was working on an 8-bar sample in manual chop mode. As I knew from the beginning that the sample would have 8 bars, I set the number of total bars in my project to 8.
Then after chopping I wanted to convert the slices to a new program and check marked "Create Events". Back in main mode I saw that only four bars had been converted into events and appr 2 bars of the following material had been placed on the 1st bar as well. So I had slices from the first 4 bars starting on the 1 and parallel to that slices from the following 2 bars on the same count. It looked as if the software just recognized 4 bars and put the following slices at the beginning on bar 1. Tried to hit play and I had a total crash, nothing responding anymore. Got a message "Audio not being processed" and a sound like a damaged CD playing. I had to close the software via task manager.
Tried everything from the beginning in a new project, same result. Tried to move the "double" slices to where they belong (starting at bar 5) manually and hit play again, same total crash. Screamed ****, threw my headphones to the side… :vomit:
Then I deleted the whole project once again, started new and worked on the same sample material, but divided the sample, so that I worked on two 4-bar samples. Everything worked flawlessly. Maybe I just overlooked something, but I cannot figure out what the hell it could have been. :hmmm:

By the way, I run a MacBook Pro mid 2013 on 10.8.5.



^^^
When in the Convert or Assign Slice window - converting slices to a new program - there is a "Number Of Bars" field that defaults to 2 bars. This could be the reason why the created events are only spanning over a 2 bar section.
I'm not sure why you are getting a crash when hitting Play after the events have been created; I cannot confirm the crash on my set up, unless I am misunderstanding your process.



Yeah, I know about that setting, but I am pretty sure I had it right. And usually when I forgot to change that number of bars it just converted the bars that were set, but no double events on the same count and especially no complete crash. Anyway, I will try again asap, just been a little busy. I will post my results.
By tonemelle Mon Apr 27, 2015 9:08 pm
Not sure if it's 1.8.2 or Decapitator but when I export my beat it bounces without the 1st on the one. pretty annoying. I'm guessing its decapitator (which I don't use as much as i used to anymore, except for this beat I'm bouncing).
User avatar
By BDRAKE Wed Apr 29, 2015 1:05 pm
Italian Beats wrote:I don't know whether it is 1.8.2 related, but I experienced some trouble for the first time yesterday.
I was working on an 8-bar sample in manual chop mode. As I knew from the beginning that the sample would have 8 bars, I set the number of total bars in my project to 8.
Then after chopping I wanted to convert the slices to a new program and check marked "Create Events". Back in main mode I saw that only four bars had been converted into events and appr 2 bars of the following material had been placed on the 1st bar as well. So I had slices from the first 4 bars starting on the 1 and parallel to that slices from the following 2 bars on the same count. It looked as if the software just recognized 4 bars and put the following slices at the beginning on bar 1. Tried to hit play and I had a total crash, nothing responding anymore. Got a message "Audio not being processed" and a sound like a damaged CD playing. I had to close the software via task manager.
Tried everything from the beginning in a new project, same result. Tried to move the "double" slices to where they belong (starting at bar 5) manually and hit play again, same total crash. Screamed ****, threw my headphones to the side… :vomit:
Then I deleted the whole project once again, started new and worked on the same sample material, but divided the sample, so that I worked on two 4-bar samples. Everything worked flawlessly. Maybe I just overlooked something, but I cannot figure out what the hell it could have been. :hmmm:

By the way, I run a MacBook Pro mid 2013 on 10.8.5.



:hmmm: This happened to me on PC 64 bit. The events were all ran together as explained above. Instead of going any further I created a new project and it worked the 2nd time around. This happened to me twice.
By Italian Beats Thu Apr 30, 2015 9:32 am
BDRAKE wrote:
Italian Beats wrote:I don't know whether it is 1.8.2 related, but I experienced some trouble for the first time yesterday.
I was working on an 8-bar sample in manual chop mode. As I knew from the beginning that the sample would have 8 bars, I set the number of total bars in my project to 8.
Then after chopping I wanted to convert the slices to a new program and check marked "Create Events". Back in main mode I saw that only four bars had been converted into events and appr 2 bars of the following material had been placed on the 1st bar as well. So I had slices from the first 4 bars starting on the 1 and parallel to that slices from the following 2 bars on the same count. It looked as if the software just recognized 4 bars and put the following slices at the beginning on bar 1. Tried to hit play and I had a total crash, nothing responding anymore. Got a message "Audio not being processed" and a sound like a damaged CD playing. I had to close the software via task manager.
Tried everything from the beginning in a new project, same result. Tried to move the "double" slices to where they belong (starting at bar 5) manually and hit play again, same total crash. Screamed ****, threw my headphones to the side… :vomit:
Then I deleted the whole project once again, started new and worked on the same sample material, but divided the sample, so that I worked on two 4-bar samples. Everything worked flawlessly. Maybe I just overlooked something, but I cannot figure out what the hell it could have been. :hmmm:

By the way, I run a MacBook Pro mid 2013 on 10.8.5.



:hmmm: This happened to me on PC 64 bit. The events were all ran together as explained above. Instead of going any further I created a new project and it worked the 2nd time around. This happened to me twice.


Yeah, I also deleted everything and started a new project. Everything worked flawlessly. Still it's a pain in the ass as I always have to be afraid of it happening again which is a major workflow killer.
By Chillin Sat May 02, 2015 10:31 am
I can't audition my sounds on the Arturia plugins. They just don't show up in the Plg: presets list.


Image

Image
User avatar
By Der Ichling Sat May 02, 2015 1:27 pm
Chillin wrote:I can't audition my sounds on the Arturia plugins. They just don't show up in the Plg: presets list.


Image

Image


This true for a longer list of plugins; including those of NI 8. not 1.8.2 specific bug but there since day one.
Win7 SP 1; 64bit
By Chillin Sat May 02, 2015 8:00 pm
Der Ichling wrote:
Chillin wrote:I can't audition my sounds on the Arturia plugins. They just don't show up in the Plg: presets list.


Image

Image


This true for a longer list of plugins; including those of NI 8. not 1.8.2 specific bug but there since day one.
Win7 SP 1; 64bit

^The legacy pack by Korg had it too, but it has been fixed along time ago.
By KASZ247 Sun May 03, 2015 1:06 am
masada2502 wrote:find any bugs yet?


After installing the update I can't open my waves SSL Compressor plug in,I get the spinning wheel forever...All the other SSL plug ins work..It also does it in Logic X after I updated the MPC...
By SkammGoodiez2 Wed May 27, 2015 2:15 pm
I don't know if that bug was there before.... Just that makes me wan to sell it

rec+play start
tap some pads while its counting in
they will all get recorded @ 1.1.1