thcilnnahoj's Forum Page

@Zynewave wrote:

• New tracks can be created in the mixer by double-clicking or right-clicking the empty space after the last track.

A nice surprise! Thank you very much.

@Zynewave wrote:

@thcilnnahoj wrote:

– I get a crash when I use a tag that has “include child tracks …” disabled, and I try to select a group track (it has to have a child track) that is the last track visible in the tracklist. Only happens in the arrangement view, and strangely doesn’t crash when I select it with the arrow keys.

I followed your description, but I could not make it crash. I must be missing some crucial step. Could you perhaps describe it more detailed, or make a gif?

Maybe it has been magically fixed… I can’t get beta 8 to crash either. Here’s how to do it in beta 7: http://www.youtube.com/watch?v=-hjJQUyDc04
I’ll spare you the 20 MB GIF!

– In an arrangement with multiple “master” tracks, they will not appear docked in the mixer, which I really think they should if docking is enabled! 🙂

If both masters are docked, then it will be difficult to see which undocked tracks belong to which master.

True, but for the use I’m thinking of (multiple monitor outputs) this wouldn’t be a problem.
Come to think of it, track tags are probably going to come in handy here, too.

Works nicely so far, but if the last track in the tracklist is a group track, you can’t drag any track below it without moving it into the group. That seems to work only when the master track is visible.

A few other ideas…

If you have the time, you could try and strip the arrangement down even further, if possible at all – remove all other tracks, effects, automation, any fades or crossfades. Also try deleting the parts of the recording that are muted.
If you still have real-time bouncing set up, try setting it back to offline mode (track menu -> bounce) and rendering again – who knows, maybe the first bounce event got corrupted somehow. :-k

I don’t think this makes a difference for bouncing, but do you have “stream muted sounds for fast response after unmuting” in the preferences (engine tab) enabled?

I can’t speak for Frits, but an example project would surely help, even if only to test whether the problems appear on different setups.

A crash report:

1. Load a project that already uses some audio files.
2. Create an arrangement and import one of the audio files into it.
3. Do something to the audio event that will disconnect the link to the original audio file. Simply cut it with the scalpel, then clone the parts.
4. Return to the project page (or use the project browser) and remove the audio file from the project.
5. Back in the arrangement, undo your steps until the original audio event would be restored.
6. You should ended up with a completely blank event, which doesn’t show anything in the embedded editor. In the end, when I tried to edit the event’s fades, it resulted a crash.

Another slightly different route:

3. Beat-slice the event and merge it back together, creating a new event.
4. Remove the original audio file from the project.
5. Undo your steps, and it should crash immediately.

You also get such blank events when doing this with note and curve events, of course, but I couldn’t get those to crash, as they don’t have fade handles.

I don’t know why or how this happened to me the first time (during normal work – I surely didn’t touch the project files then), but I thought I’d at least report the crashing action.

@Zynewave wrote:

There seem to be a few discrepancies with the “depth” of the group level strips. I’m pretty tired, so I’m not sure what to make of it right now…
Here’s an example picture (thumbnail). On the left is what the actual hierarchy looks like.

Not really a bug. When the parent group track is hidden, I draw the header of the track all the way up to the top, instead of showing the arrow at the actual group level. That’s what happens in the middle part of your screenshot. I don’t know if it would make more sense to show the arrow when it does not point to a parent group :-k

Okay, less sleepy today, so I can try to explain better what struck me as strange here. 😉

If you only show tracks that are at a deeper group level than other tracks, they’re displayed as if there were no tracks above them in the hierarchy in both the mixer and the arrangement. (ex. 1)

At the same time, tracks that are not as many levels down still have a group level strip as wide as the arrangement’s hierarchy is deep. This is the case if you only show a track that is at the top level (directly below the master) – in the mixer, however, it is displayed differently. (ex. 2)

Finally, if you show a track at the deepest, and a track at the highest level (below the master) together, the group level strips are the width/height of the whole hierarchy in both the arrangement and mixer. (ex. 3)

I couldn’t say if this is a problem, or which way it’d be best to display at all times. On one hand, if the group level strip width isn’t always the same, the track controls will start to jump around again when selecting different tags (even on the same track – compare examples 1 and 3). On the other hand, it might save space and look better in some cases, should the group level strips not always be as wide as the hierarchy is deep.

Also in beta6:

Inserting a bus send on a track will automatically add the matching bus return track. Pressing undo once will undo the creation of the bus return track. Pressing undo again will undo the insertion of the bus send.

The return track is not created, though, when you assign the send mapping to an already existing effect track.

Also, when you use the “move track to new group” command, the track created is not assigned a tag. I don’t know if the command will be around after multiple track selection comes around, but here you go anyway.