When importing scanned project data into a session, now file conflicts are recognized and a dialog is opened that suggests several solutions.
When an audio file already exists for a project and track on a recorder in a session, you may either import the new file on a new track that gets a name appended by a timestamp, or you can make a backup of the already imported file or simply skip it. Like before you may still even choose to overwrite previously imported and transferred files. ... read more
I have implemented a huge improvement over the previous default track mapping strategy. I have spent the afternoon analyzing several PRJDATA.ZDT of R16 projects and managed to find out, how the audio files in the projects are associated to channels.
From MuTrack V0.1.2-SNAPSHOT on, this information is used instead of the file name, to properly set up or select tracks when importing audio files into a session. This further reduces the cases, where files have to be manually rearranged and will save users a lot of time.... read more
I have updated the current snapshot build v0.1.1 with the simplest and quickest solution to platform independent audio pre-listening. Just double-click a file and it will open in your current default audio player.
I consider the ability to easily determine, what's in a file that otherwise just appears as label in a table, a very important foundation for deciding on track names and plan re-arrangements of files.... read more
As the project is getting closer to a first binary alpha release for evaluation (proof of concept), it is time for a little "lessons learned" and "what's next?" post. Especially, I would like to explain, why I am throwing JPA over board for the favor of self implemented JSON repositories based on Jackson and Java Generics. Most importantly: File transfer of Zoom R-16 content is in!
One task that took a little more effort than I initially expected was the persistence of the project data, meaning everything but the audio files. There are four main entities: source directories, recorders, libraries and sessions. Their implementation reaches from simple POJOs to the complex hierarchical collection structure with cross references of the session objects. MuTrack must be able to present the same state after start-up, as it had just before closing it the last time, with exception of updated reachability of known audio files. ... read more