Notifications
Clear all

Don't follow/When Running

4 Posts
2 Users
0 Reactions
249 Views
Kendall W Cochran III
(@pbeprod)
Re-Membered
Joined: 4 years ago
Posts: 335
Topic starter  

@getdunne

Hey I'm doing a backwards breakdown of a patch I created by pulling out all the parts into Reason. I selected one of my BPM SPLITS I use when I play live cause I was wanting to add an organ Part that is played by MIDIBox. I added UNIFY on a track then opened UNIFY when I started playing it was playing on the tempo of Reason which is always 120 bpm when it's opened. This was expected, it showed the reference bpm that was set when I created the patch. So I switched it to "Don't follow" which I've done before and it worked. Well this time it didn't. On the one patch of the patch I'm breaking apart, when I switched to ALWAYS it quit playing any of the MIDIBOX's. It just played like MIDIBox had been bypassed. So I started switching to different BPM SPLITs it did the same, it wouldn't change to the ref bpm would continue playing at the DAW tempo. The other patches didn't do the same as the one at ALWAYS. This isn't hampering me in that the only reason I opened it this way is to create a few Midi files that I'll incorporate into the patch. But wondered if you would have the same issue. This is on the PC version inside Reason, I just recently updated to version 12.7d3, in the past they had made some changes inside Reason in the way it handles VST's etc. so who knows.

I went over to my Mac and at first it was doing the same thing. So I did an update while selected Lock Master Effects it started behaving properly so I tried the same thing with the PC version but still ignored the ref bpm.

I also had several other strange occurrences but I'll leave it with the above.

Thanks!

KWCIII

This topic was modified 9 months ago 4 times by Kendall W Cochran III

   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4487
 

I’m away from the office until the 24th.

Your post is a bit difficult to follow. It would help if you could attach a (zipped) patch that exhibits the problem.


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

@getdunne

Ok, I'll try a video once I re-read it and remember what the problem was. I had a crash this morning while creating one of those large "Live Show" patches I create. Had 5 tracks. 1. Intro 1 2. Intro 2 3. Intro 3 Then a verse and Chorus track. They really get my Mac fan going. This one is using instances of Roland's Juno - 60 and Juno 106 in all 5 tracks. I'm thinking about trying to use Cherry Audio's DCO-106 see if that's any more efficient or I"ll do "Audio Tracks" like I have on my "Live Versions" of my songs. I've attached the Crash code.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4487
 

@pbeprod

Thank you for the crash report. It looks like the crash occurred when trying to open a new MIDI file in MIDIbox. Please test opening that same file again, and if Unify crashes again, there might be a problem with the MIDI file itself.


   
ReplyQuote
Share: