Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 1,861 through 1,875 (of 5,966 total)
  • in reply to: Podiums Hierarchy (please vote)… #16168
    Zynewave
    Keymaster

    @Conquistador wrote:

    Also I just cannot add any FX to that Master track.

    Assuming you want your “ANALYSIS” track (Ozone) in the master chain:

    Delete the empty “Track 1”. Open the properties for the “Playback 1+2” track and clear the “use as group track” option. That should move all the normal tracks into the center section and keep only the return group docked to the right.

    in reply to: Podiums Hierarchy (please vote)… #16160
    Zynewave
    Keymaster

    @Conquistador wrote:

    A question for you Frits…

    The master chain is just the effect chain that is present on the master track. You have that docked on the right edge of the mixer. If you want to show the mixer strip for the zPEQ effect you added, just disable the “hide mixer strip” option in the zPEQ track menu.

    Zynewave
    Keymaster

    @Noely71 wrote:

    Can you create a midi track without a midi input device?? i can create the track, and a new track event, and edit it in a piano roll, but i can’t get any sound to it, i cant insert sounds, i can’t even find where assign a drum editor profile into a track? 💡

    Hi,

    You can create tracks without using MIDI input devices, just like you described it. To get any sound out of the MIDI track you need to assign an instrument to the track. If you have any VST plugin instruments, then you can assign one using the “source” submenu in the track right-click menu.

    To set up a drum track can be a bit tricky. You’ll need to assign a drum instrument to the track, and then specify the “use as drum-kit” option in the properties for the preset you select. The whole drum-map editor is scheduled for an overhaul sometime later this year.

    Frits

    in reply to: 2.20 #16140
    Zynewave
    Keymaster

    For the 2.21 release I’ve renamed “load default setup” to “restore default setup” and added a “restore default editor profiles” command. That at least enables you to restore all the editor profiles without affecting your other settings.

    in reply to: Tascam Fire One #16136
    Zynewave
    Keymaster

    It will need to support emulation of the Mackie MCU protocol to work as a control surface in Podium. If it’s just simple stop/play actions, then it should work if the device supports sending standard MIDI clock messages.

    in reply to: Podiums Hierarchy (please vote)… #16135
    Zynewave
    Keymaster

    I’ll get round to revamping the mixer. Some of the “spreadsheet” like behaviour of the effect headers is a leftover from the old expanded track mode. With that mode gone in 2.20, I can now start cleaning up some stuff.

    Before the mixer, I will be looking at the tracks region. For 2.21 I’m trying out a new feature that will make navigation easier. I’m not quite ready for a preview topic on that yet.

    After that, I’ll be looking at the track header contents. I’m not entirely happy with the current design. I think it tries to cram too much functionality into the small space of the header. It can be confusing at times with all the controls, menus and different mouse actions. I’m thinking about a solution where the contents in the header is mainly information, and then add a single button on each header. Clicking this button will show a larger popup panel to the right of the track header (semitransparent overlay on the track lanes) with easy controls for managing the effect chain etc. That’s beyond 2.21 though.

    in reply to: Wave form Peak display… #16134
    Zynewave
    Keymaster

    Not a small thing to implement, and not something that I think will fall under the areas I’m going to work on the coming months.

    in reply to: Waveform changes… #16133
    Zynewave
    Keymaster

    This is not a small UI thing to implement, so this is far into the future.

    in reply to: zPitch default value #16132
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    I read in the Guide that curve event points can be reset by holding ALT: “Use this to reset for example pitch bend or pan parameter curves to their center position.”

    Would it be possible to update zPitch so the default value for its pitch parameter corresponds to no pitch change? Right now it defaults to zero, meaning -12 semitones.

    Seems it can be done by the user (by changing the parameter properties for ‘pitch’ in the inspector param tab) but of course I only found out about that now. Anyway, zero cents would make for a better default than -1200 for everyone, I think.

    Currently you’ll need to do it via the parameter properties dialog. In a future update I may update the zPitch plugin to support extended parameter info. I think that will make it possible for Podium to detect what the default value should be. But that is far into the future.

    By the way (not via PM this time :wink:), the help for all three draw mode buttons in the curve editor says to hold CTRL to reset instead of ALT (Podium 2.19).

    Fixed. Thanks.

    in reply to: 2.20 #16131
    Zynewave
    Keymaster

    @kyran wrote:

    Changing profiles isn’t really snappy though. It takes at least a second before it changes on my vista laptop here.

    After I’ve just loaded an arrangement it takes a lot longer even.

    I’ll try to speed optimize the editor profile switching for the next release.

    in reply to: Podium Releases #16123
    Zynewave
    Keymaster
    • Changed the default setup to use the new editor profile bar.
    • Independent timeline zoom in the embedded editor.
    • Each MIDI and audio input can be assigned to multiple tracks.

    Topic: 2.20

    in reply to: Real Future #16122
    Zynewave
    Keymaster

    @Markus wrote:

    So Frits, makes this topic anything sense?

    So far not much new has come to light in this topic. I already knew that Darcy wants a Mac version of Podium. I need to grow a second brain to make that happen though 😉

    in reply to: Real Future #16121
    Zynewave
    Keymaster

    @bladerunner wrote:

    it seems to me that podium is reporting a more accurate cpu reading than other hosts and that podiums engine is based on real time performance (so, equivalent to reapers synchronous mode right? – forgive me if i am repeating stuff that has been mentioned in other related threads) and not the rendering ahead type ability of reapers anticipative mode. when reaper is in synchronous mode i get a similar performance to podium but when in anticipative i get more performance but the trade off is in a delay to real time performance tweaks to plugins etc. (right?!). hope i’m making sense

    Exactly. I’ve spent a lot of time optimizing the performance of the engine, so I’m glad to hear that your performance test shows that Podium matches the synchronous mode in Reaper.

    in reply to: Real Future #16116
    Zynewave
    Keymaster

    @bladerunner wrote:

    the ongoing cpu spike issue which can be clearly be seen in frits own video here

    http://www.youtube.com/watch?v=Jv39dX7NP_Q

    its reassuring to know that it happens on the devs own computer as i thought it might be an issue with my own particular set up. it really makes podium almost unusable for me. i haven’t seen behaviour like it in any other host. the spiking seems to be directly linked to the asio buffer size which has to be set at 2048 samples to tame the spikes. in reaper i have no such problem and can run many more softsynths at 512 samples. i have read through all of the cpu related threads in this forum and played around with all of the recommended tweaks etc. but the issue still very much remains.

    i have also mentioned timestretching as an issue but i could just rewire reaper for that duty if i needed it so the cpu issue being addressed is my one wish.

    i can regularly bounce tracks as a workaround but i think there is an issue that needs addressing here. do others find this is still a problem or are you bouncing tracks to get around it?

    Sigh! 😥

    If it leaves the impression that Podium suffers from CPU spikes, then I guess I have to redo the video with some tracks bounced. The spikes you see in the video are not random. They occur at places in the song where a lot of notes are playing simultaneously. I shot the video with a buffer size of 2048. As I’ve explained in previous topics, Podiums CPU indicator is deliberately sensitive, to give a clear warning of where there may be problems. Other hosts may use a slower updating CPU indicator, but that does not mean that CPU spikes are more likely to occur in Podium. As you can hear in the video, the spikes does not produce an audible degradation of the audio output.

    That you find that Reaper produces lesser CPU spikes at low ASIO buffer sizes can be due to the anticipative mode, which has been discussed here:

    http://www.zynewave.com/forum/viewtopic.php?p=13556&highlight=anticipative#13556

    in reply to: Podium preview topics #16109
    Zynewave
    Keymaster
Viewing 15 posts - 1,861 through 1,875 (of 5,966 total)
© 2021 Zynewave