Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterAdded ‘Draggable inspector panels so more than one panel can be open.’ to the list.
ZynewaveKeymasterAdded ‘Advanced quantize edit dialog with percentage settings etc.’ to the list.
ZynewaveKeymasteri mean the list that opens in the right of the screen, you know, the file browser, where you can hit enter and play files from hdd (view menu->new list window, ctrl+L, or the List button near the help button)
You can’t change the audition volume in the lists. They are played straight through to the soundcard output.
ZynewaveKeymaster1. ok, i understand, i agree with you on this now. But B buton does not offline bouncing (offline bounce = ctrl+b), it just switches between already bounced track and the the unbounced ones.
You need to hold the control key and click on the B button to do the bounce rendering. Toggling the B button can be used to compare a previous bounce render with edits you made on the track.
2. i always use the same midi ins/outs and audio ins/outs, so why should i tell podium each time this thing?
You can create a default project file with a basic studio setup, which will be loaded when you select the ‘new project’ menu. This is explained in the project wizard.
3. what are those checkboxes for tempo and time signature for?
With those you can select whether a tempo event sets a new tempo, a new time signature, or both.
4. how can i set the volume of files played in the list? and what its audio path ? (i cant see it in the mixer)
You use the gain dial to control the output of the track. Support for setting a volume curve on each sound event on the tracks is coming in a future update.
but the bounce audio event does not extend automaticaly so it does not bounce the new added samples too until i manualy resize the bounce track audio event.
Is this the desired behaviour for a bounce track?That is the intended behaviour, as it was originally designed. After I recently added bounce rendering, I’m considering changing this, so that bouncing automatically creates the sound events, like when you record audio inputs.
If for bouncing i need a specialy created bounce track, then why there is an option for each track to make it bounceable ? Or in reverse order, if any track can be bounceable why there is a “Wrap in a new bounce track” option?
The ‘wrap in new bounce track’ is just a shortcut. It does the same as the ‘wrap in new group track’ and then enabling the bounce mode in the group track properties.
ZynewaveKeymasterHi Juanito. Thanks for your input.
it doesn’t make any sense to me that a huge battery of commands are not there to see when I right click on an object weather it be a midi or an audio track, Bus or a group
Do you have some examples of what commands you are missing?
Please implement all editing functions within podium through the use of the right mouse button and middle scroll wheel
The mouse wheel currently is used for scrolling and zooming (using the zoom tool key shortcuts). I intend to add an option for using mouse wheel to edit value dials and mixer sliders.
ZynewaveKeymasteri have 4 tracks (ch 1/2,3/4,5/6,7/8 of multichannel vsampler 3.5) grouped under a master track in podium, in a new clean. When i draw a 4 bar wave with the pencil into the master track and i hit ctrl+b podium crashes.
Could you email me the project file as it is just before the crash?
Change the word “bounce” to “freeze” and add a freeze button on each track (that do exactly what ctrl+b does)
If you have set up a bounce track, then the freeze button is there in the disguise of the ‘B’ button. I think the word ‘bounce’ is a better description than ‘freeze’, considering that bounce tracks can be used with hardware devices and realtime recording too. But maybe other users have some input on this?
ZynewaveKeymasterI cant find how to do that , where are these commands?
If you right click on the header of a track with a plugin mapping, they are in the ‘plugin preset’ submenu. You can also find the menus in the track inspector preset panel, by clicking on the arrow button at the right edge of the preset page header.
ZynewaveKeymasterThe best essay I ever read on unicode was…
I read that article a few weeks ago. If only all tech articles could be this entertaining.
Localization of Podium is on the list. It will be a big task to implement, but it will become important when Podium gains a bigger crowd.
ZynewaveKeymasterThanks.
ZynewaveKeymasterAny clues as to what you are working on?
I’ve finally managed to do some work on the Podium guide, so that will be the next release, along with minor changes to the editors.
ZynewaveKeymasterDid you still have arrangement monitoring turned on? When you close Podium, it will check the current settings of any loaded plugins and if the presets differ from the last retrieved synced preset (which were retrieved when you saved), then the project is marked as edited. Some plugins return different settings every time a host retrieves the settings, even if you have not changed anything in the plugin editor.
ZynewaveKeymasterI have no timeframe for this feature. I’ve got the list full of fun stuff for at least a couple of months.
ZynewaveKeymaster@Joachim wrote:
I do a “File->Save Project” in the browser window,
yet still Podium asks me to save changes when I shut it down. ❓/Joachim
After saving and before quitting, did you enter the arrangement editor? The 1.49 release introduced saving of the track focus, so if you move the track focus in the arrangement editor, the project is marked as edited.
ZynewaveKeymaster@Max wrote:
Current Podium behavoir is clicking and dragging everywhere in track inspector changes hierarchy level of the track. No problem to interrupt operation or undo, but unwanted change of hierarchy level occurs casually too often for me. Maybe should be better to use only strip at the left side of track inspector for dragging? That’s VERY annoying 🙁
This also happens to me too often. I’ll see if I can improve this for the next release.
ZynewaveKeymasterIs this the way it’s supposed to be, or am I doing something wrong?
If I understood your setup correctly, it is behaving as designed. I can verify it if you email me a minimal project file with just the synth mappings and the track setup.
I assume your nord rack mapping is configured as both MIDI input and output, and your keyboards are mapped as generic MIDI inputs. When you assign the MIDI input mapping to the nord track, this will override the input functionality of the nord mapping. If this is the problem, I need to check the code to see if it is possible to enable MIDI input both from the dedicated MIDI input mapping and the synth mapping.