Build 6.0.23 in public beta

[TSC]

Go at it guys and let us know if you discover anything

Linux version coming soon - currently only Mac/PC

Tracktion ChangeList

6.0.23
- Fix for loading Meledyne on Windows 8 64-bit
- Fixed a rare crash when minimising the app
- Fixed a rare crash opening newly created Edits
- Fix for editing files in an external editor (app has to be minimised)
- Fixed an occasional crash when closing an Edit with racks in
- Improved sort times for the plugin settings page when Edits are open
- Fix for Sampler plugin start times when archiving Edits
- Fix for marquee selection when dragged off last track

6.0.22
- Disabled changing track inputs whist recording
- Fix for updating automation curves with no points
- Fix for sampler displaying waveforms of trimmed audio files
- Fix for adding up to 8 empty tracks to Edits
- Fix for incorrect automation curves being displayed on tracks with racks
- Fix for record enable states not updating correctly from controllers
- Ensured punch recordings can be started/stopped from controllers and keyboard shortcuts

6.0.21
- Performance improvements for Edits with lots of MIDI data
- Fixed a rare crash using external controllers assigned to parameter values
- Fixed a crash when deleting tracks using other tracks as inputs
- Fixed an issue where recordings would disappear if tabs are changed
- Fix for track inputs not updating correctly when moved
- Fix for track input devices not being saved correctly
- Fix for track input devices not being named correctly

[ibne]

The Volume Automation Stutter bug is still here.

look at this post :
http://www.kvraudio.com/forum/viewtopic ... 9&start=30

Note that it works well in Tracktion v5.

[lkingston]

Melodyne Edit now works! My Roland audio interface now works! Unfortunately my Waves plugins still have all their parameters forced down to zero. Two out of three ... not bad!

[aMUSEd]

How do you use an external editor?

[dupont]

The good :

Annoying issue with huge audio latency (> 5s, yes s and not ms !)after moving midi controler seems to be solved. It's a pleasure to tweak that knobs again.
Plugins UI refresh is faster. I noticed AU versions are slower than VST ones, nevertheless not as fluent as in Logic X and still micro freezes but better.
It seems something changed on the note drawing, overlapped notes are better drawn.
An option to delete "hidden" notes would be handy.
Battery 4 preset loading is faster and more stable.

The bad :

Poof crash after moving midi entry from a track to another, cannot replicate, it happens at random.
Poof crash at start up while loading an edit done on 6.0.21.


TSC did a great job this week, lots of bugs fixing

OSX Yosemite.

[gigazaga]

How do you use an external editor?

From and Edit:
1. Select an audio clip
2. Click "View Source Info" in the Properties section
3. Click "Edit Audio File > Launch this wave file in its default application..."

From the Project tab:
1. Select a file from the "All Items" list
2. Click "Edit Audio File > Launch this wave file in its default application..."

Those are the ways I know, there might be others!

[gigazaga]

... My Roland audio interface now works! ...

My Roland Tri-Capture is working in ASIO mode now too on Windows. Good progress!

On Mac, AU and VST Waves plugins seem to be working. Waves VST3 take forever to load and then don't work. I previously reported that bug.

Update: Actually, after waiting 5 minutes for the Waves dbx-160 mono to load to one track. It did pass sound and the controls work. The collapse button doesn't work right. Once you hit that, you can't expand. That is the same for VST.

On the AU version of Waves dbx-160, the Collapse button works and UI works, but the plugin has no effect on the sound. The meter doesn't move and the controls spin but are otherwise dead.

[aMUSEd]

How do you use an external editor?

From and Edit:
1. Select an audio clip
2. Click "View Source Info" in the Properties section
3. Click "Edit Audio File > Launch this wave file in its default application..."

From the Project tab:
1. Select a file from the "All Items" list
2. Click "Edit Audio File > Launch this wave file in its default application..."

Those are the ways I know, there might be others!

Yeah but how do you set the default external application in the first place? I can't find any preference for doing this.

[gigazaga]

Yeah but how do you set the default external application in the first place? I can't find any preference for doing this.

That's done in the operating system. It's whatever app opens when you double click a certain file type. It shouldn't be hard to fine out how for your OS.

[aMUSEd]

I see, it would be better if you had a preference to choose the app though. For example if I am opening an audio file for editing on my system I tend to open it in Wavelab which is more powerful, so that is the default app, but if I wanted to open an audio file for editing from Tracktion I would probably choose something lighter like Audacity.

[tatsf]

Plugin-Enabled(shortcut"F" or radio button in the property area) works right,but frequently the Big Red Cross GUI doesn't reflect its state.


macbook pro mid 2010
C2D 16GBRam
Yosemite

[chico.co.uk]

I see, it would be better if you had a preference to choose the app though. For example if I am opening an audio file for editing on my system I tend to open it in Wavelab which is more powerful, so that is the default app, but if I wanted to open an audio file for editing from Tracktion I would probably choose something lighter like Audacity.

Is that on Mac?

On windows, if I highlight a wav file in the project tab, and go to "Edit Audio File", I get an option for "Set the audio editor to use", that lets me browse for the exe i want to use.

[frankvg]

Yeah that's on mac. I made it a FR, years ago probably but they never followed it up.

[Kang]

Plugin-Enabled(shortcut"F" or radio button in the property area) works right,but frequently the Big Red Cross GUI doesn't reflect its state.


macbook pro mid 2010
C2D 16GBRam
Yosemite

This is a problem I can confirm has been happening since at least T3, and possibly as early as T1. I'm used to it by now (I just count clicks in my head sub-conscioiusly), but a fix would be awesome.

A similarly old and re-occuring issue is that very often when trying to crossfade clips that just barely overlap each other you get a message that says something along the lines of "in order to crossfade, clips must overlap" (even though they do overlap, albeit just barely).

[dupont]

Midi controller mappings properties panel says the plugin has no parameters mapped to midi control but midi learn panel clearly shows volume plugin is mapped to 1/1 controller 1 chanel 1.
Behaviour is OK, if I move controller 1, volume slider is moving.

See video.