jendakub

Hello, MIDI FX Freeze plugin has been updated to Audio Unit v3 and now works well in macOS Mojave, Catalina & Big Sur with Logic Pro X version 10.5.1. More info at http://www.audiocr.com

This is a issue, as for example in score editor you can do that, and before 10.1 update you could drag and hold the playhead in midi region too. This should be definitively fixed.

Hello, I have released Capture Midi in Apple AppStore and I am attaching a new demo version. This demo version is working fully for 15 days (Once you validate via internet), after that you can get the application from AppStore if you like it. New in (1.0) Audio sample browser added, simply add your sample libraries folders on your disk to quickly preview, drag and drop and play audio samples. Quick Video: Capture Midi Demo(1.0).zip Capture Midi Demo (1.0)

I am interested it too. Anyone any info?

Hello, do not understand the issue, can you explain?

Hello, it does connect to validate 30 days for beta evaluation. It will not need internet at all in release. The release version will be targeted for AppStore to include iCloud synchronization, and will not need any internet connection. This is a beta version, and it can still change considerably depending on any input. I have been thinking including a quick tap tempo counting there too as it is not so easy to do in Logic.

Hello, I will try to compile version compatible with 10.6.8 will post once I update it.

Hello, yes, the limit is OSX system that is set to 10.8 (Mountain Lion), Logic Pro 8,9,X will work.

Yeah, coincidence I did not saw this..., however what the person says is true. I always missed the Retrospective record from Cubase in logic. So it is here now. Open to any suggestions you all find to improve or make it better.

Hello, I am working on a Retrospective midi manager especially for Logic Pro X, however works with any DAW too. The application is a retrospective midi manager allowing you to have a constant backup of your midi keyboard plays. The idea goes further to implementations of retrospective midi such in Cubase (static buffer of 10 000) midi events, or Logic Pro X limited (Capture Recording functionality) that only works if you playing back project. The Idea of Capture Midi is to have backup of melodies played on keyboard, maybe while you improvise or try to come out with something nice. Main features: - Connects automatically to your midi keyboards on startup - Records your keyboard plays and place last melodies in a grid for instant playback or drag and drop to arrange. Melody items are created after musical interval of silence. (While you stop playing for 1 bar of tempo time as example) You can import just the last play for example, not the whole midi buffer. - Export to library, midi file, favorite, transposed playback via armed track in DAW. Here is a small introduction video I am attaching the current beta version, if anybody wants to try it. Any comments or suggestions appreciated. Capture Midi Beta.zip Capture Midi Beta 0.5.3

I do not know why this has been removed. It was really nicely working before as it was. Now you always have to edit full automation. It has been better having this feature, because you could just focus on single track. I would like this behavior get back definitively.

Hello In Logic Pro X 10.0.4 if you wanted to see automation on single track you could enable Auto Zoom on track and if your auto zoomed track had certain height, the automation for this track has been revealed, leaving other track heights untouched. In 10.0.5 regardeless the auto zoom option, all tracks are sent to show automation mode scaling all tracks to certain height. This has been removed or is a bug?

I had problem making the quick tip example video. I was trying to change velocities for some notes and I could not do that as the transform has been changing the whole region regardless my selection on operate. I will check this project once I got home. Anyway good that seems to be not an issue. Will check later.

I have tried just in fresh project restarted logic pro x, It did not happened again. I will have an eye on this as It really has been affecting all notes in region.

Still cannot reproduce here. Tried with sixteen notes with 16 different articulation ID's and also with the same Articulation ID: Same result as before: only selected notes are affected by the transform window. J. Just tried with fresh project, could not reproduce, however several times it has affected whole region instead my selected notes when I pressed Operate only. I will take a look if there is way to fully reproduce it.