Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 1,801 through 1,815 (of 5,969 total)
  • in reply to: Lock loop range #16356
    Zynewave
    Keymaster

    Wouldn’t it be easier to adjust the timeline rulers so that you are less likely to accidentally edit the loop range? You’ll avoid the extra clicks needed to toggle loop lock on/off.

    You can increase the height of the non-loop timeline ruler, or you can visually divide the timeline rulers by inserting space regions between them. You can also disable the default auto-hide option of the loop/punch/segment rulers.

    in reply to: Lock loop range #16354
    Zynewave
    Keymaster

    I would say no, but please explain what you mean with locking the loop range, and why you need it.

    in reply to: Do you think this might work? #16350
    Zynewave
    Keymaster

    If the the x64/x86 versions of a plugin has the same dll filenames, then you can easily exchange them. You just need to move/rename the x86 plugin folders temporarily, so that Podium will not find the plugins when the project is loaded. Then the auto-search will grab on to the x64 dll files with the same names. If the dll filenames are different, then you need to edit the filename in the device mapping properties dialog.

    in reply to: CPU issue? #16345
    Zynewave
    Keymaster

    @eyeknow wrote:

    For whatever reason, it likes the off position better.

    Some plugins can have problems when multiple instances of the plugin are running in multiprocessing. If you are using multiple instances of a plugin, try replacing this to see if the spikes with the “multiprocessing” option enabled goes away.

    in reply to: CPU issue? #16343
    Zynewave
    Keymaster

    @eyeknow wrote:

    Are these problems related to the demo restrictions?

    No.

    Is there a multicore switch I should be implementing?

    Check the “plugin multiprocessing” option in preferences. Also try disabling the option as a test.

    Also, any tips/tricks for cpu spiking/inconsistency will be appreciated.

    Try stepping up the buffer size to 256/512, and see if this improves it. Many plugins do some extra processing the first time they are started, so that can explain why you see spikes when inserting new plugin instances.

    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: Rename "Effect" please… #16331
    Zynewave
    Keymaster

    @Conquistador wrote:

    Is it possible for you to rename the track right click “Effect” drop down list to “Replace Effect”?

    Hmm, I’m not keen on that. To be consistent, then the “Preset” menu should be “Replace Preset”, and “Parameter” should be “Add Parameter Track”. I’m trying to use as few words as possible. Maybe this will change when I start my planned revision of the track headers.

    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: FR: folder for .mini files #16322
    Zynewave
    Keymaster

    @bladerunner wrote:

    @Zynewave wrote:

    In both cases it can be a nightmare to maintain the mini folder, and to validate it against moved sound files etc.

    the way i think of it (and of course put me right if i have it all wrong 😉 ) there wouldn’t be any need to maintain the allocated folder would there?

    I’m mostly concerned that the contents of the mini folder could grow out of proportions with thousand of mini files. But maybe it’s not a problem. The user can just delete all the files in the mini folder if he is worried about having too many orphaned mini files. I’ll consider it for a future update.

    in reply to: FR: folder for .mini files #16319
    Zynewave
    Keymaster

    @bladerunner wrote:

    is a .mini file fulfilling the same purpose as a reaper peaks file? they have an option to store all reapeaks files in one folder. does a .mini file differ in any way?

    They probably are comparable.

    if you did move the audio file to a new location would a new .mini file be created the next time the project is opened?

    If a mini file is not found, it will be regenerated when the sound file is loaded in the project.

    in reply to: FX dragging…?!?!? #16318
    Zynewave
    Keymaster

    The mixer will get an overhaul eventually, but not right now.

    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: FR: folder for .mini files #16310
    Zynewave
    Keymaster

    In theory a good idea. There are some practical issues like: How are the mini files associated with identical named files from multiple folders. Should the mini filename be encoded with the full path of the sound file, or should subfolders be created within the mini folder. In both cases it can be a nightmare to maintain the mini folder, and to validate it against moved sound files etc.

    But perhaps a configurable mini folder could be used as a mini file storage for sound files located outside the project folder. That way you can still move your project folders around without having to redo the mini files.

Viewing 15 posts - 1,801 through 1,815 (of 5,969 total)