T5 bugs + FRs

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I tried to reverse a .OGG clip and it did not work - the clip was highly distorted.

Also, please reset my Bug Tracker account login - Sorry, I think I messed it up. Never mind - got it!
D Scarlatti, Dell XPS8700 i7/8gb mem/1tb hd/Steiny UR22/Presonus ER5s/Nektar LX61 kbd ctrlr/Win 10 Pro/S1 4.6/ my music here: https://www.magix.info/us/profile/my-profile/media/

Post

Bugs 2 things .
1. Export to mp3 at 320 I get a click/pop just one , a couple of seconds i to the render even at 1x speed , I havent tried 192 . Renders fine to 16bit 44.1 wav though . UPDATE -just figured it out , I rendered 3 solo tracks , one of those solo tracks is a aux return for valhalla room . My muted tracks had an aux send going there too , so I went back and disabled there aux send filter and bam no pop .. But this is just mp3 export ?
2. EZdrummer , dragging midi clip from EZ to the edit does not not fill the Bar , you have to drag the clip arrow to the right to fill the Bar still ...
These are Non show stoppers for me , But just thought Id chime in .
T5 X64. Windows 7 X64

Post

Bug: Tracktion poofs when I randomly audition loops in the loop browser. I have the same issue in 4.5.6 as the 5.1.0 demo. There's no predicting when it will do this. The loops are a mix of aiff and wav, and auto play is enabled. Mac OSX running Mavericks, stable system otherwise.
11, 418th in line to the KVR throne

Post

danbroad wrote:Bug: Tracktion poofs when I randomly audition loops in the loop browser. I have the same issue in 4.5.6 as the 5.1.0 demo. There's no predicting when it will do this. The loops are a mix of aiff and wav, and auto play is enabled. Mac OSX running Mavericks, stable system otherwise.
Odd.. The loop browser code was completely rewritten for T5. Must be something in the low-level file reading, perhaps because of the particular files you're looking at.. Can you email us a log file?

Post

On its way, Jules. I should be clearer - I audition my loops through the file browser rather than the loop browser, as I have them organised so I can access the same structure regardless of audio application.
11, 418th in line to the KVR throne

Post

It would be nice, when Tracktion does crash, if it could so in a more useful way than just a "poof" eg on Mac most crashes initiate a system level error log that helps with bug tracking but Tracktion doesn't even do that. At least one thing it does do well is retain a temp copy of the project you are working on, that is good, but your ability to track and fix bugs us severely limited by the lack of logging.

Post

aMUSEd wrote:It would be nice, when Tracktion does crash, if it could so in a more useful way than just a "poof" eg on Mac most crashes initiate a system level error log that helps with bug tracking but Tracktion doesn't even do that. At least one thing it does do well is retain a temp copy of the project you are working on, that is good, but your ability to track and fix bugs us severely limited by the lack of logging.
Not sure where you got that idea.. The tracktion log file has always contained all the info we need about crashes - if you get a crash you should always send us a copy of that.

The OSX system reports are generally pretty useless, which is why we use an internal one instead.

Post

Jules, further to my previous log file, I have updated my audio loops to 16/44.1 wav across the board to see if it was a bit depth or filetype issue. All loops [around 16Gb in nested folders never more than three tiers deep] reside in a hierarchical directory in the /documents folder. Still getting the crashes on an otherwise stable system [OSX Mavericks, T5 32 bit] when I randomly click around the folders in the <files> browser. Happy to send any more information if you need it.
11, 418th in line to the KVR throne

Post

danbroad wrote:Jules, further to my previous log file, I have updated my audio loops to 16/44.1 wav across the board to see if it was a bit depth or filetype issue. All loops [around 16Gb in nested folders never more than three tiers deep] reside in a hierarchical directory in the /documents folder. Still getting the crashes on an otherwise stable system [OSX Mavericks, T5 32 bit] when I randomly click around the folders in the <files> browser. Happy to send any more information if you need it.
Thanks Dan - no, you don't need to send me anything else. I'm sure we'll get a new version out within a week or so with a handful of minor fixes like that.

Post

FR:

It would be great if T5 could do MIDI clip aliases, i.e. exact copies of a MIDI clip that change when the original clip is changed.
My other host is Bruce Forsyth

Post

jules wrote:
aMUSEd wrote:It would be nice, when Tracktion does crash, if it could so in a more useful way than just a "poof" eg on Mac most crashes initiate a system level error log that helps with bug tracking but Tracktion doesn't even do that. At least one thing it does do well is retain a temp copy of the project you are working on, that is good, but your ability to track and fix bugs us severely limited by the lack of logging.
Not sure where you got that idea.. The tracktion log file has always contained all the info we need about crashes - if you get a crash you should always send us a copy of that.

The OSX system reports are generally pretty useless, which is why we use an internal one instead.
I got the idea from the fact that a crash doesn't initiate the OS-X system report at all, if Tracktion makes it's own logs that's cool but not something I would have known about before you telling me as it's not as visible to the user. Where are they located, I can send some? Are there separate logs for each crash?

Post

Try the yellow help button

Post

Changing audio device from Windows Audio to ASIO or anything for that matter crashes it immediately. I didn't know about the log file. I will send it later today.
My System spec is Win 8.1 Pro 64-Bit, 4GB RAM, T5 64-Bit demo.

Post

fedexnman wrote: 2. EZdrummer , dragging midi clip from EZ to the edit does not not fill the Bar , you have to drag the clip arrow to the right to fill the Bar still ...
The same for me, but I can’t see the MIDI info in the EZD clips. They're all possibly only one tick long?

Post

I think either the swipe comping or the waveform drawing for it is off. If you comp things that way and zoom in you can clearly see audio waves being drawn where there shouldn't be any. I'm also not clear on if those edits are crossfading or not.

Image

Post Reply

Return to “Tracktion”