aMUSEdSeems a lot darker on my system – I can barely make out the graphic. Maybe it’s my contrast settings then. I seem to remember it having a cooler grey one though at one time.
aMUSEdIndeed – thankyou
aMUSEd@swindus wrote:
@aMUSEd wrote:
@swindus wrote:
MIDI control change != VST automation
You can record midi controller messages like VST automation. Have a look here:
http://www.zynewave.com/forum/viewtopic.php?p=12407#12407
You need to create the cc message first then it works. Would be better if Podium creates a parameter track on incoming cc messages in record mode automatically.And there is no mapping between controller messages and VST automation. So a knob controlled by cc messages does not create a VST automation sequence. I think that is what aMUSEd is talking about.
Oh right – I don’t really understand why if I move it with a mouse it’s VST automation but if I move it with hardware it’s treated so differently. Ideally I’d prefer to use hardware to tweak knobs where possible (many plugins do have built in midi learn on knobs)
Because MIDI is MIDI and VST automation is VST automation. They are simply two different things. You don’t need a MIDI cable for VST automation and VST automation works without any MIDI devices/setups.
Sure I get the theory – but in practice if I move a knob I would like the host to record it and draw an envelope – I know why there is a difference but I don’t see why it should make a practical difference in terms of the end result. It’s still moving a knob. My other hosts do not seem to make this distinction in practice – for example if I move a knob with my mouse or with my controller in Live the end result is still an automation lane and envelope. As a musician I’m not interested in the technical details I’m afraid, I just want it to work.
aMUSEd@swindus wrote:
MIDI control change != VST automation
You can record midi controller messages like VST automation. Have a look here:
http://www.zynewave.com/forum/viewtopic.php?p=12407#12407
You need to create the cc message first then it works. Would be better if Podium creates a parameter track on incoming cc messages in record mode automatically.And there is no mapping between controller messages and VST automation. So a knob controlled by cc messages does not create a VST automation sequence. I think that is what aMUSEd is talking about.
Oh right – I don’t really understand why if I move it with a mouse it’s VST automation but if I move it with hardware it’s treated so differently. Ideally I’d prefer to use hardware to tweak knobs where possible (many plugins do have built in midi learn on knobs)
aMUSEd@Zynewave wrote:
@Zynewave wrote:
@LiquidProj3ct wrote:
The last stretch of the curve hasn’t slope in sequencer. Curve editor snap is 1/16, while sequencer snap is set to 1/1.
It’s not a bug, but perhaps a bit confusing. It’s because the snapped point at bar 2 is actually beyond the end of the curve sequence event. When the end of a sequence/sound event is snapped at bar 2, it will stop playing events/audio just before the bar 2 start.
Maybe I should change this behaviour for track automation curves, and actually include point events snapped on the end of curve sequence events?
There is a new beta5 where point events snapped on the sequence end is included in the track curve.
Beta5 also has a new “transform to grid aligned points” command in the curve editor. The old “digitize spline curve” is renamed to “transform points to spline curve”. Next I’m going to add a “transform spline curve to lines” command.
This is a good idea. I would repeat an earlier request to make it possible to choose an envelope type as an option before recording (in preferences or maybe a rightclick option as in Reaper) rather than converting it afterwards. Most of the material I make involves fairly smooth transitions so I tend to convert lots to splines anyway so it would be useful to just set it to splines unless I’m doing something that involves sharp transitions in which case I would keep it as it is (or would lines be better?)
aMUSEdApart from that (and still getting the divide by zero crashes occasionally at first run of the programme) Podium finally is working for me with regards to recording my playing with plugins faithfully. That is very pleasing and it moves Podium from something I try occasionally to see how it’s progressing to something I can consider using as my main host (although after this some attention to project management would be greatly appreciated). Thanks for this Fritz 🙂
aMUSEdJust experimenting some more with the automation – how come it records fine if I use the mouse to move a knob or slider but if I use midi learn to assign it to a hardware controller it ignores it?
aMUSEdSorry I’ve only had a brief opportunity to test this so far. Busy with other things. It seemed to work OK – didn’t need to insert a marker to make it record properly this time and no reversions to zero but I’ll try and test some more if I get a chance this weekend.
aMUSEd@Zynewave wrote:
Personally I’m quite happy with not having to worry about saving individual arrangements, and all the related pit falls with lost changes and unintentionally overwritten arrangement files, etc.
Seems to me the current system is full of these pitfalls as this is just what has happened to me. I had a default arrangement, changed the plugin loaded and recorded some tracks, then, in order not to overwrite the starting point arrangement I saved it as a new project thinking this would leave the old project intact. However I now try and open the saved new project but it’s lost all my edits and it’s just a copy of the original one.
Also its so confusing that if I save say a copy of “VSTi Project 1” as “VSTi Project 4” it still appears as “VSTi project 1” when I open it in the project menu.
aMUSEdStill struggling with this approach to saving iterations. Just had a nice arrangement and saved it as a new project (since there is no “save as” for arrangements) but now I can’t find it – it’s just gone 🙁 The logic of this system eludes me – it all feels so back to front
aMUSEd4. Additional Automation types Touch, Latch…(more info on these in the Cubase link above Page 191 onwards).
Not sure about this. One of the things I always liked about Podium’s approach to automation was that when you click record it records all you play including knob tweaks – no having to decide type of automation wanted or setting up of params to record in advance which really kills the creative juices for me. The last thing I would want would be to lose that and be given an array of confusing automation options and types like in some apps (Reaper was terrible for this for a while). All I really want is for it to record those knob tweaks etc more faithfully than it currently does.
aMUSEdAwesome – you will have my eternal gratitude if you can get this working right
aMUSEdAbsolutely. No rush as such but I would like to see this prioritised. The fact is there are many features Podium doesn’t have yet and I’m sure they will add much to it, but this is one of the few things Podium already has but that doesn’t work properly and as such really should be attended to before moving onto other things.
aMUSEdIs this going to be fixed yet?
aMUSEdI was going to say it had the same error message as my crash so that might be it