Hi, I’m in the process of building a new template from scratch in CP8 and I can confirm that MIDI Input Routing and Expression Maps are lost after disabling the track, quitting Cubase, launching it again, opening the Project and enabling the same track.
I don’t use Quick Controls so I can’t confirm that.
What is even more curious is that the MIDI Input Routings are always lost, but, for example, only 8 out of 10 tracks loose their Expression Map assignments randomly.
I was so happy about the new Instrument Tracks Disable function, it is IMHO the best feature along with RIP for film musicians with big templates, who don’t want to use VEP, but it’s inconvenient to loose ExpMaps after every restart with a 300 tracks plus template.
Re-assigning the MIDI input is relativly easy, but trying to find the right ExpMap trough hundreds in the list (which by the way scrolls very slow if the list is longer than your screen can hold) is a showstopper.
This is on the issue list since 8.0. Annoying for template buidlers. It is important to detail the issue properly, since in some conditions everything seems fine, but in fact it is a bug in the CPR itself and what is written to it.
Best way to show what is going wrong is this simple workflow:
1: start an empty project
2: add groove agent 4 on a instrument track
3: add a midi insert (f.e. beat designer)
4: make some basic rhythm on the beat designer
5: save the track preset (optional)
5b: disable the track
6: save the project
7: shut cubase down (no menu bar, so complete closure)
8: reload cubase and reload the project
9: enable the track
10: press play
You will notice that the midi insert rack is empty. But in fact it isn’t. If you start your project you will hear it playing, and if you push the edit button on the midi insert, then the beat designer will show up. But it isn’t listed as it should be in the midi insert fields.
Shure this is a bug, and yes it’s the same with midi inputs.
The CPR does not contain track information from disabled tracks like it does with enabled tracks.
They know the issue. It is a matter of priority in fixing such a thing.
Untill they are able to fix it, i’m getting used to it.
Maybe, once fixed, i’m going to miss this little spooky bug. Because youcan baffle nonaware users with it.
and FWIW. Ifyou want to impress the guys at steinberg. Make a small project with several of those tracks containing “ghost” data, and then send it to them. They will be looking to a completly empty project containing no parts at all, and still be hearing your song when pressing play.
I’m too busy for the moment for doing this, but maybe someone can do it. It’s funny after all.
as said, here a link to a short demofile (cpr).
If you load it you should notice the entire CPR is visually empty at all levels, but still it contains a 16 bar mini-song with real musical data and mixer automation. So this is a bug… and it shows why…
I used only halion sonic SE + retrologue + prologue so everyone with a cubase 8 should be able to play this.
workflow: load the cpr, reconnect the soundcard to your own settings, enable all tracks, and press play
It would be logical for the midi inserts to be present in the rack on Instrument track, but the inserts rack section in Instrument tracks is for audio inserts. The midi inserts don’t show up as they do in midi tracks.
I don’t know if SB is checking on that. I can’t reproduce it here; the expression map and quick controls, which I believe has also been mentioned, does stay configured on the track. If it’s broken consistently for you, have you tried starting Cubase in safe start mode, or checked it in an empty project, etc…?
I agree with Pablo. It’s a generic issue with everything that is midi related. Saving it as a preset does not help.
midi input is not remembered (when loading in a project --) for the disabled tracks)
expression maps are not remembered (when loading in a project --) for the disabled tracks)
quick controls are not remembered (when loading in a project --) for the disabled tracks)
midi inserts ARE remebered but are not shown correctly in the insert efx field where there should at least be an indication of what efx is being used --) for the disabled tracks)
Some important information related to the track is thus getting lost when you save it, close cubase completely, and reopen the same project.
Really something that should be solved.
But tx for looking in to it !
And it will get solved, i am shure of that.
I can confirm this on my system too. Unfortunately I just created over a 1000 track template with all instrument tracks, disabling all tracks to dump memory, with expression maps for all, and to my shock find that the midi inputs are lost as well as the expression maps.
If I had known this before I probably would not have gone this route.
Is there any word that Steinberg is aware of this and intends to work on fixing it?
Edit: After further testing I have found that some expression maps are restored properly and some are not, it’s totally random so I consider this a bug.
The disable track feature is completely awesome for those of us who want to build large templates but don’t want to run VEPro or have multiple networked computers like Junkie XL. That being said though, re-enabling a track should restore everything as it was in my opinion. Hopefully Steinberg can make this work properly…
Edit#2: I just did a test with building a smallish template from instrument track presets that included expression maps. I disabled all the tracks and then exited Cubase then restarted and loaded the template. I re-enabled the tracks and all of the expression maps recalled correctly. Some strange behavior…
it is one of the possible solutions
maybe they limit the size of the content in the CPR for BU-reasons
not enough insight to get that figured out
but if so, it should not be that way
they should give us a choice to go that path or not
that being said, i still use it every day.
for he moment it’s a bit more clicks then needed,but the function is superb.
just need to get used to enable the midi and the quickcontrols and the rest…
but it is still a lot faster then before
direct connection to the favorites without using the complex internal browser and focussed on your own sound…