Notifications
Clear all

Still crashing after Omnisphere Patch

11 Posts
3 Users
2 Likes
635 Views
Kendall W Cochran III
(@pbeprod)
Re-Membered
Joined: 3 years ago
Posts: 282
Topic starter  

Hey Shane,

It's still crashing with the Omnisphere patches. I was able to get the crash code. Not sure if this will help you but

thought you could look at it. Also having issues with Unify not playing midi files that I create correctly.

Here's an email that I sent to John last week hadn't heard back from him.

I've been trying to create midi files to use in Midibox. I have been working on it going on my second day now.
It will not play these files right nor will it recognize one of them as the correct bar length. I've tried editing and exporting
them from Logic Pro, Reason, and Cubase. Tried several different formats, making the notes shorter etc. but
to no avail. I've attached them to see if this happens for you. I've also attached some screenshots showing
how they look in Reason. I did read through the whole Midibox section and don't see where I'm doing anything
different that would make it play them wrong.

They couldn't be anymore basic. I do have screen shots and the midi files I had attached of course this service only allows one file

attachment at a time so I chose the Crash code. It's a MS Word file hopefully that works for you.

Thanks

KWCIII


   
Quote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3813
 

@pbeprod

There are some important fixes to MIDIBox coming in a Unify maintenance update very soon, which I think will address the problem you describe.

As for the Omnisphere problem, please describe in more detail. Thank you for the crash report. It indicates the failure is occurring in Omnisphere itself, but this could be a red herring. With more detail I may be able to figure out what's actually going on.


   
ReplyQuote
Kendall W Cochran III
(@pbeprod)
Re-Membered
Joined: 3 years ago
Posts: 282
Topic starter  

Well, The patch itself is 4 layers, layer 1 is a Keyscape  with a duo- Upright Harpsivibe, Layer 2 is an Omnisphere with a Patch I created called WOODWIND - Baritone Sax - C3- Whole Note, Layer 3 is another Keyscape with a keyboard split of Upright Harpsivibe, and Layer 4 is a patch I created called SPOKEN - Lurch "You Rang" It's pretty simple, this is the version I created trying to get away from the FULL Multi I created on 6 layers but decided  to split out the different parts and removing the parts I actually wasn't using. So when I'm done I click on the red dot to close it and it asks if "Have you saved all the changes? Are you sure you want to QUIT the Unify Stand-Alone app?" I chose OK. Most of the time it doesn't crash immediately I come back to my computer later and crash notification is up. 

Also:  Today I was able to create a patch using Unify's own patches using 3 layers one each for a Kick, snare and a shaker, created the rhythm for each in Reason, and they actually worked and were in sync. I even used Reasons Shuffle mode to make the rhythm "Swing" and still worked. I did realize I had to move the little slider that notifies the end of the track at the end of the midi data and it came up when I loaded the midi file that it was the 2 measures I had created.


   
hallenberg reacted
ReplyQuote
hallenberg
(@hallenberg)
Irritant
Joined: 3 years ago
Posts: 142
 
Posted by: @pbeprod

Layer 4 is a patch I created called SPOKEN - Lurch "You Rang"

LOL! Buy this man a beer.


   
ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3813
 
Posted by: @pbeprod

So when I'm done I click on the red dot to close it and it asks if "Have you saved all the changes? Are you sure you want to QUIT the Unify Stand-Alone app?" I chose OK. Most of the time it doesn't crash immediately I come back to my computer later and crash notification is up. 

This suggests Unify is crashing while trying to clean up the Omnisphere instances. The delay before the crash-report comes up is normal; MacOS needs time to prepare the report.

Can you please try a little experiment: manually remove each Omnisphere layer and then quit Unify, and see if it still crashes.

To remove INST layers, option-click on the layer ops button, or click it and choose "Delete Layer". You won't be able to delete the last remaining INST layer (because there must always be one), so try clicking on the ops-button in the instrument box and swap Omnisphere for e.g. Sine Wave Synth.


   
ReplyQuote
Kendall W Cochran III
(@pbeprod)
Re-Membered
Joined: 3 years ago
Posts: 282
Topic starter  

@getdunne I did that, and so far(40 min) it hasn't produced a crash report.


   
ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3813
 

@pbeprod

Thanks for checking that. In that case, the upcoming v1.1.4 should fix this issue.


   
ReplyQuote
Kendall W Cochran III
(@pbeprod)
Re-Membered
Joined: 3 years ago
Posts: 282
Topic starter  

@getdunne Hey, just watched last Saturday's live stream, been working nights the last 4 days and noticed the right click to unselect all the solo's that have been selected, would be cool to have that on the mutes as well. That's one thing I kept asking Eric Persing for was a master unmute and unsolo buttons at the top of the multi mixer but they don't seem to want to. I asked for that several years ago. Also would there be a way to include a "Chord" mode inside Midibox?


   
ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3813
 

@pbeprod

Right-clicking on a Solo button means "Solo this layer only". The corresponding function for Mute would be "Mute this layer only". Is that what you'd like?

I'm not sure what you mean by a "chord mode inside MIDIBox", but as John showed in the livestream ( https://youtu.be/1prS7PdHzuw?t=3278), you can replicate INST layers with MIDIBox and drive the whole layer-stack with PolyBox on a MIDI layer to get MIDI patterns to play polyphonically. If that's not what you're looking for, please describe in detail.


   
ReplyQuote
Kendall W Cochran III
(@pbeprod)
Re-Membered
Joined: 3 years ago
Posts: 282
Topic starter  

@getdunne I know what you're saying but you can also use the right click when all the solos are already selected and when you right-click one that's already solo'd they all un-solo. Mute won't do that.

Yeah but like in blue arp there is a chord mode, I wonder if there would be a way to play chords based on the rhythm that is being played from the midi file. Right now when you have a midi file on a layer it will only play the one note. Of course I know I can just use blue arp, or do the poly box thing. But I haven't figured them out yet. 🙂

I did set up a midi file that has chords in it and when I hold the one note, it will play chords from Midibox. Just wondering.  Most of what I do I use Live, I do a hybrid of music and comedy. I play like 6 to 10 secs of well known songs and then stop just as they're getting into the song I stop and tell very bad puns. Basically Dad jokes.

I also noticed that sometimes the patch I'm working with after it's been saved and I continue to work on it will say [modified]. And then in the browser it also said modified but it wouldn't go away after re-saving it. Then when i clicked save and it opened the Save window and clicked save it crashed. But when I opened Unify again the [modified] was gone.

Also are you two thinking of getting Unify to where you can drag layers and reorder them in the window?


   
ReplyQuote
getdunne
(@getdunne)
Illustrious Member Admin
Joined: 3 years ago
Posts: 3813
 

@pbeprod

Whew! One question at a time would be easier...

  • I'll think about possible future chord modes for MIDIBox
  • "[modified]" gets added to the current patch names if you use any of the new options to load another patch as a new layer(s) in it
  • If you don't want "[modified]" at the end of the patch name, just delete it manually from the end of the patch name when you save
  • Dragging layers in the layer stack is partially implemented, but what remains is very tricky, so it may be a while before this appears.

   
ReplyQuote
Share: