Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 3,061 through 3,075 (of 5,969 total)
  • in reply to: 1.97 beta: Extended VST support #11545
    Zynewave
    Keymaster

    Could you eventually add also a multichannel mapping for instruments who have multiple outputs together with the stereo one ?

    I’m not too happy with that. It would mean that importing a stereo-only multiple output instrument will create a useless surround mapping, which may confuse users that only work in stereo.

    Absynth4 and Cronox3 are the only surround capable instruments I know of. Can you list other surround instruments?

    Zynewave
    Keymaster

    I want to use the Casio keyboard only for playing the onboard synth on the SB Audigy.

    Ok. To play the onboard SB audigy synth:

    Make sure you have enabled the SB synth MIDI outputs in the MIDI interfaces dialog. You should probably enable all your available MIDI outputs, except the Microsoft GS wavetable synth.

    On the project start page, open the “import hardware definition” submenu with the menu button at the top of the devices panel. The submenu contains a few hardware specific definitions. If the Audigy synth supports the GM or GS MIDI format, then select the generic GM or GS instrument. Otherwise select the “generic multitimbral instrument” from the menu. In the import dialog that appears, select the Audigy synth in the MIDI output listbox. Leave the other three listboxes at the default first line. Press OK.

    If you now go into the arrangement editor, you will find mappings for each of the 16 MIDI channels in the track inspector device list. Assign one of these mappings to a track, assign the MIDI input to the same track, enable monitoring with the power button in the transport toolbar, and then you should be able to play the Audigy synth on that MIDI channel. You can select a preset in the inspector preset panel. Assign one of the other Audigy MIDI channel mappings to another track, move the MIDI input there, and you can then play that channel, select another preset etc.

    Zynewave
    Keymaster

    I have a Casio CZ 3000 synthesizer with a midi out cable going directly into my Sound Blaster Audigy card on Midi Port II

    If you wan’t to use Podium to play the Casio synthesizer, then you also need to connect the MIDI in on the Casio to a MIDI out port on the SB. Or do you want to use the Casio keyboard only for playing the onboard synth on the SB Audigy?

    in reply to: French language #11540
    Zynewave
    Keymaster

    Support for other languages is on the future plan, but it requires a lot of work to implement this and to keep it up to date with each software release. Currently there are other features that have a higher priority.

    in reply to: 1.97 beta: Extended VST support #11539
    Zynewave
    Keymaster

    @acousmod wrote:

    All plugins are now well recognized, including ambisonic and Pluggo made, except the 8 channel versions from Acon : Studio Necessities and Studio Clean.
    http://www.acondigital.com/us_StudioNecessities.html
    I think that they are linked to an ini file or something like that.

    I downloaded the Studio Necessities demo, and modified the ini file to support the maximum 8 channels. Through debugging it appears that the plugins support the setSpeakerArrangement function, but it only reports success with the mono in/out arrangement. It fails on all other channel combinations I’ve tried. I don’t think I want to fix anything in Podium to compensate for this. If a plugin reports success on one or more setups, then Podium must assume that any setup that it reports failure on is unsupported by the plugin.

    in reply to: French language #11536
    Zynewave
    Keymaster

    Hi senga,

    Sorry, there is no French language version of Podium or the Podium guide.

    Frits

    Zynewave
    Keymaster

    As an example I don’t see a “Project Wizard” in my version.

    This must be from one of the old videos. They are indeed outdated, but I keep them online because some of the features shown in the videos are still valid. The project wizard was removed a long time ago, and is replaced by the project start page you see when you first start up Podium. I recommend you study the written “getting started” tutorial in the Podium guide pdf file. This is also available in the wiki section:
    http://www.zynewave.com/wiki/doku.php?id=guide:getting_started

    What kind of device do you have connected to the MIDI input of your SB card? Is it a synthesizer or a simple MIDI keyboard controller (without sound)?

    To play an instrument in Podium, you can either use VST instruments or hardware synthesizers. There are no VST instruments bundled with Podium, so you need to download those from other websites. There are plenty of freeware VST effect/instrument plugins available. A good database to search can be found at: http://www.kvraudio.com

    in reply to: 1.97 beta: Extended VST support #11533
    Zynewave
    Keymaster

    @swindus wrote:

    Found another bug:
    – Insert a wav file on a track.
    – Open the wav file in the sound editor and copy a segment from the wav file to the clipboard.
    – Create a new track.
    – Create a new event on the track and open it in the sound editor.
    – Place the edit cursor outside the range of the new event!
    – Paste the clipboard content to the event (Ctrl+V or menu command).
    – Crash.

    Happens only when the edit cursor is not in the range of the event where the audio content is pasted in.

    Thanks for the project file. This bug is fixed in the new beta6.

    @acousmod wrote:

    There is no change for the plugins that are not recognized as multichannel (the list in my previous post).
    Is this because you are yet working on it or because it is not possible ?

    I tried the Tobybear DMO bag from your list, and made some further changes to the import. I think Podium now will import all multichannel plugins correctly as inserts. Let me know if there still are plugins that are not recognized as multichannel.

    The beta6 has a new “enable plugin processing during preset recall” option in the preferences dialog. This is disabled by default, and when disabled Podium will work as in previous versions. Enabling this option may reduce the CPU spikes that can occur when activating monitoring and when changing plugin programs/presets. Podium has so far always skipped processing while preset recall was in progress, due to the fact that there were some older plugins that would crash otherwise. This was years ago, and with a bit of luck there are not many plugins left that have problems with simultaneous processing/preset recall. Please try enabling the new option and let me know if you notice any change at all in CPU spikes, or if you find plugins that behave badly with the new option enabled.

    Zynewave
    Keymaster

    Question 1 – Do you always have to choose a new assignment to reset the sample rate to 48000Hz?

    If the “default sample rate” setting in the MIDI/Audio Interfaces dialog is set to 48000, then all new arrangements you create will by default be set to this rate as well.

    Question 2 – Where is the rewind button after play back?

    There is no button for this. You can use the Q/W key shortcuts to move the edit cursor. Also check out the “link edit cursor to play cursor” option found in the view menu. If you keep this option disabled, then stopping playback will reset the play cursor to the last edit cursor position.

    Question3 – How do I assign a track 2 to access my midi port II input?

    I assume you followed the instructions on the “create new project” start page, and enabled your MIDI inputs prior to the final creation the project. If so you should see the MIDI inputs in the input panel of the track inspector. If you have created a new track, you can assign the MIDI input by double clicking the input object in the inspector, or by using the “Input” submenu when right-clicking the track header. On the same track you also need to assign the instrument that you want to play with the MIDI input.

    If I get input should I add it to the string of this post or start another one?

    Just hit the “post reply” button at the bottom of this topic page to add another post.

    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: 1.97 beta: Extended VST support #11527
    Zynewave
    Keymaster

    @swindus wrote:

    Found another bug:
    – Insert a wav file on a track.
    – Open the wav file in the sound editor and copy a segment from the wav file to the clipboard.
    – Create a new track.
    – Create a new event on the track and open it in the sound editor.
    – Place the edit cursor outside the range of the new event!
    – Paste the clipboard content to the event (Ctrl+V or menu command).
    – Crash.

    Happens only when the edit cursor is not in the range of the event where the audio content is pasted in.

    I’ve tried this various ways now, but I cannot get a crash. Can you send a project file with the tracks and events prepared, or post some more details?

    in reply to: 1.97 beta: Extended VST support #11523
    Zynewave
    Keymaster

    @swindus wrote:

    I did a quick test and beta 4 is still crashing when I delete the last track in the project I sent you if the inspector is hidden.

    Ouch. Please try the new beta5. I had only tested that it didn’t crash when you hid the inspector after entering the arrangement. Now it should work also when the inspector is hidden before opening the arrangement.

    in reply to: Minor suggestion about track height #11522
    Zynewave
    Keymaster

    I thought this had been changed already!?

    What you describe is true. However if you have zoomed out so that the tracks are higher than the contents, then the track heights will be scaled when you e.g. open the mixer. I intend to make the track heights pixel fixed, as Mike described.

    in reply to: Minor UI niggles #11516
    Zynewave
    Keymaster

    2. The Outputs and Busses folder separate to Inputs. Again, wouldn’t it make sense to house these with the Inputs area? The outputs in particular are changed infrequently – whenever I go to the VST Mapping area I have to also encounter outputs and busses. These are small things I know, but why not have a section for structural objects like in’s, out’s and busses, and a distinct plugins compartment?

    I’ll probably change the device panel so that the list contents are filtered to show only mappings relevant for the current track. E.g. the audio outputs folder will only be shown when focus is on the master track.

    in reply to: Minor suggestion about track height #11515
    Zynewave
    Keymaster

    I’m going to change this at some point. After the recent introduction of the track header chain panels it has become more sensible that the tracks retain their heights, as you described.

Viewing 15 posts - 3,061 through 3,075 (of 5,969 total)