Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By TalkingHats Music Thu Jul 26, 2007 10:32 pm
This seriously needs to be addressed.

Here is the steps.

1. Sync MPC with Cubase or Live or other Host
2. Press Mode + Pad 16 (Song Mode)
3. Load up a few sequences
4. Play Cubase (Host)

This should play the MPC,

5. Stop Cubase (Host)
6. Rewind Cubase (Host) back to start position
7. Start Cubase (Host)


Basically the mpc does not locate back to the top of the song mode when locate back to start on the master host. This used to work fine on 2.1 -3+
Last edited by TalkingHats Music on Sun Aug 05, 2007 6:36 pm, edited 1 time in total.

By deranger Sun Aug 05, 2007 7:18 pm
d'yer report it to JJ?

TalkingHats Music wrote:MOFOBUMP!!
User avatar

By TalkingHats Music Mon Aug 06, 2007 1:57 pm
deranger wrote:d'yer report it to JJ?

TalkingHats Music wrote:MOFOBUMP!!


YUP!
By YOke Breaker Mon Aug 06, 2007 2:32 pm
My MPC (JJ OS v4.76) syncs just fine with Sonar 6 (Producer Edition); double-check all settings in Cubase and your MPC. It's probably user error!
User avatar

By rinseout Mon Aug 06, 2007 2:59 pm
Tried this too, normally i have the mpc as master, but it works fine the other way too.

You got mmc activated?
By YOke Breaker Mon Aug 06, 2007 5:14 pm
MPC Settings = Sync in: 1 (Slave) / Mode: MIDI CLOCK
Sync out: Off

Sonar 6 Settings = Options > Project > Sync > (underneath the "Send
MIDI Sync" heading, check the box next to "Transmit
MIDI Start/Continue/Stop/Clock.

Secondly, underneath the same heading, check the
box next to "Transmit MIDI Song Position Pointer
(SPP).

Finally, in the sub-heading area which is titled ("MIDI
Sync Output Ports:"), you need to check the output
port that your MPC is connected too. [My MPC is
connected to MIDI I/O ports 6 on my MIDI interface.
Therefore I checked the box next to port six, of the
appropriate MIDI interface].

Using the above settings in Sonar 6 (Producer Edition) and my MPC, I have no problems with syncing my MPC to my computer via MIDI Clock. If you are syncing via MIDI Machine Control (MMC) by necessity and not by mistake; make sure all of your settings are correct under: Options > Project > “MIDI Out:” in Sonar.

If you are not using Sonar as your MIDI timing "Master" for sequencing, but another application such as Cubase, I would suggest you hit the manual hard and look for similar settings (as found in Sonar)! Hope I have been of some service to you!?!
User avatar

By stan steez Mon Aug 06, 2007 7:32 pm
For using Cubase as the maser with the MPC you should use MTC as syncing method. I've lately been doing some research about this to finish the syncing tutorial of my new manual. I haven't had the problems you describe above yet. It's not all finished yet, but here's a step by step tutorial:

    01. Open Nuendo or Cubase SX.

    02. In the menu, click on Transport and select ­Syncronizing Options... or similar ­(depends on the ­language of your software).

    03. Next, set the following options and press OKAY:

      Timecode Source: select MIDI Time Code.

      Timecode Settings: select the MIDI Interface from the dropdown menu.

      Machine Control Options: select MIDI ­Machine Control.

      MIDI Timecode Destinations: select your MIDI Interface.

      MIDI Clock Destinations: select your MIDI Interface.

    Technically, Cubase / Nuendo is now set up to receive and send MMC signals. Also, it can be ­synchronized by either MTC or MIDI Clock. Which method will be used depends on the synching settings you apply inside the MPC 1000. Since you want to use Cubase / Nuendo as Host here, set the MPC to Slave

    04. Go to your MPC and enter the MIDI/Sync settings by pressing [MODE] + Pad 9.

    05. Move the cursor to the 'Sync in' field and set it to ' x (Slave)' (x = MIDI Input connected with your MIDI Interface which sends the signal coming fom Cubase). Select MTC as syncing mode. Turn on 'Receive MMC'.
    Setting the framerate inside the MPC is not needed, because it is sent by the host. You can set the Framerate in the Project settings of Cubase/Nuedo. I've set it it to 30 fps in my project.


More info here http://www.steinberg.net/502+M52087573ab0.html

When using MTC, you should leave one or two bars inside the cubase sequencer empty, to sync both devices. Not needed for MIDI Clock, though. There should be no more problems now.

Greetings
User avatar
By TalkingHats Music Tue Aug 07, 2007 11:23 am
You guys are talking to the MIDI EXPERT!

no seriously its not my Cubase settings, its the OS. My cubase settings are the same as they have always been, and to confirm I have downgraded back to 2.1 to make sure and it worked fine.

So it has to be the OS.

do u guys understand my actual problem?
By YOke Breaker Tue Aug 07, 2007 3:32 pm
Ha ha, MIDI expert! I understand your standpoint with regards to having your basic MIDI connections/assignments correct. I also understand your suspicions of JJ’s OS being flawed. Although I sync my MPC to Sonar using "MIDI Clock" and not "MMC," which really does not qualify me to speak in this area (MMC syncing problems); I still don't have any problems with Song Position Pointers (SPP) in JJ's OS v4.76, using “MIDI Clock.”

In your case, when attempting to sync via MMC in Cubase, I don’t believe an overwhelming number of user’s (Cubase / MPC) are having problems in this area. That being the case, and following the process-of-elimination with regards to troubleshooting, I would lean towards "User Error" or a corrupted file within your personal version of JJ’s OS.

If you have not done so already, download a fresh new copy of JJ’s OS and reinstall it exactly as instructed. Hopefully that works for you! If not, you may have to permanently revert back to the latest OS by Akai. In addition, if you haven’t done so already, thoroughly search the forum for similar posts. You may just find the answer you’re looking for deep within the mounds of forgotten posts!

Personally I think you corrupted your version of JJ’s OS or you are overlooking one minor, BUT MAJOR, aspect to your system configurations. I hope it all works out for you in the end!!! God bless!
User avatar

By Mr modnaR Tue Aug 07, 2007 3:36 pm
MMC is not a syncing protocol like MTC or MIDI clock.
User avatar
By stan steez Tue Aug 07, 2007 4:50 pm
TalkingHats Music wrote:You guys are talking to the MIDI EXPERT!

no seriously its not my Cubase settings, its the OS. My cubase settings are the same as they have always been, and to confirm I have downgraded back to 2.1 to make sure and it worked fine.

So it has to be the OS.

do u guys understand my actual problem?


Yes, I think I do. Maybe you should just export the Song from Songmode into a new song-sequence. For me, this works, using the settings I explained above.
User avatar
By TalkingHats Music Tue Aug 07, 2007 6:46 pm
stan steez wrote:
TalkingHats Music wrote:You guys are talking to the MIDI EXPERT!

no seriously its not my Cubase settings, its the OS. My cubase settings are the same as they have always been, and to confirm I have downgraded back to 2.1 to make sure and it worked fine.

So it has to be the OS.

do u guys understand my actual problem?


Yes, I think I do. Maybe you should just export the Song from Songmode into a new song-sequence. For me, this works, using the settings I explained above.


No, why should i change my work flow because of an error not cause by myself?

In a previous version, I cant remember MMC did bring back the MPC to the start of the song rather than the sequence, but the problem that then came up was the mpc would not start from 0.0.0.0 and start .24ms out.

there is a offset function somewhere hiding in cubase or the mpc but by that time i was so angey that my usual setup no longer works.

I have been programming this way for years and its very fustrating to have some bull come and mess it up!
User avatar

By TalkingHats Music Tue Aug 07, 2007 6:48 pm
anyway when i get some time i will look into a bit deeper, see what resolves i can find, so that i can show others how to get round it if thier having this problem.

btw, its not a bad download as all previous version have the same bug.