duncanparsons.
duncanparsonsI have an issue with a pod file that I can only work with if I go thru a series of hoops..
The file started life in version 1.79 on a particular machine, and was fine. When I moved to version 2.x all seemed OK as well. But when I switched machine (also with 2.x) it doesn’t open any of the projects successfully without following a series of steps which I’ll describe in a moment. I discovered this in January/February time, and tested by installing 1.80 on the machine, and the older project file opened fine; but on reinstalling 2.x the problem returned I’ve stayed with 2.39 on this machine for a while now, and all has been well with other projects that were migrated. I have just lived with it, but I’m now at the stage of mixing it for an album I’m working on, and I thought I’d try and get it sorted.
The file loads fine, but opening an arrangement with the driver I wish to use loaded causes it to fail, the graphics show but the cursor never returns from the hourglass.
The driver I wish to use is the ASIO driver for my Alesis MultiMix16USB2, which works perfectly with every other project I have.
If I use the driver setup dialog & put it to
I cannot stress enough that the issue is with the file, not my setup. My guess is that somewhere along the line the file has gained driver information it cannot resolve. On the previous machine, I did use a Firewire version of the same mixer, and it’s possible that driver information relating to that is still stored in the pod – I don’t know how the pod is laid out in tha regard. However, other files have survived the same transition that this one has had.
I’ve tried creating a new file and importing, but the same thing happens.
So, Frits, is this a settings thing that I can resolve myself with instructions, or should I make the file available to you to look at and correct?
🙂
DSP
thcilnnahojThis might be too simple to actually work, but did you try the option “Update Audio and MIDI Mappings” found in the devices menu? Maybe the faulty mappings can just be replaced by correctly working ones this way…
ZynewavePlease email the .pod file to me. All the driver stuff is encapsulated in the Device Mapping objects. Podium should of course not freeze even if there is something wrong with the mappings. I’d like to take a look at that.
duncanparsonsPM sent 🙂
ZynewaveThanks for the file. I can load the project and start the arrangements ok with my RME ASIO driver. I of course do not have any of your sound files and plugins, so playback does not produce sound on my system.
The mappings in your project are quite messy. Both your audio inputs and outputs have duplicate (redundant) mappings, and you have three “Devices” folders, each with their own set of bus mappings and plugins.
Unless you already tried the “Merge Project” feature, I would suggest you create a new project with no arrangements, but with a clean set of audio/MIDI/bus/plugin mappings, and then merge your old project into the new one. Perhaps that will clear up some of the redundant mappings.
duncanparsonsthanks for that
I’ve tried what you said, but with the merge I get the multiple Device folders turning up again. Pre-merge, all is stripped down how I want it; post-merge all the devices from the imported file are there.
Is there a way of telling what is mapped to what? I’d like to delete those folders so I have a single device tree, but I’m worried about losing things that are mapped and the settings with them. If there are multiple mappings to the same VST dll, do these all count as a single (but replicated) mapping, or is each node treated as an individual entity, so deleting it removes all trace from a project?
I fear it’s the latter so I’ll have to save fxbs of current settings, remap to the devices first in the VST tree, import the fxb, then delete the unwanted nodes.. would I be right in that assumption?
This is somewhere it could be handy to have a tick next to the item selected when the menu is open.. having said that, most of the time you’d know what was selected, as there’d only be one occurance of a device in the tree! [Edit]well, wadderyaknow.. there already is a tick! I’d never noticed!! how very odd :-)[/Edit]
Zynewave@duncanparsons wrote:
I fear it’s the latter so I’ll have to save fxbs of current settings, remap to the devices first in the VST tree, import the fxb, then delete the unwanted nodes.. would I be right in that assumption?
Yes. Sorry about that. I guess the reason you ended up with multiple Devices folders, is that you used the deprecated import feature found in older Podium versions. The merge project command replaced the import command, and it handles remapping mappings from the merge project to the mappings in the current project. It does not handle remapping redundant mappings within a single project.
duncanparsonsno worries, I’m almost done on remapping it 🙂
if it still doesn’t open, they’ll be questions 😉
duncanparsonsok still not doing it.. An arrangement will return from hourglass if there’s no driver loaded. When I assign a driver in setup if have the option to remap the devices.
If I choose yes, the arrangement closes, and on reloading there’s no return from the hourglass.
If I choose no, the arrangement works fine – business as usual for a normal Podium session.
The file I sent has been cleaned up, right busses, duplicated devices gone, just the minimal folders.
I tried a clean project and merging the cleaned pod. Same thing (only without multiple device mappings!)
If I save all changes, it saves fine. If I quit when there are unsaved changes, it hangs if I press No.
I’ll PM you again with the better file. Again, this is the only project file I have that does this.
I can work with the roundabout way of delayed loading of audio, but getting things ‘right’ would be nicer!
Duncan
ZynewaveThe project looks clean now.
Still not seing any problems when I use my RME driver. Tried the audio driver disabling, entering arrangement, enabling driver, reentering arrangement, without problems.
Do you see the problem with the latest Podium 3.0.2?
My best guess is that this is caused by a plugin. You could try to pinpoint the issue by making a copy of the project, and gradually remove tracks/plugins, until you get the absolute minimal arrangement that can produce the issue.
duncanparsons🙂
successively removing VSTs was my next avenue.
Must confess, not tried v3.x yet, I’m in the middle of a large project and was going to wait until it’s finished in about a month’s time.. Have there been non-backwards compaitble changes in the pod structure?
duncanparsonswell, after all that it was a Betabugs plugin, SpinBug. It’s the only song I use it on! I reinstalled it, and all appears to work as it should do now.
Sorry about that, and thank you for bearing with me!
DSP