Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 2,026 through 2,040 (of 5,969 total)
  • in reply to: One track to trigger two instruments? #15499
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    Hey, DFusion! I caught notice of the thread you made in the VIP Lounge, but it disappeared (?) before I could download your template file. 😕

    I didn’t delete the topic, so I assume it is DFusion that deleted it himself?

    Now that I got a look, I’m interested in how you got that set up! I mean, it’s kind of buggy behaviour to have an input on multiple tracks, isn’t it?

    I have noticed that there are some situations where you can end up with multiple tracks having the same MIDI input object assigned. Copy/paste of a track is another way. There should be no buggy behaviour in having the same MIDI input assigned to multiple tracks. It’s just in the UI that I have implemented the restriction so that assigning/dragging an input object will remove it from the track it is already assigned to. In most cases I think this is what you would expect. In the future I may add a command for assigning an input without removing it from it’s current track.

    in reply to: One track to trigger two instruments? #15490
    Zynewave
    Keymaster

    No.

    If you use two tracks, remember to copy the sequencs events as phantom events. That way you only have to edit the notes on one of the tracks, and it will automatically be applied on the second track.

    in reply to: Preview 2.18: New compiler and x64 test version #15487
    Zynewave
    Keymaster

    Beta4 is up with just a small bugfix:

    Fix: The Podium generic plugin editor did not update the parameter value display when the parameter was changed through MIDI control changes.

    in reply to: Preview 2.18: New compiler and x64 test version #15485
    Zynewave
    Keymaster

    @swindus wrote:

    Found another graphic quirk. The peaks of audio sequences are not drawn at the beginning in the arrangement. Its the same on imported or bounced audio. As you can see in the sound editor the audio event is complete.

    Thanks, now fixed in beta3.

    It was an optimization I made yesterday that turned out to be a little too optimized.

    in reply to: Preview 2.18: New compiler and x64 test version #15484
    Zynewave
    Keymaster

    @swindus wrote:

    Its working now, thanks!

    I have a request. The key ‘H’ is used for minimizing and maximizing tracks. Would it be possible to add the command ‘Ctrl’ + ‘H’ for minimizing all tracks and maximizing the selected one?

    Ctrl+H is already used for toggling the “hide track lane” option.

    When you say maximize, do you mean that the selected track should zoom out vertically to fill the entire tracks region?

    in reply to: Preview 2.18: New compiler and x64 test version #15481
    Zynewave
    Keymaster

    @swindus wrote:

    On the way ….

    Thanks. Bug fixed in the new beta2.

    New features in beta2:

    • Redesigned the save progress dialog that appears when saving project and sound files. The progress bar indicates the total save progress of all files. Number of saved files is displayed at the bottom info line. The dialog has an Abort button.

    • Speed optimized load times of large multichannel sound files.

    It’s been a while since the last release, so I’ll probably release 2.18 this weekend, even though there is not that many new features.

    in reply to: Preview 2.18: New compiler and x64 test version #15478
    Zynewave
    Keymaster

    @swindus wrote:

    Got some graphic problems with 2.18. Some stripes in the backround in the arrangement and on the project page too.

    In the migration to the new compiler, I had to replace an old graphics library I had been using for loading various image file formats. It looks like you are using a panel texture image that is not loaded properly. Please email me the texture file so that I can debug the new image loading function.

    in reply to: Ticks per quarter note #15475
    Zynewave
    Keymaster

    Podium uses an internal resolution of 16384 ticks per quarter note. This cannot be changed by the user.

    in reply to: Preview 2.18: New compiler and x64 test version #15467
    Zynewave
    Keymaster

    @Conquistador wrote:

    My initial results with the x64 version bear this out and as Frits said it may very well crash well…it did. 🙂 😛

    Let me know when you have another x64 version to test…sadly this version cannot get past that error message. :-k

    Ahh, too bad. Thanks for testing. I googled around for the error description, but I could not find clues for what needs to be fixed. I have removed the x64 test download. I will have to postpone further development of the x64 version until I get a x64 Windows platform that I can debug on. Hopefully by November it will be possible to order a Dell PC with Win7 x64 preinstalled.

    in reply to: Preview 2.18: New compiler and x64 test version #15466
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    Frits, I sold Gladiator2 because I was in crisis, if you have the NFR version 2.1, please, could you test if it works in this new Podium version (32bits)? (do you remember the presets problems with GUI resize?). I’m thinking into buy it again.

    I have not received the 2.1 update. I was only given a download code for version 2.0.

    in reply to: Podium preview topics #15456
    Zynewave
    Keymaster
    in reply to: Groove/Shuffle #15450
    Zynewave
    Keymaster

    @moikkelis wrote:

    Would you tell us what is in that list? So we can know “what is coming next”?

    The future roadmap is a twisting road, that is often determined by discussion on this forum. I often post “preview” topics in the future forum for the next release, but what comes after that release is not etched in stone 😉

    in reply to: Groove/Shuffle #15448
    Zynewave
    Keymaster

    @moikkelis wrote:

    Is this going to happen? This is really wanted.

    Groove/shuffle is on the list, but I have quite a few higher-priority features before this.

    in reply to: idiots corner here #15443
    Zynewave
    Keymaster

    @moikkelis wrote:

    Well this same thing affect on master channel. Sometimes that mixer channel just ignore that limiter (waves L2). Now happened to me twice. After closing podium and loading song again it works fine. So i think this is some kinda bug?

    Could it be that you had bypassed the effect? (The yellow X buttons).

    Try to replace the L2 limiter with another non-waves limiter plugin and see if you get the same buggy behaviour.

    in reply to: idiots corner here #15441
    Zynewave
    Keymaster

    @moikkelis wrote:

    Hi again

    Well, i have limiter on last one and it still goes over and red one? Looks like the limiter doesnt even affect anyway. is this bug or what?

    Limiter volume faders will move, but there is no gain reduction, so i cannot rly understand what is going on. I have tryed move that limiter in different slots, same result. 🙄

    Have you placed it in the master effects chain?

    Perhaps you could post a screenshot.

Viewing 15 posts - 2,026 through 2,040 (of 5,969 total)