Forum Replies Created
-
Posts
-
yes and there a few other quirks..POS rotating can result in different pitches i believe.
To avoid the misaligned pages enter "edit" mode (orange flashing) then double click. I’ve already got this in muscle memory and dont double click in the green toggle mode or whatever its called.
Or hold page and the choose but i’m not sure if this only works if your already in page level, not grid.
Duncan (and others), how is this working for you when the Octo is slaved? I’d like to find out if this is the same for everyone.
the files are mp3’s with the Nemo running synced with Live at varying tempos and 2 files with the midi sync to 707
it worked!
You have to replace "OCT_OS.elf" with "NEMO_OS.elf" in "Write the OS ?le from RAM to FLASH" step.
In my tests the midi clock is now consistant over varying BPM’s but it appears that the NEMO is early when midi-slaved.
I tested with Ableton Live as master playing a sample and running the DC sync unit plug-in from a Motu 828MK2 to an old Korg KMS-30 which converted the sync24 to midi-clock.
The second test was directly connecting a TR-707 with the NEMO running master and slave. Here you can hear that the NEMO is early when slaved but in time when master.
Post edited by: chaosmoon, at: 2010/10/22 01:34
Post edited by: chaosmoon, at: 2010/10/22 01:34
Post edited by: chaosmoon, at: 2010/10/22 01:36
Very, very good to hear.
Does anyone have a link to instructions on dealing with these elf files?I’d like to add i’ve had very good results syncing my hardware boxes to Ableton Live with this free project:
http://users.telenet.be/darffader/rv0/
It outputs sync24 (from a soundcard with DC-coupled outputs) so you need something to efficiently turn that into midi clock. I’ve had good results with a KMS-30, but the (relatively cheap) TR-707 and 727 boxes are very good at turning sync into midi clock; And good fun to jam with too..My 707 has a 25 pin sub-d connection to fry its brain with a patchable bend box when i get tired with the stock sounds.
He just released an AC version which should work with standard soundcards using tape-sync. Again you’ll need a box like the KMS or 707 that can deal with it though.
i havn’t measured as yet, but connected the 2 units and already could hear the problem.
With the Nemo as master it was triggering early. Moreso at low BPM. The MPC as master was closer and stable but jittery. I’m not sure if this is the Nemo, MPC or both.
DIN sync with the Roland boxes doesn’t seem to have this problem. Is this because the machines/processors were simpler back then?
This worries me. Especially if the offset varies per BPM. Live performance will be seriously limited if this is the case.
recently i’ve been running a 707 as master to a 606 via din-sync and Nemo as midi slave which is triggering synths and a "touched by sound drm"
The DRM isn’t in time and i’ve been offsetting STA values to try and compensate.
Yesterday an mpc1000 arrived wich i hope to combine with the Nemo for a performance setup with a few synths.
I will try to measure for offsets using a similar technique.
i dont follow from here.
empirix wrote:
Quote:…first initial step is recognised on first sequence iteration for each instrument, 2nd sequence iteration -> instruments double up, so for example the kick and snare double up as the kick is led 1 on page1 and snare is led 1 on page 2, do you see my problem => what am i doing wrong.thanx for your help<br /><br />Post edited by: empirix, at: 2010/09/07 01:16
your setting up whole the tracks in the page on the second row to different midi notes right?
for example:
row 1, page 1:
track 1 = C-1
track 2 = D-1
track 3 = E-1
track 4 = F-1row 2, page 1:
track 1 = G-1
track 2 = A-1
track 3 = B-1
track 4 = C-2your setting up the whole track right? Not just the first step in each track. I usually start by triggering all steps in a track then holding the track selector button to the left of the rows in page mode and turning PIT till i arrive at the desired instrument, which machine-guns. Then copy this track down and offset to the next instrument.
