Thanks
Actually I had been using a couple of hosts prior to Podium in that session so maybe one of them was “hanging on” to the BCF driver ?
I’ll try again on a fresh boot.
Many thanks
Will look into those !
Obviously I’m hoping this is a single episode specifically related to the strange combination of things I was doing at the time.
One thing I will try is reverting back to the Windows RME Midi driver in Cubase, as the Direct Music driver is very recent addition to their driver.
I guess the fact that SX2 is old and hasn’t been updated for 4 years may possibly be related as well … ?
@Zynewave wrote:
@swayzak wrote:
This seems to happen after I minimise the arrangement and then right click on the Windows Start button to open the Explorer.
Minimize the arrangement? You mean minimize the main Podium window?
Have you enabled the “release drivers when Podium does not have focus” option in Preferences?
Please send me a copy of your project file, as it is before the crash.
Yes – minimising the whole Podium window.
Unfortunately I saved over the original with this new non VST scan version.
Would it help if I recreated the original and sent it to you ?
EDIT Actually I think the minimising thng is a red herring – I recreated the VST plugin search and came back to the PC a few minutes after the search had finished. The crash message was there with Podium window maximised. I’ve sent it to you anyway Frits in case it gives any other clues.
@ronin wrote:
I had a similar problem. I use a lot of free plugs and almost every host I’ve tested crashes while scanning them. Podium was clever enough to mark plugins which crashed immediately but there seem to be some other bad plugs which crashed podium after the scan was completed. You can try to save a template after the scan has completed, reopen podium and use the template.
I don’t suppose there is a list round here of “rogue” plugins for Podium is there ?
I got no message about a specific .dll.
It HAS to be a plugin though because it’s stopped doing it on this project (with no VSTi scan).
I’ve got too many now to try them one by one.
I will say that Renoise also flagged up Vaz Modular 3 Effect dll, Korg midifilter/mixer/mixer 2/mixer 3 dlls (from Legacy collection) and the Tascam GVI nfx as problems (and disabled them).
I could try these to start with …
However, after deleting the scan file created (as advised by Renoise) to try and scan them again, they have been enabled now.
Ah – I may be getting somewhere …
Decided to create a new project from scratch.
This created Midi input devices available in the “Input” part of inspector.
Assigned to default Absynth VSTi & could then play from keyboard.
However these Midi devices are not present in my main default project – just a folder of device mappings (Midi In 1 to 16).
Can I easily recreate all the midi devices (RME HDSP etc.) in my main project or have I got start from scratch ?
thanks
@Zynewave wrote:
Which browser? Double-clicking objects opens the properties dialog, except in the track inspector where double-clicking assigns the object to the track.
Ah- OK. I see why you can’t now.
thanks
@Zynewave wrote:
Click the pin button at the top of the preset panel.
Genius 🙂
Also, is there a keyboard shortcut to move focus between a track and the inspector e.g for quickly changing presets assigned to a number of different tracks ?
Yep – that’s better.
Changed default New Track colour to something more revealing.
@Zynewave wrote:
It’s deliberate that is omitted from the track context menu. However, if you left-click on the map row in the mixer, you will get a device menu. I’m probably going to extend this to the group panel in the inspector, and maybe also to the mapping box in the track lane header.
Ah – I see. That’s probably just as useful – although the map row is difficult to see on my monitor…rather dim against the background. Can this be edited ?
Yep – that was the problem.
thanks
Great – thanks.
I knew it had to be something simple.
@Podianer wrote:
Not yet.. it is on the plan.. I think Frits said, I would look into this later this year..
OK – thanks.
Is there an alternative method for remote midi control usable at the moment ?
Or is it restricted to those assigned within VST plugins ?