Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By mikolo Sat Jan 03, 2009 9:19 pm
The way it is now is driving me mad: A select a slice - turn data wheel, ups this changes the slice - where was my slice to edit again - here it is- whoops, wrong column - end point instead of starting point.


yeah it is annoying at the moment, especially considering how good os2 and os1 is for chopping hits. what im doing at the moment is going all the way to the end of the sample with the region field. then adjusting start points from the end of the sample, step by step back to the beginning of the sample- its way quicker than having to click between region and end all the time.
By Olby Sun Jan 04, 2009 12:16 am
im just curious, by why anyone still does chopping destructive way when you have non destructive chopping. which is even faster as you do not need to save those chopped samples and it also saves memory.
User avatar
By le rat Sun Jan 04, 2009 2:32 am
As Nym replied in another thread, you can use the LOOP function after using destructive CHOP.
By Sovereign Sun Jan 04, 2009 2:53 am
Olby wrote:im just curious, by why anyone still does chopping destructive way when you have non destructive chopping. which is even faster as you do not need to save those chopped samples and it also saves memory.


True it has it's advantages but the default 32 is not a good method.
Instead you should be able to select how many chops or just add them as needed.

The non-destructive chopping would be excellent if you could drop points in realtime like on the 4k.
User avatar
By laban Tue Jan 06, 2009 3:44 pm
you should be able to change frequencies on pgm eq hi and lo, that would make daw useless for basic mix :) (for my needs atleast :D)
User avatar
By le rat Wed Jan 07, 2009 3:58 am

i miss this bigtime. it was such a simple and clear way to represent the data.


So i ask murai about that grid stuff. In fact, he told me that while in grid edit mode pressing a cursor + data wheel makes tick moving 1 by 1 ( which you can see at the end of that video http://jp.youtube.com/watch?v=7-m-tuRvj0A )

Indeed it's more precise than os1 but i still think it's not dope for visual programming.
User avatar
By elevated Wed Jan 07, 2009 4:19 am
Stan Steez-- Did you find the sample layers? You have to press the Window button when the pad number is highlighted, in the Sample section of GPE mode.
User avatar
By stan steez Wed Jan 07, 2009 12:02 pm
elevated wrote:Stan Steez-- Did you find the sample layers? You have to press the Window button when the pad number is highlighted, in the Sample section of GPE mode.


Okay, thank you! Got lost in GPE somehow. PEACE
User avatar
By illiterati Wed Jan 07, 2009 12:25 pm
illiterati wrote:New bug?

from main screen double tap a kick drum (something like a third of a beat apart or less) - press main - double beats are displayed in grid edit - hold shift f3 (view) - double beats no longer displayed, only sinlge beats remain. - you have to put them back in in 'view' mode for them to stay for good.


just got back from holiday and downloaded the 1.06 - the problem above seems to have been fixed between 1.03 and 1.06.

nice.
User avatar
By wudsiba Wed Jan 07, 2009 2:58 pm
In response to the non destructive chopping question... I have yet to try it. The reason it was so important in the past was the limited amount of memory. I just love the way it is in ver. 2. I guess if its not broke don't fix it type of thing. My old Roland S-550 had this option. That's when you needed it! I guess I should check it out.. But let me just ask, do you really need it? I'm not trying to be a smart ass, I'm just wondering how you are working that you need so much memory?
By dtaa pla muk Wed Jan 07, 2009 4:22 pm
NDC's nicest thing to me is the ability to switch between chops via qlink.
this is like qlink velocity range switching, except instead of a resolution of 3, there's a resolution of 32. pretty excellent.

otherwise i destructively chop every time so i can use alternate loop