[phpBB Debug] PHP Notice: in file /viewtopic.php on line 988: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.
[phpBB Debug] PHP Notice: in file /viewtopic.php on line 988: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4505: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3706)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4507: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3706)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4508: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3706)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4509: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3706)
Sagan Technology Metro • View topic - Freeze Function

Freeze Function

Topics related to MIDI

Freeze Function

Postby fastlanephil » Sun Jul 23, 2006 4:43 pm

Does Metro use less CPU if sections in a file that are not being sequenced at the moment are kept frozen or is just the section that is up at the time working the CPU.

Phil Lovgren
fastlanephil
 
Posts: 333
Joined: Tue Feb 11, 2003 10:44 pm

Postby Jerm » Mon Jul 24, 2006 1:04 am

Metro will only enable plug-ins within scope. Within scope means that if you have any tracks assigned to plug-ins on an aux buss then those plug-ins are enabled and using up CPU. If the plug-in is installed on a track in a different section than the one that is selected then that plug-in is dormant and will not be using CPU.

Now if the track is assigned to an aux buss plug-in and the track is frozen and there are no other tracks assigned to that plug-in then the plug-in is auto-bypassed. If and when a track is reassigned to that plug-in then the plug-in is once again automatically enabled. This can be witnessed first hand by looking at the bypass button in the effects window.
Jerm
 
Posts: 2707
Joined: Tue Feb 11, 2003 12:50 pm
Location: Massachusetts

Freeze Function

Postby fastlanephil » Sat Jul 29, 2006 11:33 am

Thanks for the quick reply on my last question Jerm. I was working with a file that was using about three instances of GPO and I was hitting the wall with my CPU but managed to get it all into audio.

I finally was able to get a good midi to audio render by thawing all the tracks first. I tested doing this with a single track file and worked whether the track was frozen or not.

So I suspect that it was more a GPO vs Mac problem as I also had trouble expanding my sections.

If you have a different idea about it or something to add please post or I'll assume it's NI's Mac unfriendly GPO player causing weird problems and avoid using too much GPO until the problem has been fixed. This might be of interest to others.

Phil
fastlanephil
 
Posts: 333
Joined: Tue Feb 11, 2003 10:44 pm

Postby Jerm » Sat Jul 29, 2006 3:04 pm

I am not quite sure what your last post is saying. If you are having trouble expanding subsections then this would be a Metro problem. Do you have the latest pre-release?
Jerm
 
Posts: 2707
Joined: Tue Feb 11, 2003 12:50 pm
Location: Massachusetts

Freeze Function

Postby fastlanephil » Sat Jul 29, 2006 11:53 pm

I expanded the subsection again with the latest pre-release without a hitch and then tried it with the previous release and it also expanded properly so I'm not sure what was going on but when I originally tried to expand my subsections twice, the second section of the three would only play one of several instruments and I'm sure I didn't have it selected to play solo.

Once for some reason I had success with the sections expansion, when I rendered to audio about five of the instruments didn't show up as audio tracks.

I deleted any instruments that I wasn't using even though they were frozen, repaired disk permissions and rebooted and thawed all the tracks. I rendered the tracks to audio again and it worked correctly.

Also when I render to audio the instrument names will be different such as trumpet 2 would be trumpet 21 or some such thing. This only happens when working with a large number of instruments so I assumed CPU stress was causing that error also.

Well, I just rendered that file to audio again and Trumpet 1 is now Trumpet 13 and Trumpet 2 is 23. 3 is 36, Tuba is Tuba3, ect. There are random numbers after all the instrument names. I forgot that also the audio tracks were not assigned to audio ports but to remaining midi ports and have to be changed manually for the audio to work.
:?

Phil
fastlanephil
 
Posts: 333
Joined: Tue Feb 11, 2003 10:44 pm

Postby Jerm » Sun Jul 30, 2006 12:21 am

The names of the files will some times have numbers added so that they don't overwrite exisiting files.
Jerm
 
Posts: 2707
Joined: Tue Feb 11, 2003 12:50 pm
Location: Massachusetts

Freeze Function

Postby fastlanephil » Sun Jul 30, 2006 3:54 pm

I see. No big problem.



Phil
fastlanephil
 
Posts: 333
Joined: Tue Feb 11, 2003 10:44 pm


Return to MIDI

Who is online

Users browsing this forum: No registered users and 0 guests