Zynewave@pquenin wrote:
Can this work ? because in the podium guide, it says that podium detects mackie compatible control surface : can a virtual midi port be detected as a valid mackie compatible control surface ? If not, maybe it’s easy to have a button that tell Podium that this virtual midi port is a mackie compatible control surface…
Hmm, do you see what I mean ?For my knowledge, can someone explain me why mackie compatible control surfaces are listed in the midi-out in Podium ?
Currently, Podium requires that a connected Mackie device responds to identity requests sent out on a MIDI out port. That’s why you have the Mackie option on the MIDI output port, since Podium will automatically link this to an input port when the Mackie device responds. Not all Mackie emulation devices responds to this identity request, so in a future update I’m going to make an option where you manually can select paired MIDI input/output ports, so that you can use all Mackie emulation devices.
ZynewaveI took a break from the guide today, and implemented a couple of small yet cool features:
MIDI file audition in the browser (this one has been requested many times).
Dragging of MIDI files directly into the timeline of the note editor, to insert the notes from the MIDI file into the current sequence. Holding the Alt key allows you to position the mouse vertically to drop the MIDI file on a specific root note. This can be useful if you have a library of simple MIDI files that for example contains chords or arpeggio patterns. Thus you can drop them on any starting note.
Zynewave@thcilnnahoj wrote:
I found some time to give reformatting (just hope I didn’t mess it up) the preferences chapter a try. Lots of stuff left that I couldn’t explain very well, or not at all. 🙁
Many thanks. The bullet point list is something I plan to use for all chapters that describes UI controls and menus. I see you placed “fixme” next to a few items that already have a description. Is that because you think the text is not clear enough?
If it’s okay, I’d like to have a go at the Loop-Recording and Composite Tracks section, which looks like it needs screenshots as well.
The page is all yours. The current text and screenshots were contributed by Mike G a long time ago, so that’s why the formatting may appear different.
Zynewave@German Fafian wrote:
Ok. No problem.
Any chance to see any of these requests in the future?
😀
Perhaps. But not this year.
Zynewave@thcilnnahoj wrote:
@Zynewave wrote:
Completed a new chapter:
http://www.zynewave.com/wiki/doku.php?id=guide:sliding_zooming
Anyone wants to add screenshots to go with the text in this chapter? (Nudge, nudge. :wink:)
I’ve added two, though I’m not sure if the scrollbar shot is needed. Just remove it if you think it isn’t. I also thought it made more sense to show the navigator & snapshot buttons together in one shot.
Many thanks. 🙂
I originally took a shot of a generic edit toolbar for the toolbars chapter, but since you’ve described the track menu, maybe it should again be updated…
I think it’s ok as it is. I’ved added “Only available in the arrangement editor.” to the track menu button description.
Zynewave@LiquidProj3ct wrote:
Frits, there is an small conflict deleting files from file explorer, if the file is playing (browser preview) and you try to delete it you get the tipical windows error that file is in use. Maybe you can change this behavior in two minutes, stoping the playback once you select ‘Delete’ 🙂
Fixed.
ZynewaveCompleted a new chapter:
http://www.zynewave.com/wiki/doku.php?id=guide:sliding_zooming
Anyone wants to add screenshots to go with the text in this chapter? (Nudge, nudge. :wink:)
ZynewaveI’m guessing the crashes you see are due to low memory. I can see you have 1 GB RAM.
Try opening the Windows Task Manager and check the memory used when you run Podium Free vs FL 4.
From the little I know about Wusikstation, I believe that it is loading all its samples into memory, and don’t use disk streaming. Correct me if I’m wrong.
Could it be that the presets that causes the crashes, uses large samples?
Zynewave@pquenin wrote:
OK. Do you know when midi plugins will be supported ?
I don’t know. I’ve tried giving out time estimates for new features in the past, but these estimates seldom come through. Feature suggestions and discussions on the forum often makes me change the focus of the development.
In the plugins preferences, what is “Enable recording of VST plugin MIDI output” for ?
If you for example have a pattern based drum plugin that supports output of MIDI notes, you can use this option to record the patterns as a note sequence on a Podium track. You can then reuse the pattern on other tracks.
Do you plan to improve the midi controllers support (a tool where we can make and save our own mapping to the Podium functions : transport and mixer) ?
I do plan to extend MIDI controller support, but again, I can’t give you a time estimate.
ZynewaveYou could try placing the 700 MB sound file on a track, use the scalpel tool to split it up in the pieces you want, select all the pieces, and then use the “Convert to Unique Cropped Copy” edit menu command.
If you want to avoid the undo history issue, you could also select the segment you want in the sound editor, and then use the “Export Selection to Sound File” file menu command.
ZynewaveVST midi plugins are not supported yet.
If your MIDI controller supports sending stop/start MIDI real-time messages, then Podium should respond to those. Loop and record mode cannot be controlled with the real-time messages. For that, you’ll need a Mackie Control Universal compatible controller.
ZynewaveThe toolbars chapter rewrite is now done:
http://www.zynewave.com/wiki/doku.php?id=guide:toolbars
I’m currently writing on a couple of new editor chapters with the titles: “Zooming & Sliding” and “Editor Menus”.
Zynewave@LiquidProj3ct wrote:
Getting started–>Mixing–>Last paragraph:
The bus send sliders will control the level of the “wet” signal that is sent to the busses. The gain fader on the track will control the level of the “dry” signal going out of the track.
I think it should be:
the level of the “dry” signal that is sent to the busses
or
the level of the “wet” signal that is come back from the busses
or delete the words “wet” and “dry” and everything will have sense:
@fixed wrote:
he bus send sliders will control the level of the signal that is sent to the busses. The gain fader on the track will control the level of the signal going out of the track.
I did not swap dry/wet by mistake, but I can see why the description can be confusing. I’ve changed the text, and removed dry/wet references.
Zynewave@thcilnnahoj wrote:
If you announce in a post here if you are going to revise a certain chapter, then we could avoid doing double work.
I’ll do that – but maybe a new topic (in the VIP lounge?) would be in order as to not bump an older preview thread. For now, I’ll try to replace all old screenshots I can find.
I think it’s ok to keep posting about guide updates in this topic, until I create a new preview topic.
Thanks for the screenshots 🙂
ZynewaveThe disk activity is because Podium stores the part of the 700mb that you crop away into the undo history. In order to “fix” this, I’ll need to implement a new “maximum storage size used by undo history” setting next to the existing “maximum sequence/sound undo levels” option. This would mean that if you crop away wave data beyond the set maximum size, you would not be able to undo the crop action.
I’m not able to import the full file again from the file browser, everytime I import it I only import the cropped loop (and I cannot slip edit it), but the 700 is there, because I can hear it with browser’s preview
If you try to drag in a sound file that is already imported in the project, the import is skipped. So the sound object that you cropped is still the one used, although it has not been saved to file yet.