# program freeze

**URL:** <https://discussion.ntrack.com/t/program-freeze/7501>\
**Category:** n-Track Studio Discussion Forum\
**Created:** [October 23, 2005, 2:42pm UTC](https://discussion.ntrack.com/t/program-freeze/7501 "2005-10-23T14:42:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hansje](https://discussion.ntrack.com/letter_avatar_proxy/v4/letter/h/839c29/32.png) [@hansje](https://discussion.ntrack.com/u/hansje)\
**Post date:** [October 23, 2005, 2:42pm UTC](https://discussion.ntrack.com/t/program-freeze/7501/1 "2005-10-23T14:42:32Z")

</div>

on trying to open .sng file

---

<div class="post-metadata">

**Author:** ![hansje](https://discussion.ntrack.com/letter_avatar_proxy/v4/letter/h/839c29/32.png) [@hansje](https://discussion.ntrack.com/u/hansje)\
**Post date:** [October 23, 2005, 2:42pm UTC](https://discussion.ntrack.com/t/program-freeze/7501/2 "2005-10-23T14:42:32Z")

</div>

When I start n-Track, the program alerts me if any audio devices, that were in use last time I ran the program, cannot be opened (e.g.: if a usb/fw device has not yet powered up).  
  
So far so good.  
  
But if I get such an alert and then try to open a .sng file, the program freezes completely and has to be forced to close.  
I don’t know exactly when this behaviour started.  
It happens with builds 1974 and 1976 and I’m quite certain it didn’t happen some time ago.  
Could someone please try to reproduce this?  
Tx.

---

<div class="post-metadata">

**Author:** ![system](https://discussion.ntrack.com/uploads/default/original/1X/20e797a188ca427644e35db6327522d0aaee3a74.png) [@system](https://discussion.ntrack.com/u/system)\
**Post date:** [October 23, 2005, 5:39pm UTC](https://discussion.ntrack.com/t/program-freeze/7501/3 "2005-10-23T17:39:10Z")

</div>

Try resetting the preferences in n-Tracks, then select your ports of choice, and giving the song a try again. Sometimes the port selections can get confused in the app (actually the ports have changed in the apps view but it doesn’t know) and that messes with opening songs.  
  
Also, look in the preferences and make sure there are enough AUX returns selected by default. There is an old bug that reverts occasionally that if there are less than the necessary number of aux returns in the master than a song uses the app will crash when opening a song that needs more. If your song was saved with 2 aux returns, even if you don’t use them, then there needs to be 2 in the mixer already when the song is opened.

---

<div class="post-metadata">

**Author:** ![hansje](https://discussion.ntrack.com/letter_avatar_proxy/v4/letter/h/839c29/32.png) [@hansje](https://discussion.ntrack.com/u/hansje)\
**Post date:** [October 24, 2005, 10:22am UTC](https://discussion.ntrack.com/t/program-freeze/7501/4 "2005-10-24T10:22:22Z")

</div>

Thank you for your reply.  
It’s definately not the “AUX-bug”; songs load flawlessly if only the currently selected audio device is working ok.  
I was just curious if someone else could reproduce this.   
If so, I would know this is a (minor and avoidable) n-Track issue and hopefully not the first sign of a general system faillure ![???](http://www.ntrack.com/iB_html/non-cgi/emoticons/rock.gif)
