ZynewaveHi Stefan,
Welcome to the forum. You are now assigned to the VIP member group.
Frits
Zynewaveonly as an optional feature because I like the minimal amount of real estate the current faders take.
But the faders will need more space than the dials. Or are you saying you want the faders next to the meters? This will make the channel strips wider, and it will not fit well with the existing parameter automation strips. The gain setting cannot be automated (you need to use the level parameter for that) so I think it would be confusing to place the gain setting as a fader in the same place as normal parameter faders.
ZynewaveI have thought about adding an “export” command to the file menu in the sound editor. This would then bring up a dialog where you can select the format of the file such as wav or mp3. For wav files there would be further options for setting bit depth and dither.
ZynewavePlease, do you have any idea, when we will be able to drag directly to a place on a certain track?
It’s on the list, but right now I’m committed to extending the audio features. Let’s talk about this again after SRC, time-stretching etc. has been implemented.
ZynewaveHow do you picture this would be implemented then? Should the option be to replace the gain dial row with a taller row containing faders?
ZynewaveIt’s a full 1.74 version without zReverb. It has the basic fade functionality but not the latest improvements (scalable waveform, crossfade etc.).
I assume the second workshop is in the mag. Could you give some details about what the topic is this time? The Beat editors have done this entirely on their own, so I have no idea what they are up to.
Zynewaveso, the start points of the individual notes will be scaled too?
Yes.
ZynewaveWhen you resize a sequence event the note events will not scale accordingly. I am planning to support this though, when I start implementing time-stretching of sound events. I’m considering putting an alternative pair of drag handles halfway up the event sides. Dragging these handles instead of the bottom pair of handles will then scale the contents of the clip.
ZynewaveHow about an option maybe that automatically disables track bouncing after an event has been bounced on a bounce enabled track, this would then re – enable fades, crossfades e.t.c on that clip without the need to drag the event to another new track just to use fades?
This will conflict with the way bounce track works. If you disable the bounce feature of the track, then both the sound events on the bounce track and all the child tracks will play simultaneously.
The primary purpose of bounce tracks is to be able to create an exact rendering of the child tracks (hence the disabled fade properties) and then be able to switch back to the child tracks to make modifications and redo the render. If you want to use the rendered sound events as a regular clip, then the recommended procedure is to move it to a regular audio track.
ZynewaveWhen working on an instrument track for instance I will wrap it in a bounce enabled track. Of course the midi is then converted to audio. Fine so far.. but when I try and apply any fades to the audio clip they are simply not available.
This is on purpose. If it was possible to set gain or fades on bounce track events, it would mean that playback of the bounce recorded track would not be identical to the unbounced playback. So the fade properties of a sound event are disabled when placed on a bounce track.
ZynewaveZynewaveThanks for the file. I found the bug and I’ll fix it for the next 1.77 release. The crash happens when you scroll the event you clicked on off the screen.
ZynewaveI think it just might!
Good. I’ve already made the modifications. Podium 1.76 is just released.
Hints:
Locate your MIDI input mapping in the devices panel on the project start page. Right-click and use the “New copy…” command. Give it a proper name and press OK. You now have two MIDI inputs in the track inspector input panel. Assign one on the track with NuBiPlus and the other on the track with Spinner. I hope that works.
ZynewaveZynewaveI guess what you are looking for is a way to assign the same MIDI input (your keyboard) to both NuBiPlus and Spinner. Podium restricts a MIDI input object to only be assigned on one track, to avoid confusion, and to make it easy to drag the mapping from track to track without having to unassign it from the old track. A solution for you would be to create a second MIDI input object mapped to the same MIDI input. You can then assign MIDI1 to Spinner and MIDI2 to NuBiPlus. In effect you duplicate the MIDI input from your keyboard into the two MIDI input objects. As a consequence, both Spinner and NuBiPlus receives the notes and CC#1 messages. This may be undesirable if NuBiPlus reacts to CC#1 or Spinner reacts to note messages.
Will this setup do what you want to achieve?
Currently Podium does not allow two MIDI input objects mapped to the same MIDI input, but I can remove this restriction.