54 postsPage 3 of 3
1, 2, 3
Quote
"Punch in scenario.
1) Input meter shows live input. at stop, pre punch and record
2) Audio input is NOT heard pre punch (since you are monitoring on your board)
3) Existing track is heard pre punch in.
4) During record input sound is heard"


Everything except #4 is correct.

With the monitor button disengaged, input sound should not loop through the system during record. This puts us back at the situation we are trying to avoid in the first place- having both the direct (board) monitored signal and the latency delayed monitor signal coming through.

The proper response for number 4 would be to have the existing track muted during a punch in.

Win7 64, Dell t7400 with dual proc. 12gb ram, studio one pro 3, Motu 24 i/o, 2408 mk3, 2408, Allen and Heath Gl4000 32ch mixer, etc.
User avatar
by Cold on Fri Sep 16, 2016 8:07 am
(Continued from prev post)

In the earlier versions, the existing track would continue to play even as it was overwritten.
While not optimal, it was not a big deal to split that part and mute or delete it to mitigate the problem.

I do agree that the developers have our best interests at heart, but I have to assume that none of them actually test the software using a hybrid type system, which is a serious oversight.
Being able to leave the buffer size at a reasonable amount and then dealing with monitoring latency outside of the system is a valid and usefull approach. Some musicians are incredibly sensitive to even small amounts of latency.

Win7 64, Dell t7400 with dual proc. 12gb ram, studio one pro 3, Motu 24 i/o, 2408 mk3, 2408, Allen and Heath Gl4000 32ch mixer, etc.
User avatar
by jpettit on Fri Sep 16, 2016 8:20 am
Ok thanks
I will report it.

How To Get Your Issue Fixed
To add your specs to your signature, click HERE
For FAQ or to submit a request go to Presonus Answers
My Website, Free Studio One Advance Training
Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, Studio 192, Audiobox 1818 VSL,StudioLive 16.4.2 AI,Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, JBL 4411's, RME 9632, Line 6 UX2, Studio One Pro 3.1, Reaper 4.77, Sonar Platinum
User avatar
by Jessa on Mon Jan 09, 2017 10:24 am
I'm having the exact same problem??, it's been 3 months, where's the fix??, This is a basic feature and has always worked up until 3.3, please get onto this ASAP as there are a lot of us that can't work this way, I have to go back to previous version until this is fixed.

Thanks
Jess.
User avatar
by jpettit on Mon Jan 09, 2017 12:21 pm
I know they are working on it. The challenge is it is a delicate balance between about a half dozen different monitoring workflows.

How To Get Your Issue Fixed
To add your specs to your signature, click HERE
For FAQ or to submit a request go to Presonus Answers
My Website, Free Studio One Advance Training
Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, Studio 192, Audiobox 1818 VSL,StudioLive 16.4.2 AI,Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, JBL 4411's, RME 9632, Line 6 UX2, Studio One Pro 3.1, Reaper 4.77, Sonar Platinum
User avatar
by Jessa on Mon Jan 09, 2017 3:08 pm
jpettit wroteI know they are working on it. The challenge is it is a delicate balance between about a half dozen different monitoring workflows.


I can appreciate that, but can you tell us when they will have a solution?. I don't understand how something this rudimentary to any DAW software can be wiped out?. Studio One is such a great platform but i fear it may be being worked to much on a software level and could lead to going backwards. Please don't forget about the traditionalist's in the recording world. Not everyone use's loops and samples to create music. Please ask them to get this sorted ASAP.

Thanks
Jess.
User avatar
by Cold on Tue Jan 10, 2017 11:43 am
I am still waiting for a solution to this as well.

Win7 64, Dell t7400 with dual proc. 12gb ram, studio one pro 3, Motu 24 i/o, 2408 mk3, 2408, Allen and Heath Gl4000 32ch mixer, etc.
User avatar
by danielpalm on Tue Jan 10, 2017 12:02 pm
Me too.

iMac 2012 21' 3.1 Ghz intel i7 8 Gb ram Mac OS 10.8.5
Studio One Pro 3
UA Apollo Quad Thunderbolt
UAD-2 Satellite Thunderbolt Octo Core
Focal solo 6 monitors, SPL MTC Monitor controller
BLUE Kiwi mic (keeps coming back to my Kiwi, just love it!)
Nord Stage 2 for all the piano sounds
Nord Electro 4D for the organ sounds
Prophet 12 for pure inspiration :D
Previously worked in Digital Performer, Cocos Reaper, Ableton Live and Logic. Gonna stick to S1 most likely!
User avatar
by g&s productions on Wed Jan 11, 2017 1:03 pm
I'm also waiting :hunf:
User avatar
by jpettit on Wed Jan 11, 2017 2:40 pm
Jessa wroteI'm having the exact same problem??, it's been 3 months, where's the fix??, This is a basic feature and has always worked up until 3.3, please get onto this ASAP as there are a lot of us that can't work this way, I have to go back to previous version until this is fixed.

Thanks
Jess.
I am not sure we are all talking about the same thing. See my first post for the bare minimum that should be reported.
viewtopic.php?p=1341#p1341
There was an external mixer monitoring scenario that was missing in 3.2 and reported to development, but I have not extensively test 3.2 vs 3.3 for other changes as the 3.2 issue has not been addressed yet.

How To Get Your Issue Fixed
To add your specs to your signature, click HERE
For FAQ or to submit a request go to Presonus Answers
My Website, Free Studio One Advance Training
Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, Studio 192, Audiobox 1818 VSL,StudioLive 16.4.2 AI,Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, JBL 4411's, RME 9632, Line 6 UX2, Studio One Pro 3.1, Reaper 4.77, Sonar Platinum
User avatar
by Jessa on Wed Jan 11, 2017 8:45 pm
jpettit wrote
Jessa wroteI'm having the exact same problem??, it's been 3 months, where's the fix??, This is a basic feature and has always worked up until 3.3, please get onto this ASAP as there are a lot of us that can't work this way, I have to go back to previous version until this is fixed.

Thanks
Jess.
I am not sure we are all talking about the same thing. See my first post for the bare minimum that should be reported.
viewtopic.php?p=1341#p1341
There was an external mixer monitoring scenario that was missing in 3.2 and reported to development, but I have not extensively test 3.2 vs 3.3 for other changes as the 3.2 issue has not been addressed yet.


At the moment with the latest version 3.3.3 if you enable record with the blue monitor button off and zero latency mode off (using an external out of box monitoring solution) you get no metering on the channel being recorded, it is only when you disengage the record button do we get metering on the track. I think this hes been an issue for the past 2 versions?, Anyways, it would be greatly appreciated by many, many , many users if this issue could be fixed asap..:)

Thanks
Jess
User avatar
by Jessa on Thu Feb 09, 2017 3:59 am
It's been a month, any word on if this issue is being addressed? ..

J.
User avatar
by Cold on Tue Feb 14, 2017 11:53 am
I'm still waiting as well.

Win7 64, Dell t7400 with dual proc. 12gb ram, studio one pro 3, Motu 24 i/o, 2408 mk3, 2408, Allen and Heath Gl4000 32ch mixer, etc.
User avatar
by jpettit on Tue Feb 14, 2017 1:49 pm
I talked to them when this was reported.
Not what you wanted to hear but there is more changes pending but in a large update like 3.5 or 4.0 and not a minor update.
They will try to simplify it and more focused on the basic use case variations of monitoring.

How To Get Your Issue Fixed
To add your specs to your signature, click HERE
For FAQ or to submit a request go to Presonus Answers
My Website, Free Studio One Advance Training
Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, Studio 192, Audiobox 1818 VSL,StudioLive 16.4.2 AI,Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, JBL 4411's, RME 9632, Line 6 UX2, Studio One Pro 3.1, Reaper 4.77, Sonar Platinum

54 postsPage 3 of 3
1, 2, 3

Who is online

Users browsing this forum: No registered users and 1 guest