Logic Pro Logic 'forgetting' instrument settings

C

CinningBao

Logician
I wonder if this is has been seen anywhere else apart from my screen

My current project, which I just reloaded, seems to have loaded and mismapped some EXS instruments
eg:

- a kick (from Logic library) turned into a hammered dulcimer
- a violin (from Logic library) turned into a snare

Now I know this isn't normal, and I've not experienced this before..
Have any of you guys had this problem?

It's pretty serious-a-bug when instruments are replaced with something else, and I'm not happy about it, but I don't have time today to attempt to recreate it for bug reporting.

Is it just me? Or?
 
Sort by date Sort by votes
I can confirm such a behavior for my Logic 10.3.2
OSX 10.11.6 (El Capitan)
  • Instrument presets are not always loaded with AAS Ultra Analog and u-he Bazille. Don't know about others yet.
  • Sometimes duplicating disabled effect plugins or instrument plugins by alt-drag produces default settings, not the settings of the original (all third-party, don't know about Logic plugins).
  • I duplicated regions with automation to other tracks and in some of them the first automation node got ignored, was at zero instead of the original value.
Seems as if we should control virtually everything at the moment.
No fun.
 
Upvote 0
Sure. Did it right now.
Everything happened in my current project within about a week and I started three times with a fresh file.

Currently I am unable to simply start recording a Bidule channel. Have to start, stop, disable, enable, move the SPL, just to get Logic to record as expected.
 
Upvote 0
Hey, another Bidule user! I don't see those very often 🙂

From my computing background, I figured there isn't really enough to actually report. I'd expect to be able to send a log, or a method to recreate, or a project which goes wrong every time.. otherwise I feel like a bad bug reporter!

Plus I've had no other failure, that I've noticed, other than the wrong sounds loaded in to EXS24.
But I will now report it.
 
Upvote 0
Peter Ostry said:
Currently I am unable to simply start recording a Bidule channel. Have to start, stop, disable, enable, move the SPL, just to get Logic to record as expected.
Click to expand...
Found out that this is a Bidule issue or something of both, Bidule and Logic. Automation data are not properly recognized if they do not change at recording start. Got a grip on that by setting the start of automation where I want it, but a little different before the start point. This way, the record pre-roll forces the automation to work since data changes before the recording begins.
 
Upvote 0
CinningBao said:
Bidule 9757
Click to expand...
On the download page 0.9756 is the latest version, this is what I have.

I automate the 'Stochastic MIDI Note List', parameter 'Chances of generating notes' and need that at zero for the start (no notes are generated) and this does not happen reliably unless I manipulate the automation value before the recording process starts, within the pre-roll phase. Now it works well.

But as I said, I am not sure if it is a Bidule or Logic issue or both.

—

Found another thing, related to store/remember:
Occasionally the status of the 'Multicore' switch in u-he Bazille is not stored. After reopening the project, one of three Bazille may have this switch off. Not often enough to report it yet.

And still an old Environment bug, also related to store/remember:
After opening a project with a cable on a port of the Physical Input object (below the SUM port), the cable is gone and I have to reconnect it. Especially annoying if there are multiple cables. Reported.
 
Upvote 0
Ah, you might not be aware of this page: https://www.plogue.com/bidule/latest/ - this isn't a news page so I think it's ok to post it here.. you'll see the latest version here, and recent bug fixes.

It's always worth letting the guys on the forum, users and moderators, know of these issues - Plogue are always very helpful when it comes to bugs and errors; they want the product to work as people expect! And you get immediate feedback, not like the Logic team..

It _may_ be related to the way Bidule handles automation, or not. But you'll be closer to an answer by letting them know.

I'll see if I can squeeze in a quick test of the Stochastic MIDI generator later, I'm interested to see if fails here as well.
 
Upvote 0
Ah, now this is becoming truly unacceptable. Been working on a project this afternoon, then closed and opened another project, then closed and went back to the earlier project and one of the Alchemy instances had loaded with the default preset! Grr..

Luckily I did have a previous version of the project so I can import that channel from the media window and that works, but having previous versions available might not always be the case.

Filing a bug report..
 
Upvote 0
Yes. Terrible. I started splitting my projects to get less channels per file and I bounce more often than usual to audio files. Currently I am in sound design and cannot check everything when I open a project. Even worse, if one has hidden tracks like me, he may not even notice the changes until it is too late for recovery because too much has changed.

Hopefully this problem gets fixed ASAP.
 
Upvote 0
Back
Top