No bypass mode currently.
I will extend the mapping bypass button (on the plan), to also bypass any parameter assignments.
Until I implement the bypass mode, you can remove the parameter assignment from the track and then undo/redo to audition the difference.
You insert tempo and timesig events by clicking with the pencil tool in the two lanes above the track area.
Drag and drop a wav file onto Podium or use the import media menu. This will create a sound object. When in the arrangement editor, open an object list (Ctrl+L) locate the sound object and drag it onto a track. Drag and drop of wav and mid files directly onto tracks are on the plan.
Frits
I’m not sure if I understand it. Do you mean it gets confusing when the midi input track is part of other tracks where the real midi data is recorded?
Yes, I think that is what I mean 🙂
In the context of what i mentioned above I tried it this way because it’s indeed the global behaviour of Podium, but also because I was trying to control two different tracks at the same time. By placing the midi input channel to connect both of them.
So, am I assuming correct that the two track tracks you want to record with one MIDI input is the track you assigned the input to (which have no output mapping assigned) and the parent track with an output mapping? What would you expect would be the outcome of recording MIDI with this setup? Maybe you could send me the project file so I could get a clearer picture of what you want to achieve.
I was sure that before when I highlighted an object and pressed the sticky button in the toolbar it was attached. If I press that button it only opens the one I attached to device folder.
Hmm, the Properties and the Stickie note buttons at the top of the browser has always been shortcuts for the current page object, and not any selected objects inside the page object. So this new behaviour you have observed is the way I intended it to work. The stickie note bugs I recently fixed should have no effect on this.
could you add a box (accessible by right mouse or a kb key) with editing tools (with move,write …) or a way faster for accessing editing tools ?
I can easily put the tools in the context menu accessed with right mouse button inside the editor area. Would that be a good idea? I prefer not to make a popup tool selector window like the one in Cubase. When I get around to implementing configurable key shortcuts you will be able to assign keys to the tools.
and i think it would be useful to put a peak indicator in mixer view on audio/vst tracks
Currently the entire meter strip turns red when >0 dB occurs. When the meter goes below 0 dB the red color will slowly fade away. What specifically would you like to see indicated?
@nproject wrote:
Quote:
– objects in arrangement window can be reduced/enlarged by mouse on left/right (like in cubase)There already is a minimize/restore button (the rightmost button in the track header) and you can zoom the height of an individual track by using the zoom tool and drag up/down on the track header. Did you have something else in mind?
i meant the audio or midi objects (containers with events in them) (in the right arrangement panel) not the tracks (on the left)
Oh, you mean resizing the events horizontally. Currently you can do that by pressing the control key and clicking on either end of the sequence/audio event and then drag. Corner drag handles like the ones you have in Cubase are on the plan.
Another explanation could be if you’re using demoversions of some plugins. These are often save-disabled meaning that Podium will get an empty response when it requests the preset data from the plugin.
Just ignore the instructions above on how to manually set up a multitimbral VSTi. The latest 0.92 release has a button in the Wizard that does all this automatically.
I think it may be a bug. I will look into it. Until then you will have to rename the presets in the plugin editor (if the plugin editor supports this). This way Podium will update the name of the library preset the next time the preset is stored in Podium.
Creating library presets for effects is possible. It should work just like with VSTi plugins. What effect plugins are you trying with?
Note that if you’re using insert plugins, these are only loaded when the arrangement monitoring is active (the lower left power button). When monitoring is not active, the preset menus are not available since the insert plugin itself is not loaded.
Could you go the Report page in the Interfaces dialog and create a report and email it to me? That way I may know a little more about the Tascam driver.
Frits
Hi,
– instead of rotary control in mixer view you could use sliders
I will add this to the list.
– a button for bypassing plugins
Already on the list. But I will put a higher priority on it. Many have asked about this.
a transport bar in audio editor
There are two sound editor profiles in the default setup. If you open a sound from within an arrangement, there is no transport bar in the new window, as the sound is linked to the arrangement transport bar. If you enter a sound from the browser page, you will get a sound editor with a transport bar. If you desire a transport bar in the window opened from within the arrangement, you can insert it yourself by opening the Profile Properties dialog in the View menu. You should then insert a new toolbar region at the bottom of the list.
– objects in arrangement window can be reduced/enlarged by mouse on left/right (like in cubase)
There already is a minimize/restore button (the rightmost button in the track header) and you can zoom the height of an individual track by using the zoom tool and drag up/down on the track header. Did you have something else in mind?
– in piano roll view there’s no indication on what you’re editing : you could add an info box with position length note and velocity for example – and the keyboard is inactive
Already on the list. When you say keyboard I assume you mean the on screen piano roll in the editor. Clicking on this will select all events on that key. Note audition is on the plan.
– in piano roll too you could add the possibility to edit multiple notes (length,heigth,velocity) at a time by selecting the one you want
So if several events are selected then dragging the length of one of the events would change the length of the other events?
i wish i was clear enough
I think I understood you ok. 🙂
Frits
Hi,
I think it would make sense that you could assign the same midi input mapping to all the tracks you want. but to make it active with a switch if you want to play/control it. Instead of having to drag or replace the input mapping the the track you want to play.
This would require that when you’re dragging the input mapping you can use e.g. control key to drop a ‘duplicate’ assignment of the mapping. Furthermore it would require that I implement the input mapping on/off button (which is on the plan). When you want to change MIDI input to another track you would need to switch the mapping on the current track off and switch it on on the new track. A lot of work and a lot of things that can go wrong or be confusing. I have another suggestion:
I could implement a global input mapping mechanism. In the input panel list in the track inspector you would have an ‘Assign as global’ menu in the list popup menu. This would set a single MIDI input mapping as global indicated e.g. by a red pinhead image in the list. Whenever you select a track and this track does not have an input mapping assigned already, then the global mapping would be in effect. This could in theory be used with audio inputs as well (e.g. a microphone input), but unwary track selections could have more drastic consequences such as loud overload or disturbing ongoing bounce recordings etc. Let me know what you think of this idea.
Also I tried to assign a midi mapping to a track to control a parent track (with a VSTi) but that doesn’t seem to work. I have to assign the midi input mapping on the VSTi track itself: is it intended that way? I assumed that in the concept of podium also midi would behave like the audio routings >> like a tree.
It is sort of intended, but you’re right that one would expect that the MIDI input is flowing up to the VSTi track. The reason I have chosen that it must be assigned to the VSTi track, is that if you start recording the MIDI input it may result in the creation of new note or parameter sub tracks under the VSTi track. I thought it would be confusing that if the input was on a subtrack then recording could create tracks in a sibling branch of the tree.
I will consider your global parameter suggestions.
Stickies are working fine here with 0.91 on all object types. As I wrote in the release note they have been inoperational in 0.90. I need more details of how you observe this bug?
Frits
Import plugins is pretty smooth, however I would request an option to import an entire directory and its subdirectories, since all of my VSTi’s are organized into directories (so that they’ll be more organized in Steinberg products).
I have just added it to the future plan.
I’m not sure why I wouldn’t want to create a master track without bounce, all projects need to go to a mixdown wave sooner or later (I think?).
Some users may want to work with MIDI devices only.
Clicked Map. Chose Hypersonic 1+2. A red exclamation mark showed up. An error message about missing parent track mappings to handle audio which means nothing to me right now…
Ok, the problem is that your new track is on the same level as the master output. Use the ‘increase group level’ menu to make it feed into the master track. The master track should always be the topmost track. I just noticed there is a bug when clicking the ‘Insert new track’ menu in the area below the tracks. It does not insert the track at the bottom but rather before the currently selected track. Will fix this. I will also implement that the default group level for new tracks will be set so they are feeding to the master track.
Went back to Map and right-clicked Hypersonic to get the properties. Clicked Device is an instrument. Clicked Stereo from source and traget channels drop-downs.
It should not be necessary to go into the properties for the device mappings. These are for configuring the setup of the plugin/external device, and they should be set automatically by the import. If not set correctly, it’s likely to be a bug in Podium (with the exception of buggy plugins that supplies wrong info to Podium).
I hope that “user case scenario” helped you a bit
Great help! Thanks
Frits
Also:
What display resolution are you running at? What brand of graphics-card and how much video memory do you have?
The black screen can be the result of not enough available video memory. I’ll implement a warning pop-up dialog in Podium when allocation of video memory failed. This will help sort out if this is the problem on your system.
Frits