Gabriel Seher

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 42 total)
  • Author
    Posts
  • in reply to: …hyper-step – inconsistency?… #2697

    Gabriel Seher
    Participant

    Hi – I was able to replicate the error you describe in the step copy procedure and solved it in the latest version of the source by not copying the hyper status of the source step to the target step.

    One could argue that the hyper status should be taken over by the target and removed from the source, but regardless, a consistency check needs to be in place, so much is sure.

    In terms of allowing more than one hyperstep to a track, that would involve a major change to the internal structures, is therefore not feasible in the short term.

    Cheers,

    Gabriel

    in reply to: Octopus dead after upgrade attempt #2619

    Gabriel Seher
    Participant

    Interestingly enough, all I am ever using is a Mac machine on currently OS X 10.5.7. Our suspicion is that these problems that some Macs have may be related to USB drivers on the Mac platform. The latest OS X update (10.5.8) was released not too long ago. While we have tried to replicate any problems with both 10.5.8 and 10.5.7 without success, there slowly appears to be some sort of pattern where the Macs seem unreliable for the operation. This is just to let you know that we are not sitting and watching but unfortunately could not pin it down yet to a particular problem in any of the system components involved.

    in reply to: legato notes? #2618

    Gabriel Seher
    Participant

    OK – understood now.

    in reply to: instant page switching video #2593

    Gabriel Seher
    Participant

    The switching rule is – when a bank is actively playing, the instant switch is active.
    When a bank is not playing but a page is queued for play, it will be started on the beat. I guess one workaround may be to stop the playing page first and then queue the next one to play. Let me know how it works for you.
    Cheers,
    Gabriel

    in reply to: First Impressions + Page Mode Niggles #2531

    Gabriel Seher
    Participant

    Hello Julian,
    thanks for the feedback and the questions. Please find my thoughts below.

    jngpng wrote:

    Quote:
    – It’s really annoying how grabbing a step in standard Page view deactivates it until you tweak the value there. It can break the flow of a sequence if you are composing on the fly. It would seem to me to be much more logical if the step did not deactivate immediately when you grabbed it (i.e. when you press the button), but instead deactivated when you release the step button. So, the behaviour would be that if you press a step button and release it without adjusting any values, it is toggled on release. If you pressed the step and and then adjusted values, its toggle state would not be changed at all.

    This has to do with the fact that in page mode we want the steps to toggle as soon as you press the button, not release the button. What you suggest would of course solve the issue above, but in my opinion feels unnatural in the general use case where you simply toggle steps.
    However, I’d be interested to hear what others think about it. I will cross post the question in the Octopus forum as well, where a related discussion on page edit modes is going on – thanks for bringing it up. The link to the discussion is here:http://genoqs.net/index.php?option=com_joomlaboard&Itemid=59&func=view&id=25317&catid=5&limit=6&limitstart=18

    Quote:
    – I don’t really understand why there are three different Page modes (standard, edit, and edit perform). As far as I can tell, the only difference between ‘edit perform’ and standard Page view is the fact that you can’t toggle notes on and off. Is this correct? I can definitely see the point of being able to preview steps audibly (edit mode) and I guess I can see the utility of stopping yourself from accidentally toggling a step. What I don’t understand is why this has to be accomplished by two extra (confusing in my opinion) modes rather than simple toggle switches controlling whether steps are toggled and/or previewed when pressing them. There’s also the issue that being in ‘edit’ or ‘edit perform’ mode prevents you from accessing step or track mode without first switching back to standard page mode.

    You bring up an excellent point that was made in parallel in the Octopus discussion I mention above. Please take a look there and feel free to contribute as you see fit. I looks like we have a solution draft, and I’d be interested to hear your thoughts on it.

    Quote:
    – It would be really useful to have more visual feedback when tweaking a particular step in Page mode. Currently, no information is shown whilst tweaking a step in standard Page mode – whilst PIT information is shown in ‘edit’ and ‘edit perform’ mode. Ideally, i’d like to see values for PIT, VEL, LEN and STA displayed in their appropriate rows whilst tweaking in all of these modes. To keep the current distinction between standard and the ‘edit’ modes, maybe it would be good to show offsets in the standard mode and absolute values for the parameters in the ‘edit’ modes?

    I will try this out and see how it feels. Also, I’d love to hear if anyone else have thoughts about this as well.

    Quote:
    Obviously, I’m new – so if any of these complaints are based on misunderstandings please do put me right! It’d be great to hear your thoughts on these issues (especially you Gabriel! ;)).

    Again, thanks for bringing it up.
    My personal feeling is that Page mode should be divided in a cleaner way between the standard (toggle) mode and the Edit mode – which needs some reduction to be more friendly, but in general it provides a good level of distinction between the respective use cases. However, I am attracted to the solution you propose in 1 though, which would probably allow the combination of both modes into a single one..

    Cheers,
    Gabriel

    Post edited by: gseher, at: 2009/09/13 09:49

    in reply to: Playtime for Hypersteps #2554

    Gabriel Seher
    Participant

    The hyperstep is a step that provides its "container" to a track to be played. Confused? Let’s consider a simple note.. assigned to a step – calling it a "note step".
    In the basic case the note step will have a pitch, a velocity and a length. With that data the note step will play a note on a sound source.
    Now we make our note step to a hyperstep, hence assiciating it with a track.
    What happens now is the following: when the hyperstep is played, not the note is played, but the associated track is played, using the step parameters: The step velocity and pitch become the track’s velocity and pitch respectively and the step length determines the time that the track will take to play full. I.e. if the step is 96/192 long, that translates to the track playing twice as fast as normal speed.
    Of course, interesting things happen when the numbers are not so "round".
    I hope this helps somewhat.
    Cheers,
    Gabriel

    in reply to: Nemo 1.62 pos bug? #2537

    Gabriel Seher
    Participant

    Yes – this is now fixed and will be part of the next OS release.
    Gabriel

    in reply to: Track RMX #2610

    Gabriel Seher
    Participant

    This is fixed on my end and will be part of the next OS release.

    Gabriel

    in reply to: Possible POS bug #2567

    Gabriel Seher
    Participant

    Just to let you know, the problem is fixed and will be part of the next OS release.
    Cheers,
    Gabriel

    in reply to: Page speed multiplier #2595

    Gabriel Seher
    Participant

    Another nice one Lars! Now we know why we had to wait so long for this one to happen :-) But I am sure it was worth it.
    Cheers,

    Gabriel

    in reply to: legato notes? #2534

    Gabriel Seher
    Participant

    jngpng wrote:
    This currently works in Page edit mode only, correct? I can certainly see the argument for not implementing it in normal Page mode, as it could obstruct the toggling of multiple steps. It would be great to have it in Step mode however, and I can’t see how it would obstruct any other functionality – thoughts anyone?[/quote]

    Can you please explain in more detail how this would work in Step mode? By Step mode I mean the mode where the matrix is dedicated to showing the attributes of only one step..
    Thanks,
    Gabriel

    in reply to: Edit modes and complexity #2602

    Gabriel Seher
    Participant

    Thanks all for the excellent discussion. It seems that the distilled solution to the complexity problem of the three modes is the following:

    – The EDIT PERFORM state (Berlin) takes the place of EDIT state, and we go back to having the EDIT button switch between two states.
    – The old EDIT state will be reached by holding some other button while pressing EDIT (or possibly another route).
    – The state of the EDIT button will get global and hence will "carry" across pages
    – the [STEP] button in the mode block should be available to quickly jump into that step (nice consistency with the overall model)
    – Add the ability to zoom into step/track mode via double-click from the ‘Berlin’ state
    It’s all on the worklist now.

    EDIT: added input from a discussion on the Nemo forum
    – There is a suggestion that the behaviour of the step buttons may be changed in the sense that pressing a button in Page mode (standard toggle behaviour) will not have an effect until one releases the button. Like that we could combine the normal Page mode with Berlin mode into one level of operation. The drawback is of course that toggling steps in the matrix will feel differently. Any thoughts on this anyone?

    Cheers,
    Gabriel

    Post edited by: gseher, at: 2009/09/14 06:40

    in reply to: Grid live mode #2594

    Gabriel Seher
    Participant

    Hi Lars, this sounds like a reasonable request indeed!
    Does anyone think differently about it?
    Cheers,
    Gabriel

    in reply to: Octopus dead after upgrade attempt #2535

    Gabriel Seher
    Participant

    Not sure if I count, but yes.. it worked fine on my end. MBP 2,33 GHz, OSX 10.5.7
    (I have not updated to 10.5.8 just yet)
    Gabriel

    in reply to: Octopus dead after upgrade attempt #2513

    Gabriel Seher
    Participant

    Hi Barry, the way to reset it would be to install 1.62 via the USB route. Let me know if you need assistance with it. Cheers,
    Gabriel

Viewing 15 posts - 1 through 15 (of 42 total)