ZynewaveHi eyeknow,
If it is audio inputs you are recording, you can mute the track, which will cut off the audio output of the track. If this is inconvenient (because muting will disable any subtracks and plugins in the track tree) then alternatively you can turn the gain dial all the way down to ‘off’ during recording.
Frits
Zynewave“Mute/Solo for individual drum presets in the drum kit.” is now added to the plan. I think the way to do it would be to make the mute/solo state part of the drum preset object. This means that all places where the drum kit preset is assigned to tracks, the mute/solo states would be effective.
ZynewaveOooh 😳 You’ve found a bug.
Selecting the ‘clone phantom…’ command, does not give the new unique sound a new file name, as it should. If you check the properties for your sound objects, you will probably find that they share the same file name. And thus each sound will save on top of the other sound.
Good one Gabriel! Fix will be in next release for the coming weekend.
ZynewaveHi,
After the next release, I’m going to improve on the file handling. Automatic placement of sounds in arrangement folders etc.
but what kept happening is my edits would get all screwwed up the next time I opened the project.
Can you tell me what I might have been doing wrong here?
Could you be more specific about how it is ‘screwed up’?
ZynewaveSo do you want to be able to switch the samplerate of the arrangement between e.g. 96 and 48, when recording final bounces, versus when just working with the arrangement?
Or are you talking about being able to import e.g. 44.1 loop files into an 48 arrangement, and have the loops sample rate converted to 48 during playback?
Sample rate conversion and dithering are a big task. I will need to spend a couple of weeks on this, to ensure that the quality of the algorithms are good. Currently I am concentrating on getting the Podium guide up to date, so I am not going to start on big features for a month or two.
ZynewaveI’ve tried your exact steps, using Podium 1.26 and eXT 1.2.9. I could not cause a crash. I’m using eXT in demo mode of course, so maybe that has an influence. Could you email me a minimal project file with your arrangement? Could be other things such as tempo or sample rate, that are causing the crash.
Is it the Podium dialog with plugin ‘illegal action’ and instruction to save your project and restart, that pops up when you experience the crash?
ZynewaveUnless there is a better way to do it?
No, that’s pretty much exactly what the ‘send input thru to output interface’ option was for 8)
I can see that the device mapping description in the guide was made using an older version which does not have this option. For the last couple of weeks I have been working on the guide again and will update this at some point.
ZynewaveHave you cleared the ‘send input thru to output interface’ option in the device mapping?
ZynewaveMaybe 7/9 as an alternative to Q/W and 4/6 to move the cursor freely left and right
I’ve now implemented this, but it will require that the ‘num lock’ key is activated. Otherwise the numeric keypad will work as key focus navigation as usual.
Zynewaveseems that this isn’t present in the future roadmap?
Just an oversight. “Map MIDI control change messages to VST parameters.” is now added to the list. Thanks.
ZynewaveHow about using the D and F keys to step back and forward between the tools that are available in the editor toolbar? Shift+D/F could then step the quantize value, and C could toggle quantize on/off.
I have just implemented the I and O keys to toggle punch in/out modes. If we can find a key for the metronome (perhaps U or N?), then all toolbar mode buttons should have a key shortcut.
ZynewaveZynewaveIt’s good to have these kind of ideas documented in this forum, for future reference. Remember to bump this topic some time next year 😉
ZynewaveI’ll add support for a ‘sum’ parameter macro to the plan.
ZynewaveIn the meantime, as far as sysex parameter objects go, perhaps a [checksum] variable in the macro language would help on the synths that require them? I’m assuming I can’t use these with the Roland as it is now, but I’ll experiment a little more just to make sure.
I’ve never encountered checksums in small parameter change SysEx messages. Does the Roland really use checksum for these as well? Do you have a link for downloading Roland SysEx docs?