Trancit@LiquidProj3ct wrote:
The mini-mixer strips are cool.
It would be nice if you could hide the master and return mixer strips since when you’re using three or more they take a lot of horizontal space from the screen. (or, is there any way to do it?)
The only way I found is when you “undock” them…
Trancit
TrancitThx very much, but one little thing:
For me the size of the level meter drops down to soon to make place for the Solo/Mute/Record buttons…
The size drops down already at the next possible step before 100%, when the buttons are “far far away”
The buttons reach the level meter at a zoom level of about 50% and it would be nice if the size drops down directly before that and not so early…
Second I noticed, if busses are docked (I always use them docked at right side as well as the master) there are not affected by zoom level…
Third, the meter scale: If you would place the level meter scale under the SMR buttons, they could be visible for much longer time…
But apart from this, this zooming works very fine…
Thx again
Trancit
TrancitSorry, I was a little to fast in my thoughts, I think 😀
Here more in detail: If I use a multi-out instrument in the group channel, like you used Kore player for this example and I don´t only want to have the midi data on different channels, but the audio as well.
So my question is: If a Multi out vsti is hosted by a group channel, can I although route the audio data to seperate other channels by using the different output devices of this multi channel instance???
My second question was, if it would be posssible to route the audio to childs as well, but you already pointed, that this is not possible, right??
Trancit
Trancit@Zynewave wrote:
I took a break from the guide today, and implemented a couple of small yet cool features:
MIDI file audition in the browser (this one has been requested many times).
Dragging of MIDI files directly into the timeline of the note editor, to insert the notes from the MIDI file into the current sequence. Holding the Alt key allows you to position the mouse vertically to drop the MIDI file on a specific root note. This can be useful if you have a library of simple MIDI files that for example contains chords or arpeggio patterns. Thus you can drop them on any starting note.
Yeah, you´re my hero!!!! 8)
Trancit
Trancit@LiquidProj3ct wrote:
– SpaceBar should start/stop playback independtly where you’ve the focus.
Yes with only one limitation: to be able to send all keyboard inputs to a plugin (selectable in a menu for example…Reaper does this in a very comfortable way)
Otherwise it would not be possible to enter names containing space for presets in plugins like Kore 2, which doesn´t open a text box for text input…
Trancit
Trancit@German Fafian wrote:
Back from the celebration!!!! 😀
Oddly enough Sytrus does not show any presets in the inspector 😕
Will reinstall it and see if it was something I did wrong during install.
Other than that I might be able to save all presets from within FL as FXB.
I’ll see when I get home tonight.
Thanks 8)
I just installed Sytrus 2.6.8 and all the presets are shown without any problems in the inspectors preset panel…. 😯
Trancit
TrancitThe problem with those two plugins is, that Podium doesn´t recognize preset changes, you make with the internal plugin preset browser…
Load Sytrus in a track, open the preset tab in the inspector and switch through the presets, using the arrow keys beside the “Synth String- Rich Ensemble” window…look at the preset tab in the inspector…there are no changes…
To let Podium recognize the used preset, use the preset tab in the inspector or save a new preset library file, if you had made changes…then Podium will save the correct preset as well…
Same with Drumaxx…
Trancit
TrancitHello Zynewave,
do you know already something new about this mousewhell behaviour???
Trancit
Trancit@Zynewave wrote:
@khaos wrote:
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.
The project was saved with 2.33
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.
If you want to use Podium to mix the individual outputs of Reason, you have indeed to use min. 2 channels per Reason “Instrument”
One to host the midi data to Reason and second for the audio data from Reason and perhaps a third one…
In the Reason standard mapping, only the Mix L/R is a stereo output…3 to 64 are mono outputs…I don´t have Reason installed, so I don´t know, if you can change this mapping in Podium to combine to mono Outputs in one stereo…but I guess, you can do so…
Trancit
Trancit@khaos wrote:
Hmm, for some reason it’s not working for me.
Any chance you can post up a project thats got rewire running? I could then see if I’m doing anything differently.
Matt
Check PM
Trancit
TrancitBefore you can use the “unassigned” ones to sound output, you have to route them in the internal mixer of Kontakt:
1. make the mixer visible
2. add channel
3. “make default” (before the new channel can be routed correctly, you have to reload kontakt)
4. reload the instance of kontakt
5. with the “Conf.” tab at the button of the channel strip you can assign the outputs, you like to use…
In this way you should be able to use all the outs of kontakt…last time I tried, was with kontakt 3…I don´t know, if something has changed since then…
Trancit
TrancitTo use midi for Reason, you have to create a second track…
under “Source” or in the device panel of the inspector there is a midi subfolder under the Reason audio outputs, where you can find all devices, which your actual Reason instance has loaded…
Choose your Thor instance from there and your done…
Don´t know, if there is another way, but this works for me…
Trancit
TrancitCould you consider to implement the midi preview from the browser???
Only sending the midi file data to the selected track…nothing more 8)
Trancit
Trancit@LiquidProj3ct wrote:
IL Plugins and Sylenth1 do work in Podium. The only problem is that those plugins steal the keyboard focus. FL Studio has an option for each plugin to avoid that it had the focus.
You have the same problem in all the host that don’t have this option.
Maybe you could add in device setup an option to force to the plugin to release the focus.
I don´t know, what you do different but for me, neither Sylenth1 nor the ImageLine Plugins react on mousewheel changes, no matter what I do…
In other hosts, I have to click on the knob or move it a little bit (sometimes only hoover over the knob) and am able then to change it´s parameters by mousewheel…no chance in Podium…
Trancit
Trancit@Zynewave wrote:
I don’t know either. I’m not doing anything to filter out mouse wheel messages before they are sent to the plugin window.
Do you know of any plugins that do support mouse wheel in Podium?
some, which work:
Synth 1
Guru
MDrummer 3
Omnisphere
Phoscyon
VSampler 3
Wusikstation
Zebra
@Zynewave wrote:
Do you know any other plugins that supports mouse-wheel in Cubase/FL, but not in Podium? Preferrably a plugin that I can download a demo of.
reFX Nexus 2
Image Line VST(i)`s like Harmless, Sytrus, Drumaxx, Maximus…e.g. with Maximus, even at hosts like energyXT2, you can simply hoover the mouse over the knob to use the mousewheel!!!
Sylenth1
That the ones, which don´t work “only” in Podium…
Hope that helps…
Trancit