Zynewave.
kingtubbyThanks – but I can’t even see the cpu meter 😳
Better check that out hadn’t I !
I should qualify my previous post in that my Podium setup is a little different from the default. Your best bet is to load the ‘default setup’
Go to menu selection ‘setup’ and choose ‘load default setup’. If you do this then you’ll find the midi monitor and cpu meter at the bottom right of the screen.
Mart
ZynewaveIncidently, I’ve noticed that scrolling in the browser of the project window (on left side) is sometimes a bit erratic – the scroll flickers / oscillates and the list flicks back to the top.
Could you describe how you provoke this behaviour. Are you dragging the slider, clicking the arrow buttons, pressing arrow keys or using mousewheel?
ZynewaveAnyway, I have the Yamaha standalone AN editor, which outputs sysex to Yoke 1 (and this is confirmed at the midi out monitor of Midi Ox). This should therefore presumably enter Podium and be passed to the plugstation ?
It is received by Podium, and can be recorded, but it is not echoed thru to the output device. I just revisited my code, and found this comment:
If an instrument is set to ‘local off’ this does not include sysex parameter changes and dumps. Echoing back sysex parameters/dumps will yield unexepected behaviour on the instrument.
I remember trying it with my AN1x, set to local off. I created a MIDI input mapping for the AN1x, which I could use to play softsynths but also play the AN1x when assigned to a track with the AN1x output mapping. The problem was that, even though the device was set to local off, adjusting some parameters with the dials on the front panel would both change the parameter on the synth and send out SysEx. When Podium receives these messages, it would send them back causing the parameter to flicker on the AN1x. I even managed to crash the AN1x in this way. So that is why I disabled SysEx thru. Are there any other way you can set up your MIDI routings so that the AN editor sends directly to the card?
swayzak@Zynewave wrote:
Anyway, I have the Yamaha standalone AN editor, which outputs sysex to Yoke 1 (and this is confirmed at the midi out monitor of Midi Ox). This should therefore presumably enter Podium and be passed to the plugstation ?
It is received by Podium, and can be recorded, but it is not echoed thru to the output device. I just revisited my code, and found this comment:
If an instrument is set to ‘local off’ this does not include sysex parameter changes and dumps. Echoing back sysex parameters/dumps will yield unexepected behaviour on the instrument.
I remember trying it with my AN1x, set to local off. I created a MIDI input mapping for the AN1x, which I could use to play softsynths but also play the AN1x when assigned to a track with the AN1x output mapping. The problem was that, even though the device was set to local off, adjusting some parameters with the dials on the front panel would both change the parameter on the synth and send out SysEx. When Podium receives these messages, it would send them back causing the parameter to flicker on the AN1x. I even managed to crash the AN1x in this way. So that is why I disabled SysEx thru. Are there any other way you can set up your MIDI routings so that the AN editor sends directly to the card?
Yes, easily. I just wanted to record them in the sequencer (like I can do in Cubase).
Would this be possible in Podium – Cubase records them as automation events which can be edited in the sysex editor.
It would be very desirable (at least for a rampant sw1000 / plg user !) because so many of the cards’ deep parameters are only available through sysex.
swayzak@Zynewave wrote:
Incidently, I’ve noticed that scrolling in the browser of the project window (on left side) is sometimes a bit erratic – the scroll flickers / oscillates and the list flicks back to the top.
Could you describe how you provoke this behaviour. Are you dragging the slider, clicking the arrow buttons, pressing arrow keys or using mousewheel?
Dragging the slider – it seems as though the slider “wants” to spring back. Weird….
PS The “cheque is in the post”… 😉
ZynewaveYes, easily. I just wanted to record them in the sequencer (like I can do in Cubase).
Would this be possible in Podium – Cubase records them as automation events which can be edited in the sysex editor.
It would be very desirable (at least for a rampant sw1000 / plg user !) because so many of the cards’ deep parameters are only available through sysex.
If you are recording a MIDI input onto a track with one of the SW1000 mappings, then Podium will try to match any incoming MIDI CC, NRPN, SysEx etc. to the parameter objects defined for the SW1000. If a matching parameter is found, then a track will be created with this parameter, and curve sequences will be recorded. If the parameter properties specifies that the parameter should not be recorded as curve sequences, then single parameter events are created on a new track. If a SysEx message is received that was not matched to a parameter, then single stream events will be created on a new track.
Zynewave@swayzak wrote:
@Zynewave wrote:
Incidently, I’ve noticed that scrolling in the browser of the project window (on left side) is sometimes a bit erratic – the scroll flickers / oscillates and the list flicks back to the top.
Could you describe how you provoke this behaviour. Are you dragging the slider, clicking the arrow buttons, pressing arrow keys or using mousewheel?
Dragging the slider – it seems as though the slider “wants” to spring back. Weird….
The only way I managed to provoke this, is if I use cursor navigation keys while dragging the slider. Moving the list caret with the keys will scroll the list if the caret is outside the visible area. Could this be what you observed?
PS The “cheque is in the post”… 😉
Got it, thanks 🙂 You’re now a VIP.
swayzak@Zynewave wrote:
Yes, easily. I just wanted to record them in the sequencer (like I can do in Cubase).
Would this be possible in Podium – Cubase records them as automation events which can be edited in the sysex editor.
It would be very desirable (at least for a rampant sw1000 / plg user !) because so many of the cards’ deep parameters are only available through sysex.
If you are recording a MIDI input onto a track with one of the SW1000 mappings, then Podium will try to match any incoming MIDI CC, NRPN, SysEx etc. to the parameter objects defined for the SW1000. If a matching parameter is found, then a track will be created with this parameter, and curve sequences will be recorded. If the parameter properties specifies that the parameter should not be recorded as curve sequences, then single parameter events are created on a new track. If a SysEx message is received that was not matched to a parameter, then single stream events will be created on a new track.
So if I want to record sysex stuff live into Podium AND hear it’s effects on the plg cards at the same time, then I have to route the output of the standalone editor to both the plg and Podium simultaneously ?
ZynewaveSo if I want to record sysex stuff live into Podium AND hear it’s effects on the plg cards at the same time, then I have to route the output of the standalone editor to both the plg and Podium simultaneously ?
Yes. If that is a problem, I’ll have to add a ‘SysEx thru’ option, either in the Podium preferences, or in the device mapping properties.