acousmod's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 556 through 570 (of 587 total)
  • in reply to: Key to split #4224
    acousmod
    Participant

    Do you want the cut action to cut through all events in the arrangement that overlap the cursor position, or just the current track, or maybe just any selected events?

    Oh, the typical behavior is when a sequence or a track is selected this one only is split, and if none is selected it is a global split for all the sequences that overlap the cursor.

    What is your typical purpose of this cut; To rearrange stuff, or to silence a section, or other?

    Yes, of course rearrange, split and then make an edge shorter (with the Ctrl key), or overlap the edges of the two new segments for a crossfade (for the future !).
    All that can be done with a special tool but which often avoid useless mouse movements…
    After, it is a matter of preference.

    in reply to: Bug in automation within plugins interfaces ? #4219
    acousmod
    Participant

    Hmm, are you sure it is not set to the default value you entered (i.e. 64 ~ 0.5)?

    Yes.. it is OK.

    I just need after to redraw with the pencil in the curve editor to obtain smooth curves.

    in reply to: Bug in automation within plugins interfaces ? #4214
    acousmod
    Participant

    An alternative solution for the values during the recording of the automation could be “keep the last value” instead of “insert the default value” ?

    Hi !
    I have changed the values in the Parameter Properties (I’ve put 0 to 127 and default to 64, is there any standard better values ?).
    Result : the last value when I stop moving is held !
    So no more jumps.
    I will update all my Devices Mapings with this values.

    Cheers,

    in reply to: Change default mode for step by step automation #4213
    acousmod
    Participant

    Rather than creating options for alternative behaviour, I would prefer to start work on ‘edit in place’.

    OK, OK, me too !
    Will wait,
    Thanks !

    in reply to: Sound File in "Inspector" #4212
    acousmod
    Participant

    I usually call it the ‘track inspector’

    so I was good…

    Each panel tab that is added to the inspector, will reduce the height available for the active panel.
    I’ll add it to the plan.

    sure, but with modern screens…
    so it would be nice for an option, thanks !

    in reply to: Key to split #4211
    acousmod
    Participant

    as for me : allways !

    It’s a habit that I have kept with older softwares (Samplitude, Vegas, Nuendo).
    I can also use the tool and the mouse, but, if it doesn’t ask you too much work I will be very happy to continue this way with Podium…

    An exemple ?
    Play…
    Stop !
    and a single pression on a key for the cut.

    in reply to: Bug in automation within plugins interfaces ? #4210
    acousmod
    Participant

    Concerning my first question, perhaps the jumps to 0 during the movements with the objects are due to the fact that they are not very regular ?
    So, each time that my hand makes a little stop Podium thinks that the automation has finished and puts the default value ?

    An alternative solution for the values during the recording of the automation could be “keep the last value” instead of “insert the default value” ?

    in reply to: Bug in automation within plugins interfaces ? #4209
    acousmod
    Participant

    Are you recording into/over an existing curve sequence that already has events?

    no, start allways with a blank one.

    Whenever there is a blank interval on the track without a curve sequence, then the parameter is set to the default value.

    oh, very annoying !

    You would have ‘holes’ in your arrangement where a given parameter could have a random value, depending on whether you have manually moved the play cursor or changed the parameter in the plugin or synth. Thus playback would sound different, depending on where you started. If you e.g. automate a pitch-bend parameter, then the pitch-bend would be left in whatever position was last played.

    ok, but what about the function that we find in Cubase (for MIDI since the ATARI version !) and others that simply consists to play the last previous value that is found on the track ?
    I founded this simple and practical…

    As it works now, Podium is in control of the parameter value at any position in the arrangement.

    Podium, but not me !!!

    So the only way is to put a continuous automation value for the entire length of the project, even for places where there is no change…
    snif

    If there a chance for an update ?

    in reply to: Key to split #4207
    acousmod
    Participant

    ooooooohhhh 🙁
    in some day, perhaps ??? (please)

    in reply to: Bug in automation within plugins interfaces ? #4200
    acousmod
    Participant

    2nd part :
    When there is no track automation, the parameters of the plugins have a “normal behavior”, BUT when I put some parameter on a track its value turns to 0 each time Podium starts playing.
    The only way to keep the actual value of a knob is to mute the automation track…
    The same thing happends at the end of an automation sequence : the last value is not hold, instead it returns to 0 😥

    Is this normal doctor ?

    in reply to: Path of the VST plugns #4199
    acousmod
    Participant

    Just a question : when some plugins are in subfolders of the VST path (for example the free VST that you use in your demos), Podium doesn’t find them and asks for the path of the plugin.
    Could it be possible that it will scan the subfolders and find the dll that are presents ?
    Or perhaps to give several paths (without subfolders) will be usefull too ?

    in reply to: snap events #4160
    acousmod
    Participant

    Could you give some examples of what you mean by ‘snap by events’?

    Yes, excuse me, it’s rather difficult for me to express in english…

    You are right : it concerns the snapping of the edges of events on the same track and the snapping of start and end of events on all tracks, if possible withe ability to select the “one track” or the “all tracks” mode.

    The relative snapping that you described will possibly be usefull if it is based on a time quantize (in seconds) rather than a bar quantize ? I personnaly don’t need this function.

    in reply to: nothing in arrangement window #4158
    acousmod
    Participant

    This problem has popped up before. Here’s a rewrite of my previous answers to this problem:

    Thank you and excuse me, I didn’t read it : it’s now fine (and I will backup my profile).

    in reply to: FR Wheel zooms #4123
    acousmod
    Participant

    What can I say ? As usual : perfect !!!

    Thanks !

    in reply to: 1.21 #4117
    acousmod
    Participant

    It is unfortunate that it comes at a cost of higher CPU usage for some SynthEdit plugins, but I think stability is to be preferred.

    Yes, I agree…

    Is it not possible to do something about the extent of idle message processing in SynthEdit?

    I don’t know… will see with others on the forums.
    Synthedit is not an ideal tool and I know that its plugins are not optimized, but it is better than nothing for me, as I am not able to write codes 🙁

    have you tried out the new SynthMaker tool

    Yes, I had tried the old version a time ago and this new one is very promising !
    I hope that the developpment will continue this time and if the VST are more stable and faster, sure that I will try to rewrite some of them inside SynthMaker.

    Thanks a lot for your support.

Viewing 15 posts - 556 through 570 (of 587 total)
© 2021 Zynewave