Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 1,081 through 1,095 (of 5,965 total)
1 2 3 … 72 73 74 … 396 397 398
  • July 12, 2010 at 23:20 in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    July 12, 2010 at 22:55 in reply to: Groups, Childs and Sends=Feedback on other tracks???? #18814
    Zynewave
    Keymaster

    Sends must be placed in the same order on all tracks. This is a restriction to ensure plugin delay compensation will work correctly.

    July 12, 2010 at 22:18 in reply to: A little improvement please… #18813
    Zynewave
    Keymaster

    @Trancit wrote:

    do you know already something new about this mousewhell behaviour???

    I got a reply from the Poise developer. He said he looked at the mouse-wheel behaviour a while back, but could not find an explanation to why it behaved differently in some hosts. He’s using a development framework that handles the mouse-wheel, so he is not directly coding the mouse-wheel support. I’ve looked at it from Podiums side, and I can’t see why it doesn’t respond to mouse-wheel messages.

    July 12, 2010 at 22:09 in reply to: Program change supported? #18812
    Zynewave
    Keymaster

    Hi Batman,

    @Batman wrote:

    1st – Does podium support program change? If so where is it?

    The method thcilnnahoj described is the way to get the prg. chg. parameter for a plugin.

    2nd – Is there something like input transformer in Cuabse i could use to transform keyswich to program change?

    Without knowing how the Cubase input transformer works, I think I will answer no to that question. There is no method for converting incoming MIDI messages into another type of MIDI message.

    July 12, 2010 at 21:15 in reply to: Preview 2.34: Minor consistency updates #18810
    Zynewave
    Keymaster

    @Conquistador wrote:

    I am a bit baffled by your response to be honest. 🙂 Surely it is more important for your users preference to be taken onboard for easier use of the application (in this case the terms /words used on those buttons) than for a personal preference you have for the names, just to avoid you having to type out an extra word in your forum posts for each button?!?!?!? :-s

    Well, I’m baffled that you’re baffled. I reread my post, and I’m surprised it can be misunderstood. What’s wrong with having a short concise name that can be used as reference to the menu, while the text in the menu button includes additional details? If the button text is “Devices – I/O, Busses, Plugins”, the menu can be abbreviated as “Devices menu”. I don’t intend to write “I/O, Busses, Plugins menu” in the guide, so my suggestion does not result in longer names.

    I have a problem with “Plugins and Mappings”, because if you consider the purpose of the “device mapping” object, then plugins are also mappings.

    IMO I still see no real problem here.

    I tried to explain why it technically is not an accurate description. You may not see that as a problem, but I do.

    July 12, 2010 at 19:39 in reply to: Preview 2.34: Minor consistency updates #18808
    Zynewave
    Keymaster

    Seems like “Arrangements & Media” and “Plugins and Mappings” are the favorite. I was looking for shorter names, and I end up with longer names :-k

    The reason I wanted shorter names, is to avoid having to write “the arrangements & sounds menu in the project start page” every time I refer to this menu in the guide, or on the forum.

    I have a problem with “Plugins and Mappings”, because if you consider the purpose of the “device mapping” object, then plugins are also mappings.

    What about this solution:

    The “Arrangements & Sounds” menu is renamed to “Contents – Arrangements, Sounds”. The “Devices” menu is renamed to “Devices – I/O, Busses, Plugins”. I included “Busses” because I assume busses are not generally classified as I/O? In this case I use “Plugins” as a general term for both ReWire devices and VST plugins.

    That way I can refer to the menus as “Contents menu” and “Devices menu”, yet the button labels still show the more detailed description. Objections? 😉

    July 12, 2010 at 19:19 in reply to: Preview 2.34: Minor consistency updates #18807
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    Brings me to a question: what do you use the “new sound” menu entry for, anyways? It doesn’t seem possible to record or do anything else besides drawing waveforms in the stand-alone sound editor.

    You can record in the sound editor. But the “new sound” menu will only be useful in rare cases.

    July 10, 2010 at 09:26 in reply to: Preview 2.34: Minor consistency updates #18772
    Zynewave
    Keymaster

    Thanks for the suggestions.

    So far I’ve renamed the old “Arrangements & Sounds” and “Devices” menu buttons to: “Media Objects” and “Device Objects”.

    Anyone think this is a poor choice of words?

    I’m out of office for the weekend, so I’ll be able to reply again monday evening.

    July 10, 2010 at 09:19 in reply to: 2.33 #18771
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    Frits, is “BasicHeader.cpp” a Podium file? I getting this crash using DirectWave (simply loading sfz and playing them), so I think it’s related with DirectWave

    Uploaded with ImageShack.us

    BasicHeader.cpp is not part of my source code. It must be from DirectWave. I assume this bug is not new to Podium 2.33, but also occurred in previous versions?

    July 10, 2010 at 09:16 in reply to: Rewire Issues #18770
    Zynewave
    Keymaster

    @khaos wrote:

    Trancit the track you sent me wouldnt open, said it was made with a differnent version. I’m using 2.32.

    Unless the file was saved with 2.33, the message you get just informs you that the file was saved with an older version. If you resave the file, then the pod file will not load in that older version. The project should still load fine.

    Zynewave is it correct that for each rewire/reason instrument I want to use I need to create 2 tracks?

    It’s been a while since I last tried Reason, but if you want to use the Reason mixer, I believe it is enough to just set up the Reason master mix l/r mapping on one track in Podium. Then add all the Reason MIDI tracks you need in Podium. You would only need to use multiple Reason outputs if you want to mix or apply effects to each Reason synth in the Podium mixer.

    July 10, 2010 at 09:09 in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    July 9, 2010 at 22:28 in reply to: Podium preview topics #18763
    Zynewave
    Keymaster

    Preview 2.34: Minor consistency updates

    July 9, 2010 at 18:33 in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    July 9, 2010 at 12:00 in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    July 9, 2010 at 11:42 in reply to: Podium Free Releases #18759
    Zynewave
    Keymaster
    • Redesigned the graphics of track events.

    • Minor bug fixes.

    Topic: 2.32

Viewing 15 posts - 1,081 through 1,095 (of 5,965 total)
1 2 3 … 72 73 74 … 396 397 398
© 2021 Zynewave