11 posts
Page 1 of 1
|
There seems to be a problem with MIDI notes that are positioned right at the top of a song (bar 1, beat 1) - the problem being that they don't play.
This happens even if I make sure the note is quantised to the start of bar 1. Using the piano roll editor, I'm having to shift the note a tiny amount later - e.g. 1ms - then it triggers properly. Is this a known problem? Adrian |
|
No one starts a MIDI track on bar 1.
IF you want the Song to start on Bar 1 you can INSERT measures into the Song so it has a pick measure or two before bar one Song/Song Setup/Bar Offset/ Set the Bar offset to -1. This will give you a Bar before bar 1 and you should be good |
|
Are you talking about external hardware or plugins?
with plugins you can enable chase long notes in the settings. For hardware, you need to give the midi clock 1 bar to sync up. I usually set a loop for the range I want to record, then go one bar back from the end of the loop, record so it loops back over itself.
Toronto, Canada
Project engineer by day, sound connoisseur by night. Main Rig: Windows 11 (21H2) 64-bit, Ryzen 3900x, 32GB RAM, RTX 2060, dual 4K Monitors Presonus 192, Faderport v2, Atom SQ, Akai Advance 49, Keystation 61 mk3, 2x Behringer X-Touch Mini + way too many synths. Mobile Rig: MBP M1/16GB, Atom SQ, IOstation |
|
I'm have the exact same issue! Not a problem in my other DAWs using basically the same configuration. However, the issue is only when using VSL Synchron Player or Synchron Pianos. With all other plugins (at least the ones I have), there's no issue.
Studio One 6 Pro | Cubase 12 Pro | Live 11 Suite | Mixbus 32c
Digital Performer 11 Focusrite Scarlett 18i20, 2i2 (2) | Presonus Audiobox USB96 Dell XPS 8930 i7-9700 32 GB (Currently cannot afford a Mac Pro Tower LOL!) Windows 11 Pro | MacBook Pro 8-Core M1 Yamaha CP4 Stage | NI Komplete S61 | NI Komplete M32 Novation Launchkey 37 | Ableton Push 2 | NI Maschine Mk3 Maschine Micro | Roland TD-50x KRK Rokit 8 | Presonus Eris 3.5 Various condenser mics Software – way to f****** much! 
|
shanabit wroteNo one starts a MIDI track on bar 1. No one? Really? I do it all the time. Every song that doesn't have a pick up anyway. No problems. At all. Ever.
Win11, 12th Gen Intel Core i7-12700K (3.60 GHz), 32GB Ram. Focusrite Scarlett 8i6 3rd Gen. Native Instruments Komplete Kontrol S88 Mark 2, Native Instruments Komplete Kontrol S61 Mark 1, Presonus FaderPort 8.
https://www.midiboy.com https://gregghart.bandcamp.com |
|
Yes I have had the same issues as well. I gave up trying to solve it. I started at bar 2!
Regardless, this needs to get fixed, I don't know what causes it. Scott
Studio One Professional v6, Apple iMac Pro 14 core, 128gb memory, 4TB SSD. macOS Ventura, Main audio interface is RME Babyface Pro. Presonus 192, DP88 (not currently used), RC500, ADL600, Focusrite ISA430, TC4000 reverb, SPL Phonitor, Monitoring: Event Opal, IK Multimedia MTM Studio Monitors x 5, DMAX audio Super Cubes. HD800s mastering reference headphones. Sequential Prophet 12, Prophet 12 modules x4, E-MU 4XT Ultra, Roland Fantom 8, Korg Pa3x, Roland Fp7-F, MOTU midi express 128, Xkey air 37, Studiolive CS18, Atari STE with Notator plus loads of microphones and plugins etc
|
|
When I ran a pci card I could record a loop from a standing start. When I went to firewire the start of the loop I created had problems.
Takes time to get things going, aka latency. So I had to start the song at bar 2 but playback starts at bar 1 and everything is up and running when the recording starts. I use punch in for that. That's just something you have to do if your hardware requires it. Some people don't need to.
Forum Moderator.
Please add your specs to your SIGNATURE. Search the STUDIO ONE 6 ONLINE MANUAL. Access your MY.PRESONUS account. OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET. Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce. Studio OnePro6 Melodyne Studio Win10 Ryzen 5 3600 - Motu M2 Ventura Mac Mini M2 - Zen Go TB |
|
Some plug-ins have problems with that. Which plug-in is used here?
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
|
Yeah, I bet it has to do with your Audio Interface and the latency. I have a Focusrite Scarlett 8i18 Gen 2. But my old Alesis also did fine with this. As does my Presonus Audio Box.
Win11, 12th Gen Intel Core i7-12700K (3.60 GHz), 32GB Ram. Focusrite Scarlett 8i6 3rd Gen. Native Instruments Komplete Kontrol S88 Mark 2, Native Instruments Komplete Kontrol S61 Mark 1, Presonus FaderPort 8.
https://www.midiboy.com https://gregghart.bandcamp.com |
|
I'm pretty sure this is a plug-in issue and not an audio interface issue.
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
|
easiest fix i have found is to always start projects bar 2 and if you have any midi missing the first note just extend the part in front of segment forward (adding silence) and it will play as it should. this has been an ongoing problem with S1 since back when i started using the software back in v2 and i suppose it has always been this way. just another bug that has not been fixed over the years and probably never will be since fender took over lol
as for trying to say it is the plugin being used is the problem i beg to differ i have seen it happen one time and not the next with the same plugin lol but good try though lol least to say it is elusive and is not very repeatable and presonus has ALWAYS ignored things that can't be repeatable. it is sad they don't track down and fix things like this as opposed to letting it slide. also sadly i have only had this problem with S1 and i use a few DAWs anyways this is how i fix it and my statement is IMHO lol cheers |
11 posts
Page 1 of 1
Who is online
Users browsing this forum: No registered users and 50 guests