@maximilians wrote:
harmless rules I love the sound of it , organic crystaline beauty 8)
I got a lot of good deals this year with all the group buys but the Harmless purchase was probably the best of the bunch…
From the OP:
@Mike G wrote:
…Uses for splitting MIDI…
1 – You could use it to have one midi input drive many “stacked” synths.
Is it possible in Podium to have the app be aware of which vsti’s/vst’s, (in use on the tracks) output midi and just add that group of instruments to the possible inputs at the track level?
@Zynewave wrote:
The problem should be apparent with 2 tracks, each with different effect processing, and each track feeding into each other post effects.
Checked it out this morning and you are correct. However, this only occurred when feeding a track back onto itself. As long as the audio from each was feeding the master only it seems to be ok.
Thanksfor the help, I guess a little bit of “rtfm” would have helped here 🙂
btw, I should mention that this is not expected behavior. I think most windows users would expect drag & drop functionality. Not a showstopper at all mind you, just unexpected.
@koalaboy wrote:
Something like this would be great:
I’m not sure how I missed this suggestion first time around.
Big +1 from me as well.
Merry Christmas to you and yours as well!
Thanks for the replies. I think the issue is really in my head more than anything else. See what you can’t see in that picture is that I had already selected an input for the track. In my way of thinking (which is often times confusing even for me) the input IS the source. Anything after that just affects the source. So, once you have a device (hardware input) that can generate audio, anything else in the chain afterwards is in essence an effect. However this would not apply to midi so I see where I erred in thinking (or not thinking).
But you are both correct, I see where I am mistaken. It comes from heavy use of other hosts where the same filtering of options is involved its just presented a bit different. If I had given it even an ounce of thought it would have occurred to me that an input device is still needed separate from the sound generator on a track. Sorry 😳
I gotta stop posting here when I’m sleepy…
And thcilnnahoj, you were so correct in the other thread by stating that I need to use the app more. If I did I wouldn’t have these small hurdles…
@LiquidProj3ct wrote:
You must reduce inspector width to the minimun.
FWIW, I was able to replicate this issue pretty easily. I added a bunch of parameters and then did a drag on the side of the window to make the inspector smaller. It happens right at the end of the drag operation.
@sam c wrote:
@thcilnnahoj wrote:
Another bug to report:
If you change the focus track with the keyboard (arrow keys or page up/down) while simultaneously adjusting any slider/dial in the rack, this slider will become stuck if the cursor lands someplace other than another slider! After this happens, it crashes when you try to load a different project.Link to GIF animation (500 KB)
Another way to provoke it is to simply switch over to the default editor or mixer profile while adjusting a slider on the tracks in the arrangement view. I haven’t been able to get a slider/fader stuck like this in the mixer yet.
Johan, you are an animal!
Now that’s an understatement!
@Zynewave wrote:
Thanks. A follow-up question:
What happens if you try to create a feedback routing? I.e. you route the output of track1 to track2, and then either track2 to track1, or track2 to track3 and track3 to track1, etc.
If that is possible in either of the hosts, what do they do about latency compensation? I would guess they at least introduce one full buffer latency (varying with the selected ASIO buffer size) to a track that feeds back into a track that already has been processed.
Just got home and gave it a shot and here’s what happened in live…
Fritz, I’m heading out the door to work but I will answer that one tonight when I get home 🙂