Zynewave's Forum Page

@thcilnnahoj wrote:

Here’s my 2 Eurocents:

1. You asked for it! Just a simple mockup for a kind of reverse group track with a thinner group bar, a little like a shadow of the receiving tracks. It’s not unlike Frits’ “ghost play” idea. (With and without “input arrows” – arrows coming from below looks even worse! :lol:)

The biggest downside to this is that there’re as many limits to these specific kind of group/ghost tracks as there are newfound freedoms. Just for example, you can’t have a few tracks from your drum group routed to the same ghost track as tracks from your guitar and synthesizer groups.

2. The other idea I had is this: Like group or composite tracks, you could configure a track to function as a “relay track.” After you set it as such, this track doesn’t feed its output into the normal signal chain anymore, but instead is available as a source or input mapping to other tracks. This mapping remains only as long as the track acts as a relay track, and is removed when the track is deleted or reconfigured. Filtering MIDI notes would probably need two of these in sequence: one to generate, one to filter and a normal track to recieve – assuming you can’t put a MIDI plugin before a track’s input any other way.

With this you can route tracks freely from one end to another – just without cables. And that’s the downside, of course… There’s no visual indication of what flows where. Simply because of this, I think it’s just not a good idea to mix and match real modularity with a linear visual/signal flow like we have in Podium. Bar something like the zGrid, or the routing window in Reaper, which are totally separate from the ‘normal’ view of the tracks. This is after all probably the best way. But really… press TAB and get to see lots of cables dangling? Ohh no, thank you! 😛

For those of us who’ve never used Tracktion, would somebody mind explaining a bit about those racks?

Thanks for the effort. I appreciate it. Maybe it’s just me, but I think offering this kind of functionality will scare many users away. I know I’m scared 😯

Ok, I misunderstood the suggestion of a reverse signal flow.

I can see the logic in your parallel routing (in addition to the current serial routing), but I can’t see a simple way to incorporate this in the current hierarchic track display. It would be helpful if someone can produce a screenshot mock-up of how this should be laid out in the inspector, tracks region and mixer.

@Podianer wrote:

Hi Frits,

Long time no see.. I hope you are doing well! As Sam I was absent from the forum for a while. Today I took a look at the new version of Podium and I must admit, you really really nailed it this time. The ui changes are beautiful! New releases are always interesting to look at, but gui changes are the most fun part to discover and explore.. 🙂 Podium really looks polished now.. This inspires me and now I want to record something in Podium… Again: Thank you Frits!!

*off-grabbing-my-guitar* 8)

Hi Podianer,

Thanks, and good to hear from you again. I hope you stick around. There are still more UI improvements to come. 8)

@MelodyMan wrote:

I have another question. Is there a way to copy a track with just the effect rack and not the audio-events on it?

Another method that does not involve track templates:

Select the track you want to copy. Select “Track/Clipboard/Copy Track” (Ctrl+C). Select the destination track. Select “Track/Clipboard/Replace Effect Chain” (Ctrl+Shift+V).

Hi Ron,

When you record or import SysEx data from midi files, these SysEx messages are stored on the timeline in stream events. As you have discovered, there are currently no way you can edit the contents of the SysEx messages. What the other users are suggesting relate to parameter objects, which can be configured to encode value changes within SysEx messages.

Can you describe what kind of SysEx messages you are trying to edit? If it is a short message for editing a parameter in your synth, then it may be worthwhile to create a SysEx parameter object. Once you have defined that parameter object, it will allow you to automate the parameter on a curve track, without worrying about the SysEx message format.

Frits

@Mike G wrote:

-Either an option for bounced tracks to unload their plugins.

If I understand you correctly, you just need to activate the “unload plugins when bounce” option in the bounce submenu. If your halion player tracks are bounced, then the plugin should never be loaded until you unbounce.