ZynewaveZynewave@Conquistador wrote:
I am having some stability and reliability issues with 1.98…
A. Crash when using the “Move Effect Track” command.
Steps…
1.Insert at least three FX on any track, even Zynewave FX
2. Use the move command a few times at least but during playback.
I think I’ve nailed this bug now. Luckily it turned out to be a simple thing to fix. It happens only when using plugin multiprocessing. If you have the time, you could try disabling the multiprocessing option in the preferences, and check if this eliminates the freezes.
ZynewaveThe “search for missing plugins” function extracts the filenames from the broken mappings and tries to locate these files in the folder tree of the base folder you select.
Check the filename in the properties of a broken mapping, and use search in Windows Explorer to verify that this plugin file is still located in the folder tree you selected.
ZynewaveI’ve added a “Stream muted sounds for fast response to unmuting” option to the Preferences dialog. Coming up in release 1.99.
Previously tracks muted by a a parent bounce track was not streaming, but normal muted audio tracks were streaming for fast response to mute/unmute. This new option now controls if streaming should occur for all muted sounds, both on normal audio tracks and bounced tracks.
ZynewaveI’ve now changed this. Will be available in Podium 1.99.
ZynewaveCan it be made so when you click on a folder and the contents don’t fit above the bottom of the browser area, that it automatically moves to show as much of the folder’s content as possible?
Coming up in release 1.99.
Zynewave@Zynewave wrote:
While loading the corrupted wav file in Podium, I noticed that Podium does not finish the waveform profiling due to file errors. I’ll get that fixed.
Fixed in Podium 1.99.
Zynewave@francois wrote:
Hi Frits , i have a strange behaviour of the sound editor , if i select a zone ,ok , then i want to select another zone , it does , but the background colour of the first one remain…
Thanks for the .avi you sent me. I have now fixed this bug. It happens with mono files. The bug was caused by the change to the new channel select buttons.
Zynewave@rinxai wrote:
I meant the VST parameters, which used to show up in the Inspector parameter panel. Currently only level pan and send are visible, with no indication or method for creating VST parameters. I’ve checked this with older and new project, thinking it might be a project setting or similar, still no VST parameters.
Perhaps the VST parameters have been deleted. Open a list window and locate the “Devices/Zynewave – Nucleum” folder. There should be a VST Parameters subfolder. If it’s gone, then you can reimport the plugin in a new project, copy the “VST Parameters” folder from there, and paste it back into your older projects.
Zynewave@rinxai wrote:
Around version .91 most of the midi parameters were available for automation in Podium. Now the parameters are not showing up. Is there something I’m missing or will there be a fix?
MIDI parameters or VST parameters?
All VST parameters are available for automation. When you import Nucleum in Podium, only the Pitch Bend and Modulation MIDI parameters are created. If you need further MIDI parameters, you can create them using the param panel menu in the inspector.
Zynewave@H-man wrote:
Just wondering if that is Nucleum done? I’m pretty sure I saw something about SM 1.1 being released now and the guide looks like a case of first time perfect.
I’ve just uploaded v0.95. This is made with SM 1.1, and hopefully it’s the last beta version before 1.00. Only thing missing are presets for the default bank. Are there anyone besides rinxai, H-man and runagate who is working on presets they want to share?
The File menu in 0.95 is extended with an “Online Resources” submenu with links to the Nucleum guide on the wiki and the Nucleum forum. Since the link to zynewave.com is now in the Nucleum UI, I’ve removed the requirement of forum registration.
One other thing I wanted to raise was, given that it’s such a good SM implentation, are you planning to offer it to the SM Examples site? And, is there any use in sticking the made with SynthMaker logo on it?
I’ll drop them an email when 1.00 is released. I don’t intend to stick a made with SynthMaker logo on the Nucleum UI.
Zynewave@duncanparsons wrote:
At the last place I worked, to be able to successfully run VS6 and VS.Net 2002 (their weapons of choice) on Vista boxes, we resorted to VMs running W2K and XP, and either opened a console, or remoted to them. Bit of a palava, but worked well 🙂
I managed to install VS6 directly on Vista, but I had to make a manual modification of one of the VS6 installer files. Found that trick by searching the web.
I know you’ve already parted with the cash, Frits, but was something like Ming/GCC considered at all? It’s sterling software and very comparable to the performance MS would boast… You then get a better choice of IDEs. Borland still turn in good C/C++ compilers these days as well, were they looked at? W98 support could potentially have been maintained with those, but I guess it’s not a problem. :shrug:
I am comfortable and confident with the VS IDE, so I don’t want to migrate to another environment. I use Visual SourceSafe which integrates nicely with VS. I also trust that any future changes to Windows SDK and MSDN documentation will work in VS.
Zynewave@H-man wrote:
Actually, it was the ‘File’ button on the Nucleum UI. The menu did not appear because Podium exited immediately.
Then it’s most likely a bug in Nucleum. I’m afraid this is out of my control, as this crash is happening in the SynthMaker engine. I’m hoping that future SynthMaker releases will improve stability.
Zynewave@H-man wrote:
Last night I was using Nucleum, pretty much just creating a new preset, clicked on the save button and BOOMF! ….desktop.
Never seen it before, ever. Podium 1.98, Nucleum 0.93.
Which save button? The save menu in Nucleum or saving the project in Podium?
ZynewaveNot so long ago I considered changing this behaviour. It’s on my todo list.
The reason the automation tracks are muted is because, even though the automation tracks are shown as child tracks of the soloed track in compact mode, they are in fact child tracks of effect parent tracks. Soloing a track will solo all child tracks, as well as each parent track all the way up to the master. I need to extend this so that any parameter child tracks of a parent track is soloed as well.