Forum Replies Created
-
Posts
-
Hi Rachel
I have not studied the details of your setup, but I will just pass my general advice in such situations:
Paper and pencil!
Draw a flow diagram of your setup, and there is a fair chance, that you solve your problem quickly. When the problem is solved, make an even nicer version of the diagram which you keep. This is your personal "setup manual", that you should always remember to update when you make changes.
So when in a year when you get a new computer and everything is re-done, it will be a walk in the park to setup your gear.Good luck.
-Lars
Mmmm, OK, after my success I have fallen into
another hole.What I wanted to do next was configure everything so I can input notes and chords into Octopus via a keyboard,
which I read in the Navigation Guide.So I set a MIDI channel to a track, press SEL
for the track and hit the record button.But depending on how I select the keyboard in Logic,
I get either no input at all or an incredible screaming
MIDI feedback loop that stops when I deselect the
track on the Octopus.So it seems the Octopus is receiving my streams from
the keyboard, echoing them to the Out port and back
again.I tried a couple of different approaches but none
seem to work that well. I am hoping I don’t need
to directly attach a keyboard to the Octopus but
go via my Interface etc…rachel
Hi Rachel,
I think you’ve pretty much nailed it. The trick is indeed to seperate your incoming data (eg. Octopus) right at the level of "Physical Input". Only data you want to record goes to the "to the Recording & Thru" object (and that’s the current selected track).
Recording your Octopus data is a little bit trickier because you use 2 different ports instead of 1, but it’s possible. If you need any help, let me know. Screenshots are handy in these situations.
Quote:(pressing one step then another to set length).Haha, I had no idea you could do this :whistle: .
For sure it doesn’t play nice with edit mode….
Unless we ask users of edit mode to press a button to set the length and press another button to set the mute… Anyway the present mute is half broken in edit mode (you cannot unmute).
The idea of the Step 4 – Step 1 order was an idea to quickly get repeating patterns in the middle of a track using a single gesture.
(and it’s linked somehow with the original request of the tenori-on tricks a few months back of rotating the mutes or the data underlying the mute so that you can have a moving window on the track as seen in this thread:
http://genoqs.net/index.php?option=com_joomlaboard&Itemid=50&func=view&id=924&catid=3#msg924
).
zinoff wrote:
Quote:Ok I have this idea (it’s not mine but it doesn’t matter)Muting by range.
To mute/unmute step 1 2 3 4 press step 1 and 4 and then press mute
To mute/unmute steps other than 1 2 3 4 press step 4 and 1 and then press mute or press step 5 and 16 then press mute.
For any single step mute press the step and then mute (as per current implementation).
The question is whether the functionality should mute or toggle mutes (probably it should mute).
It’s not "modulatable" but it makes it pretty fast to mute a range of steps.
Ideas?<br /><br />Post edited by: zinoff, at: 2008/11/21 20:44
Hi, I´m back!
Nobody commented on the above idea, but I think it sounds great. I am not sure that it should matter if you press (example) 1 before 4 or 4 before 1. Perhaps both should toggle the skip of 1 to 4 when followed by MUT.
Then if you have 1 to 8 playing and 9 to 16 skipped you could hold 1 and 16 and hit MUT. This would inverse the state and now you have 9 to 16 playing. Nice.I cracked the best part of it…
I will write up the process here to assist others as vague descriptions are not useful!I spent about half a day on this and most of tonight.
Now I have it so that I can use the Octopus to trigger
selected Instruments through Logic but still use
my keyboard controller to play selected tracks in
Logic without Octopus treading on my turf!The part I have not got yet, I will write up separately, which is recording the MIDI output of each instrument into Logic, from the Octopus. This is purely for monitoring purposes at this stage,
using Logic as a big MIDI router.In all this time, Logic is stopped – ie I am not
sending a Clock to Logic and it is not syncing the
Octopus.Anyway, for MIDI monitoring and jamming with the Octopus in Logic here is the walkthrough:
Go to the Environment and Create a new Page named
"Octopus".In this new environment, Create a Multi Instrument
for each Octopus MIDI Port. Label the Multi Instruments "Octopus 1" & "Octopus 2".Leave all the channel boxes unchecked (ie no icon)
and click on the Global part of the Multi Instrument.In the Inspector column on the left, Set the MIDI Port
to the ones your Octopus is attached to, in my case
this is Port 8 and Port 16 in my 2 AMT’s.
In the Inspector, set the MIDI channel to "All".Create a Channel Splitter object for each Multi Instrument Octopus 1 & 2.
Cable the Multi Instrument to each one. I use
a Monitor in between for debug purposes.Each MIDI channel on the Splitter can go to any
destination you can get off the picklist (Option|Click the cable). So the Instrument must have at least an Environment Object representing it as a destination, eg an Instrument or Multi Instrument or VI.The MIDI channel of the target instrument is irrelevant.
Make sure your Octopus is setup to transmit
data on the track/port/channel of your choice.In my demo I am a newbie so I only have 2 instruments setup in Octopus right now but it is the same
for 32. I have a Drumstation set to Channel 10
as it’s MIDI channel in the instrument, Logic and
AudioMidiSetup. I have a Doepfer A100 set to Channel
1, likewise. Both are on their own AMT port.But the Octopus has Channel 1 set for the Drum parts (DS) and Channel 2 set for the Bassline (A100).
Select Ch1 in the Channel Splitter and cable it
to the chosen instrument. In my case "Drumstation".Select Ch2 in the Channel Splitter and cable it
to the chosen instrument. This time it’s "A100".Now all your MIDI port assignments are complete.
The next step is to give Octopus its own realm
to play in.Go to Environment|Clicks And Ports
Ensure you have a Physical Input somehow connected
to a Sequencer Output. Mine has a keyboard and
a couple of transformers in the middle, from the SUM
out to the Seq Out.On the Physical Input, Locate the MIDI Ports your
Octopus is using. Mine uses Port 8 and Port 16
for Octopus Ports 1 & 2.Create a Monitor Object for each Port. Label them
"Octopus 1" & "Octopus 2".Select the Physical Input that represents your
Octopus Port 1 – in my case it’s Port 8.Connect it to the Monitor.
Connect the output of the Monitor to cable up
to the Octopus 1 Multi Instrument you just created.Repeat for Octopus Port 2, using the appropriate Physical Input in Logic.
Note: If you have Octopus Port 2 configured and cabled to your MIDI interface, you must cable it from the Physical Input Port you have connected, to the Octopus 2 Multi Instrument even if you do not use it, because otherwise you will get summed data sent to the SUM port of the Physical Input.
You do not need anything connected to the Channel Splitter outputs if you don’t need to yet.
Start Octopus – you should see MIDI Data coming through the Monitor(s) depending on how you have the Ports setup. You should also hear the appropriate
music being played by the appropriate instrument.Go to the Arrange Page in Logic. Run the Octopus.
It should not trigger any instrument except the ones connected via the Environment.Select different instruments in the Arrange tracks.
You should be able to jam along with the Octopus
as your backing or whatever without Octopus
triggering your currently selected Logic track.Note that this setup could well work for other
gear as well, such as MPC’s and the rest.At this point, I have only got a monitoring
setup going. It is what I need to work with the
Octopus and jam with it via my controller keyboard
together. It may well work in a "live" setting,
but remember, Octopus is not syncing and Logic
is "stopped".I will try to get MIDI recording
of the tracks going from this configuration
and then try and see what sync Options I can
have. It may involves tweaks to the Environment.If anyone wants to post this as an FAQ or something
for other Logic users, go ahead. I can also offer
up the Environment I put together, but it is
for Logic 6.4.3.rachel
Hello Rachel,
that is not a misprint, it is a little hint to a "centerpoint" as orientation if you want. it happens to be on track 5 which has pitch middle C and it is in the column of C if you look at the markers on top of the matrix.
It’s just a visual anchor.
Cheers,
GabrielHello Rachel,
and congratulations to your new machine!
NC001 is indeed #001 of the New Classic series, as Awave’s was among the first New Classic orders as soon as we’d announced it, and it just so happens that things do not happen in perfect sequence in life
It has of course no technical significance at all, only an aesthetic one – what a nice number to have!
Enjoy the machine, and let us all know how it goes.
Cheers,
GabrielWoohoo! My machine is now updated to 1.60 ie
in System mode it’s got a 100 and 6 red LED’s lit.Then I did the reset and memory refresh, so I guess
I am ready to fly!I now have to buy longer MIDI cables as the 4m ones
I have now are too short so I will need 5-6m instead!So my next trick is to walk through the manual
and give the Octopus some thought….rachel
OK,
my Octopus arrived yesterday but I’ve only just
powered it up and got it in the rack.I still have to hook up the MIDI ports to my AMT
but I will do that shortly.It seems I have Serial Number #NC001 – is this
significant? Doesn’t "NC" mean "New Classic"
and if so, is it #001 in the series? I am surprised
if #001 ended up in Australia!Anyway, it seems to have OS 1.42 installed. That is,
if I am reading the display correctly. When I go into
System Mode, the number 100 is lit, plus numbers
1,3,4 in red and 2 in green – so that is 1.42, right?Once I get confirmation, I will need to do the
update to 1.60 or latest. How many files do
I need to do this?rachel
Hi Timo,
with the updater installed, please try to install OS 1.42 from this link:
http://genoqs.net/downloads/OCT_OS_v142.syx
From 1.42 to 1.60 you should be able to do a direct step.
Cheers,
Gabrielthe instalation of the upadter utility worked (its showing the number 99 in the number display/ outer ring) the instalation of os 160 (on top of it) did not work. please give me downloadlinks for os-files that i can install to later install os160 in "2nd step".
thank you very much,
t.
Post edited by: Timo, at: 2008/12/02 21:47
