gseher

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 746 total)
  • Author
    Posts
  • in reply to: Chaining + Clustering bug or just a noob? #1994
    gseher
    Keymaster

    Hi zac, this is a bug, and also being discussed in the support area of the forum and the next OS release will contain a fix for it.

    in reply to: Keyboard Input is Transposed #2190
    gseher
    Keymaster

    Hi Rachel, did you ever figure this one out? I was at least not able to reproduce an inconsistency from what you describe. Gabriel

    in reply to: 14-bit bender fixed, but not other 14bit mccs #2125
    gseher
    Keymaster

    From a usability perspective I think this is once again raising the complexity in the sense that now you have to service 2 channels per track. I think the available real estate on Octopus does not necessarily require this.
    Gabriel

    in reply to: New Listmember intro/ progam change problem #2298
    gseher
    Keymaster

    After some in-depth discussion with Klaus on the phone, it appears that we may have a solution here. I will ask Klaus to evaluate it and tell us how it works for him, once he gets around to trying it out.
    Thanks again Klaus for all the good input and pointers!
    Gabriel

    in reply to: Automation Mode #2304
    gseher
    Keymaster

    If you really need to do that, I think you will be better off recording the Octo into a (computer based) sequenser.
    IF one could record all actions inside the Octo, I imagine the next question being: "How do we edit all these actions?". And then: "Why can´t I connect a display screen to my Octo, ´cause this is getting really complicated".;)

    I guess what I am saying is: Let us focus on making the Octo/Nemo even better and more fun at the core level and be true to it´s heart.

    Just my 5 cents.

    -Lars

    EDIT: Oh, I believe you intended to post this in the Octo forum, not? Perhaps we can have it moved.

    Post edited by: LDT, at: 2009/03/12 22:06

    in reply to: STEP copy and paste in PAGE edit mode #2229
    gseher
    Keymaster

    Same here – just seems natural to copy paste steps like this…

    Klaus

    in reply to: Cubase slave to Octopus master – will it work? #2299
    gseher
    Keymaster

    Thanks guys for your help, I did figure that i going to have to slave to cubase though that was not what I wanted ideally but there you go, such is life and software. I’m looking at ableton live now as well so I’ll see how i get on with that, the Octopus is due to be delivered today so I’ll have lots to do.

    in reply to: Cubase slave to Octopus master – will it work? #2301
    gseher
    Keymaster

    I’m feeling lazy at work, so I’ll help out.

    From a quick google, only MTC is supported since VST32 (source: gearslutz)

    to get more details on cubase and sync options:
    http://www.soundonsound.com/sos/jun04/articles/cubasenotes.htm

    I work in a similar way as LDT with reaper/live/sonar. sonar for example can be enslaved to the octopus midi but it will disable Audio processing (midi clock not enough resolution to work with audio)

    However, when I am using the PC as a simple multitrack recorder to record a session to be later chopped-up, I slave everything (but the PC) to the Octopus.

    Cheers,

    /R

    in reply to: Cubase slave to Octopus master – will it work? #2300
    gseher
    Keymaster

    You might want to try the other way: Octo synced to your DAW. That is what works for me, and the reason is:

    Timing difference between the tracks played by Octo and the tracks that was played by Octo but you now recorded them into the DAW.
    Of course it depends on your workflow and what you are trying to accomplish.
    I build up a bunch of tracks in the Octo, and then record them one by one into (in my case) Ableton. With Octo synced to Ableton, everything stays completely in sync throughout the whole process. Syncing the other way raises several timing issues.
    If you record all tracks at once, you would be ok though.

    And whether or not Cubase "likes" to sync to something else is an entirely different matter, but if it insists on being the master, well, that is your answer.

    Oh, and welcome to the forum, and congrats with your new machine!

    Post edited by: LDT, at: 2009/03/10 12:52

    in reply to: Maybe the only good reason to look into OSC #2296
    gseher
    Keymaster

    Here’s a few questions…

    any particular reason you sold capybara kyma originally?

    what do you think is unique to kyma? the algorithms, the workflow, anything else?

    what’s so special about the tau oscillator? is it really unique?

    What do you detest about the Kyma Capybara system?

    how effectively can it be used live (on stage)? do you need to fiddle continuosly with laptop? How long does it take to switch sounds?

    is half a pacarana system enough? or fairly limited?

    cheers, /R

    in reply to: snapshot trouble! #2294
    gseher
    Keymaster

    sysex?

    in reply to: Maybe the only good reason to look into OSC #2295
    gseher
    Keymaster

    Well, I think that very well might be the use of the ethernet port, and there are a couple of expansion ports also, but as far as I know there have been no announcements made as to what exactly their function will be. I got some hints that this will come soon, but it can be dangerous to presume that certain functionality will exist before it’s here.

    You’re welcome to ask me questions about the kyma system, or email me at implode7@comcast.net .

    in reply to: Maybe the only good reason to look into OSC #2292
    gseher
    Keymaster

    droolmaster0 wrote:

    Quote:
    Of course, you can use the osculator program to convert osc to midi signals for the kyma, but there is no direct osc support.

    I must have read the press release too fast… and I thought that was what the ethernet socket was for.

    btw, would you mind sharing your experience or can I ask a few questions? I’m vaguely considering getting this box.

    in reply to: snapshot trouble! #2293
    gseher
    Keymaster

    Let me start by saying…RTM…. ;)

    If you go to page 98 it states the following, so there is no need to keep the Nemo turned on 24/7 :

    Saving data to flash memory

    Nemo can save its full state for later recall – all settings are stored to FLASH memory and automatically recalled upon power-on.

    Note that only one state may be saved to FLASH, replacing any previously saved machine state.
    Also note that in order to perform this
    operation the sequencer has to be stopped.

    W A R N I N G:
    Please make sure that Nemo is not turned off or reset during the save operation!

    Saving the machine state
    To perform a save of the machine state go to Grid mode and press and hold the GRID button.
    While you hold down the GRID key, the Program LED will start to flash red.
    Pressing the Program key will start the save operation.
    Expect the save operation to take about 5-10 seconds.

    in reply to: snapshot trouble! #2034
    gseher
    Keymaster

    I tend to work on patterns/songs/sessions for months at a time, so I basically am afraid to ever turn the Nemo off. Is there any harm and/or possibility of lights burning out by keeping the Nemo on 24/7?

Viewing 15 posts - 31 through 45 (of 746 total)